At a glance
AdRoll-attributed conversion value. SUM(conversion_value) for every purchase event AdRoll’s pixel + server-side tag captured within the configured attribution window, summed across line items at the advertisable level. This is AdRoll’s self-reported revenue, not the truth from your commerce platform; the two often disagree by 20, 50% post-iOS ATT. See Reconcile for the gap explanation.
| What it counts | Sum of conversion_value for purchase events tagged with AdRoll’s pixel or sent via Conversions API, attributed back to a click or view on AdRoll inventory inside the attribution window. Includes display retargeting, prospecting, native, video, and email-orchestrated conversions if all channels are tagged. |
| Cost basis | N/A for revenue. (For ROAS pairing: divide this by adr_total_spend to get account-level ROAS.) |
| Currency | Advertisable currency, single. AdRoll does not normalise multi-currency conversion value; if your pixel sends events in mixed currencies, the figure is meaningless. Configure pixel currency consistently per advertisable. |
| Conversion attribution | Last-touch with view-through credit. AdRoll’s default is 30-day post-click + 7-day post-view, configurable per advertisable. Click conversions get 100% credit; view conversions get 100% credit if no click in the window touched the same conversion. Cross-platform deduplication is the merchant’s responsibility (AdRoll claims any conversion that touched its inventory regardless of last-click on Meta or Google). |
| Attribution window | 30-day click + 7-day view (default). Wider than Meta’s post-iOS-14.5 7d/1d default, narrower than Google’s 30d/1d default. Window is account-level, not line-item-level. Tightening to 7-day click typically drops reported revenue by 15, 30%. |
| iOS 14.5+ ATT impact | Severe. AdRoll’s retargeting model depends on cross-site cookie tracking and third-party identifiers. ATT removed IDFA on iOS, Safari ITP killed third-party cookies. Without server-side tagging (AdRoll’s Conversions API or Pixel Server-Side), reported revenue typically under-states real AdRoll-driven revenue by 25, 50% on iOS-heavy audiences. With server-side live, gap narrows to 10, 20%. The card cannot correct for this; it reports what AdRoll reports. |
| Bot / invalid traffic | Conversion-side IVT filtering is post-billing; AdRoll removes detected fake conversions before they hit conversion_value. Real-world IVT-conversion rate is <0.5% on properly tagged accounts; if you see purchases with no order in the commerce platform, your pixel is misfiring (most likely on the cart-abandon flow, double-firing on add-to-cart). |
| Time window | T/7D/30D vsP (default 30D vs the prior 30D). Real-time updates with up to 4-hour ingest lag on “today”; view-through conversions can keep accumulating for up to 7 days post-impression. |
| Alert trigger | drop >20% vsP. A 30-day-vs-prior-30-day drop greater than 20% fires the alert. The usual cause is pixel breakage (most common), an ATT-related audience shrink, or a creative refresh that hasn’t yet warmed up. |
| Roles | owner, marketing, finance |
Calculation
Calculated automatically from your AdRoll data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A UK homeware DTC brand running AdRoll for site retargeting + lookalike prospecting + cart-abandon orchestration. The 30-day window is 02 Apr 26 to 01 May 26. Account currency GBP. AdRoll Conversions API server-side tagging is live (rolled out 18 Mar 26).| Channel | Spend (£) | Conversions | Conversion value (£) | Per-channel ROAS |
|---|---|---|---|---|
| Site retargeting (web visitors, 30d) | 6,800 | 412 | 58,400 | 8.59× |
| Lookalike prospecting (purchaser LAL) | 4,200 | 84 | 9,200 | 2.19× |
| Cart-abandoner email + display | 1,900 | 196 | 26,800 | 14.11× |
| Brand-safe contextual prospecting | 800 | 12 | 1,400 | 1.75× |
| Account total (this card) | £13,700 | 704 | £95,800 | 6.99× |
- The headline £95,800 is what AdRoll claims; the truth is closer to £55, 65k. Real AdRoll-driven Shopify revenue (probabilistic blend of UTM truth, GA4 display attribution, and AdRoll’s own measurement) is in that range. Don’t quote £95k to the CFO without the gap caveat. The honest read is “AdRoll is contributing £55, 65k of Shopify revenue per month at £13.7k spend, business ROAS 4, 4.7×.”
- Cart-abandon orchestration at 14.11× is mostly cannibalised email revenue. Many of those buyers would have completed the purchase via your existing Klaviyo cart-recovery sequence anyway. AdRoll’s email + display add-on claims credit alongside Klaviyo for the same orders. Run an A/B holdout (10% of cart abandoners get no AdRoll touch) for 30 days to measure incremental value, expect the “real” lift to be 30, 50% of claimed.
- Retargeting at 8.59× is in-band for warm-audience retargeting. Typical retargeting ROAS sits at 6, 10×; if you’re seeing <5× on retargeting, audience match rate is degraded (usually iOS / Safari ITP shrink). If you’re seeing >12× consistently, you’re probably defending revenue you’d already capture organically (same dynamic as Branded Search on Google).
- Prospecting at 2.19× is acceptable cold-audience performance for retargeting platforms. Pure cold prospecting on AdRoll typically lands 1.5, 3×, lower than Meta or TikTok cold audiences because AdRoll’s prospecting inventory is mostly GDN remnant. If prospecting is the growth lever, Meta or TikTok will outperform.
- Pre-CAPI on this account, conversion value was reading £71,400 on £15,200 spend (4.7× ROAS). The CAPI rollout in March lifted reported revenue by ~34% (catching iOS conversions Pixel-only had missed). The lift is real measurement, not inflation; the underlying business performance was the same.
- iOS share is 47% on this account. ATT and Safari ITP impact is material; CAPI is closing most of the gap but expect a residual 10, 20% under-report on iOS retargeting line items. Plan a creative + audience refresh on retargeting line items every 21, 28 days; ATT-eligible audience pools shrink fast and creative-fatigue accelerates the decline.
- Revenue up + spend up = healthy scaling, the optimiser is finding incremental conversions.
- Revenue down + spend up = scaling beyond the efficient frontier. Cap spend, refresh creative, audit per-line-item ROAS.
- Revenue flat + spend down = budget cut without channel deterioration; channel is still healthy.
- Sudden revenue drop with spend stable = pixel breakage (most common, check pixel diagnostic in AdRoll dashboard) or ATT audience collapse.
- Revenue dropped 20%+ but Shopify revenue is stable = AdRoll is losing claim on conversions Meta or Google are now winning. Attribution shift, not real loss.
Sibling cards merchants should reference together
Total Revenue on its own only tells you what AdRoll claims. Pair it with these to know whether the revenue is real and incremental:| Card | Why it matters next to Total Revenue | What the combination tells you |
|---|---|---|
| Total Spend | The cost side. Revenue without spend context is meaningless. | Revenue and spend rising together = healthy scale; revenue rising while spend rises faster = efficiency loss. |
| ROAS | The ratio. The headline efficiency reading. | Revenue rise driven by ROAS holding above 4× = green light; revenue rise driven by ROAS dropping below 2× = stop signal. |
| Conversions Trend | The volume side. Conversions × AOV = revenue. | If revenue moved without conversions changing, AOV changed (mix shift, currency drift, or a refund spike). |
| Conversion Rate Trend | Funnel efficiency. Click-to-conversion rate. | Falling CR while revenue holds means you’re getting more clicks for the same conversions, audience-quality drift. |
| Conversion Lag | View-through latency. How many days after impression do conversions land? | Critical for retargeting / native. Today’s spend may credit revenue 3, 7 days from now. Lag rising signals iOS attribution stress. |
| Clicks vs Conversions | The broken-tracking canary. Clicks rising while conversions stagnate = pixel issue. | Most common cause of false revenue alerts. Confirm pixel health before reacting to a revenue drop. |
| Revenue by Campaign | Per-line-item attribution. Which campaigns drove the headline number? | Headline revenue hides huge variance. Cart-abandon orchestration typically eats 30, 50% of credit on accounts that run it. |
| GA4 Revenue by Channel | Independent attribution check. GA4 Display + Referral attribution should roughly match AdRoll’s claim. | If AdRoll claims 2× what GA4 sees on Display, AdRoll is over-claiming. Common post-iOS without proper CAPI dedup. |
| Shopify Total Revenue | The truth side. Real business revenue. | Real AdRoll-driven Shopify revenue (UTM-tagged) is typically 40, 70% of AdRoll’s claim. Use the gap to size your CFO read. |
Reconciling against the vendor’s own dashboard
Where to look in AdRoll’s own dashboard:AdRoll Dashboard → Reporting → Performance Report → “Conversion Value” (filter to the same advertisable and date range used in this card).The “Conversion Value” column matches the field this card sums. AdRoll’s Home tile and Reporting → Custom Report → Group by Day both surface the same number for the chosen window. For a sanity check, the Conversions column × the Avg Order Value column should equal Conversion Value within rounding. Why our number may legitimately differ from AdRoll itself:
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | AdRoll uses the advertisable’s configured time zone. Vortex IQ uses UTC. For a 30-day window the gap averages out; for “today” or “yesterday” the boundary can shift figures meaningfully. |
| Ingest lag | Ours lower for “today” | AdRoll Reporting API has a 2, 4 hour lag on conversion events; view-through conversions can keep accumulating for up to 7 days post-impression. Today’s number is structurally low. |
| Attribution model changes | Direction depends | If you change the attribution window (e.g. 30d-click → 7d-click) mid-period, AdRoll retroactively reflows the data; this card matches whatever the current model says. A 30d→7d switch typically drops reported revenue 15, 30%. |
| Pixel currency mismatch | Ours could be wrong | If your pixel sends conversion events in mixed currencies (e.g. some in GBP, some in USD without conversion), AdRoll’s conversion_value becomes meaningless. Confirm pixel sends a single currency per advertisable. |
| Modeled conversions | Ours matches AdRoll UI | AdRoll auto-fills attribution gaps with statistical modeling for ATT-blocked iOS conversions. Both this card and the AdRoll UI read the blended (real + modeled) number. Modeled fill is typically 8, 18% of conversion value for Pixel-only accounts. |
| Removed line items | Ours captures them | Deleted (not paused) line items are hidden from the AdRoll UI; the API still returns historical conversions. Our card includes them. |
conversion_value AdRoll reports is what the pixel + Conversions API saw, attributed back through AdRoll’s last-touch model. That value flows from your tag setup:
- If the pixel sends order revenue with VAT, AdRoll reports VAT-inclusive revenue (matches what the customer paid).
- If the pixel sends only first-purchase value (a common cap), AdRoll under-reports returning-customer revenue.
- If the pixel sends modelled value, AdRoll includes some imputed revenue that wasn’t actually paid.
shopify.total_revenue attributed to AdRoll UTMs by AdRoll spend. The two figures should be within 30, 50% post-CAPI; bigger gaps usually mean (a) commerce-platform attribution disagrees with AdRoll’s window (different click windows, different last-touch logic), (b) the pixel is misconfigured, or (c) iOS / Safari ITP impact is degrading attribution despite CAPI.
Cross-connector reconciliation:
This card is AdRoll’s view of AdRoll-driven performance. The same purchase will be claimed differently by every platform with a tag in the path:
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
google_analytics.ga_revenue_by_channel | GA4 Display + Referral (AdRoll-tagged) revenue ≈ this card × 0.6, 0.85 | GA4 uses last-non-direct-click; AdRoll uses last-touch within 30d-click + 7d-view. AdRoll over-claims on view-through that GA4 ignores. |
shopify.total_revenue | (AdRoll conversion_value) is structurally larger than UTM-tagged AdRoll Shopify revenue, often 1.5, 2.5× | View-through credit + iOS modeling inflate the AdRoll number relative to UTM-only Shopify attribution. The “true” answer sits between the two. |
criteo.cri_total_revenue | Independent retargeting platform. Comparable benchmark only. | Different audiences, different inventory, different attribution defaults. No reconciliation. |
facebook_ads.fac_total_revenue | Different funnel position. Meta is top + retargeting; AdRoll is mostly retargeting. | Both will claim overlapping conversions. Sum exceeds Shopify truth, that’s the multi-platform double-claim pattern. |
Known limitations / merchant FAQs
My AdRoll says £95k revenue but Shopify shows £52k from AdRoll UTMs, which is true? Both are true; they measure different things. AdRoll’s £95k is AdRoll-attributed revenue: every purchase that touched AdRoll inventory inside the 30-day-click + 7-day-view window. Shopify’s £52k is UTM-tagged AdRoll-source revenue: only orders where the customer’s last referrer carried AdRoll UTM parameters. The gap (£95k vs £52k) is structural and expected. Drivers:- View-through credit. AdRoll claims any purchase from a user it served an impression to within 7 days, even if the user later arrived via Google search, an email, or direct. Shopify only sees the last UTM.
- iOS / Safari ITP. AdRoll’s UTM strip-rate is 30, 50% on Safari and iOS-app-WebView traffic; those orders show as Direct in Shopify but are still counted by AdRoll’s pixel.
- Modeled conversions. AdRoll auto-fills attribution gaps with statistical estimates; that revenue exists in AdRoll’s number but not in Shopify’s UTM count.
- Identify a user across sites (the basis of retargeting).
- Tie a conversion back to the impression that influenced it.
- Shopify: AdRoll has a native Sales Channel app; one-click install enables CAPI. Auto-deduplicates Pixel + CAPI via
event_id. 30-minute setup. - BigCommerce: AdRoll BC app + manual CAPI via Tag Manager + custom event_id. 2, 4 hours.
- Adobe Commerce / Magento: AdRoll extension + custom server endpoint. 1, 3 days.
- Custom / headless: Build a server-side proxy mirroring Pixel events. 1, 2 weeks.
- Test in AdRoll → Pixel → Server-Side Events tab; if dedup is working, both Pixel and CAPI events show but AdRoll credits one per conversion.
- Allow 7, 14 days for retraining before judging the revenue lift; AdRoll’s models recalibrate over that window.
conversion_value invisibly. Patterns:
- Pre-CAPI: modeled fill ~18, 28%. Inflated.
- Post-CAPI clean: modeled fill ~6, 12%. Healthy.
- Post-CAPI but still high (>20%): implementation gaps; audit
event_iddeduplication and event coverage.