Audience activation (reverse-ETL)

Activation pushes CDP segments and lists out to ad platforms as custom audiences — the reverse direction of importing ad-platform data in.

Connect a destination

curl -X POST https://api.wezend.com/v1/activation/destinations \
  -H "X-API-Key: $WEZEND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "provider": "meta", "name": "Meta — lapsed customers", "credentials": { "access_token": "..." } }'

Supported connectors: Meta Custom Audiences, Google Customer Match, TikTok, LinkedIn, and a generic webhook destination for anything else. Meta/Google/TikTok/LinkedIn connectors require your own ad-platform API access and app review with that platform — the webhook connector works immediately with no external approval.

Create and run a sync

curl -X POST https://api.wezend.com/v1/activation/syncs \
  -H "X-API-Key: $WEZEND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "destination_id": "dest_..." , "segment_id": "seg_..." }'

curl -X POST https://api.wezend.com/v1/activation/syncs/sync_.../run \
  -H "X-API-Key: $WEZEND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "dryRun": true }'

dryRun: true previews the sync (record counts, matched fields) without actually pushing anything.

What leaves the platform

Emails and phone numbers are normalized and SHA-256 hashed locally, before egress — the ad platform never receives raw PII, only the hashes it needs to match its own user base. Destination credentials are encrypted at rest.