Questions we hear every week.

No. The work is GA4, GTM, and server-side, so the timezone matters more than the postcode. Most of our active clients sit in the Netherlands, but we've delivered for companies across the UK, Germany, Belgium, Spain, and the US. Anywhere comfortable in CET or GMT working hours is fine.

Usually one to two weeks from a signed proposal. Faster when there's a fire (broken conversion tracking, an audit deadline, a migration locked in), but those still need a 30-minute scoping call first. We don't take work we can't ship cleanly.

Yes. About a third of our work is for agencies, either delivered direct to their client or as a silent technical partner behind the agency brand. NDAs and white-label terms are standard. We'll match your client-facing language and stay invisible if that's what the engagement needs.

Audit and remediation usually lands between €4k and €8k fixed.

A full server-side GTM build with GA4 architecture and a proper consent layer for a multi-domain ecommerce site is €12k to €25k, depending on stack complexity and platform spread.

Smaller scoped pieces (specific tag fixes, conversion tracking repairs, GCM v2 implementation, CAPI setup) start at around €1.5k.

Every quote is fixed price for fixed scope. No padded hours, no surprise add-ons mid-engagement.

Fixed price for defined work. Retainers only after a project where we already know your stack and you've decided ongoing support makes sense. Padded retainers with vague scope are how agencies hide behind hours, and we'd rather not.

GTM container with at minimum Edit access, Publish if we're shipping fixes. GA4 property as Editor. Google Ads and any other ad platform tag manager you want covered as Standard access. Cloud project Editor if we're deploying to a server-side container you own.

We never ask for login credentials. Everything happens through Google account access invitations to a verified Voxxy email.

Yes. We have a standard mutual NDA ready to send, or we'll sign yours. Either works. If your legal team needs a few rounds, that's fine, we'd rather get the paper right than rush a call.

GA4 reports what fires. It can't tell you what should be firing but isn't, what's firing twice, what's tagged with the wrong event name, or what's getting blocked client-side before the request leaves the browser.

Around 70% of audits we run surface at least one of those, often all four. The dashboard looks healthy because it has no idea anything is missing. That's the issue.

It depends. If you run paid media, deal with iOS Safari traffic, care about consent, or have an ad blocker problem (and you do, it's around 40% of users in some sectors), the answer is usually yes.

If you're a low-volume content site with no advertising, probably not. We'll tell you straight in the audit. We don't sell server-side as a default.

No. It will recover a meaningful chunk of what client-side blocks, give you a single canonical event stream you can route to multiple destinations, and make consent enforcement cleaner.

"Perfect data" doesn't exist in tracking. Anyone selling it should be politely declined.

We start from what you have. Rebuilding from scratch is rarely the right answer. Most setups need restructuring, naming consistency, deduplication, and a cleaner data layer, not a clean wipe.

If a full rebuild is genuinely required, the audit will say so with reasoning, including what gets preserved and what gets retired.

Yes. All three regularly, plus Pinterest, Snap, LinkedIn Insight Tag, and Microsoft Advertising. Server-side endpoints are the default delivery whenever the platform supports them, with client-side fallback only where it doesn't.

Event deduplication, parameter mapping, and consent gating are part of the standard delivery, not bolt-ons.

Consent is part of every engagement, not an afterthought. We implement Google Consent Mode v2 properly (advertised behaviour, not the version that quietly waves traffic through), wire enforcement at the GTM level, and verify against your CMP of choice.

If you don't have a CMP yet, our own product CoMo Banner handles it as a GTM custom template. If you already use Cookiebot, OneTrust, Usercentrics, or a custom solution, we work with what you have.

A 30-minute look at your live container, GA4 setup, conversion events, and consent layer. We flag the top issues we see, give a rough estimate of remediation effort, and tell you whether the gaps are worth fixing now or later.

It's not a full deliverable audit. The full one is a paid engagement with documented findings, prioritised remediation plan, and implementation guidance. The free version is enough to tell whether your tracking is broken.

It's free. The catch is that we use it as a qualifier on both sides.

About a third of audits turn into engagements. A third turn into "you don't actively need us, here's what to fix yourself." The remaining third we politely don't pursue further. You leave with information either way.

Usually three to five working days. We don't sit on requests for a week. If you're on a tighter deadline, say so in the form and we'll see what we can shift.

No. CoMo Banner is delivered by email after signup or purchase as an importable JSON template. The Community Gallery has its own approval cycle and content rules, and we chose to ship and iterate independently.

The import takes about 30 seconds in your GTM workspace, no developer required.

CoMo runs entirely as a GTM custom template. No external SDK loading on every page, no separate vendor cookie tied to a CMP product, no monthly subscription per domain.

It's lighter (around 15kb), supports Google Consent Mode v2 out of the box, hits WCAG 2.2 AA, and ships with 143+ region presets covering GDPR, CCPA, LGPD, and the rest. The full performance comparison sits on the CoMo Banner page if you want the numbers.