Guides / Zapier & Make
Contacts created by automations arrive with no click IDs — the classic attribution black hole. Here's what recovers automatically, and the one mapping worth adding.
⏱ About 4 minutesIf the person visited a page running our capture script and submitted any form there, we captured their click IDs alongside a privacy-hashed copy of their email. When your automation later creates the contact — from a webhook, a spreadsheet, a booking tool, anything — we recognise the email and reunite the contact with its click history automatically.
You'll see these in the dashboard with provenance identify.
If your automation source knows the click IDs (its trigger data includes URL parameters), map them into the contact's custom fields in your create/update step: ps_fbclid, ps_gclid, ps_ttclid, and ps_utm_source. Explicit beats inferred — when these are set, they win.
Building lead-ad contacts through Zapier/Make instead of the native integration? Map the trigger's lead id — Zapier's field is called ID, Make's is Lead ID — into ps_meta_lead_id. That's Meta's strongest match key; the Lead Ads guide explains why it matters.
How the automatic path stays private: emails are hashed (SHA-256) in the visitor's browser before anything leaves the page — the same normalization ad platforms use. We never store or transmit a raw email address from your pages.
Pipeline Signals · dedup, retries, expiry windows and consent flags handled automatically