Attribution Systems Agency · Dubai · UAE · KSA
Attribution that shows what channels actually earn, not what they claim.
Every platform attributes the conversions it can see — and claims maximum credit. When Meta, Google, and TikTok attribution windows overlap, the same purchase is counted three times. Summing platform reports produces 160–240% of actual conversion volume. A business attribution system builds an independent model on your first-party data — resolving the cross-channel credit overlap and connecting media spend to the actual revenue the business records, not the attributed credit each platform reports for itself.
1.4×
average platform attribution overstatement vs. business-attributed ROAS across active engagements
28%
average budget reallocation following first attribution-accurate cross-channel ROAS report
3.8×
improvement in budget decision confidence when operators move from platform reporting to unified attribution
02 / Why Attribution Breaks
Every platform grades its own homework. The results add up to more than 100%.
Single-channel attribution is straightforward. Two-channel attribution is manageable. Three or more channels with overlapping attribution windows, cross-device journeys, and platforms measuring their own performance produce a measurement environment where the same conversion is claimed multiple times simultaneously — and the operator has no independent view of what actually happened.
Platform self-attribution inflation
Every platform attributes every conversion it can associate with an ad impression or click — using its own attribution window and its own identity graph. Meta reports a conversion for every user who saw a Meta ad within 7 days and then purchased anywhere. Google claims the conversion for every user who clicked a Google ad. TikTok reports the conversion for every user who viewed a TikTok ad in the last 7 days. When attribution windows overlap — as they do for every customer who encountered multiple channels — the same purchase is claimed by two or three platforms simultaneously.
Budget consequence
Summing platform-reported conversions typically produces 160–240% of actual conversion volume. ROAS appears higher than it is. Channels that appear efficient are often claiming credit they do not own. Budget decisions made on platform self-reports over-invest in high-impression channels and under-invest in the channels that are actually driving incremental revenue.
Cross-device and cross-session attribution gaps
A customer engages with a TikTok ad on mobile, searches the brand name on desktop 4 days later, clicks a Google Shopping result, and converts via a direct URL from a bookmarked page. Last-click attribution assigns the conversion to Direct. Google's model assigns it to Shopping. TikTok's model assigns it to the original TikTok click. Without User ID stitching and a server-side event stream connecting the mobile and desktop sessions, no attribution model can see the full journey — and the channels that drove top-of-funnel intent are systematically undercredited.
Budget consequence
Mobile acquisition channels — TikTok, Instagram, Snapchat — appear to underperform because their conversions complete on desktop in sessions that carry no visible link back to the original mobile ad interaction. Budget shifts away from the channels driving upper-funnel intent and toward channels that appear at the end of a journey they did not initiate.
Revenue-proxy attribution — optimising for the wrong outcome
The attribution model counts a proxy metric — form submissions, trial starts, raw purchases — rather than the revenue outcome those events produce. A form submission from a Google Ads click that generates a qualified deal is assigned the same credit as a form submission from a Meta click that generates a junk lead that never qualifies. The attribution model cannot distinguish between them because it has no connection to the CRM data that holds the qualification outcome and the closed revenue figure.
Budget consequence
Optimization flows toward high-volume, low-quality conversion sources that produce cheap proxy events. LTV deteriorates as the channel mix optimises for quantity over quality. The problem is invisible in the attribution dashboard until CRM data is connected — at which point the channel ranking often reverses completely.
The attribution gap
What over-attribution costs an operator in a multi-channel programme
Attribution overstatement is not a reporting inconvenience — it is a budget allocation problem. When platform-reported ROAS overstates actual performance by 1.4×, the operator is making budget decisions on a signal that is 40% more optimistic than reality. Channels that appear efficient are often claiming credit from channels that appear inefficient — and budget shifts accordingly, away from the channels that are actually driving incremental revenue.
1.4–1.8×
typical aggregate attribution overstatement across multi-channel paid media programmes — platforms collectively claiming 40–80% more credit than an independent model assigns
63%
of operators running 3+ paid channels report a discrepancy between their platform-reported blended ROAS and their finance team's revenue-to-spend calculation
90 days
typical timeframe to complete a full attribution system build and produce the first actionable cross-channel ROAS comparison report
03 / The Attribution Systems Framework
Architecture, mapping, model, revenue integration. In that order.
An attribution model configured without a specification is a reporting tool, not a decision system. The specification defines the rules — which events count, what parameter quality is required, how windows are assigned by channel, and how platform self-attribution is separated from business attribution. Every downstream configuration follows the specification. The model is only as trustworthy as the rules it was built on.
Why revenue integration changes the channel ranking
Most attribution systems stop at the conversion event — a form submission, a trial start, a raw purchase. The CRM holds the outcome data: which leads qualified, which trials converted to paid, which purchases were returned. When CRM revenue events are connected to the attribution model via Measurement Protocol, the channel ranking frequently inverts. The channel that was driving the cheapest form submissions is often not the channel driving the most closed revenue. Without the CRM connection, the attribution model is optimising a proxy — and budget follows the proxy, not the outcome.
- 01
Attribution Architecture
Define the attribution model before any reporting is configured. The specification covers: which events count as conversions and at what parameter quality threshold, how attribution windows are defined by channel type and conversion intent, how platform self-attribution is isolated from business attribution, and how revenue data from the CRM will connect to channel-level acquisition data. The specification is the contract — every downstream configuration follows it.
Output: Attribution specification document — conversion event taxonomy, attribution window definitions by channel, identity resolution requirements, platform vs. business attribution separation methodology - 02
Source and Event Mapping
Map every acquisition source to a standardised UTM taxonomy enforced across all paid channels. Every campaign, ad group, and creative must carry consistent UTM parameters that survive landing page redirects, cross-domain sessions, and mobile handoffs. Server-side event capture preserves UTM attribution through the full conversion journey. GA4 custom channel grouping reflects the actual channel structure — not GA4's defaults, which systematically misclassify paid traffic when UTM parameters are absent.
Output: UTM taxonomy specification, GA4 custom channel grouping configuration, UTM preservation audit across all landing page redirect chains, server-side UTM capture confirmation - 03
Attribution Model Configuration
Build the business attribution model in GA4: data-driven attribution for channels with sufficient conversion volume, linear attribution for upper-funnel channels with long consideration cycles. The model is configured against the server-side event stream — so attribution inputs are complete, not browser-pixel-partial. A comparison view is built alongside platform self-reported ROAS so the discrepancy is visible and quantified from the first report.
Output: GA4 attribution model configuration, initial cross-channel ROAS discrepancy report (platform-reported vs. business-attributed), data-driven vs. last-click delta by channel - 04
Revenue Integration and Monitoring
Connect the attribution model to actual revenue. CRM webhook sends qualification and revenue events to GA4 via Measurement Protocol. Offline conversion upload closes the attribution loop for Google Ads. The model receives revenue-attributed conversion events — not proxy events like form submissions or trial starts. Ongoing monitoring tracks UTM coverage decay, channel grouping anomalies, platform API changes, and attribution model drift over time.
Output: Revenue-attributed ROAS by channel, CRM integration confirmation, offline conversion upload verification, attribution monitoring dashboard with anomaly alerts
Want to see how this applies to your funnel?
A senior strategist reviews your specific setup — complimentary, no pitch deck.
04 / Source & Event Mapping
The attribution model is only as good as the data it receives.
A data-driven attribution model built on incomplete UTM coverage, misclassified GA4 channels, and proxy conversion events produces an output that is structurally inaccurate — regardless of how sophisticated the model is. Source and event mapping is the foundation layer: ensuring every paid session carries a consistent UTM parameter, every channel is correctly classified in GA4, every conversion event is mapped to a revenue outcome, and every cross-device journey is stitched into a single attributable path.
UTM taxonomy
Standardised campaign parameters across all paid channels
UTM parameters are the foundation of campaign-level attribution. Without a standardised UTM taxonomy enforced across every paid channel, GA4 sessions fall back to `(direct)/(none)` — erasing channel attribution for every paid conversion where the URL parameter was missing, redirected away, or overwritten by a subsequent click. A UTM taxonomy specification defines source, medium, campaign, content, and term for every active channel — with naming conventions that survive redirects and produce clean GA4 channel grouping.
- source: meta / google / tiktok / snapchat (platform-standardised)
- medium: paid-social / paid-cpc / paid-video (intent-standardised)
- campaign: [service]-[objective]-[YYYYMM] naming convention
- content: creative ID or ad set label for creative-level attribution
- Redirect chain preservation: UTM must survive all landing page redirects
GA4 channel grouping
Override GA4 defaults with your actual channel architecture
GA4's default channel groupings misclassify paid traffic when UTM parameters are absent or inconsistently structured. Paid social traffic without utm_medium=paid-social falls into Organic Social or Unassigned. Google Ads traffic without gclid auto-tagging falls into Organic Search. Custom channel grouping rules correct these misclassifications and add channel definitions that GA4 does not recognise by default — TikTok, Snapchat, programmatic, affiliate — so the channel breakdown reflects your actual investment structure.
- Custom rules overriding all GA4 default channel definitions
- TikTok, Snapchat, and programmatic channel additions
- Paid vs. organic split verification against platform-reported sessions
- Campaign-level breakdowns within each custom channel group
Conversion event mapping
Define which events count, what parameters they carry, and how they connect to revenue
Attribution models produce outputs that reflect the events they receive as inputs. A model that counts all form submissions as equivalent conversion events attributes equally to traffic that drives high-quality leads and traffic that drives junk leads. Conversion event mapping defines the hierarchy: primary revenue-attributed events, secondary qualified-intent events, and micro-conversion engagement events — each with distinct attribution window rules and credit weights that reflect their distance from actual revenue.
- Primary: revenue-attributed events (purchase, paid subscription, closed deal)
- Secondary: qualified-intent events (qualified lead, consultation booked)
- Micro: engagement events (checkout initiation, deep scroll, CTA click)
- Attribution window by event type: 7-day purchase, 28-day lead, 90-day enterprise
Identity resolution
Connect cross-device and cross-session journeys into a single attribution path
Without identity resolution, the attribution model sees three separate sessions for a customer who browsed on mobile, researched on desktop, and converted from a direct link — and assigns the conversion to the last visible touchpoint. User ID implementation in GA4, combined with server-side session stitching and hashed PII matching, connects the cross-device journey. Credit flows to the touchpoints that actually influenced the decision — not just the one that was visible at the moment of conversion.
- GA4 User ID implementation across all authenticated sessions
- Server-side User ID relay via GA4 Measurement Protocol
- Hashed email matching for cross-device identity resolution
- Cross-device journey paths in GA4 attribution reports
Conversion event implementation
The conversion event taxonomy defined in the attribution specification must be implemented correctly in GA4 and on every platform before attribution model configuration begins.
05 / Platform vs. Business Attribution
Each platform attributes by its own rules. The business needs one independent model.
Platform attribution is not dishonest — it is self-interested. Every platform's attribution window, identity graph, and credit rules are designed to maximise the conversions it can claim. Meta's 7-day view-through captures conversions from users who saw an ad and purchased anywhere within a week. Snapchat's 28-day view-through does the same for a month. An independent business attribution model applies consistent rules across all channels — separating what each platform actually drove from what it claims to have driven.
The overstatement problem
What platform attribution collectively claims versus what the business earned
The overstatement problem compounds as channels are added. A single-channel programme has no cross-channel overlap problem. A two-channel programme has modest overlap. A three-channel programme with overlapping view-through windows and cross-device journeys produces attribution totals that may be double the actual conversion volume. The business attribution model resolves the overlap using consistent credit rules and a first-party event stream rather than each platform's self-interested measurement.
1.4–1.8×
aggregate attribution overstatement across 3+ channel programmes — the platform total versus the business total for the same conversion period
160–240%
of actual conversion volume when summing platform-reported conversions in a typical multi-channel programme — one purchase, three platform claims
3.2×
business-attributed ROAS versus 4.8× platform-reported — the gap that determines whether a channel receives more or less budget next quarter
Paid media performance — independent view
Attribution-accurate ROAS by channel determines where the next increment of budget goes. Decisions made on platform self-reports consistently overinvest in high-impression channels and underinvest in channels that drive incremental revenue.
Meta Ads
High biasDefault window: 7-day click, 1-day view (default)
Self-report: Claims any conversion from a user who saw a Meta ad within the attribution window — regardless of other channel interactions in the same window
Correction: GA4 data-driven model reassigns view-through credit and cross-channel overlaps; typically reduces Meta-attributed conversions by 20–35%
Google Ads
Medium biasDefault window: 30-day click, 1-day view (Search); 30-day click (Shopping)
Self-report: Search campaigns overclaim brand-keyword conversions that would have occurred regardless of the ad — branded search ROAS is structurally inflated
Correction: Incrementality testing separates brand-keyword attribution from non-brand; typically reduces Google's attributed share for brand-heavy programmes
TikTok Ads
Medium biasDefault window: 7-day click, 1-day view (default); up to 28-day view available
Self-report: View-through attribution window captures conversions from users who only watched a TikTok ad; particularly aggressive at 7-day view with high-reach campaigns
Correction: GA4 model shifts TikTok's share upward for top-of-funnel contribution — TikTok is frequently undervalued in last-click models despite driving significant consideration
Snapchat Ads
High biasDefault window: Up to 28-day view, 1-day click (GCC default)
Self-report: The most aggressive view-through window of major GCC platforms; 28-day view-through attribution inflates credited conversions significantly in GCC markets where Snapchat reach is high
Correction: Business attribution model reduces Snapchat view-through credit to 7-day maximum and weights click interactions more heavily; typically reduces Snapchat-attributed share by 30–50%
06 / Signal Quality & Attribution
The attribution model is built on its inputs. Incomplete inputs produce inaccurate attribution.
Attribution accuracy is constrained by signal completeness. A GA4 data-driven model built on browser-pixel events is working with 60–75% of the actual conversion stream. The 25–40% that is missing — due to iOS ITP, ad blockers, and cross-device gaps — is not randomly distributed. It systematically removes conversions from specific channels, specific device types, and specific audience segments, producing an attribution output that is structurally biased against the channels that drive those conversions.
Attribution signal dependency
How signal loss translates to attribution error
The signal loss from browser-only tracking is not a uniform reduction in conversion volume — it is a selective removal that targets specific channels, devices, and audience segments. The attribution model then distributes credit across the conversions that remain visible, producing a channel ranking that reflects the measurement gap as much as actual channel performance.
40%
of conversion events are lost to iOS ITP, ad blockers, and cross-device gaps in browser-only tracking — making 40% of the attribution model's inputs incorrect
3.2×
higher attribution accuracy when business attribution is built on server-side event stream versus browser-pixel-only GA4 data
18%
of paid media budget is on average reallocated when operators switch from browser-pixel attribution to server-side-accurate attribution
Attribution accuracy starts with signal integrity
Server-side tracking is the prerequisite for accurate attribution — recovering the events that browser restrictions remove and ensuring the attribution model operates on a complete input stream.
Missing events → wrong channel credit
When browser pixel events are lost to iOS ITP or ad blockers, the conversion event disappears from the attribution model's input stream. The model cannot assign credit to the channel that drove the conversion — so either no channel receives credit (the session falls to Direct/None) or the wrong channel receives it (the last visible touchpoint in a partial journey). Mobile acquisition channels are disproportionately affected: they drive top-of-funnel interactions that convert in later desktop sessions that carry no visible connection back to the mobile ad.
Fix
Server-side event stream with User ID — preserves the mobile session connection through the cross-device journey
Missing UTM parameters → attribution erased
Every paid session that arrives without a utm_source parameter falls into (direct)/(none) in GA4 — regardless of what channel drove it. UTM parameters can be missing because a redirect stripped them, because the ad platform was configured without auto-tagging, or because a link shortener discarded the query string. In GA4's default channel grouping, these sessions are classified as Direct — not as the paid channel that actually sent them. The attribution model assigns credit to Direct, and the paid channel's performance is understated by exactly the proportion of its traffic that arrived without UTM.
Fix
UTM taxonomy enforcement, redirect chain audit, and GA4 custom channel grouping that captures UTM-missing paid sessions by IP or referrer pattern
Proxy metrics → misaligned channel ranking
Attribution models that count form submissions as the conversion event attribute equally to channels that drive high-value leads and channels that drive low-value leads — because the model has no way to distinguish between them. The CRM holds the qualification outcome and the revenue figure, but without a CRM webhook connecting that data back to GA4, the attribution model operates on a proxy that may have no correlation with revenue. The channel ranking by cost-per-form-submission frequently inverts when CRM revenue data is connected.
Fix
CRM integration via GA4 Measurement Protocol — qualified lead and revenue events attributed back to original acquisition channel
07 / Decision Intelligence
Attribution data is only valuable if it changes the decision.
An attribution model that produces a report no one acts on is infrastructure investment with no return. The dashboarding layer is built around the three decisions operators make with attribution data: which channels to scale (cross-channel ROAS), which channels are driving the right customers (funnel attribution), and what the actual revenue return is on each channel's spend (revenue attribution drill-down). Each view is designed to answer a specific decision question — not to display data.
Cross-channel ROAS comparison
Platform-reported vs. business-attributed side by side
The primary operator view: platform-reported ROAS for each active channel versus business-attributed ROAS from the independent attribution model. The delta is expressed as both a ratio (1.4× overstatement) and an absolute ROAS figure (platform says 4.8×, business says 3.2×). Updated daily as conversion events arrive and are attributed. Budget decisions are made against the business-attributed number — not the platform self-report.
Funnel attribution view
Which channel drives which stage of the customer journey
Beyond total conversion attribution, operators need to know which channels are driving awareness and consideration versus which are capturing existing intent. A channel that appears to underperform on last-click attribution may be driving 40% of the top-of-funnel engagement that eventually converts through another channel. The funnel attribution view shows touchpoint contribution by journey stage — entry, consideration, and conversion — using the data-driven attribution model's credit weights.
Revenue attribution drill-down
Closed revenue attributed to source, campaign, and creative level
The CRM-connected attribution layer attributes closed revenue — not proxy conversion events — back to the source, campaign, and creative that initiated the customer journey. This view inverts the channel ranking that proxy-metric attribution produces: the channels that generate the most form submissions are frequently not the channels that generate the most qualified revenue. The revenue drill-down is the data that drives budget reallocation decisions with confidence.
Analytics dashboards
The attribution model outputs are surfaced in operator dashboards built for daily budget decisions — not data exploration.
Conversion optimization ROI
Attribution-accurate channel data is required to calculate the revenue return on CRO investment — knowing which channel drove the conversion being optimized.
08 / GCC Attribution
Attribution systems in GCC markets are engineered for Snapchat, cross-device journeys, and PDPL compliance — not adapted from Western-market models.
Three factors make GCC attribution structurally different from a Western-market equivalent: Snapchat's material role in the media mix produces a 28-day view-through window that inflates aggregate overstatement beyond what Meta and Google alone would produce; mobile-first browsing with cross-device conversion creates a systematic undervaluation of social channels; and KSA's PDPL requirements constrain how identity resolution can be implemented. An attribution system built for GCC markets addresses all three.
UAE & KSA platform
Snapchat attribution in GCC media mix
Snapchat occupies a materially larger share of the GCC paid media mix than in Western markets — particularly for fashion, beauty, entertainment, and consumer goods targeting 18–34 UAE and KSA audiences. Snapchat's default 28-day view-through attribution window is the most aggressive of any major GCC platform, meaning GCC campaigns with significant Snapchat investment have structurally higher aggregate attribution overstatement than equivalent Western campaigns without Snapchat. Business attribution must explicitly model Snapchat view-through credit at a corrected window.
- Snapchat view-through window corrected from 28-day to 7-day in business model
- Incremental contribution testing for Snapchat reach campaigns
- Snapchat CAPI integration required for server-side attribution accuracy
- GCC Snapchat conversion volume sufficient for data-driven attribution in high-spend programmes
Mobile-first, desktop-convert pattern
Cross-device attribution in GCC markets
GCC audiences over-index on mobile browsing but maintain high desktop conversion rates for considered purchases — financial products, real estate, B2B services, and premium ecommerce. The cross-device gap in attribution (mobile ad interaction → desktop conversion) is proportionally larger in GCC markets than in markets with more uniform device behavior. Without User ID stitching and server-side session continuity, mobile-first GCC channels (TikTok, Snapchat, Instagram) are systematically undervalued in attribution models.
- User ID stitching required for mobile-to-desktop attribution continuity
- Server-side event stream preserves cross-device session attribution
- Mobile vs. desktop conversion split by channel — GCC benchmarks differ from global
- Attribution window extension for cross-device journeys in high-consideration categories
Seasonal measurement
Ramadan attribution window adjustment
Ramadan produces a structural shift in the GCC consumer journey: browsing and research concentrate in the late evening and post-Iftar hours; consideration cycles shorten for gifting purchases and lengthen for personal investment decisions; conversion windows shift relative to campaign exposure. Attribution models calibrated on off-peak baseline data misclassify Ramadan-period conversions — over-attributing to the channels that were active at conversion moment and under-attributing to the channels that drove the pre-Ramadan research phase.
- Attribution window extension during Ramadan consideration phases
- Seasonal baseline separation for attribution model calibration
- Post-Iftar session attribution weighting adjustment
- Year-on-year Ramadan attribution comparison as performance benchmark
KSA compliance
PDPL-compliant identity resolution
Saudi Arabia's Personal Data Protection Law (PDPL) constrains how PII can be used for cross-device identity resolution in attribution systems. Hashing protocols are required before PII is used for identity matching; consent must be captured and documented before any cross-device session stitching occurs; data residency requirements affect where attribution event logs can be stored. PDPL-aware attribution uses consent-gated User ID implementation and SHA-256 hashing for all PII used in identity resolution.
- Consent-gated User ID — assigned only with valid PDPL consent
- SHA-256 hashing for all PII used in cross-device identity matching
- PDPL-compliant event log retention and data residency configuration
- Consent signal passed as GA4 event parameter for attribution segmentation
09 / Systems We Build
Ecommerce, SaaS, lead generation, and multi-channel. One attribution framework.
The attribution architecture is consistent across business models — GA4 data-driven model, UTM taxonomy, custom channel grouping, server-side event stream. The conversion event taxonomy, revenue integration method, and channel priority differ by model. An ecommerce system attributes purchase revenue. A SaaS system attributes LTV-weighted subscription revenue. A lead generation system attributes qualified lead cost. Each is calibrated to the specific revenue metric the business controls.
Ecommerce
Ecommerce attribution system
Objective: Purchase revenue attributed to source, campaign, and creative
Server-side purchase events with full UTM preservation attributed across Meta, Google, TikTok, and Snapchat via a unified GA4 data-driven model. Platform-reported ROAS compared against business-attributed ROAS in a daily Looker Studio dashboard. Creative-level attribution enables performance comparison across ad formats and platforms — connecting the creative investment to the purchase revenue it drives.
Primary metric: business-attributed ROAS by channel and creative
SaaS
SaaS attribution system
Objective: Trial-to-paid and LTV attributed to acquisition channel
Attribution model connected to CRM via Measurement Protocol — so trial start, activation, upgrade, and renewal events are all attributed to the original acquisition channel. LTV-weighted channel attribution reveals which channels drive durable subscribers versus trial-churners. The model makes channel ranking by LTV visible — which frequently inverts the channel ranking by cost-per-trial.
Primary metric: LTV-attributed ROAS by channel (vs. trial-start CPL)
Lead Generation
Lead generation attribution system
Objective: Qualified lead and closed revenue attributed to paid source
CRM-connected attribution that separates cost-per-form-submission from cost-per-qualified-lead and cost-per-closed-deal. GCLID offline conversion upload closes the loop for Google Ads. CRM webhook sends qualification events to GA4 with original UTM parameters preserved — so the attribution model assigns channel credit to the qualified revenue outcome, not the proxy form submission event that may not correlate with it.
Primary metric: cost per qualified lead and cost per closed deal by channel
Multi-Channel
Multi-channel attribution system
Objective: Unified attribution view across 4+ platforms — resolving cross-channel credit overlap
A single business attribution model reconciling platform self-reports from Meta, Google, TikTok, Snapchat, and affiliate channels against an independent GA4 data-driven model. Cross-channel deduplication prevents the same conversion from being credited to multiple platforms. The daily dashboard surfaces the aggregate overstatement ratio — the gap between what platforms collectively claim and what the business actually earned — as the primary budget allocation signal.
Primary metric: aggregate attribution overstatement ratio and business-attributed blended ROAS
10 / Results
One standard: did the independent attribution model change the channel ranking — and did budget follow the evidence?
Measured against cross-channel ROAS accuracy improvement and budget reallocation outcomes — not platform-reported conversion counts. Three attribution system engagements — UAE ecommerce, KSA lead generation, global SaaS — each judged on whether the independent attribution model produced a channel ranking materially different from platform self-reporting, and whether that difference justified a reallocation decision. Budget reallocations were operator decisions made from attribution-accurate data — not recommendations imposed by the engagement.
- Fashion EcommerceUAE+41%
blended ROAS improvement after attribution-accurate budget reallocation
A UAE fashion ecommerce operator running Meta, Google, and TikTok with a platform-reported blended ROAS of 4.2×. Attribution audit revealed Meta was claiming 38% of conversions that GA4 data-driven attribution assigned to Google Search. A 28% budget reallocation from Meta to Google Search improved blended ROAS to 5.9× over 90 days — without any changes to creative, bidding strategy, or audience targeting.
of budget reallocated from over-attributed to correctly attributed channels28%Read the case study - B2B ServicesKSA-52%
cost per qualified lead after switching from proxy to revenue attribution
A KSA B2B services operator optimising against raw form submission events. Connecting CRM qualification data to channel attribution revealed Google Ads drove 3× more qualified leads per spend than Meta — despite Meta showing a lower cost per form submission. Shifting optimisation to CRM-attributed CPL reduced cost per qualified lead by 52% and tripled lead quality from the remaining Meta spend.
lead quality improvement from attribution-aligned channel spend3.1×Read the case study - B2B SaaSUAE+67%
LTV-to-CAC ratio improvement after attribution-accurate channel mix
A UAE SaaS operator attributing against trial-start events. Attribution system connected subscription revenue to channel acquisition data — LTV-weighted ROAS by channel. Meta was driving twice the trial volume of TikTok but 0.6× the LTV per acquired customer. Shifting to LTV-positive channel mix improved LTV-to-CAC ratio by 67% over 12 months and revealed two previously dismissed channels as top performers by lifetime value.
channels confirmed LTV-positive (was 2 pre-attribution audit)4Read the case study
Results are reconstructed from server-side tracking and verified attribution. Figures are representative of typical engagements, not guarantees.
11 / Questions
What operators ask about attribution systems before engaging
Questions from ecommerce operators, SaaS businesses, and lead generation brands evaluating an attribution systems engagement.
Platform attribution is what each ad platform reports as its contribution to your conversions — calculated using its own attribution window, its own identity graph, and its own conversion credit rules. Business attribution is an independent measurement of channel contribution, built on your first-party data (GA4 events, CRM revenue, server-side signals) and a model that does not give each platform the opportunity to grade its own homework. The gap between the two is typically 1.3–1.8× in favour of platform attribution — meaning platforms collectively claim 30–80% more credit than an independent measurement assigns them.
The overstatement varies by platform and attribution window, but a reliable benchmark for multi-channel paid media programmes is 1.3–1.8× aggregate overstatement. This occurs because attribution windows overlap: a customer who saw a Meta ad, clicked a TikTok ad, and converted via a Google Shopping click is counted as a conversion by all three platforms simultaneously. The platform with the last click claims full credit; the others claim view-through credit. The business makes one purchase. Three platforms report one conversion each. An independent attribution model counts it once.
Attribution accuracy depends entirely on signal completeness. A GA4-based attribution model built on browser-pixel events is working with 60–75% of actual conversion data — because iOS ITP, ad blockers, and cross-device gaps are removing events from the stream. The model assigns credit based on the touchpoints it can see, not the full journey. Missing events consistently skew attribution away from mobile acquisition channels (TikTok, Instagram, Snapchat) that drive top-of-funnel intent on mobile and convert on desktop in a later session. Server-side tracking is not a prerequisite for attribution — but it is the prerequisite for accurate attribution.
A standard attribution system — UTM taxonomy audit and specification, GA4 custom channel grouping, data-driven attribution model configuration, CRM revenue integration, and initial cross-channel ROAS comparison report — takes 4–6 weeks from specification to first report. The timeline extends when UTM parameters are inconsistent across channels (requiring remediation before model configuration) or when CRM integration requires custom webhook development. The first actionable attribution report — showing platform-reported ROAS versus business-attributed ROAS by channel — is typically available in week 5.
The answer depends on the channel mix, conversion volume, and sales cycle length. Data-driven attribution (Google's machine learning model) is the correct default for channels with over 700 conversions per month — it has enough data to learn which touchpoints actually contribute to conversion. Linear attribution is more appropriate for upper-funnel channels with long consideration cycles, where each touchpoint plays a role across weeks or months. Last-click attribution is appropriate only for direct-response search (brand keywords, high-intent non-brand) where the intent at the click moment is unambiguous and the conversion is immediate. Multi-channel programmes typically use a hybrid: data-driven for high-volume bottom-funnel events, linear for upper-funnel brand and social channels.
Attribution is only valuable if it changes decisions. The attribution system is designed around the decisions the operator needs to make: which channels to scale, which to reduce, which creative is driving LTV-positive acquisition, and which audience segments are under- or over-invested. The cross-channel ROAS report puts platform-reported ROAS and business-attributed ROAS side by side, so the delta is visible and quantified. Budget decisions are made against the business-attributed number — not the platform self-report. Operators who switch to attribution-informed budget allocation typically reallocate 15–30% of spend in the first quarter.
B2B attribution requires offline conversion upload and CRM integration. The paid media click happens in week 1. The form submission happens in week 2. The lead qualifies in week 4. The deal closes in week 12. Without CRM integration, the attribution model counts the form submission as the conversion — which is a proxy metric that may not correlate with revenue. CRM webhook integration sends the qualification event and the closed-revenue event to GA4 via Measurement Protocol, with the original session's UTM parameters preserved. The attribution model then assigns channel credit to the closed revenue — not the form submission. This typically reverses the channel ranking for B2B operators.
Yes — three material differences. First, Snapchat plays a significant role in UAE and KSA paid media mix; Snapchat's attribution window (up to 28-day view-through) is one of the most aggressive of any major platform, meaning GCC campaigns with significant Snapchat spend have higher aggregate overstatement than equivalent Western campaigns. Second, GCC markets have high mobile-first browsing and cross-device conversion patterns — which means mobile acquisition channels are systematically undervalued in attribution models built without User ID stitching. Third, Ramadan's dramatic shift in conversion window length requires attribution window adjustment during the seasonal period.
Start with an attribution review
Know exactly what your paid media is actually earning — not what it claims.
An attribution review audits your current channel tagging, quantifies the gap between platform-reported and business-attributed ROAS, and identifies where proxy-metric optimisation is misallocating budget away from actual revenue. Attribution architecture brief delivered within five business days. Specific findings: where platform self-attribution windows are overstating channel contribution, where budget is following a proxy metric rather than closed revenue, and what to configure first. No pitch. No commitment beyond the audit.
- Senior attribution strategist on every engagement
- UAE · KSA · Global
- Attribution brief delivered within five business days