01
Do you need to change the site's code for this?
Usually not. We work mainly in GTM and on the server side.
If something on the site does need changing, we agree it separately first — usually a small, specific change.
02
What about cookie consent?
We only pass on the data the user has consented to.
Our job is to fix the case where consented events drop out of measurement due to a technical fault.
03
Whose accounts does the system live on?
All configurations stay on your accounts and your domain.
If the collaboration ends, the whole system stays with you — access, configuration and documentation.
04
How quickly do the numbers improve?
Setup and validation usually take 1–2 weeks. After that, ad algorithms need a little time to re-learn from the new, cleaner signal — usually a couple of weeks.
05
Why don't Meta and GA4 numbers match?
Because they measure different things: Meta counts conversions by its own attribution model and window, GA4 by another — and both lose a share of events to ad-blockers, iOS limits and consent choices. Some gap is normal; a large or growing gap usually means technical data loss. The only honest baseline is real orders in your store admin.
06
Why doesn't GA4 or Meta show all my purchases?
The usual causes: ad-blockers and iOS privacy limits block the browser-side pixel; checkout runs on an external domain and the session breaks; a consent setup drops permitted events along with denied ones; or tracking broke during a site update. Industry measurements put browser-only tracking losses at 20–40% of conversions. Quick check: compare a week of orders in your store admin against GA4 and Meta — a gap over ~10% usually means something is broken.
07
What is server-side tracking and when do you need it?
Server-side tracking sends conversion data from your own domain straight to Meta's and Google's servers instead of the user's browser — so the signal doesn't vanish behind ad-blockers or cookie limits. You need it when you spend on ads and the numbers don't add up: Meta and GA4 disagree, ROAS is computed on the wrong value, or purchases don't show at all. The result has to be measurable: one store's Meta Purchase match quality 6.3 → 9.2, measured on real orders.