Many agencies run Google Ads and Meta campaigns very well, but tracking is not their core work. Setting up GTM, GA4, Consent Mode v2 or a server container takes time, and a mistake there affects every campaign that follows. White-label tracking means we do that part, and the agency keeps the client relationship.
What white-label means in practice
- We work under your name. Your client talks to you, not to us, unless you want us in a call.
- Documentation and reports have no Metryx Studio branding, so you can pass them on as your own.
- The client keeps ownership of every account: GTM, GA4, Google Ads, Meta Business and the server hosting. We work with user access, and nothing is set up on our accounts.
How a project runs
1. Short brief
You send the website, the platforms the client advertises on, what should be measured (purchases, leads, calls, sign-ups) and the deadline. For webshops, also the shop platform and payment methods.
2. Fixed price
Based on the brief you get a fixed price for the project type, for example a basic GA4 and Google Ads setup, Consent Mode v2, a webshop with ecommerce events, or server-side tracking. Agencies get partner pricing. There are no hourly surprises.
3. Access
The client or the agency adds us as a user: GTM with publish rights, GA4 as editor, Google Ads and Meta with access to conversions and events. If the website needs a data layer, we also need access to the CMS or a contact with the developer.
4. Check of the current setup
Before changing anything, we check what is already there: containers, tags, duplicates, consent and conversions. If something would affect the plan or the price, you hear about it before we start.
5. Implementation
All changes are made in a separate GTM workspace. Nothing goes live before it is tested.
6. Testing
Every event and conversion is tested: in Tag Assistant and GA4 DebugView, in Meta Events Manager with test events, with accepted and rejected cookies, and for webshops with a test order where possible.
7. Publishing and the first days
We publish the changes with a clear version name and description. In the following days we compare the data with the backend or CRM, to catch anything the tests did not show.
8. Handover
You receive documentation: which tags and events exist, what triggers them, how consent works and what to watch out for. It is written so that your team can understand it and pass it on to the client.
Who it suits
- Performance agencies that want reliable conversion data for their campaigns without hiring a tracking specialist.
- Web agencies that build websites and want tracking included in the launch.
- Agencies with clients in several countries that need Consent Mode v2 set up the same way everywhere.
Getting started
The easiest way to start is with one client where tracking is clearly not working. Send us the website and a few sentences about what should be measured, and you will get a fixed price for that project: contact us.