In this guide
- Start with the questions the business needs answered, then choose the events that answer them.
- Write naming rules, ownership and consent rules once.
- Review the plan twice a year and after every major site change.
Most tracking set-ups grow by accident. Someone adds a tag for a campaign, another adds one for a report, and a year later nobody knows why half of them exist. A tagging strategy is the cure. It is a short document, one or two pages, that says what you track, why, how and who owns it. This page gives a template. It builds on GA4 event tracking, Google Tag Manager best practices and data validation.
1. Business questions
List the five to ten questions that matter: Which channels bring profitable customers? Where do visitors drop in checkout? Which landing pages produce leads? Which products have the best margin? For each question, write what you would do with the answer. If there is no decision attached, the question is not worth tracking.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
2. Events and parameters
| Question | Event | Parameters |
|---|---|---|
| Which channels bring customers? | purchase | value, currency, transaction_id, source and campaign (from UTMs) |
| Where do visitors drop? | view_item, add_to_cart, begin_checkout | item_id, price, step |
| Which pages produce leads? | generate_lead | form_name, page, lead_id |
3. Naming rules
- Lower case with underscores for events and parameters.
- Use GA4 recommended names where they exist.
- Name tags
Platform - Event, triggersEvent - name, variables by type. - Write every name in the document before you build.
Connected in minutes
Add your domain, install the pixel, connect your ad platforms and watch the first events land.
4. Tools and ownership
| Item | Owner |
|---|---|
| Tag Manager container | Named person |
| GA4 property | Named person |
| Ad platform accounts and tokens | Named person, business accounts |
| Server container and hosting | Named person |
| Consent platform | Named person |
| This document | Named person |
5. Consent model
Write which tags need which consent, what the defaults are by region and how consent reaches the server container. See cookie banners and GTM and GDPR.
6. Data flow
Draw one picture: website, web container, tagging subdomain, server container, destinations. Add the places where data is stored. With Open Tracked, that picture includes the Data Store and the power-ups you use.
7. Quality checks
Decide how you will test: Preview, platform test tools, a weekly comparison with store orders. See data validation techniques.
8. Review cycle
- After every major site change: run a test order.
- Monthly: check key events.
- Twice a year: review this document and the container.
A realistic example
A mid-size store writes a two-page tagging strategy before a replatform. It lists six business questions, a table of twelve events with their parameters, the naming rules, the owners of each account and the consent model. During the build, the agency refers to it every day, and when a developer proposes adding a heat-map tag, the document makes the team ask which question it would answer. They decide it is not needed. Six months later a new analyst reads the document and understands the whole set-up in an hour. The strategy did not make tracking more advanced. It made it deliberate, and deliberate tracking is easier to trust and to change.
Keep the document short enough that people read it. If it grows past two pages, move detail into an appendix, and keep the front page for the questions, the events, the owners and the rules.
Orders from your store, back to the ad that earned them
Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.
Frequently asked questions
What is a tagging strategy?
A short document that defines what you track, why, how it is named, who owns it and how it is tested.
How long should it be?
One or two pages is enough.
When should I write it?
Before you build, and update it when the site or goals change.
Who should own it?
One named person, usually in marketing analytics or the agency.
How often should I review it?
After major changes and at least twice a year.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Blog · 5 min read
