A tag is a small piece of code on a website that sends information about what visitors do to another tool. The GA4 tag sends page views and events to Google Analytics, the Google Ads conversion tag reports enquiries and sales, and the Meta Pixel does the same for Facebook and Instagram advertising.
How a tag works
When a page loads, the browser runs the tag’s code. The tag collects details such as the page address, the referring site and an identifier stored in a cookie, then sends them as a request to the tool’s servers. Some tags fire on every page; others fire only when something specific happens, such as a form being submitted or a booking being confirmed.
Tags can be pasted straight into a site’s code, added through a CMS plugin, or managed in a tag management system. In Google Tag Manager each tag is paired with a trigger, which says when it fires, and uses variables, which supply values such as the order total. All of them live in one container that is installed on the site once. A tracking pixel is an older name for the same idea, from the days when tags were a tiny invisible image.
Tags also differ in where they send data from. A client-side tag runs in the visitor’s browser. A server-side setup sends one stream of data to a server you control, which then forwards it to each tool. The second gives you more control over what leaves your site, but it still needs the same consent decisions.
Why it matters
Tags are where your marketing data is born. If a conversion tag fires twice, your ad platform reports double the leads and its automated bidding chases the wrong signal. If it does not fire at all, campaigns that are working look like they are failing. A large share of reporting problems trace back to a tag that is missing, duplicated or firing at the wrong moment.
In the UK, tags also carry legal weight. Most analytics and advertising tags set or read cookies, and PECR requires consent for non-essential cookies before they are set. The ICO has written to operators of many of the UK’s most visited websites about cookie banners that did not give a real choice. Tags that fire before a visitor has answered the banner are a frequent cause, and the fix lives in how the tags are set up, not in the banner text.
Common mistakes
- The same tag installed twice. A plugin adds GA4 and someone also adds it in Tag Manager, so every page view counts double.
- Tags firing before consent. Without consent mode or consent-based triggers, tags run regardless of what the visitor chose.
- Conversion tags on the wrong trigger. Firing on a button click rather than a successful submission counts failed attempts as leads.
- Tags nobody remembers adding. Old agency pixels and abandoned trial tools slow the site and send data to companies you no longer work with.
How to act on it
Make a list of every tag on your site, what it sends, which tool receives it and who asked for it. Your browser’s developer tools and Google’s Tag Assistant will show what actually fires. Remove anything without an owner, move the rest into one tag manager, and check that each non-essential tag waits for consent. Then test your main conversions end to end with a real form submission or test order.
A clean, consented tag setup is the foundation of the paid media work in my performance marketing service, and a tracking audit is usually where it starts.