First-party domain routing
Everything runs from your domain rather than google-analytics.com or pixel.facebook.com, so there is nothing on a list to match.
Conversion Recovery
Recover the conversions ad blockers and ITP hide
Your consented users buy. But ad blockers stop pixels from firing and Safari ITP kills cookies before the attribution window closes. TrustData captures those conversions server-side and sends them back to your ad platforms.
Server-side capture
Server-side capture catches what pixels miss
TrustData routes tracking through your own domain and captures purchase events server-side, from Shopify webhooks or your CRM, so ad blocker status is irrelevant.
Server-side purchase events
Confirmations are captured from Shopify or your backend, the case a client-side pixel loses in silence.
Persistent first-party identifiers
With consent a first-party cookie is set on your domain, outside the 24-hour cap that truncates journeys on Safari.
Signal forwarding
Recovered conversions flow back to your ad platforms
Once captured, TrustData forwards enriched conversion events to Google, Meta, and TikTok via their server APIs, so their algorithms learn from complete data.
Google Enhanced Conversions
Hashed customer data travels with the conversion event, recovering matches a cookie alone cannot make.
Meta Conversions API (CAPI)
Conversion events go server to server from TrustData to Meta, so a blocked browser stops meaning a lost conversion.
TikTok Events API
Purchase and lead events forward server-side, past the pixel that ad blocking and tracking prevention reach first.
ROI impact
Better signals → better bidding → lower CPAs
More complete conversion data means platforms stop over-spending on non-converting audiences. The feedback loop works as intended.
Smarter automated bidding
The bidding models learn from your real conversion rate rather than a partial sample, so CPAs come down.
Higher match rates
Enhanced Conversions and CAPI typically lift match rates by 15 to 30%, in what the platform sees rather than what you report.
One consistent number
Own the conversion definition and stop arbitrating between dashboards. One deduplicated source of truth, instead of three platforms each disagreeing in its own favour.
FAQ
Direct answers.
Client-side pixels (Google Tag, Meta Pixel) run in the browser and can be blocked by ad blockers or expire early due to ITP. TrustData captures events server-side (from your Shopify order webhook or CRM) then forwards them to platforms via their server APIs (Enhanced Conversions, CAPI, Events API). These server-side signals can't be blocked.
No. Server-side forwarding to ad platforms only applies to users who have given marketing consent. Without consent, conversions are counted anonymously in TrustData for your own reporting, but not sent to ad platforms.
Typically 15–30% more conversions matched by ad platforms after enabling server-side forwarding. The lift is largest for sites with high Safari/iOS traffic or significant ad-blocker usage among their audience.
Yes. TrustData has a native Shopify integration. Purchase events are captured via webhook on the server side, so ad blocker status has no effect.
You can keep them running in parallel for redundancy. TrustData deduplicates server-side events against browser pixel events automatically, so you won't double-count conversions in your ad platforms.
14-day free trial
Stop optimizing on incomplete conversion data
14-day free trial. Connect your first ad account in 5 minutes.