Unified on-site and paid analytics

Measure site and spend against one conversion

Your site, your ad accounts and your store stop reporting three totals for the same week, because all three are measured against the same conversion.

Key takeaway

Your on-site behaviour and your ad spend are read against one deduplicated conversion, so the two halves of the funnel stop reporting different totals for the same week. The reconciliation spreadsheet exists because nothing else does this.
One conversion, both sides of the funnel

Ground truth

One order counts once, whoever claims it

Google reports 100 conversions, Meta reports 120, your store recorded 80. Everything on this page starts from the 80, because that is the number you can check against a bank statement, and the gap is the double count rather than a rounding error.

Your orders are the denominator

Start from the number your bank agrees with. Conversions come from Shopify or your CRM and platform claims are reconciled against them, which is where most brands find their real ROAS sits 30 to 50% below what the platforms show.

One definition, every surface

Stop defending a number that changes between tabs. The same conversion definition feeds the on-site view, the paid view and every attribution model, so a discrepancy is a finding rather than a formatting difference.

Read on revenue, not counts

Rank channels on what they actually bring in. Order value carries through, so volume at a low basket does not outrank fewer, larger orders.

TrustData deduplicated conversion list with order value and touchpoint sequence

On-site

What actually happened on your site

The behavioural half. Where visitors came from, what they did, and the sequence that ended in an order, all on first-party events collected from your own domain rather than sampled by a tag that half your traffic blocks.

Acquisition by channel

Compare organic, paid, direct and AI-referred traffic on equal terms. Sessions, conversions and revenue per channel are measured the same way instead of each source grading its own homework.

The conversion list, before any model

Read the raw journey before you argue about credit. Every order carries its timestamp, its value and the touchpoints that led to it, so the model is a choice you make rather than one you inherit.

Journeys and their shape

Find out whether multi-channel journeys are worth more on your data, not on a benchmark. You get the sequences that appear most often in converting paths, the typical touchpoint count and how long a journey runs.

TrustData acquisition view by channel with sessions and conversions

Paid

And what your ad accounts did about it

The spend half, on the same conversion. One all-platform view to compare channels, then per-platform depth when a channel is the thing you are actually working on, without leaving the number you trust behind.

Attribution

Six models, because one number answers one question

A single model is a single opinion about how credit should work. Running several on the same deduplicated conversions turns the disagreement between them into information, starting with the gap between last-click and data-driven attribution.

Data-driven attribution

Allocate budget from the model built for it. DDA distributes credit by each channel's marginal contribution across every combination of channels in your observed paths, using a cooperative game theory framework rather than a fixed rule.

Last-click, kept for one reason

Run last-click to see exactly what your platforms are reporting and why. Against DDA on the same conversions it is the clearest picture of platform bias you will get, and it takes one dropdown.

Four rule-based baselines

Pick the lens that fits the question. First-click for what opens the relationship, linear for a neutral split, time decay for short cycles, position-based at 40, 40 and 20 when both ends matter, all on the same window.

Assist and closer, separated

See which channels open the relationship and which close it. DDA splits each channel's credit between the two, and whether that credit was causal is a separate question that belongs to incrementality.

TrustData attribution model comparison across channels

What else the view carries

The settings and exports that stay one click away, so the story above does not have to carry them.

Windows and comparison

Attribution windows of 7, 14, 30 or 90 days, configurable per analysis, with all six models running on whichever window you pick. Compare periods without rebuilding the view.

Where the numbers come from

First-party events from your own domain, orders from Shopify or your CRM, and spend from the connected ad accounts. Every connector is included on every tier, because capping them would charge twice for one thing.

Reporting and export

A Monday summary of the week's moves, plus CSV export and a raw export to your own storage. Full history with no retention limit, so a year-old cohort is still queryable.

Against the tools you are probably running

The difference is whether the two halves of the funnel are measured against the same conversion.

On-site behaviour and paid performance in one view

TrustData

GA4

Partial

Other tools

Rarely

Conversions deduplicated against your own orders

TrustData

GA4

Other tools

Sometimes

Platform-reported and deduplicated shown side by side

TrustData

GA4

Other tools

Six attribution models on the same window

TrustData

GA4

Limited

Other tools

Usually 3 to 4

Drill to creative without losing the conversion definition

TrustData

GA4

Partial

Other tools

Sometimes

Raw events exportable to storage you own

TrustData

GA4

Via BigQuery

Other tools

Rarely

FAQ

Direct answers.

14-day free trial

See both halves of the funnel agree

14-day free trial. On-site behaviour, paid performance and six attribution models, all on one deduplicated conversion.