The questions we hear every week.

Three fixed-scope packages. The price is fixed after a 30-minute scoping call and only moves with scope: more domains, more platforms, more systems to connect.

• Tracking Audit, from €1,500. One domain, delivered in 5 working days, credited against a Rebuild within 60 days.
• Server-Side Rebuild, from €4,000. Most projects land between €4,000 and €8,000. Live in 2 to 4 weeks.
• Full Data Stack, from €12,000, typically €12,000 to €25,000. Multi-domain, BigQuery, attribution, offline conversions, dashboards. Live in 4 to 8 weeks.

Hosting for the server container is paid to the provider, from about €22 per month, never marked up. Full breakdown on the services page.

Fixed price for defined work. Ongoing support is available after a project, as a monthly retainer priced per container that you can cancel any month. Padded retainers with vague scope are how agencies hide behind hours, and we'd rather not.

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

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

Yes, and it's a growing share of the work. Either delivered direct to your client or as a silent technical partner behind your brand: white-label audit reports and handover documentation, NDAs as standard, per-account pricing that drops with volume. We match your client-facing language and stay invisible if the engagement needs it.

GTM container with at least Edit access, Publish if we're shipping fixes. GA4 property as Editor. Google Ads and any other ad platform as Standard access. Editor on the Google Cloud project or TAGGRS workspace if we're deploying a server container you own.

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

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

Usually not. We work inside Google Tag Manager and your hosting provider. If a data layer change is needed on your site, we write the exact spec for your developer or make the change ourselves on WooCommerce and Shopify.

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 blocked client-side before the request leaves the browser. Most audits we run surface at least one of those, often all four. The dashboard looks healthy because it has no idea anything is missing.

It depends. If you run paid media, have iOS Safari traffic, care about consent, or lose events to ad blockers, the answer is usually yes. If you're a low-volume content site with no advertising, probably not. The audit says which, and we don't sell server-side as a default.

No. Every purchase is sent from the server with the same event ID as the browser pixel, so Meta and Google receive it once. Deduplication is part of every build, and we verify the rate against your order list before bidding switches over.

No. It recovers a meaningful share of what the browser blocks, gives you a single event stream you can route to every platform, and makes 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 containers need restructuring, naming consistency, deduplication and a cleaner data layer, not a wipe. If a full rebuild is genuinely required, the audit says so with reasoning, including what gets preserved and what gets retired.

GA4, Google Ads including Enhanced Conversions, Meta Conversions API and TikTok Events API on every relevant project, plus Pinterest, Snap, LinkedIn and Microsoft Advertising. Server-side delivery is the default wherever the platform supports it, 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.

On TAGGRS, an EU-hosted, ISO 27001 certified provider we partner with, or on your own Google Cloud if you prefer to own the infrastructure. Hosting is paid directly to the provider, from about €22 per month on TAGGRS or roughly €90 on Cloud Run, and is never marked up.

• A Reject all button on the first layer, same size, weight and number of clicks as Accept all. Hiding reject behind "Manage preferences" is treated as a dark pattern by the EDPB and has been fined by CNIL, AEPD and the German authorities.
• A Manage preferences option with every non-essential category off by default.
• Non-essential tags blocked until consent, enforced in the tag manager, not just promised in the banner text.
• A way to change the choice later, usually a persistent link in the footer.

The UK and the US states work differently (opt-out, with Global Privacy Control in a growing list of states), so a banner needs region-aware behaviour if you sell in both.

Google's framework for passing the visitor's consent state to its tags. If you advertise to EEA or UK users with Google Ads, you need it, or conversion measurement and audiences degrade. We implement the advanced version, configured before any tag fires, and validate what happens in both the granted and denied states.

Yes, and it's one of the most common leaks we find. When the banner and the tags load at the same time, purchases from consenting visitors get dropped before consent is even read. It looks like a low consent rate; it's a firing-order bug. We fix the order rather than patching the numbers in reporting.

Yes. We wire Consent Mode v2 and GTM enforcement to whatever CMP you have. If you don't have one, or yours costs more per domain than it should, our own banner is an option, but we don't require it.

Our product family, built from the same architecture we deploy for clients and packaged as GTM templates: Beexy Consent, a GTM-native cookie banner; Beexy Webloader; and Beexy Pixel, a server-side data client that sends clean, deduplicated events to GA4, Meta and Google Ads. See the product pages.

It runs entirely as a GTM custom template: no external SDK loading on every page, no separate vendor cookie, no monthly subscription per domain. Consent Mode v2 out of the box, Accept all and Reject all at equal weight on the first layer, WCAG 2.2 AA, and region presets covering GDPR, CCPA and LGPD.

No. Beexy templates are delivered as importable JSON after purchase. The Community Gallery has its own approval cycle and content rules, and we chose to ship and update independently. The import takes about 30 seconds in your GTM workspace, no developer required.