Smile.io → Outbrain · Conversion tracking
Connecting Smile.io to Outbrain
Smile.io issues points that customers redeem later, which means every point awarded is a liability and every redemption is a discount against a future order. Outbrain is the other major native discovery network, with the same audience-intent problem and its own conversion configuration. The join between them succeeds or fails on one thing: whether the Outbrain click identifier reaches the Smile.io points redemption before the conversion happens, because Outbrain 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 Smile.io → Outbrain
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 Smile.io → Outbrain tracking rebuild — in their own words, on camera.
Why this join usually fails
The Outbrain click identifier never reaches Smile.io
The single most common cause. The rewards widget renders in a Smile-served frame that does not share your page's storage.
Points liability invisible in the conversion value
An order that awards points is worth its value minus the eventual redemption. Reporting the gross figure on every order overstates margin by the whole cost of the loyalty programme.
Shallow conversions on discovery traffic
A newsletter signup from discovery traffic converts to revenue at a very different rate than the same signup from search. Optimizing on the shallow event flatters the channel and misleads the budget.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. Outbrain reports at campaign and section level. Reconcile against your own records, and compare the downstream conversion rate of discovery traffic against your other channels before judging the numbers.
Architecture
How Smile.io and Outbrain actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Smile.io holds the truth
A redeemed order is retention revenue at a reduced margin. Crediting it to the paid click that acquired the customer originally counts one acquisition twice and at the wrong value.
Step 2
Outbrain needs a click to match
Outbrain matches server events on the click identifier and hashed customer information, against conversion definitions configured in its interface.
Step 3
The identifier is the bridge
The Outbrain click identifier, captured at the visit and carried into the Smile.io points redemption. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send orders net of the discount points redeemed, with first orders and reward-driven repeats marked.
Step 5
Deduplication at the destination
Outbrain deduplicates on a shared event identifier between the pixel and the server event.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the Outbrain dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The Outbrain click identifier present on the redemption
Visible on the record itself in Smile.io, not merely captured somewhere on the site.
Sent from your order feed with Smile attributes attached
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Outbrain deduplicates on a shared event identifier between the pixel and the server event.
Reconciles with the source
Outbrain's count and Smile.io's records agree within a few percent over a closed window.
Actually broken
The Outbrain click identifier missing on most records
The rewards widget renders in a Smile-served frame that does not share your page's storage.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. An order that awards points is worth its value minus the eventual redemption. Reporting the gross figure on every order overstates margin by the whole cost of the loyalty programme.
Counted twice, or not at all
A newsletter signup from discovery traffic converts to revenue at a very different rate than the same signup from search. Optimizing on the shallow event flatters the channel and misleads the budget.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Smile.io. 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 redemptions carrying the Outbrain click identifier
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Smile.io and into Outbrain.
- 3
Compare gross order value against value net of points issued and redeemed
The gap is the programme's real cost, and it is rarely in any marketing report.
- 4
Compare downstream conversion rates for discovery traffic against your other channels
If they differ substantially — and they usually do — the conversion you optimize toward has to sit deeper in the funnel here.
- 5
Read the match rate, not the success message
Outbrain reports at campaign and section level. Reconcile against your own records, and compare the downstream conversion rate of discovery traffic against your other channels before judging the numbers.
Source-of-truth validation
How it gets proven
Against Smile.io's own records, not against either platform's dashboard.
- The Outbrain click identifier confirmed present on a live redemption.
- A real conversion followed from click through Smile.io to Outbrain.
- Downstream conversion rate for Outbrain traffic measured separately from other channels.
- First orders reconciled against imported conversions, with redemption-driven orders 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 Outbrain already reports conversions that reconcile against Smile.io'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 redemptions and count how many carry the Outbrain click identifier. Ten minutes, free, and it tells you whether any of this is worth doing.
- If you run no loyalty programme, this reduces to an ordinary store integration.
- If you have no top-of-funnel content worth discovering, native placement has nothing to work with regardless of measurement.
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 Smile.io → Outbrain (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 Outbrain click identifier on every redemption
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in Outbrain
8+ EMQConversions appear against campaigns and publisher sections, which is the level at which the channel is actually managed.
Reconciled against the source
DedupedSmile.io's own records are the reference, not either dashboard.
What gets built
Identifier capture into Smile.io
Capture on your own domain before the widget loads and record points activity on the order so acquisition and retention stay separable.
Event source: your order feed with Smile attributes attached
Send orders net of the discount points redeemed, with first orders and reward-driven repeats marked.
Dispatch to Outbrain
Server events to Outbrain's conversions endpoint with the click identifier and hashed customer data.
Reversals where they exist
Refunds reverse and should claw back awarded points.
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 Smile.io conversions showing in Outbrain?
Almost always because the Outbrain click identifier never reached the Smile.io points redemption. The rewards widget renders in a Smile-served frame that does not share your page's storage. Measure coverage before debugging the dispatch.
02What identifier does Outbrain need?
Outbrain appends a click identifier to the landing page URL alongside its pixel. As with any discovery network, the measurement challenge is less about capture and more about whether the conversion you are counting is deep enough in the funnel to be meaningful, because top-of-funnel actions are cheap to generate here and weakly predictive.
03Where should the event come from?
Your order feed with Smile attributes attached. Send orders net of the discount points redeemed, with first orders and reward-driven repeats marked.
04How do I know it worked?
Outbrain reports at campaign and section level. Reconcile against your own records, and compare the downstream conversion rate of discovery traffic against your other channels before judging the numbers.
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 yourSmile.io → Outbrain 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 Smile.io → Outbrain 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 Smile.io and Outbrain 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
