Skip to main content
Connect Meta to keep a Custom Audience in lockstep with a Senderz segment: whoever enters the segment joins the audience, whoever leaves is removed.
This is outbound only. There are no inbound events from Meta — Senderz pushes membership, it never reads back.

​
How it works

1

Connect Meta

Authorise Senderz to manage your Custom Audiences.
2

Link a segment

Map a Senderz segment to a Meta Custom Audience — a 1:1 connection.
3

Continuous sync

On a schedule, Senderz diffs the segment against the last-synced snapshot and applies only the changes (joins and removes).

​
Identity & hashing

Members are matched on hashed email and phone. Normalisation is provider-specific — Meta’s rules differ from Google’s, so Senderz normalises per provider before hashing. Feeding one provider the other’s normalisation produces a valid hash that matches nobody.
Ad-audience matching depends on correct per-provider normalisation. Senderz handles this internally — the point is that email/phone must be normalised Meta’s way before the SHA-256, which the connector does for you.

​
Shared foundation with Google

Meta and Google Customer Match share provider-agnostic tables and the same membership-diff engine. The two connectors reuse that foundation rather than forking separate models.
The Meta connector is in progress. See Google Customer Match for the sibling ad-sync integration.