Zapier Conversions API: send CRM stages to ad platforms
Use Zapier to send leads, booked calls and won deals to Meta's Conversions API and other ad platforms, matched to the ad click and without duplicates.
By DATALYR · · 3 min read
Contents
Two ways to use Zapier
Zapier can send conversions to Meta's Conversions API directly with its Facebook Conversions app, whose actions include Send Lead Event, Send Purchase Event, Send Funnel Event and Send Other Event. It can also post any record to any endpoint with Webhooks by Zapier.
Either way, a Zap starts from a CRM or booking record. That record knows the person and the deal, but usually not the ad click. How well the conversion matches depends on what identifiers you can attach.
This guide covers the direct route, the matching problem, sending stages through DATALYR, and the details that keep a Zap from creating duplicates.
The direct route to Meta
The Facebook Conversions app sends an event from a Zap to your Meta dataset. It suits a single destination and a simple funnel: a new CRM contact becomes a Lead, a closed deal becomes a Purchase.
Meta also documents a Zapier path for its Conversions API for CRM, which serves the Conversion Leads goal for Instant Form leads. Those events need Meta's lead ID and the event_source and lead_event_source fields.
Each destination needs its own Zap. Meta, Google Ads and LinkedIn each have their own field requirements, so the same deal is wired three times.
The matching problem
A CRM stage usually carries an email and maybe a phone number. It does not carry the Meta fbc and fbp cookies, the Google GCLID or the LinkedIn li_fat_id from the visit weeks earlier. Platforms can match on hashed email and phone, but the click identifiers tie the conversion to a specific ad click.
Google is strict about it: an upload needs a click ID, an email or a phone number. LinkedIn matches on fields such as hashed email and its own first-party click ID.
The fix is to join the stage to the original visit before sending it. If the email was captured on the landing visit, the later stage can inherit the click context that visit recorded.
Send stages through DATALYR
With DATALYR, a Zap posts each stage to the /track endpoint with the workspace write key: call_booked, lead_qualified or deal_won. DATALYR matches the email to a tracked visit and the stage inherits that visit's campaign. One Zap per stage replaces one Zap per stage per platform.
Set up conversions on the Zapier card and DATALYR creates the rules: call_booked to Meta as Schedule and TikTok as SubmitForm, lead_qualified to Meta as Lead, and deal_won to Meta as Purchase, TikTok as CompletePayment and your Google Ads purchase action, with the deal ID as the order ID.
deal_won carries the deal amount as a contract value. DATALYR sends it as the conversion value but never counts it as revenue; cash comes from a payment source such as Stripe or Commas. This is the route for Salesforce, Pipedrive, GoHighLevel and any other CRM without a DATALYR source.
One Zap per stage
1. CRM or booking tool
Stage changes
New booking, qualified lead or won deal.
2. Zap
POST to /track
Email, stable event ID and, for won deals, the amount.
3. DATALYR
Matched and sent
Joined to the visit by email; rules deliver to each platform.
Example: retries and event IDs
This is a hypothetical month. Sales wins 30 deals. Zapier's history shows 34 runs of the won-deal Zap, because 4 runs were retried after a timeout.
With the deal ID mapped into the event ID, the 4 retries are recognized as duplicates and 30 conversions are recorded. With a random event ID, all 34 runs become conversions, and the platform counts 4 deals twice. With a fixed text event ID, the first run is accepted and the other 33 are rejected as duplicates.
Map a real record ID into every event ID, and test the step until it returns success with a real record.
What the event ID does
Deal ID in the event ID
34 runs → 30 conversions
Retries are duplicates of the same deal.
Random event ID
34 runs → 34 conversions
Four deals counted twice.
Verify the Zap end to end
Open your landing page in a private window with ?utm_source=doctest, submit your form or book a call with a test email, then trigger the Zap for that record. In DATALYR, confirm the stage arrived with source zapier and that it sits on the same user as the doctest page view.
If events arrive without a campaign, DATALYR has never seen that email on a tracked visit; call identify with the email on your form. If a won deal shows in revenue reports, the body lost its non-cash role field, so copy it again from the Zapier card.
Related articles.
Tracking ·
Server-side tracking: architecture, responsibilities and limits
Understand what moves to the server, what still depends on browser identity, and how to verify one conversion without creating duplicate events.
Conversion delivery ·
Offline conversion tracking: connect a lead to the sale that follows
Define the lead-to-sale record, preserve eligible matching data, and verify imported outcomes without confusing acceptance with advertising credit.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
