Connecting Magento to Roku Ads
Magento is self-hosted and endlessly customisable, which means every installation is different and full-page caching is always in the way. Connected TV is a household medium with no click surface, which makes every conversion it reports a matched inference rather than a followed link. The join between them succeeds or fails on one thing: whether household-level identity, not a click reaches the Magento order before the conversion happens, because Roku can only match a conversion it can tie back to a click it recognizes.
Free30 minutesNo obligation
Specific to this pair
Roku TV ads and Magento orders: matched households, checked by holdout
Roku ads aren't clicked, so send Magento orders server-side from the observer or a scheduled sales_order upload with hashed email and phone, ZIP, increment_id, base_grand_total and order time, confirming field names with Roku. Use the billing address when gift orders ship elsewhere. Test the matched number with a holdout by shipping ZIP or DMA, comparing new-customer orders in Magento.
Nobody clicks a Roku ad, so there is nothing to capture on the Magento landing page. Roku matches its exposures to households and needs your orders, with hashed identifiers, to make that match. Send them server-side from the order observer or as a scheduled upload from sales_order: hashed email, hashed phone, ZIP, increment_id, base_grand_total and the order time. Confirm in Roku's documentation which fields its upload accepts, since we do not list exact names here.
Address choice matters more here than on click-based platforms, because the household is the unit. A gift order shipped to someone else's home will match the recipient's household, which may never have seen the ad, so use the billing address for identity when the two differ. Do not send the customer's IP address unless Roku requires it and your privacy notice covers it.
Treat the matched number as a claim to test. Magento order data makes a holdout straightforward: pick test and control regions by shipping ZIP or DMA, run Roku in one, and compare new-customer orders per thousand households in your own database across both. If the lift does not appear in Magento's data, a matched number from Roku is not proof that the campaign worked.
Magento → Roku · what breaks
Why this join usually fails — Magento → Roku
- 01
Household-level identity, not a click never reaches Magento
Magento's full-page cache serves a stored render to the visitor, which means anything relying on dynamically rendered values can silently fail — and in Magento this has historically included serving one customer's cached block to another, which is a data problem as well as a tracking one.
- 02
Full-page cache between the visitor and your code
The page the customer saw is not the page your code assumed. This is the defining Magento tracking failure and it produces intermittent, hard-to-reproduce loss.
- 03
View-through on a screen nobody clicked
Every CTV conversion is view-through by definition. Some of that influence is real and some is a household that would have bought anyway, and no amount of pixel work separates the two. Only a holdout does.
- 04
Nothing reconciles afterwards
Roku reports matched conversions and match rates. The match rate tells you how much of your audience it could resolve at all — and a geo holdout tells you whether the campaign moved anything.
Magento → Roku · the fix
What working looks like — Magento → Roku
Household-level identity, not a click on every order
Conversions arriving in Roku
The conversion is matched to an exposed household within the attribution window and feeds the campaign reporting.
Reconciled against the source
Magento → Roku · architecture
How Magento and Roku actually connect
- 1
Magento holds the truth
You own the database, so the truth is as good as the query. Pin down which order statuses count as revenue — processing, complete, or both — because that choice moves the number substantially.
- 2
Roku Ads needs a click to match
A pixel or server event on your side that Roku can match against, plus the hashed customer information the match depends on. Without that, the channel is measurable only by holdout.
- 3
The identifier is the bridge
Household-level identity, not a click, captured at the visit and carried into the Magento order.
- 4
The event source decides reliability
Fire server-side from the observer rather than from the success page template, which is cached and may not execute anything.
- 5
Deduplication at the destination
The deduplication problem is across platforms, not within this one. A household exposed to a TV ad and later reached by search and social produces a conversion all three will claim.
Magento → Roku · normal or broken
Working vs. broken, side by side — Magento → Roku
Normal, not a fault
Household-level identity, not a click present on the order
Sent from the Magento order placement observer
Deduplicated correctly
The deduplication problem is across platforms, not within this one. A household exposed to a TV ad and later reached by search and social produces a conversion all three will claim.
Reconciles with the source
Actually broken
Household-level identity, not a click missing on most records
Magento's full-page cache serves a stored render to the visitor, which means anything relying on dynamically rendered values can silently fail — and in Magento this has historically included serving one customer's cached block to another, which is a data problem as well as a tracking one.
Sent from the browser
The page the customer saw is not the page your code assumed. This is the defining Magento tracking failure and it produces intermittent, hard-to-reproduce loss.
Counted twice, or not at all
Every CTV conversion is view-through by definition. Some of that influence is real and some is a household that would have bought anyway, and no amount of pixel work separates the two. Only a holdout does.
Nobody has reconciled it
Magento → Roku · diagnose
Diagnostic order — Magento → Roku
- 01
Count orders carrying household-level identity, not a click
- 02
Follow one real conversion end to end
- 03
Place a test order as an anonymous visitor through cache
Not as an admin, which bypasses it. If the order data is missing on the cached path, caching is your cause.
- 04
Ask whether a geo or audience holdout exists
If it does not, the reported figure is exposure correlated with purchase, which is not the same as a campaign that caused one.
- 05
Read the match rate, not the success message
Roku reports matched conversions and match rates. The match rate tells you how much of your audience it could resolve at all — and a geo holdout tells you whether the campaign moved anything.
Magento → Roku · prove
How it gets proven — Magento → Roku
Source of truth
Magento's sales order records in your own database, for the same window and order status set.
- Household-level identity, not a click confirmed present on a live order.
- Incremental lift measured against a holdout, with platform-reported conversions shown alongside rather than instead.
- Order data confirmed populated on an order placed through a fully warmed cache.
Magento → Roku · free audit
What we check in the free audit
- Count orders carrying household-level identity, not a click
- Follow one real conversion end to end
- Place a test order as an anonymous visitor through cache
- Ask whether a geo or audience holdout exists
- Read the match rate, not the success message
Checked against
Magento's sales order records in your own database, for the same window and order status set.
Free30 minutesNo obligation
Magento → Roku · when not to buy
When you don't need this — Magento → Roku
- Measure identifier coverage yourself first — pull your last hundred orders and count how many carry household-level identity, not a click.
- If your Magento build has heavy customisation by another team, scope their availability first — the build is usually blocked there.
- If you cannot run a holdout, keep CTV budget small and report it as unproven. That is a more useful position than a matched number nobody can check.
Magento → Roku · what we deliver
What gets built — Magento → Roku
Identifier capture into Magento
Capture the identifier and persist it as order data through an observer on order placement, server-side, so it never depends on what the cache served.
Event source: the Magento order placement observer
Fire server-side from the observer rather than from the success page template, which is cached and may not execute anything.
Dispatch to Roku
Server-side conversion upload with hashed identity, from your order system.
Reversals where they exist
Credit memos are recorded against the original order and should reduce the reported figure.
Written guarantee
95%+ tracking accuracy
Measured against Magento's sales order records in your own database, for the same window and order status set.. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Magento → Roku questions, answered
Only through a household match on hashed customer data you send from Magento, and that match is probabilistic. A geographic holdout measured in your own order data is the check that matters.
Hashed email and phone, location such as ZIP, an order ID, value and timestamp, sent server-side. Confirm the exact accepted fields in Roku's own documentation.
Almost always because household-level identity, not a click never reached the Magento order. Magento's full-page cache serves a stored render to the visitor, which means anything relying on dynamically rendered values can silently fail — and in Magento this has historically included serving one customer's cached block to another, which is a data problem as well as a tracking one. Measure coverage before debugging the dispatch.
Roku matches exposure on a television to activity on other devices in the same household, using identity graphs and IP. Nobody clicks a TV ad. That means there is no identifier to capture, the match is probabilistic, and the unit of measurement is a household rather than a person.
The Magento order placement observer. Fire server-side from the observer rather than from the success page template, which is cached and may not execute anything.
Roku reports matched conversions and match rates. The match rate tells you how much of your audience it could resolve at all — and a geo holdout tells you whether the campaign moved anything.
More on Magento → Roku
- Magento → Google AdsConnecting Magento to Google Ads
- Magento → Microsoft AdsConnecting Magento to Microsoft Ads
- Magento → Apple Search AdsConnecting Magento to Apple Search Ads
RELATED GUIDES
Where Magento → Roku fits in the rest of your tracking
- Wix → RokuConnecting Wix Stores to Roku Ads
- Gumroad → RokuConnecting Gumroad to Roku Ads
- Swell → RokuConnecting Swell to Roku Ads
- Magento → DV360Connecting Magento to Display & Video 360
- Magento → OutbrainConnecting Magento to Outbrain
- SupplementsConversion tracking for supplement brands, built around subscription value
- OpenCart → RokuConnecting OpenCart to Roku Ads
- Checkout Extensibility → RokuConnecting Shopify Checkout Extensibility to Roku Ads
Free · 30 min
Get Magento and Roku joined properly
Free30 minutesNo obligation
