At a glance
Taboola-attributed conversion value, the revenue Taboola Backstage credits to clicks on your sponsored content. NOT order revenue from your commerce platform; the two often diverge sharply because Taboola is content-recommendation native, an upper-funnel channel where last-click revenue understates real contribution.
| What it counts | Revenue attributed to Taboola conversion events fired by the Taboola tracking pixel within the attribution window. Pulled from conversionsValue on the Backstage campaign-summary report. Includes only the orders the Taboola pixel saw fire; orders from users who blocked the pixel or arrived via a different last touch are not counted here. |
| Cost basis | Not applicable; this is the revenue side of the ROAS pair. The cost partner is Total Spend. |
| Currency | Account currency, single-currency per Taboola account. |
| Conversion attribution | Click-through, last-click within Taboola’s window. A user who clicks Taboola, then later clicks Google Ads, then buys, is typically credited to Google Ads (the last paid click), not Taboola. Taboola only claims it if the user did not subsequently click another paid channel. |
| Attribution window | 30-day click default (configurable 1, 30 days). Native is patient: 50, 70% of conversions arrive in the first 7 days, but a long tail extends to 30. |
| Bot / invalid traffic | Conversion events from IVT-filtered clicks are excluded by Taboola. Some IVT slips through; minor revenue inflation is possible but typically <2%. |
| Time window | T/7D/30D vsP (default 30D vs prior 30D). 1, 4 hour ingest lag from pixel fire to Backstage report. |
| Alert trigger | drop >20% vsP. The two most common causes: (a) the Taboola pixel broke (check Clicks vs Conversions first); (b) traffic shifted to publishers with weaker conversion rates. |
| Roles | owner, marketing, finance |
Calculation
Calculated automatically from your Taboola data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The same UK supplements brand as Total Spend. The 30-day window is 02 Apr 26 to 01 May 26.| Campaign | Spend (£) | Taboola-attributed revenue (£) | Conversions | AOV (£) |
|---|---|---|---|---|
| Article Distribution | 4,200 | 6,800 | 142 | 47.89 |
| Product Promotion | 6,800 | 22,400 | 412 | 54.37 |
| Premium Publisher (paused) | 2,400 | 3,200 | 68 | 47.06 |
| Lookalike Retargeting | 1,600 | 7,800 | 132 | 59.09 |
| Account total (this card) | £15,000 | £40,200 | 754 | £53.32 |
- Multi-touch overlap. A user clicks Taboola on Sat reading a wellness article, browses your site, leaves; clicks Google Ads on Mon for a branded search; buys Tue. Shopify sees the Google referrer (last click), Google Ads claims £55 revenue, Taboola also claims it within its 30-day window. Multi-counting is structural across all paid channels.
- Pixel block rate. Native readers tend to be heavy ad-blocker users; Taboola pixel fire rate is typically 75, 85% of GA4 sessions on this audience. Some legitimate Taboola-driven orders never get credited back.
- iOS/Safari ITP. Cross-domain conversion attribution loses 15, 30% on Safari due to ITP. Taboola compensates with deterministic ID-based matching where possible, but the gap is real.
- Lookalike Retargeting AOV (£59) is meaningfully higher than Article Distribution (£48). The retargeting audience is closer to purchase intent; they buy more per order. That justifies the higher CPC.
- The 30-day window had revenue down 12% vs the prior 30D (£45,800 → £40,200). Spend was up 21% over the same period. Spend up + revenue down = real efficiency erosion. The smartBid algorithm is finding more clicks but less qualified ones; check campaign settings, target CPA, and publisher allowlists.
- The pause on Premium Publisher Push removed £3,200 of revenue but freed £2,400 of spend; ROAS on that campaign was 1.33×, below the account average of 2.68×. The pause was the right call.
- Don’t read 40,200 as the contribution to Shopify. It is the Taboola-pixel-credited number; a chunk of these orders also fired in Google Ads or Meta. The “honest contribution” is closer to £18, 25k once you net out multi-touch overlap.
- Revenue up + spend up + ROAS flat = healthy scaling at constant efficiency.
- Revenue down + spend up + ROAS dropping = scaling beyond efficient frontier.
- Revenue down + spend flat + ROAS dropping = something changed in attribution, conversions, or audience quality. Check pixel health first.
- Revenue down sharply + spend flat + clicks unchanged = pixel is broken. Investigate before changing anything else.
Sibling cards merchants should reference together
| Card | Why pair it with Total Revenue |
|---|---|
| Taboola Total Spend | The denominator pair. Revenue ÷ Spend = ROAS; the two together tell you whether efficiency is rising or falling. |
| Taboola ROAS | The headline efficiency reading; uses this revenue figure as the numerator. |
| Taboola Clicks vs Conversions | The pixel-health canary. Clicks held while conversions cratered = the Taboola pixel broke; revenue will read low but the channel is fine. |
| Taboola Conversions Trend | The conversion-count side of revenue. Revenue down + conversions down = volume issue; revenue down + conversions held = AOV dropped, check basket composition. |
| Taboola Revenue by Campaign | Revenue concentration by campaign. One Lookalike Retargeting campaign often drives 40, 60% of revenue. |
| GA4 Revenue by Channel | Independent attribution check. GA4 Paid Native channel revenue vs Taboola Backstage revenue is the multi-touch reality check. |
| Shopify Total Revenue | The truth side. Real Taboola contribution is a subset of Shopify revenue, usually much smaller than Taboola Backstage claims. |
| Outbrain Total Revenue | Peer native channel. Compare conversion patterns across native networks; the audience profile differs. |
Reconciling against the vendor’s own dashboard
Where to look in Taboola Backstage: Backstage → Campaigns → Performance → “Conversions Value” column at the account level. The footer total should match this card to within sub-percent rounding once ingest catches up. Other Backstage views that look similar but are not the same number:- All Conversions Value: includes view-through and offline conversions where configured. This card uses click-attributed conversions only (the conservative read).
- Reports → Audiences → Revenue: revenue per audience segment. Sum should equal the account total, but per-audience attribution is approximate.
- Reports → Site Breakdown → Revenue: revenue per publisher site. Same total, different cut.
| Reason | Direction | Why |
|---|---|---|
| Time zone | Boundary days off | Taboola uses account time zone; this card uses UTC. For 30D windows the gap averages out; for “today” it can shift the daily figure noticeably. |
| Real-time ingest lag | Card runs slightly low for “today” | Conversion events take 1, 4 hours to ingest after pixel fire. Yesterday and earlier are stable. |
| Attribution window changes | Direction depends | If the merchant changed the attribution window mid-period, Taboola reflows the data retroactively to the current window; this card matches whatever is currently configured. |
| Pixel deduplication | Card == Backstage | Taboola dedupes within a click by event_id; both this card and Backstage UI reflect the deduplicated count. |
| View-through inclusion | This card excludes; some Backstage views include | ”All Conversions Value” includes view-through. This card uses primary (click-attributed) only. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
google_analytics.ga_revenue_by_channel | GA4 Paid Native (Taboola) revenue ≈ this card × 0.5, 0.75 | GA4 uses last-non-direct click; Taboola uses last-paid-click within its 30-day window. Taboola wins more credit because of the wider window. Taboola typically over-claims by 30, 80% versus GA4 for the same orders. |
shopify.total_revenue | Taboola revenue is a subset; UTM-tagged Taboola-source Shopify revenue is typically 25, 50% of Taboola’s claim. | Multi-touch overlap (other paid channels claim the same orders) plus pixel block rate. Use a weighted blend (40% Taboola-claim + 60% Shopify-UTM) for the CFO read. |
outbrain.out_total_revenue | Independent. Aggregate the two for “total native revenue”. | Different publisher networks; minimal overlap. Both can claim the same order if a user clicked both, but rare. |
google_ads.gads_revenue | No mathematical relationship; benchmark only. | Different funnel positions. Google Search captures intent; Taboola seeds intent. |
Known limitations / merchant FAQs
Why does Taboola say I’m at £40k revenue but Shopify says £18k? The classic native-attribution gap. Three layers stack:- Multi-touch overlap. Native is upper-funnel; users who click your Taboola sponsored content rarely buy on the same session. They come back days later via Google search, branded URL, or email and buy then. Taboola’s 30-day click attribution claims that order; Shopify’s UTM truth credits the last-touch channel (often Direct, Branded Search, or Email). Both numbers are mathematically right; they measure different things.
- Pixel block rate. Native readers tend to be heavy ad-blocker users. Taboola pixel fires on roughly 75, 85% of GA4-tracked sessions; the missing 15, 25% means some Taboola-driven orders never make it back to Backstage.
- iOS / Safari ITP. Cross-domain attribution loses 15, 30% of conversions on Safari. Taboola compensates with deterministic ID matching where it can, but the gap is structural.