Zappush captures subscription starts, renewals, upgrades, and cancels as distinct server-side signals, then feeds subscriber lifetime value back to Meta and Google. Renewals happen on your billing system with no browser session, so only a server-side spine can give the platforms the recurring revenue that makes a subscriber valuable. They stop chasing one-time buyers and start acquiring subscribers who reorder for months.
From $59/month · 14-day free trial · Cancel anytime
Clara Jensen
Monthly subscriber
At the moment of first purchase, a subscriber worth $500 over the next year looks identical to a $25 one-time buyer: same Purchase event, same value, same bid. Smart Bidding and Advantage+ optimize toward whoever converts cheapest today, which is almost always the discount-hunting single-order shopper, not the person still paying in month twelve. The pixel also goes blind after checkout. Renewals happen on your billing system with no browser session, so Meta and Google never see the recurring revenue that makes subscription customers valuable. Cancellations are invisible too, so the platforms keep building lookalikes off people who already churned. The signals that separate a durable subscriber from a churn risk are first recurring purchase, upgrade, downgrade, cancel, and each customer's renewal cadence. They live in Recharge, Stripe, or Shopify, disconnected from the ad accounts spending your money. So you pay full CAC to acquire subscribers, then let the algorithm optimize away from them because first-order value under-reports their worth by 10-20x.
Zappush ingests subscription starts, first recurring purchases, renewals, upgrades, downgrades, pauses, and cancels from your billing platform (Recharge, Stripe, Shopify subscriptions) via webhooks. It writes each one to one persistent customer profile and keeps them distinct rather than collapsing them into a generic Purchase, including the renewals no pixel can see.
For every subscriber Zappush tracks renewal cadence, cumulative recurring revenue, tenure, and a churn-hazard curve derived from time-since-last-renewal versus the subscriber's own billing interval. Raw billing events become a live predicted lifetime value and a days-to-churn estimate per customer.
Zappush maps events to Meta's Subscribe event with the predicted_ltv parameter and to Google's value-based conversions, streaming renewals through the Conversions API (there is no client-side session to fire a pixel on a rebill). Every field is SHA-256 hashed and deduplicated via a shared event_id. Loyal subscribers seed value-based lookalikes, and Zappush suppresses cancelled subscribers so budget stops chasing churn.
Zappush tracks start, first recurring purchase, renewal, upgrade, downgrade, pause, and cancel as separate signals. You can see the difference between a subscriber who upgraded and one who quietly stopped renewing, instead of one undifferentiated Purchase.
Rebills happen on your billing system with no browser session, so the pixel never sees them. Zappush streams every renewal server-side via CAPI, giving the ad platforms the recurring revenue that actually defines subscriber value.
Instead of sending a $25 first order, Zappush sends predicted_ltv on the Subscribe event. Meta and Google bid on the customer's forecasted lifetime value, so you can afford a higher CPA on people who will renew for a year.
A per-subscriber churn-risk score and days-to-churn estimate rise as a missed renewal or cancel window approaches. Retention offers fire before the cancel, not in a win-back email a month too late.
Your highest-LTV subscribers seed value-based lookalikes, so the platforms find more people who stay. Zappush pushes cancelled subscribers as suppression lists, so budget stops retargeting people who already left.
CONSUMABLES
At signup, a subscriber worth $500 over a year fires the same $25 Purchase as a one-time buyer. Zappush sends predicted_ltv on Meta's Subscribe event and value-based conversions to Google, so acquisition is priced against forecast lifetime value. You can afford a higher CPA on the customers who keep renewing.
RECHARGE / STRIPE
Rebills run on your billing system with no browser session, so the pixel records nothing after the first order. Webhooks from Recharge, Stripe, or Shopify subscriptions write every renewal, upgrade, downgrade, pause, and cancel to one customer profile, then stream server-side through the Conversions API. Recurring revenue becomes visible to the ad platforms.
CHURN SUPPRESSION
Cancellations are invisible to the pixel, so churned subscribers stay in retargeting pools and lookalike seeds. Cancel events are captured as distinct signals, so cancelled customers are pushed as suppression lists while your highest-LTV subscribers seed value-based lookalikes. Budget follows the people who stay.
Start free in minutes, or see it live on a call.
From $59/month · 14-day free trial · Cancel anytime
