Personyze reports matches to Meta over the Conversions API, from its own servers. Meta builds a website custom audience from those events, and a lookalike from that audience.
What you need
| Field | Where to find it |
|---|---|
| Pixel (dataset) ID | Meta Events Manager → your dataset |
| Access token | The same dataset → Settings → generate a token |
Switch on Ad platform matching
An email address alone reaches only the visitors who ever gave you one. Ad platform matching, one switch on the Meta card, captures the identifiers Meta recognises people by: the browser id from the _fbp cookie, and the click id both as the _fbc cookie and as the fbclid URL parameter.
What it captures, and why it is worth more than the token.
Use a standard event name
Meta only optimises for, and only builds dynamic ads from, its own standard event names — ViewContent, AddToCart, Purchase and the rest. Pick the matching one in Meta event name on the action; your own event name still goes to every other destination unchanged.
Building the audience and the lookalike
- Events Manager → your dataset. The event should appear within a few minutes of the campaign going live.
- Audiences → Create audience → Custom audience → Website → choose that event.
- Audiences → Create audience → Lookalike audience → that custom audience as the source.
Meta needs at least 100 people from one country in the source before it will build a lookalike. Sending an Event value and Currency is what makes a value-based lookalike possible — the currency must be a three-letter code such as USD, which is the one thing Meta rejects outright rather than accepting silently.