FloorSync / Check your Stripe event
Check your own Stripe event: what would Meta and GA4 get?
Paste a checkout.session.completed, invoice.paid or invoice.payment_succeeded event. See if it’s a new sale or a renewal, the Meta Purchase and GA4 purchase it makes, the id that keeps retries from counting twice, and what’s missing for matching. Worked out in this page: nothing is sent or stored.
- Event type
- New sale or renewal
- Value
- event_id used
What’s missing
What Meta’s Conversions API gets
What GA4’s Measurement Protocol gets
Email, phone and customer id are SHA-256 hashed in your browser, as FloorSync does before sending. Your Meta token and GA4 secret are never needed here.
Get your key, free
FloorSync sends events like this one to your own Meta pixel and GA4.
Just your email to get a key, no card. Free for 50 live sales a month; $29 a month per business for more, after 7 free days.
What this checks, and how
It runs the same mapping FloorSync’s server uses, in your browser.
- New sale or renewal: a paid checkout is a new sale (a $0 subscription checkout is a trial). An
invoice.paidwithbilling_reason: subscription_createis a new sale; any other paid invoice counts as a renewal. - event_id: the checkout session id (
cs_…) or invoice id (in_…). Stripe’s retries carry the same id, so Meta counts the sale once. - Matching: the buyer’s email and Stripe customer, hashed. From the checkout’s
metadata:fbp,fbc(orfbclid) and the GA client id (ga_client_id,_gaorga). - Renewals: they carry no browser cookies, so they match on what was kept at checkout. Your renewal setting decides what Meta gets.
Want the whole picture first? Read why Stripe sales go missing in Meta and GA4, or try the dry run with ready-made events.