Tracking

Tracking is the wiring that records what happens on your website and reports it back to you. How many people arrived, where they came from, what they did, and which of them turned into an inquiry or an order. Without it, marketing is a set of receipts and a feeling. With it, you can say which channel produced which customers. Nothing about tracking happens by accident. Somebody has to decide what counts and set it up.

In short

• Tracking connects what you spend to what you get.
• A conversion is whatever you decide counts. Define it before you measure it.
• Two tools reporting different numbers is normal, not a bug.
• Consent rules apply in the Philippines, and they are not optional.

How tracking actually works

The mechanism is simpler than the jargon suggests, and knowing it explains why tracking breaks in the ways it does.

A small piece of code sits on every page of your site. When somebody loads the page, that code runs in their browser and sends a message to a reporting service saying what happened: a page was viewed, a button was clicked, a form was sent. Each message carries some context, such as which page, which device, and which site referred the visit.

The reporting service collects those messages and groups them into sessions and users, so it can tell you that four hundred people arrived and eleven of them sent a form.

Two things follow from this. First, if the code is missing from a page, that page is invisible, and pages get missed all the time during redesigns. Second, because the code runs in the visitor’s browser, anything that blocks scripts also blocks your measurement. Neither problem announces itself. The report simply shows a smaller number and looks completely normal.

The tools, and what each one actually does

• Google Analytics 4, usually written GA4, is the free tool that reports what happened on your site. Visitors, where they came from, what they viewed, what they did. It is the general record.
• Google Tag Manager, or GTM, is not a reporting tool at all. It is a container you put on the site once, so that every tracking script afterwards can be added and changed without touching the website code. Almost every setup should have it, and its absence is why so many businesses cannot get tracking changed without booking a developer.
• Google Search Console is separate and often forgotten. It reports what people searched on Google before seeing you, which no other tool can show. It is the only view of Google’s own data about your site, it is free, and it is the foundation of any honest SEO reporting.
• Platform pixels, the Meta pixel and the Google Ads tag, report back to the advertising platforms so they can optimise delivery and tell you which ads produced results.
• Call tracking, optional but useful for businesses whose customers phone. It shows which marketing produced the call rather than only the clicks.

Conversions, which is the part that matters

A conversion is any action you have decided counts as valuable. Not a visit. An outcome.

For a service business that usually means a contact form sent, a click on the email address, a booking made, or a phone number tapped on a mobile. For a store it means a purchase, and usually a few steps before it so you can see where people drop out.

The decision is yours and it is the most important one in the whole setup. Track too little and you cannot tell what works. Track everything, including scrolls and page views, and every channel looks successful because everything counts.

It is worth separating the two kinds. A primary conversion is the thing the business actually wants: an inquiry, a booking, an order. A secondary conversion is a useful signal on the way there, such as reaching the contact page. Report them separately, or the secondary ones will quietly inflate every number you look at.

A useful test: if this number doubled, would the business be better off? If not, it should not be counted as a conversion. Once they are counted, the share of visitors producing them is your conversion rate.

Words you will hear, and what they mean

• Session. One visit. It ends after a period of inactivity, so the same person returning tomorrow is a new session.
• Source and medium. Where the visit came from and how. Google organic, Facebook paid, direct, referral.
• UTM parameters. Tags added to the end of a link so the analytics tool, usually Google Analytics 4, knows exactly which campaign sent the visit. If your links are untagged, that traffic lands in a vague bucket and stays there.
• Event. Any recorded action. A page view, a click, a form submission.
• Attribution window. How long after seeing or clicking an ad a conversion still gets credited to it.
• Bounce rate. The share of visits where nothing happened. Useful on a service page, meaningless on a page whose whole job is to be read.
• Direct traffic. Visits with no known source. Some are genuinely typed in, and a lot are just visits whose source got lost.

Why two reports never agree

This confuses everybody and it is worth understanding once.

Meta Ads Manager, Google Ads and GA4 will each report different conversion numbers for the same week, which is why the figures in a paid social report rarely match the ones on your own site. They are not broken. They count differently.

Meta counts a conversion if somebody saw or clicked an ad and converted later, across devices, within a window it sets. Google Ads credits the click that led to the conversion, using its own window. GA4 attributes the visit that converted based on its own model, and it does not know what happened on a different device.

Somebody sees your ad on their phone at lunch, searches your name that evening on a laptop and fills in the form. Meta claims it. Google claims it. GA4 records a direct visit. One customer, three stories, all defensible.

The way out is not reconciliation. Pick one source as the reference you make decisions on, keep the others as supporting views, and watch the trend rather than the absolute number.

What tracking cannot see

Being clear about the blind spots is what stops the reports being trusted too much.

• Conversations. If the sale happens in Messenger, your website analytics never sees it. In this market that can be most of the business.
• Cash and walk-ins. Somebody finds you on Google, drives over and pays at the counter. Real, caused by your marketing, invisible in every tool.
• Blocked visitors. Ad blockers, privacy settings and people declining consent all reduce what is recorded. The visit still happened.
• Why. Tracking is very good at what and never explains why. It will tell you a page loses people and never tell you what was wrong with it.

The correct posture is to treat the numbers as a reliable direction and an unreliable total.

Consent, and the law here

The Philippines has the Data Privacy Act, administered by the National Privacy Commission. If you collect personal data through your site, and a contact form collects personal data, you have obligations: tell people what you collect, why, and how long you keep it, and let them ask for it to be removed.

In practice that means a privacy policy that describes what you actually do, a cookie notice if you load tracking or advertising scripts, and consent handled before those scripts run rather than after. If you sell to customers in Europe, GDPR applies to those customers as well, and it is stricter.

This is not just compliance. Both Google and Meta now expect consent signals to be passed correctly, and setups that ignore it increasingly report less than they should.

What good looks like

You should be able to answer these four questions without asking anyone.

• How many inquiries came from the website last month? A number, not an impression.
• Which channel produced them? Search, ads, social, direct, referral.
• Which pages produce inquiries and which only produce visits? This is how you find out which service page is quietly failing.
• What does it look like compared with three months ago? One month in isolation tells you almost nothing.

If your current reporting cannot answer these, the reporting is decorative.