Skip to content

Optimize for Deals, Not Forms

Zappush gives you a built-in CRM. Dragging a lead to Qualified or Closed-Won fires a server-side conversion event to Meta and Google, so the platforms optimize for the leads that become deals instead of the forms that just fill. The click ID is already on the lead, so there is no weekly export or middleware to maintain.

Book a Demo

From $59/month · 14-day free trial · Cancel anytime

Marcus Webb

Meta lead ad · Jun 2

Qualified
  • SourceMeta lead ad
  • StageQualified
  • CAPI eventFired → Meta
  • Deal value$4,200
  • Days in pipeline6
Qualified, not filled
Platforms optimize toward leads that reach Qualified and Closed-Won, not raw form-fill volume
Click ID for months
GCLID/FBCLID stays attached from first click to closed deal, so late conversions still match their ad
Source on every lead
Campaign, ad, and session context travel with the lead through every pipeline stage

Meta and Google Optimize for Junk Leads

When you run lead-gen ads, the only signal the platforms ever receive is the form fill. Their algorithms learn to find more people who fill out forms, not more people who buy. Meta and Google cannot tell a $50K-deal lead from a bot or a tire-kicker, because that judgment happens later, offline, in a sales conversation the pixel never sees. Only about 5-15% of form fills ever become real opportunities. Yet every fill goes back as an equal-weight conversion, so Smart Bidding and Advantage+ train on a pool that is mostly noise. The GCLID/FBCLID that tied the lead to its ad sits unused in a spreadsheet, never sent back after qualification. So you pay a rising cost per lead for a falling lead quality, sales burns hours chasing junk while the ads that actually source pipeline get starved, and your cost per qualified lead and cost per closed deal drift completely out of view. The platforms confidently scale the exact audiences that generate the most unqualified leads.

What Zappush seesWhat your CRM seesAd click3 visitsCartForm fillPurchaseRepeatTHE “BEFORE”, INVISIBLE TO A CRM

How it works

  1. Capture the click ID on every lead

    When someone arrives from an ad, Zappush persists the GCLID, GBRAID/WBRAID, FBCLID (fbc/fbp), and MSCLKID in a server-set first-party cookie that survives ITP's 7-day JavaScript cap. It stamps them onto the lead the moment someone submits the form, so the ad that sourced the lead stays joined to it for months.

  2. Work the lead in the built-in CRM

    Every lead lands in a pipeline with source, campaign, and full session context attached. Your team moves it through your own stages: New, Contacted, Qualified, Opportunity, Closed-Won. The click ID and SHA-256-hashed contact details ride along the whole way.

  3. Moving a stage fires a conversion event

    A stage change fires a webhook that sends a deduplicated server-to-server event to Meta CAPI, carrying a lead_stage parameter, and to Google's Enhanced Conversions for Leads / offline import keyed on the GCLID. The event is tagged with the stage and a value. The platforms retrain on which clicks turn into deals, not which turn into forms.

What you get

  • Stage-triggered conversion events

    Map any pipeline stage to its own conversion action: Qualified, Demo Booked, Opportunity, Closed-Won. Moving a card fires the exact event you want Meta and Google to optimize toward.

  • Click ID captured and stored per lead

    Zappush grabs GCLID, FBCLID, and other identifiers on arrival and stamps them onto the lead. The offline conversion matches back to the original ad interaction even months later.

  • Value passback per stage

    Attach a proxy value to early stages (Qualified = $200, Demo = $500) and the real deal amount at close. The platforms can then run value-based bidding on pipeline value instead of counting every form fill as equal.

  • Source context on every lead

    Each lead carries its source, campaign, ad, landing page, and full session path. Sales sees where a lead came from, and marketing sees which campaigns actually source qualified pipeline.

  • Built-in CRM, no separate tool

    The pipeline lives inside Zappush next to the tracking, so there is no CRM sync to wire up or middleware to maintain. Moving a lead and firing the conversion are the same action.

Use cases

CRM PIPELINE

Send Qualified and Closed-Won back

Form fills tell Meta and Google nothing about lead quality, and only about 5-15% of them ever become real opportunities. Dragging a lead to Qualified or Closed-Won fires a server-side conversion keyed on the stored GCLID and hashed contact details. The platforms retrain on clicks that reach a stage, not clicks that fill a form.

B2B SERVICES

Bid on pipeline value, not lead volume

High-ticket deals close weeks after the click, long after a JavaScript cookie would have expired. Attach a proxy value to each stage, $200 at Qualified and $500 at Demo, then the real amount at close, and send it with the click ID held in a server-set first-party cookie. Bidding works on pipeline value instead of counting every fill as equal.

LOCAL SERVICES

Keep junk leads out of the training set

Home services, clinics, and legal firms drown in bot fills and tire-kickers that the ad platforms score as conversions. Every lead lands in the pipeline with its source, campaign, ad, and session path attached, and disqualified leads simply never fire an event. Only the leads your team qualifies reach Meta and Google.

Questions, answered.

Do I have to replace my current CRM to use this?
No. The pipeline is built into Zappush and works out of the box, so you can run leads through it directly. Because the click ID and tracking already live on the lead, there's no separate CRM-to-ads connector to configure, moving a lead to Qualified is what fires the conversion.
How does Meta or Google know which ad a closed deal came from weeks later?
Zappush captures the GCLID and FBCLID when the lead first arrives and stores them in a first-party cookie on the lead. When you move that lead to Qualified or Closed-Won, the event is sent back with the stored click ID (and hashed email/phone), so the platform matches the offline outcome to the original click even months later.
Which stage should fire the conversion event?
Whichever stage represents a lead you'd want more of. Firing on Qualified teaches the platforms to find sales-ready leads instead of form fills, and firing on Closed-Won with the real deal value lets them bid for revenue. You can fire on multiple stages, each with its own value, to feed the algorithm a fuller picture of the funnel.

See what your data is missing.

Start free in minutes, or see it live on a call.

Book a Demo

From $59/month · 14-day free trial · Cancel anytime