Your segments, everywhere you advertise.
SegmentHub keeps audiences in sync with ten advertising networks. Build a segment once and it is pushed to every connected destination on a schedule, as normalized SHA-256 hashed identifiers — raw email addresses never leave your account.
Refreshed every three hours
Every connected network is rebuilt on a three-hour cycle, so an audience a visitor qualifies for this morning is targetable the same day. Yandex is the exception and runs once a day, because it locks a segment for around two hours after each upload.
Hashed before it leaves
Identifiers are normalized and hashed with SHA-256 before upload, which is what every network's customer-match programme expects. Only profiles carrying the identifier a network can match are included, so nothing is sent that could never match.
Every run is auditable
The panel records each synchronization: audience size, eligible records, how many were added, removed or rejected, the duration, and the error returned if a run failed. When a network stops accepting an audience, you can see exactly when and why.
Advertising networks
Each network has its own minimum audience size and matching behaviour. These are the ones that matter in practice.
| Network | Destination | Sync | Minimum to target |
|---|---|---|---|
| Google Ads | Customer Match list via Data Manager | HTTPS feed, rebuilt every 3h | Google's own thresholds apply |
| Meta | Custom Audience | API push every 3h | Meta's own thresholds apply |
| DMP segment | API push every 3h | Matched asynchronously | |
| Microsoft Advertising | Customer list | Full rewrite every 3h | 300 matched people |
| TikTok | Customer File audience | File replaced every 3h | ~1,000 matched users |
| X (Twitter) | Custom audience | API push every 3h | 100 recently active users |
| Customer list audience | API push every 3h | 100 matched accounts | |
| Custom audience | Delta sync every 3h | ~1,000 matched redditors | |
| Yandex | Yandex Audience segment | Once a day | 100 email identifiers |
| OpenAI | Custom audience, CSV export | Manual upload — no audience API yet | 25,000 matched users |
Delta sync means only what changed is sent: profiles that join the audience are added and those that leave it are removed, so a list never drifts out of step with the segment behind it.
The parts that usually go wrong
Tokens that expire quietly
LinkedIn, Pinterest, Reddit, Microsoft and Yandex all mint a short-lived access token from a refresh token. SegmentHub refreshes them on every run, so a connection does not silently stop working weeks later when a token expires.
Large audiences and feed timeouts
The Google Ads feed is regenerated on a schedule and served from cache, so Google gets it instantly regardless of how large the audience is, instead of waiting on a query that might time out.
Identifiers a network cannot match
Reddit and Yandex match on hashed email only. Profiles identified by phone number are left out of those uploads rather than padded in, because that column could never match and would only depress the reported rate.
Stable segment IDs
Yandex and Reddit audiences are created once and then refreshed in place, so the ID you target in a campaign never changes underneath you.
Data sources and destinations
Beyond advertising, SegmentHub connects to the tools your data already lives in.
Anything not listed can be reached through the REST API.