Recurly → Segment · Conversion tracking
Connecting Recurly to Segment
Recurly is built around keeping subscriptions alive, which means a large share of the revenue it recovers comes from payments that failed and were retried rather than from anything marketing did. Segment is a customer data platform rather than an ad network, so sending to it is not about matching a conversion — it is about putting one clean event where every other destination can read it. The join between them succeeds or fails on one thing: whether the userId and anonymousId reaches the Recurly subscription before the conversion happens, because Segment can only match a conversion it can tie back to a click it recognizes.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Recurly → Segment
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Recurly → Segment tracking rebuild — in their own words, on camera.
Why this join usually fails
The userId and anonymousId never reaches Recurly
The single most common cause. Checkout may run through Recurly's hosted pages, and the renewal that actually matters happens months later with no browser session at all.
Dunning recovery counted as acquisition
A retried card that succeeds on day three looks identical to a new subscription in most exports. On a mature book that recovery is a meaningful share of monthly revenue and none of it was bought.
One bad event multiplied across every destination
Segment's value is fan-out, which is also its risk. An inconsistent identity or a duplicated event does not break one report — it breaks every connected tool simultaneously, and tracing it back is harder than debugging a direct integration.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. Segment's debugger shows events arriving and which destinations accepted them. Arriving is not the test — check a destination you care about and confirm the event landed there with the identity intact, then reconcile against your own records.
Architecture
How Recurly and Segment actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Recurly holds the truth
Dunning recovery is Recurly's core product. Revenue rescued from a declined card three days after it failed is real money and it is not a conversion — attributing it to whatever campaign is running that week is the standard mistake here.
Step 2
Segment needs a click to match
Segment needs a consistent identity model — the same userId everywhere, an alias when an anonymous visitor becomes known, and event names that follow one spec. Feeding it inconsistent identities pushes the mess to every connected destination at once.
Step 3
The identifier is the bridge
The userId and anonymousId, captured at the visit and carried into the Recurly subscription. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send new subscription starts at first successful payment. Renewals and dunning recoveries belong in separate figures.
Step 5
Deduplication at the destination
Segment deduplicates on messageId within a window. Because it fans out to many destinations, a duplicate here becomes a duplicate everywhere, which makes idempotent messageIds more important than in any single-destination integration.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the Segment dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The userId and anonymousId present on the subscription
Visible on the record itself in Recurly, not merely captured somewhere on the site.
Sent from the Recurly subscription webhook
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Segment deduplicates on messageId within a window. Because it fans out to many destinations, a duplicate here becomes a duplicate everywhere, which makes idempotent messageIds more important than in any single-destination integration.
Reconciles with the source
Segment's count and Recurly's records agree within a few percent over a closed window.
Actually broken
The userId and anonymousId missing on most records
Checkout may run through Recurly's hosted pages, and the renewal that actually matters happens months later with no browser session at all.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. A retried card that succeeds on day three looks identical to a new subscription in most exports. On a mature book that recovery is a meaningful share of monthly revenue and none of it was bought.
Counted twice, or not at all
Segment's value is fan-out, which is also its risk. An inconsistent identity or a duplicated event does not break one report — it breaks every connected tool simultaneously, and tracing it back is harder than debugging a direct integration.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Recurly. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count subscriptions carrying the userId and anonymousId
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Recurly and into Segment.
- 3
Split subscription events into new, renewal and recovered
Three categories, three owners. Until they are separated, no acquisition number is readable.
- 4
Check identity resolution before checking anything downstream
If anonymousId is never aliased to userId, every destination sees two people where there is one, and no downstream fix helps.
- 5
Read the match rate, not the success message
Segment's debugger shows events arriving and which destinations accepted them. Arriving is not the test — check a destination you care about and confirm the event landed there with the identity intact, then reconcile against your own records.
Source-of-truth validation
How it gets proven
Against Recurly's own records, not against either platform's dashboard.
- The userId and anonymousId confirmed present on a live subscription.
- A real conversion followed from click through Recurly to Segment.
- An anonymous session confirmed aliased to a known user, with the event visible in at least one downstream destination.
- New subscription starts reconciled against imported conversions, with recovered revenue reported separately.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If Segment already reports conversions that reconcile against Recurly's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred subscriptions and count how many carry the userId and anonymousId. Ten minutes, free, and it tells you whether any of this is worth doing.
- If your churn is mostly voluntary and you run no dunning, this collapses to an ordinary subscription integration.
- If you send to one or two destinations, Segment is infrastructure you do not need — direct integrations are simpler and cheaper. It earns its place at genuine fan-out.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Recurly → Segment (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What working looks like
The userId and anonymousId on every subscription
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in Segment
8+ EMQEvents land in Segment and forward to every connected destination, warehouse included, on one shared definition.
Reconciled against the source
DedupedRecurly's own records are the reference, not either dashboard.
What gets built
Identifier capture into Recurly
Capture on your own domain, persist against the account, and attach to the subscription so a renewal or a recovery can still be traced without being credited as new.
Event source: the Recurly subscription webhook
Send new subscription starts at first successful payment. Renewals and dunning recoveries belong in separate figures.
Dispatch to Segment
Server-side track and identify calls with a stable messageId, consistent userId, and the click identifier carried as a trait or property.
Reversals where they exist
Cancellations inside the first billing period reverse, and so should subscriptions that never recover from a failed first charge.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Why aren't my Recurly conversions showing in Segment?
Almost always because the userId and anonymousId never reached the Recurly subscription. Checkout may run through Recurly's hosted pages, and the renewal that actually matters happens months later with no browser session at all. Measure coverage before debugging the dispatch.
02What identifier does Segment need?
Segment identifies people by anonymousId before they are known and userId afterwards, and the alias between them is what stitches a session to a customer. Click identifiers travel as event properties or traits rather than as a matching key — Segment does not match anything itself, it forwards. That distinction changes the whole design: get the identity resolution right and every downstream destination inherits it.
03Where should the event come from?
The Recurly subscription webhook. Send new subscription starts at first successful payment. Renewals and dunning recoveries belong in separate figures.
04How do I know it worked?
Segment's debugger shows events arriving and which destinations accepted them. Arriving is not the test — check a destination you care about and confirm the event landed there with the identity intact, then reconcile against your own records.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourRecurly → Segment setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Recurly → Segment setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Recurly and Segment joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
