Skip to main content
Upstack Data
Request demo

Recharge to Meta Conversions API

Forward every Recharge event to Meta Conversions API server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demoStart free trial

Connection

Connect Recharge to Meta Conversions API with Upstack Data

SourcePayments & subscriptions

Recharge

Bring subscription events into the same resolved customer — new subscriptions, renewals, churn and reactivation.

Recharge integration
DestinationAd platforms

Meta Conversions API

Forward deduplicated, identity-resolved conversions to Meta through the Conversions API — and give the model a customer instead of a session.

Meta Conversions API integration

What changes

What changes when Recharge feeds Meta Conversions API.

Higher Event Match Quality

More hashed identifiers on every event — email, phone, external ID, click ID — so EMQ rises and Meta matches more of what you send.

Pixel and CAPI, one install

One source of truth for both, with browser and server events deduplicated on event_id so purchases are never double-counted.

Subscriptions as their own conversion

Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.

Renewals counted properly

Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.

What actually moves

What Recharge carries, and what Meta Conversions API needs.

Recharge and Meta Conversions API describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Recharge can put on an event, the right is what Meta Conversions API can actually use.

Recharge sends

subscription_id
the subscription, not the order
charge_id
each recurring charge
email / phone
subscriber contact
status
active, cancelled, paused, reactivated
is_first_charge
new subscription versus renewal
product / frequency
what they subscribed to and how often

Meta Conversions API receives

em, ph (SHA-256)
raise Event Match Quality
fbclid / _fbp
credit the click that drove it
external_id
stable person across sessions
event_id
dedupe against the browser pixel
value / currency
value-based bidding

Delivery you can audit

How you know it is working.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

  • Per-event inspection

    Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

  • Deduplication

    Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

  • Bot and fraud filtering

    Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

Where to check in Meta Conversions API

Events Manageryour datasetEvent Match Quality. Server events appear with a Conversions API badge, and the match-quality score is scored per parameter so you can see which identifiers arrived.

Related connectors

Other places Recharge can send to.

Other sources that feed Meta Conversions API.

Get Recharge talking to Meta Conversions API.

A 15-minute walkthrough of this connector on your own account.

Request a demoStart free trial