Skip to content

Make invisible revenue visible.

Your store, phone, and CRM close sales your pixel never sees. Zappush matches each sale to the ad click on the customer profile and sends it to Meta and Google as an offline conversion with value. The platforms optimize for revenue, not checkouts.

Book a Demo

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

Rohan Mehta

COD · confirmed

Offline
  • ChannelIn-store / POS
  • Order$210
  • Matched toMeta ad click
  • SentOffline CAPI
Delivered revenue
Meta and Google optimize toward customers who take delivery and pay, not whoever taps "Place Order"
Phone, POS & CRM visible
Revenue that never touches the website is matched to the ad click and fed back to the platforms
Counted once
COD orders event_id-matched across the browser and the offline confirmation, so nothing is double-counted

The sale happens offline. The ad platform never sees it.

Ad platforms only see what happens in the browser. Sales that close in a store, on a call, or in your CRM never fire a pixel, so Meta and Google optimize for the people who click buy, not the people who pay. In cash-on-delivery markets the gap is wider: the pixel fires at checkout, and 15-35% of those orders are never paid. Either way, the algorithm trains on order intent while the campaigns that drive real revenue get starved.

How it works

  1. Match the sale to the ad click

    Zappush stores the click identifiers from the first visit: Meta's fbclid, Google's gclid, and SHA-256-hashed email and phone, in a server-set first-party cookie that lasts up to 400 days. When a sale closes in your POS, CRM, or delivery system, Zappush matches it to that profile deterministically.

  2. Send the confirmed amount

    Zappush fires the conversion when the outcome is confirmed: the deal closes, the invoice is paid, or the delivery completes. The event carries the amount you actually collected, so platforms optimize for revenue instead of order intent.

  3. Deliver it as an offline event

    Zappush pushes the conversion to Meta's Conversions API and Google's offline conversion import, keyed by the click ID and hashed identifiers. Each event is deduplicated by event_id and stamped with the original click time, so it lands inside the attribution window and credits the right campaign.

What you get

  • Delivered-revenue optimization for COD

    Hold the Purchase event until the order is delivered and paid, then send the confirmed amount. Meta learns from delivered revenue and stops finding customers who order and refuse.

  • Phone, in-store & POS conversions

    Send call-center closes, POS receipts, and in-store sales back to the platforms, matched to the click that drove the visit.

  • CRM-closed revenue sync

    A deal marked won, delivered, or paid in your CRM fires a value-carrying offline conversion automatically. No CSV exports, no manual click ID uploads.

  • Confirmation-timing control

    Choose when the conversion fires: on order, on dispatch, or on delivery. Start with an online proxy until offline volume is stable, then shift optimization to the real outcome.

  • Deduplicated, high-EMQ delivery

    Every offline event is deduplicated by event_id and enriched with hashed email, phone, and click IDs. Match rates stay above Meta's 30% floor and Offline Data Quality holds in the 8.5+ range.

Use cases

UPSELL FUNNELS

Optimize past the tripwire purchase

Webinar and e-book funnels close their real revenue days later, on a sales call or an upsell page. Send the $2,000 close back with the customer's phone and email, and Meta and Google stop optimizing for $27 tripwire buyers. The algorithms learn who becomes a program buyer, not who downloads PDFs.

RETAIL / COD

Count the sale after delivery, not checkout

COD orders are not revenue until the courier delivers and the customer pays. Zappush holds the conversion until delivery is confirmed, then sends the amount actually collected with the original click ID and hashed phone. Platforms receive delivered revenue instead of order intent, so high-refusal profiles stop registering as wins.

PHONE / POS

Attribute walk-ins and phone sales

Cafés, clinics, and showrooms close revenue at the counter or over the phone, where no pixel fires. Mark the sale won in your POS or CRM and it matches back to the profile already holding the gclid, fbclid, and hashed email from the ad click. Revenue that never touched the website becomes visible to optimization.

Questions, answered.

How do you connect a COD order or in-store sale back to the ad that drove it?
Zappush captures the click identifiers, Meta fbclid/fbp, Google gclid, and hashed email/phone, server-side on the persistent profile at the first visit. When the COD order is delivered or the POS/phone/CRM sale closes, it's matched deterministically to that same profile, so the offline revenue is tied back to the exact click and sent to Meta and Google as an offline conversion.
When does the conversion actually fire for a COD order?
You control the timing. Instead of firing at checkout, Zappush can hold the event until the order is delivered and cash is collected, then send the confirmed amount, so platforms optimize for delivered revenue, not order intent. Until offline volume is stable you can learn against an online proxy like InitiateCheckout, then shift optimization to the real outcome. Uploads stay inside Meta's 62-day-from-event / 90-day-from-click window.
Won't sending an offline Purchase double-count orders that also fired a pixel event?
No. Every offline event carries a shared event_id and is deduplicated against the browser/checkout event, so a single COD order is counted once. Identifiers are normalized and hashed to keep match rate above Meta's 30% floor and push Offline Data Quality toward the 8.5+ band, so the events land clean instead of degrading your account.

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