Skip to content
ChangelogBook a demoSign up

Sync array identifiers to audience destinations

Audience syncs automatically send each element of an array-valued identifier as its own record, so every identifier can match.

AudienceMarketers and data teams running audience syncs to ad platforms
PrerequisitesAn audience sync to a destination that matches on identifiers.

Audience syncs fan out array-valued identifier fields into separate records — one per element — so a column holding multiple identifiers (such as several email addresses or mobile advertising IDs) syncs each value individually. It needs no configuration; it happens at sync time whenever a mapped identifier field contains an array. To add identifiers beyond what your source data provides, see Match Booster.

This is distinct from array expansion, which is a separate feature that explodes array columns at the model query level for non-audience sync types. Audience identifier fan-out is automatic and applies only to identifier fields in audience syncs.

How it works

If your model contains a row with an array-valued identifier field:

user_idmobile_ids
123["GAID_1", "GAID_2", "GAID_3"]

Hightouch sends three separate records to the destination:

user_idmobile_ids
123GAID_1
123GAID_2
123GAID_3

Each array element is synced individually so the destination can match on every identifier. Scalar (non-array) values are unaffected and synced as-is.

Supported destinations

Fan-out works with audience destinations that match on identifiers — the ad platforms, such as Google Ads (Customer Match), Meta (Custom Audiences), and TikTok. Any audience destination that accepts identifier fields supports it. For the current list of destinations and their capabilities, see the integration catalog.

Requirements

  • The source column must be a true array type, not a JSON string. For example, Snowflake ARRAY, BigQuery ARRAY<STRING>, or Postgres text[] / jsonb arrays all work.
  • A string like '["id1","id2"]' stored as VARCHAR will not be fanned out. If your data is stored this way, use a SQL transformation (e.g., PARSE_JSON() in Snowflake) to convert it to a native array before syncing.

Fan-out increases the number of API requests sent to the destination. If your arrays are large, this may affect sync duration.

Linked identifier fields

When multiple identifier fields are mapped (for example, first name and last name), Hightouch preserves the association between values at the same array index. For independent fields like email and mobile ID, all combinations are sent to maximize match rates.

  • Match Booster — Enrich your audience data with additional identifiers to improve match rates across audience destinations.

Ready to get started?

Jump right in or a book a demo. Your first destination is always free.

Book a demoSign upBook a demo

Need help?

Our team is relentlessly focused on your success. Don't hesitate to reach out!

Feature requests?

We'd love to hear your suggestions for integrations and other features.

Privacy PolicyTerms of Service