FLEX YOUR IDEA
DIGITAL MARKETING ANALYTICS TAG OPTIMISATION · SINGAPORE
Your analytics are probably lying to you.
Most sites have tracking installed. Far fewer have it installed correctly, and the difference only shows up when you try to make a decision with the data.
SOURCE
REPORTS
PURCHASES
Google Ads conversion tag
GA-conv
312
Meta Pixel
browser
288
GA4 purchase event
gtag
241
Orders in your bank
actual
194
Four sources. Four different answers. Only one of them pays your bills.
tag health, last 30 days
Illustrative of the reconciliation gap this page describes. Not client data.
WHY IT MATTERS · 02
What is the difference between analytics and reporting?
Reporting looks backwards at what already happened. Analytics decides where the next dollar goes. One is admin. The other is the input to every commercial decision you make this quarter.
Without numbers you can trust, three questions stay permanently unanswered, and every one of them is a budget decision:
✓
Which channel actually produces customers, rather than which one produces traffic
✓
What a customer costs you to acquire, honestly, across every channel
✓
Which pages do the persuading, and which are just in the way
The cost compounds. Every month of bad data is a month of budget allocated by guesswork, and that allocation repeats monthly. The damage is not one wrong report. It is a wrong habit, running unexamined.
Bad data does not just report badly. It spends badly.
Advertising platforms now optimise themselves using the conversion data you send them. Feed Google Ads or Meta the wrong signal and the platform does not simply produce a misleading dashboard. It goes and buys more of the wrong audience with your money, and it gets better at it every day.
This sits underneath your organic search performance too. Attribution decides whether search gets credit for the customers it earned.
THE SYMPTOMS · 03
What goes wrong with website tracking?
You can skim the bold lines alone and still know whether this page is about you. Most businesses recognise at least two.
01
Your revenue does not match your bank.
The same purchase counted twice, because a tag fires from the platform's native integration and from a manual install at the same time. Ecommerce is where this is almost universal.
02
You are reporting leads that never arrived.
A form submission counted on page load rather than on submit. The platform records a conversion every time somebody merely looks at the contact page.
03
Your own team is polluting the data.
Staff visits, staging traffic and internal testing all counted as genuine customer behaviour. The smaller your traffic, the more this distorts everything downstream.
04
Everything is credited to "direct", so you defund what was working.
Missing or broken UTM tagging means the channel that actually earned the sale gets no credit. It then looks unprofitable and gets cut. This is the worst outcome on the list, because the business actively destroys the thing that was succeeding.
05
A site change quietly broke it and nobody noticed.
A redesign, a theme update or a new checkout. The number does not drop to zero, which would be obvious. It just drifts, and drift is invisible for months.
06
Consent is either firing too early or blocking too much.
Tags running before the visitor has decided, or blocked after they agreed. One creates a compliance exposure under Singapore's PDPA, the other leaves a hole in your data. Both are common and neither announces itself.
07
Nothing is recorded at all.
The genuinely common case, and the one nobody admits. Everyone assumed somebody else set it up during the website build.
tag debugger, one page load
Green fired. Grey never fired. Red fired and failed. Most businesses have never seen this view of their own website.
Sound familiar? →
PLAIN ENGLISH · 04
What is a tag in Google Tag Manager?
A tag is a small piece of code on your site that reports one specific event to one specific platform. That is the whole idea. Everything else is detail.
Why a tag manager exists
Rather than hard-coding twenty separate scripts into your website, one container holds them all and controls when each one fires. That container is why Google Tag Manager keeps appearing in the list below. It is also why one broken container breaks every platform at once, and why fixing the container fixes all of them at once.
Browser side against server side
Client-side tagging reports from the visitor's browser, and is increasingly blocked by ad blockers, browser restrictions and consent tools. Server-side reports from your own server, which is more reliable and more work to set up. That is the trade-off, stated plainly. Not everyone needs the second one.
one purchase, end to end
1
customer completes checkout
trigger
2
purchase
with the order value attached
3
→ Google Ads
learns which click produced the sale
That is the entire mechanism. The platform now knows which advertisement earned money, and spends accordingly.
01
The trigger
What makes it fire. A page loading, a button being clicked, a checkout completing.
02
The event
What happened, named consistently, with the values worth knowing attached to it. Naming is where most setups start to drift, because two people name the same thing differently.
03
The destination
Which platform gets told, and therefore which platform can act on it. One event often needs to reach several destinations at once.
THE LANDSCAPE · 05
How do consent, tags and analytics platforms connect?
Read it top to bottom. A visitor does something, consent decides what may fire, one container collects it, the platforms receive it, and it ends at you deciding where the next dollar goes.
the tracking pipeline
1 · YOUR SITE
Wix, Shopify or WooCommerce
page view, cart, form, purchase
2 · CONSENT
Cookie banner, Consent Mode v2
decides what is allowed to fire
3 · COLLECTION
dataLayer → Tag Manager
one container feeds everything
server-side GTM, your own server
BROWSER + SERVER ROUTE
Google Ads, Meta, TikTok
resilient to ad blockers
these platforms act on your data
BROWSER ONLY
LinkedIn, Microsoft UET,
Pinterest, Snap, X
YOUR REPORTING LAYER
GA4
5 · THE DECISION
Looker Studio
dashboard
where the next dollar goes
OUTSIDE THE PIPELINE
Clarity, Hotjar
behaviour, on the page directly
your budget is spent on whatever you report
1
Your site
Wix, Shopify or WooCommerce. Page view, add to cart, form, purchase.
2
Consent
Cookie banner, Consent Mode v2. Decides what is allowed to fire.
3
Collection
dataLayer to Tag Manager. One container feeds everything; server-side GTM runs on your own server.
4
Destinations
Browser and server route: Google Ads, Meta, TikTok. Browser only: LinkedIn, Microsoft UET, Pinterest, Snap, X. Your reporting layer: GA4.
5
The decision
Looker Studio dashboard: where the next dollar goes. Your budget is spent on whatever you report.
Outside the pipeline: Clarity and Hotjar record behaviour directly on the page.
Consent sits before collection, not after
Nothing reaches any platform until consent has been decided. That is precisely why consent cannot be bolted on at the end of a build.
One container feeds everything
Every advertising and measurement platform is fed by the same tag manager. One broken container breaks all of them simultaneously, and one fix repairs all of them.
The grouping is by connection, not by owner
Google Ads, Meta and TikTok each accept a browser route and a server-to-server route, which is what makes them resilient. LinkedIn, Microsoft UET, Pinterest, Snap and X are browser-only, so their numbers are the first to under-report. A logo chart hides that distinction entirely.
The green arrow points backwards
That loop is the whole argument. Those platforms do not merely receive your data, they spend your budget and build your audiences from it. Wrong tags steer your money.
EVERYTHING THAT HAS TO BE MANAGED
The platforms
GROUP A
Core measurement
Google Analytics 4
The base reporting layer. Where sessions, events and conversions are recorded.
Google Tag Manager
The container that holds and controls every other tag on the site.
Google Search Console
Organic search performance and indexing health. Not a tag, but part of the stack.
Looker Studio
The reporting surface that turns the above into something a business can read.
GROUP B
Advertising and conversion
Google Ads conversion tag
Tells Google Ads which clicks produced a sale or a lead.
Meta Pixel and Conversions API
Facebook and Instagram tracking. The API is the server-side half.
TikTok Pixel and Events API
TikTok's equivalent pair.
LinkedIn Insight Tag
B2B audience and conversion tracking.
Microsoft Advertising UET tag
Bing and the Microsoft network.
Pinterest Tag
Pinterest conversion and audience tracking.
Snap Pixel
Snapchat conversion and audience tracking.
X Pixel
X conversion and audience tracking.
GROUP C
Ecommerce platform native
Shopify Web Pixels API
Shopify's own sanctioned way to run tracking on checkout.
Shopify native channels
Built-in Google and Meta connections. A very common source of double counting.
Wix Analytics and tag manager
Wix's built-in measurement and tag handling.
WooCommerce tracking plugins
Plugin-based tracking on WooCommerce stores.
GROUP D
Behaviour and experience
Microsoft Clarity
Session recordings and heatmaps. Free.
Hotjar
Session recordings, heatmaps and on-site surveys.
GROUP E
Consent, quality and server-side
Google Consent Mode v2
Adjusts what tags may collect based on the visitor's consent choice.
Consent management platform
Captures and stores the consent decision.
Server-side Google Tag Manager
Runs tagging from your own server rather than the browser.
Google Enhanced Conversions
Improves match rates using hashed first-party data.
SELF-QUALIFICATION · 06
When does a business need a tracking audit?
If you recognise your own situation in this list, you already have your answer.
→
You are about to spend on paid advertising.
Platforms optimise on the conversion data you send them. Launching before tracking is correct means paying to teach the platform the wrong lesson, and that learning is difficult to undo.
→
You run an ecommerce store.
Revenue, product performance and checkout drop-off all depend on correctly configured events. Ecommerce also carries the highest double-counting risk, because platform integrations and manual tags overlap. Often part of an ecommerce build.
→
You are running more than one channel.
The moment there are two sources of traffic, the only question that matters is which one deserves the next dollar. Attribution is the only thing that answers it, and that includes your social campaigns.
→
You have a new website or a redesign going live.
Tracking does not carry across a rebuild. This is the single most common way a working setup silently breaks.
→
You are reporting to someone.
A director, an investor, a partner or a franchisor. Numbers that will be questioned need to be defensible when they are.
→
Your numbers do not agree with each other.
The ad platform, the analytics and the actual sales all say something different. This is the symptom that most often brings people to this page.
→
You are being asked about consent and data handling.
Cookie consent and PDPA obligations now sit inside the tracking conversation rather than beside it.
→
You are handing marketing to an agency, or taking it back.
Either direction, you need to know the measurement is yours and that it is correct.
THE METHOD · 07
How does Flex Your Idea set up tracking?
Most setups fail because they were installed tool-first rather than question-first. That is the whole difference, and it is the second step below.
01
Audit before we touch anything
Establish what is currently installed, what is firing, what is double firing, and what is silently dead. You get the findings either way.
02
Measurement plan before implementation
Decide what the business actually needs to know, then work backwards to the events required to answer it. Every setup we are called in to rescue was built the other way round.
03
Implementation through a single container
One tag manager, documented, so the setup is legible to whoever inherits it after us.
04
Consent handled as part of the build
Configured with the tags, not bolted on afterwards. The pipeline diagram above shows why the order matters.
05
Verification in real conditions
Test transactions and test submissions, checked in every destination platform, not just in a preview mode that only proves the tag exists.
06
Documentation and handover
The business owns the accounts, the container and the documentation. We state that plainly because plenty of agencies do not, and readers have been burned before.
07
A reporting layer someone actually reads
The data becomes a dashboard that gets opened. Otherwise the work is invisible and gets cut at the next budget review.
We build websites with the measurement infrastructure already inside them, rather than bolting analytics on afterwards. This page is what that claim actually means in practice.
DELIVERABLES · 08
What do you receive at the end of a tracking setup?
Every item below is a thing you keep, in your own accounts, whether or not you carry on working with us. Nothing here is held on an agency login.
✓
A documented audit of the current setup, including what was found broken
✓
A measurement plan tied to your actual business questions
✓
A configured tag manager container with every required tag
✓
Conversion tracking verified live in each advertising platform
✓
Consent configuration, built in rather than added later
✓
A reporting dashboard built around your questions, not a default template
✓
Full account and container ownership, in your own name
✓
A written handover document any future agency can pick up
the reporting layer
One surface, built around the questions your business actually asks. Not forty metrics nobody opens.
STRAIGHT ANSWERS · 09
Analytics and tagging questions from Singapore businesses
How do I know if my tracking is set up correctly?
Do the two-minute version yourself. Take last month's conversions as reported in your advertising platform and compare them against the actual orders or enquiries you received. If those two numbers do not reconcile, something in the chain is wrong. That single check catches the majority of broken setups.
GA4 reports what happened on your site. It does not tell the advertising platforms what to optimise towards. Those are two different jobs, and only one of them decides how your budget gets spent.
Is Google Analytics not enough on its own?
Installing the base code is not the same as configuring events, conversions and consent. The base code is roughly a tenth of the work. It proves the site can talk to the platform. It does not decide what gets said.
Typically five to seven working days. What moves it is how many platforms are involved, and how much of the existing setup needs repairing rather than building from scratch. You get a firm timeline after the audit and before any work starts, so it is a commitment rather than an estimate.
My developer already installed the tracking code. Is that not the same thing?
Not everyone does. It matters most for ecommerce and for meaningful advertising spend, where browser-side losses to ad blockers and browser restrictions become material. If you are running a modest budget on a lead-generation site, it is usually not the first thing to fix.
You do. Always, and in your own name. The accounts, the container and the documentation stay yours whether or not you continue working with us.
How long does it take?
Existing data stays as it is. A correct reconfiguration changes what is collected from that point forward, so history is not retrospectively fixed. Worth knowing before you expect old reports to change.
Yes, and both carry platform-specific traps. On Shopify the checkout is the difficult part, and its native channel integrations are a frequent cause of double counting. On Wix the built-in tag handling has to be reconciled with anything installed through a container, or you get two of everything.
Do I need server-side tracking?
Not everyone does. It matters most for ecommerce and for meaningful advertising spend, where browser-side losses to ad blockers and browser restrictions become material. If you are running a modest budget on a lead-generation site, it is usually not the first thing to fix.
You do. Always, and in your own name. The accounts, the container and the documentation stay yours whether or not you continue working with us.
Existing data stays as it is. A correct reconfiguration changes what is collected from that point forward, so history is not retrospectively fixed. Worth knowing before you expect old reports to change.
Yes, and both carry platform-specific traps. On Shopify the checkout is the difficult part, and its native channel integrations are a frequent cause of double counting. On Wix the built-in tag handling has to be reconciled with anything installed through a container, or you get two of everything.
Who owns the accounts?
What happens to my historical data?
Does this work with Shopify and Wix?
THE NEXT STEP
Ready to build a website that actually performs?
Tell me about your business. I'll come back with a build plan within two working days. Not a quote. A plan. So we both know what we are agreeing to before any number lands on the table.
Let's discuss a growth plan