Five years ago installing tracking was a different job. You put a pixel in the head and it worked. Not anymore, and knowing why makes you a different person in front of a client.
Consent
Consent means permission. The EU's GDPR and the laws that followed it say you must get a person's permission before setting cookies. Google built this into its own systems, under the name Consent Mode v2.
The consequence is plain: on a UK or EU client's site, if there is no consent banner, or there is a banner but Consent Mode is not implemented correctly, Google Ads remarketing audiences stop working.
If your clients are in the UK or the EU, this applies to every site you touch. Shops in Bangladesh, where I started, are not yet bound by these laws, but the moment I took UK clients on Fiverr I had to know this. A large share of my orders come from this one cause: someone broke Consent Mode, and the audiences in Google Ads dropped to zero.
The full Consent Mode setup is not in this book; that is Module 8. But know one thing now: every consent default must be set to denied, and it updates after the visitor clicks the banner.
// Consent default: must run before every tag in the GTM container
window.dataLayer = window.dataLayer || [];
function gtag() {
dataLayer.push(arguments);
}
gtag('consent', 'default', {
ad_storage: 'denied',
ad_user_data: 'denied',
ad_personalization: 'denied',
analytics_storage: 'denied',
wait_for_update: 500,
});First-party data
Third-party cookies are dying. That means cookies set on someone else's domain no longer work. What does work is cookies set on your own domain, and information you hold yourself: email, phone, order history.
The result: clients who have their own customer list will be fine. Clients who do not will stay dependent on the platforms.
Server-side
Anything that runs in the browser can be stopped by an ad blocker or cut by Safari. Sending from a server avoids that, because a server does not play by the browser's rules.
That is where server-side tracking and the Conversions API came from. It is not the subject of this book, but you need to know why it arrived: the browser route became unreliable, so a second route was needed.
AI
Platforms now estimate. Google and Meta both fill gaps where there is no data with modeled conversions. That means part of your report is not a count; it is an estimate.
So keeping your own events accurate matters more than ever. The more real events you send, the less the platform has to estimate.
Steps
- Check whether your site, or a client's, has a consent banner.
- In Chrome, open DevTools and look at Cookies in the Application tab. Separate the cookies on your own domain from those on other domains.
- Read the consent default block above. Write down what each key means, in your own words.
- List every place the client holds customer emails or phone numbers. That is their first-party data.
What not to do
- Do not add new tags to an EU or UK client's site without first checking whether Consent Mode is in place. You could become the reason the client breaks the law without knowing it, and the blame will land on you.
- Do not jump to server-side. If you open a server container before you understand the browser side, you will send the same event from two places and every number will be counted twice.
Proof
You can explain what a consent default is, the difference between first-party and third-party cookies, and why server-side came about. And you have seen both kinds of cookie in DevTools with your own eyes.
Want the full chapter list, or to jump to another chapter?
All chapters in the book