FIORIANALYTICS

Signal quality · e-commerce

Three systems, three revenue numbers, one client asking which one is real.

Signal quality is the service that makes an e-commerce client's conversion data trustworthy: server-side tagging on infrastructure they own, Meta Conversions API events that actually deduplicate against the pixel, and a GA4 that can be reconciled with the store. Built for e-commerce agencies, under the agency's brand.

Get a free teardown Or book a 20-min partner call →

What does broken signal look like on a store?

  • Meta reports more purchases than the store did, and nobody can say which ones are duplicates
  • GA4 revenue and Shopify revenue disagree by a margin that changes every month
  • Purchases fire twice, once from the browser and once from the server, because the two were never tied together
  • A chunk of traffic lands as direct because the campaign data never survived the checkout hop

None of these are visible from inside a reporting dashboard, because the dashboard is downstream of the problem. They are visible in the event payloads, the order export, and the difference between the two.

What the build includes

  • Server-side tagging, with the container running on infrastructure the client owns
  • Meta Conversions API events matched to the pixel through event_id and event_name
  • A deduplication check done against real orders, not a screenshot of the Events Manager
  • GA4 purchase events reconciled against the store's own order export
  • Consent handling wired to the client's banner, so the tags respect the visitor's choice
  • Documentation and a recorded walkthrough, in your agency's branding

What it doesn't include

  • Running the media. That stays with you
  • Replacing the client's analytics stack with a tool I resell (there isn't one)
  • Promising a ROAS number. I fix the data. Running the media is still your job

Questions agencies ask

How does deduplication actually work?
Meta documents two methods. The recommended one matches the pixel's eventID to the Conversions API event_id, with event_name matching on both sides. Meta's documentation states that events are deduplicated when received within 48 hours of the first event carrying that event_id.
Why not just install the Shopify app and be done?
The apps send events. They don't tell you whether the events match, whether the same order is counted twice, or whether the number in GA4 can be reconciled with the store. That check is the work.
Does the client need their own cloud project?
For server-side tagging, yes. That's the point of it. The container runs somewhere the client owns, so the data path belongs to them and not to a vendor.
Will GA4 and Shopify ever match exactly?
No, and anyone who promises that is selling something. They can be brought close enough that the difference is explainable, which is what a client actually needs before they trust a number.

Platform documentation

Read on September 23, 2026. Platform behavior changes, so check the source before you quote it to a client.

Send me one store. I'll show you what its events are doing.

A free outside-in teardown, delivered unbranded so it can go to the client under your name.

Get a free teardown