CONNECTIONS / Tencent COS
Tencent COS + Datahash: APAC exports become ad signals.
Conversion and CRM exports land in your Tencent Cloud Object Storage (COS) bucket across Asia-Pacific regions. Signals reads each file as it arrives, hashes the identifiers, and routes the rows to every connected ad platform.
- ● tencent-cos :: signals live
- > object arrived cos://ap-singapore/exports/orders-2026-07-18.csv
- > parse rows=27,610 schema=orders
- hash sha256(email,phone)
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 79%
The signal Tencent COS yields, and receives.
Every kind of signal that moves between Tencent COS and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A file written to the watched COS bucket, whether from a Singapore or Hong Kong region, is picked up on schedule and parsed as it lands, so a regional export job needs no separate delivery step.
- Lead conversions
- The column mapper aligns whatever headers a regional CRM or POS export uses to each platform's event fields, so teams running separate exports across APAC markets do not need to standardize file layouts first.
- Custom audiences
- Emails and phone numbers are SHA-256 hashed as the file is read, and the file itself is discarded after processing, so no raw export lingers on our side regardless of which COS region it came from.
- Lead generation inbound
- Every row comes back with a per-destination status, so a record malformed by a regional encoding difference is flagged and quarantined instead of failing the whole file.
Pick your platform. Every use case for it, in one place.
Every way Tencent COS data moves, grouped by platform and ranked by how many use cases Tencent COS supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Tencent COS with scoped, read-only access.
-
Watch
Choose the bucket, region, and file pattern to watch.
-
Map
Map columns to events and identifiers in the visual mapper.
-
Go live
Verify sample rows in the live debugger and go live.
Tencent COS questions, answered.
Which file formats are supported?
CSV and TSV are the formats teams typically export, each with headers Signals can remap, and less common fixed-width layouts still work through the column mapper. Because the watch is set at the bucket and file-pattern level, a regional job in Shanghai or Singapore can write in whatever format it already produces without a migration step first.
Is customer PII stored by Datahash?
Identifiers are SHA-256 hashed at ingestion and no PII is stored on host servers in Datahash Cloud, with the source file discarded once processed. This holds regardless of which Tencent COS region the file was written from. A self-hosted Core deployment is available when data cannot leave your own environment, with hashing happening before anything reaches a platform.
How often are files picked up?
Cadence is configurable, from minute-level checks to a single daily run, and every file gets processed once with row-level reporting back. A new object appearing in the watched COS bucket is what triggers the next pickup, so a team running exports out of Hong Kong on one schedule and Singapore on another keeps each region's own timing.
NEXT STEP
See your Tencent COS data working in every ad platform.
Ready to enable a use case, or still mapping what Tencent COS data could do? Our team helps you find the right place to start.
