Conversion Linker in Google Tag Manager

Analytics Mania - Google Analytics & Tag Manager
9 Jul 202411:41

Summary

TLDRThis video explains how to create a Google Ads conversion linker tag in Google Tag Manager. It covers the process of capturing Google click IDs through cookies, tracking conversions, and setting up cross-domain tracking. Tips on advanced cookie settings and server-side tagging are also provided.

Takeaways

  • 🔗 Conversion Linker is a tag in Google Tag Manager that helps track Google Ads conversions by creating a first-party cookie containing the Google click ID (GCL ID).
  • 🔍 When a visitor clicks a Google ad and lands on your website, the URL may contain the GCL ID, which is captured by the Conversion Linker tag.
  • 📝 To set up Conversion Linker, create a new tag configuration in Google Tag Manager, select 'Google Ads Conversion Linker', and apply it to all pages.
  • 🔎 Testing the Conversion Linker involves entering a URL with the GCL ID into Google Tag Manager's preview mode and checking if the cookie is created and contains the correct click ID.
  • 💡 The cookie created by Conversion Linker stores information about the last ad click and is used to attribute conversions to specific ad clicks in Google Analytics.
  • 🌐 Enabling 'linking on all page URLs' can help persist the GCL ID across pages, especially if consent is given on a subsequent page.
  • 🔄 Cross-domain tracking is essential for journeys that span multiple domains, allowing the GCL ID to be passed and recognized across different websites.
  • 🔗 To enable cross-domain tracking, enter the involved domains in the Conversion Linker settings, ensuring that the 'Accept incoming linker parameters' checkbox is checked.
  • 🛠️ Advanced settings in Conversion Linker allow for customization of cookie prefixes, domain limitations, and cookie flags like 'SameSite=None' or 'Secure'.
  • 🏢 For server-side tagging, ensure that the Conversion Linker tag is set up in the server-side container, allowing the server to set cookies based on the GCL ID in the Google Analytics page view request.
  • 📚 If using server-side tagging, the Conversion Linker tag in the client-side container is not necessary, as the server-side container handles the tracking.

Q & A

  • What is a Google click ID, also known as GCL ID?

    -A Google click ID, or GCL ID, is a parameter in the URL that tracks a visitor who clicks on a Google ad and lands on a website. It helps in attributing conversions to specific ad clicks.

  • What does the conversion Linker tag do when a visitor lands on a page with a GCL ID?

    -The conversion Linker tag creates a first-party cookie that contains the value of the Google click ID, allowing for tracking of ad clicks and their conversions.

  • How do you create a conversion Linker tag in Google Tag Manager?

    -In Google Tag Manager, you click on 'New Tag Configuration', select 'Google Ads Conversion Linker', keep the settings as they are, select 'All Pages' for triggering, name the tag, and click 'Save'.

  • What is the purpose of testing the conversion Linker tag with a URL containing the GCL ID?

    -Testing ensures that the conversion Linker tag correctly creates a cookie when a visitor lands on a page with the GCL ID in the URL, which is crucial for tracking conversions accurately.

  • Why is it important to send the value of the cookie along with conversion data to Google Ads?

    -Sending the cookie value with conversion data allows Google Ads to accurately attribute conversions to specific ad clicks, improving the measurement of ad performance.

  • What is the role of the 'Enable linking on all page URLs' setting in the conversion Linker?

    -This setting ensures that the Google click ID is persisted across different pages of the same subdomain, even if the visitor hasn't given consent on the initial page.

  • How does cross-domain tracking work with the conversion Linker?

    -Cross-domain tracking allows the conversion Linker to decorate links with Google click information when a visitor's journey spans multiple different domains, enabling consistent tracking across those domains.

  • What should you do if your website does not accept URL parameters due to functionality issues?

    -You can instruct the conversion Linker to use fragment identifiers instead of query parameters, which appends the parameters after a hash (#) in the URL.

  • What is the purpose of the 'Accept incoming clinker parameters' checkbox in cross-domain tracking?

    -This checkbox allows the conversion Linker to read the Google click information from the URL on the second domain and create a cookie from it, maintaining tracking consistency across domains.

  • How can you manage cookie settings for the conversion Linker in advanced scenarios?

    -In the 'Advanced' section, you can manage cookie settings such as the cookie prefix, domain limitations, path restrictions, and cookie flags like 'SameSite=None' or 'Secure'.

  • What is the difference between using conversion Linker in a client-side and server-side Google Tag Manager container?

    -In client-side, the conversion Linker runs in the visitor's browser, creating cookies directly. In server-side, the conversion Linker operates on the server, setting cookies in response to incoming requests, which is useful for tracking across multiple domains or complex setups.

Outlines

00:00

🔗 Understanding Google Ads Conversion Linker

The script explains the process of setting up the Google Ads Conversion Linker in Google Tag Manager. It details how the linker tag works by creating a first-party cookie with the Google click ID (GCL ID) when a visitor lands on a website from a Google ad. The script covers the steps to create a new tag configuration, select all pages for triggering, and test the functionality using the preview mode in GTM. It also discusses the importance of this tag for tracking conversions and sending data to Google Ads, along with additional settings like enabling linking on all page URLs and cross-domain tracking for visitors journeying across multiple domains. The summary emphasizes the need for this tag if using Google Tag Manager for tracking Google Ads conversions.

05:02

📝 Advanced Settings for Conversion Linker in GTM

This paragraph delves into the advanced settings of the Google Ads Conversion Linker in Google Tag Manager. It covers how to enable cross-domain tracking for user journeys across different domains, using comma-separated domain entries in the linker settings. The script also explains how to handle cases where URL parameters might not be accepted by certain websites by using fragment identifiers instead. It touches on form submissions and server-side tagging, where conversion data is sent to a server-side endpoint. Advanced cookie settings are discussed, including custom prefixes, domain limitations, and cookie flags. The summary highlights the flexibility of the linker to adapt to various website structures and tracking needs, ensuring accurate conversion tracking across domains and subdomains.

10:03

🛠️ Server-Side Tagging and Conversion Linker Best Practices

The final paragraph focuses on the use of server-side tagging in conjunction with the Google Ads Conversion Linker. It clarifies that if a website uses server-side Google Tag Manager, the Conversion Linker should be implemented there rather than in the client-side container. The script explains that when a page view request is sent to the server with the GCL ID parameter, the server will set a first-party cookie in the visitor's browser. It also advises that if server-side tagging is used, there is no need for a Conversion Linker in the client-side website container. The summary emphasizes the importance of proper implementation of tags according to the website's tracking setup, ensuring efficient and accurate tracking of Google Ads conversions.

Mindmap

Keywords

💡Google Ads Tag

A Google Ads Tag is a piece of code that is implemented on a website to track the performance of Google Ads campaigns. It is crucial for understanding how users interact with ads and what actions they take after clicking on them. In the video, the creation of a Google Ads tag within Google Tag Manager is discussed, which is essential for setting up tracking on all pages of a website.

💡Google Click ID (GCL ID)

Google Click ID is a unique identifier that is passed through the URL when a user clicks on a Google ad. It helps in tracking the source of the traffic and is vital for attributing conversions back to the specific ad click. In the script, it is mentioned as a parameter in the URL that, if present, triggers the creation of a first-party cookie by the conversion linker tag.

💡Conversion Linker

Conversion Linker is a tag in Google Tag Manager that creates a first-party cookie containing the Google Click ID. This cookie helps in tracking conversions that occur on a website after a user has clicked on a Google ad. The video explains how to set up the Conversion Linker tag and its importance in linking ad clicks to conversions on a website.

💡First-Party Cookie

A first-party cookie is a type of cookie that is set by the website that the user is currently visiting. In the context of the video, the Conversion Linker tag creates a first-party cookie to store the Google Click ID, which is then used to attribute conversions to the original ad click.

💡Google Tag Manager

Google Tag Manager is a free tool offered by Google that allows marketers to add tracking and marketing tags to their website without having to edit the code of the site. The video provides a step-by-step guide on how to create and test a Conversion Linker tag within Google Tag Manager.

💡Cross-Domain Tracking

Cross-domain tracking is a feature that allows tracking of user behavior across multiple domains. In the video, it is discussed as an option in the Conversion Linker settings to handle situations where a visitor's journey spans across different domains, ensuring that the Google Click ID is maintained for conversion tracking.

💡Consent Mode

Consent Mode is a setting in Google Tag Manager that helps comply with privacy regulations by ensuring that tags are only fired after the user has given consent. The script mentions implementing Google Consent Mode to make the 'Enable linking on all page URLs' feature work effectively.

💡Server-Side Tagging

Server-Side Tagging refers to the practice of sending data to a server-side endpoint rather than executing tags directly in the browser. The video explains how to set up Conversion Linker in a server-side container and the importance of having it in the server-side container when using server-side tagging for Google Ads.

💡Advanced Cookie Settings

Advanced Cookie Settings in the video refer to options that allow customization of how cookies are set, such as the domain they apply to, their path, and additional flags like 'SameSite' or 'Secure'. The script explains how these settings can be adjusted in the Conversion Linker tag for specific use cases.

💡GA4 (Google Analytics 4)

GA4, or Google Analytics 4, is the latest version of Google Analytics that offers advanced tracking capabilities and a more user-friendly interface. The video mentions GA4 in the context of tracking conversions with Google Tag Manager, indicating that the Conversion Linker tag is compatible and useful for tracking within GA4.

Highlights

Creating a Google Ads conversion linker tag in Google Tag Manager is essential for tracking conversions from Google ad clicks.

Google click ID (GCL ID) is a URL parameter that helps attribute conversions to specific ad clicks.

Conversion linker tags create a first-party cookie containing the Google click ID when the parameter is present in the URL.

Testing the conversion linker tag involves entering a URL with the GCL ID and observing cookie creation in developer tools.

The cookie holds information about the last ad click and is sent with conversion data to Google Ads for tracking.

Additional settings in the conversion linker allow for enabling linking on all page URLs and cross-domain tracking.

Cross-domain tracking is necessary when a visitor's journey spans across multiple, distinct domains.

The conversion linker can decorate links with Google click information for cross-domain tracking.

Accepting incoming linker parameters is crucial for reading and creating cookies from Google click information on different domains.

Using server-side tagging with Google Tag Manager can streamline the process of tracking conversions from Google Ads.

Server-side container setup involves configuring the Google Analytics G tag and conversion linker for tracking across domains.

When using server-side tagging, the client-side container does not require a conversion linker tag.

Advanced cookie settings in the conversion linker allow for customization of cookie prefixes and domain limitations.

The conversion linker can be configured to use URL fragments instead of query parameters in specific website scenarios.

Decorating forms is an alternative method for tracking conversions when a visitor is redirected from one domain to another after form submission.

The video provides a comprehensive guide on setting up and utilizing the conversion linker in Google Tag Manager for Google Ads tracking.

Julius from Analytics Mania offers valuable insights into Google Tag Manager and GA4 for optimizing Google Ads conversion tracking.

Transcripts

play00:00

you create a Google ads tag in your

play00:01

Google tag manager container and then

play00:03

see this notification what is conversion

play00:06

Linker and what should you do about it

play00:08

let me

play00:10

explain when a visitor clicks a Google

play00:12

ad and then lands on your website the

play00:14

URL may contain various parameters and

play00:17

one of them is Google click ID also

play00:19

known as GCL ID in reality the value of

play00:22

this parameter will be much longer but

play00:24

this is just an example so if a visitor

play00:27

lands on a page and URL contains this

play00:29

parameter and you fire a conversion

play00:32

Linker tag on all pages of the website

play00:34

then conversion Linker will create a

play00:36

first party cookie that contains the

play00:38

value of Google click ID let's see how

play00:41

that works so in Google tag manager I

play00:44

will click new tag configuration then

play00:47

Google ads conversion Linker and for now

play00:50

let's keep all these settings as they

play00:52

are and just in triggering select all

play00:55

pages then let's name this tag and click

play00:58

save now we will test if this is working

play01:01

so click preview then you will be asked

play01:03

to enter the URL of the website where

play01:06

you want to test this so I will just

play01:08

copy the URL with Google click ID I

play01:11

enter it right here and I click

play01:14

connect now if I open developer tools

play01:17

and then go to application cookies and

play01:20

then select my domain here you will see

play01:23

two cookies and this one is the one that

play01:26

contains the click ID so I entered this

play01:29

number right right here and you can see

play01:31

it right here now if I close this and

play01:35

then try another parameter I mean

play01:37

another value so I will just enter abc1

play01:40

2 3 and then we'll connect again the

play01:42

conversion Linker tag will fire again

play01:45

and if I check the value of the cookie

play01:48

you will see that now it stores abc1 2 3

play01:51

so basically this cookie will contain

play01:53

the information about the last add click

play01:56

then later down wrote If the visitor

play01:58

converts and that conver verion is

play02:00

tracked by Google analytics the value of

play02:03

this cookie will also be sent together

play02:05

with that conversion if you're wondering

play02:07

if you actually need to install

play02:09

conversion Linker on your site I have

play02:11

information on my blog and I will post a

play02:13

link to it below the video but to

play02:15

simplify things here are just very

play02:17

simple questions are you using Google

play02:19

tag manager if yes then are you tracking

play02:21

Google ads conversions with Google teag

play02:24

manager if you answered yes to both

play02:25

questions then think no more and create

play02:29

the conversion link tag in your

play02:30

container visually the entire process

play02:32

looks like this a visitor clicks a

play02:34

Google ad then lands on your website and

play02:36

Google click ID is in the URL if it's

play02:39

not then conversion Linker will not be

play02:40

able to create a cookie so here the

play02:43

cookie is created then the visitor

play02:45

converts maybe signs up for something or

play02:48

makes a purchase then conversion is

play02:49

tracked and that conversion event

play02:52

together with cookies data is sent to

play02:55

Google ads now let's take a look at some

play02:57

additional settings in the conversion

play02:59

Linker

play03:00

the first one is enable linking on all

play03:03

page URLs this is related to situations

play03:05

where let's say the visitor comes to

play03:07

your website from Google ad the URL

play03:10

contains GCL ID but the visitor still

play03:12

hasn't given consent then the visitor

play03:15

goes to the next page and gives consent

play03:17

there normally Google click ID will be

play03:19

lost on that second page but if you want

play03:21

to persist that across different pages

play03:24

of the same subdomain then you can

play03:26

enable this option right here but keep

play03:28

in mind that in in order for this to

play03:30

work you also have to implement Google

play03:32

consent mode then the other option is

play03:34

related to cross-domain tracking if the

play03:37

Journey of your website visitors spans

play03:39

across multiple domains and I'm not

play03:41

talking about subdomains different

play03:43

domains mean for example website one.com

play03:46

and website two.com so they are totally

play03:48

different domains if you have let's say

play03:51

blog. website.com and

play03:55

www.website.com which are two subdomains

play03:57

of the same domain then you don't need

play04:00

cross-domain tracking cross-domain

play04:02

tracking means two completely different

play04:05

domains because cookies cannot be shared

play04:07

between different domains but thanks to

play04:10

this feature right here you can actually

play04:12

mitigate that issue let's remember that

play04:14

previous example of two domains website

play04:16

one and website two so if your visitor

play04:18

Journey spans across multiple domains

play04:20

and the visitor can go from website one

play04:22

to website 2 or vice versa from website

play04:25

2 to website one then just enter both

play04:29

the domains comma separated in this

play04:31

field right here if the journey spans

play04:34

across more domains then enter them

play04:36

right here what this will do is that

play04:38

when the visitor is on website one and

play04:41

clicks the link that redirects the

play04:44

visitor to website 2 conversion Linker

play04:46

will decorate the link right here with

play04:49

Google click information and it will be

play04:51

available right here as well then on

play04:54

website 2 when conversion Linker fires

play04:57

it will take that information and create

play04:59

a cook key on this domain as well let's

play05:01

take a look at how this works also make

play05:03

sure that accept incoming clinker

play05:05

parameters checkbox is enabled here I

play05:08

have a demo page on GTM playground.com

play05:10

if I click this link it will open a tab

play05:14

with another website which has a

play05:16

completely different domain let's say

play05:19

that both of these pages are part of the

play05:21

same user Journey so I want to use cross

play05:24

domain tracking that's why I will go to

play05:26

Google tech manager then go to

play05:28

conversion Linker and instead of of

play05:29

these two fake domains I will enter GTM

play05:33

playground.com and then GTM course my

play05:37

shopify.com like that and then click

play05:40

save then I will hit preview to refresh

play05:44

the preview mode and on this first page

play05:46

I will click the link and once I am

play05:49

moved to the second page this is the

play05:52

information that was added by conversion

play05:54

Linker tag on this first page because if

play05:57

I inspect it you will see that the your

play05:59

URL is decorated in the preview mode I

play06:02

see that on container loaded my

play06:04

conversion link are fired so this is

play06:05

happening on the second website and if I

play06:08

go to the developer tools of the second

play06:10

website and I look for the aw cookie or

play06:14

any cookie that starts with gccl then

play06:16

you will see that its value contains

play06:19

abc123 which is the same as right here

play06:22

so now the cookie value is the same

play06:24

across both websites and if the

play06:26

conversion happens on the second site

play06:28

Google ads will be be able to track that

play06:30

and attribute that properly so this part

play06:32

right here is responsible for decorating

play06:34

the URL which means that we have this

play06:37

and this checkbox is responsible for

play06:41

reading this parameter on the second

play06:43

domain and then creating cookie from it

play06:45

on most websites adding the parameter

play06:48

with a question mark which means that

play06:49

this is a URL parameter will work just

play06:52

fine however in very rare cases on very

play06:54

few websites this is not accepted

play06:57

because it might break the functionality

play06:59

of the website in that case you can tell

play07:02

conversion Linker to use not query

play07:04

parameters but fragment instead this

play07:06

means that instead of this question mark

play07:09

the parameter will be added like this

play07:11

but again I want to emphasize that in

play07:13

most cases the question mark will work

play07:15

just fine then if the website visitor

play07:17

moves from one domain to another domain

play07:20

with the form submission for example the

play07:22

form is submitted and then the visitor

play07:24

is redirected to a completely different

play07:26

domain then you can try to use decorate

play07:28

forms however keep keep in mind that

play07:30

there are various ways how forms can be

play07:32

tracked and not all forms will be

play07:35

supported by this feature and then there

play07:37

is one more section which is Advanced

play07:40

and that is rightfully so because in 99%

play07:44

of situations you will not need this

play07:46

section basically here you can manage

play07:49

cookie settings for example conversion

play07:51

Linker when it creates a cookie or

play07:53

actually two cookies they start with GCL

play07:56

but if for some reason you want to use a

play07:58

different prefix for example gcl2 or

play08:02

something else then you can add that new

play08:05

prefix right here then by default when

play08:08

the cookie is created it is set on all

play08:11

subdomains of the website it will be dot

play08:14

then your domain and then or something

play08:16

else but if again for some reason you

play08:19

want to limit the domain of the cookie

play08:22

for example you just want to set it on

play08:24

one subdomain only then you would need

play08:27

to enter that domain or that subdomain

play08:30

right here for example like that in this

play08:33

case the cookie will be accessible only

play08:35

on this subdomain then by default the

play08:38

cookie is set on all pages of the

play08:41

subdomain for example demo page SL

play08:45

homepage SL contact whatever so anything

play08:47

will be covered by this but if for some

play08:50

reason you want to limit that to just

play08:52

particular page paths for example just

play08:55

to the English version of the site you

play08:57

can enter it like that and then if

play08:59

needed you can also insert some cookie

play09:01

Flags an example is visible right here

play09:04

same site none or secure but as I've

play09:07

said this is definitely Advanced and in

play09:10

most situations you will not need this

play09:12

section so don't overwhelm yourself too

play09:14

much with this and then the final tip is

play09:16

related to server side tagging so if you

play09:20

have Google tag in the client side

play09:22

Google tag mag container and that Google

play09:24

tag is sending data to your server s

play09:27

side endpoint which means that of course

play09:29

all other tags in your container are

play09:31

also using this server container URL

play09:33

then all ge4 requests will be sent to

play09:36

your server side Google teag manager

play09:37

then in server side container it will be

play09:39

enough for you to have the Google

play09:42

analytics G for client and then go to

play09:45

tags click new tag configuration

play09:48

conversion Linker and then if you're

play09:50

working with multiple domains then

play09:52

enable this option right here and then

play09:54

here there are also some things related

play09:57

to Advanced cookie settings but again in

play09:59

in many cases you might not need that

play10:01

because the default options are more

play10:02

than enough and then here in the

play10:04

triggering set to fire on all pages of

play10:07

course in your server side container you

play10:09

would also need to have the Google ads

play10:11

tags but this video focuses on

play10:14

conversion Linker that's why I'm showing

play10:16

just this part so what will happen here

play10:18

is that when Google analytics page view

play10:20

request is sent to your server then this

play10:22

tag will fire and if the request

play10:25

contains the GCL ID parameter then

play10:28

thanks to the this tag the server will

play10:30

set the first party cookie in the

play10:32

visitors browser and one final thing is

play10:34

that if you're using server side tagging

play10:36

and your website container has Google

play10:38

analytics tracking code while your

play10:40

server s side container has the

play10:41

conversion Linker you don't need

play10:43

conversion Linker in the client s side

play10:45

container which means the website

play10:46

container so if you're not using server

play10:48

side tagging but you're running Google

play10:50

ads and you're using website Google tag

play10:52

manager then have conversion Linker in

play10:55

your website container but if you're

play10:56

using servicei tagging and your Google

play10:58

ads are being tracked in the server

play10:59

container then have conversion Linker

play11:02

here and you don't need conversion

play11:04

Linker in the website container

play11:06

hopefully this video cleared the doubts

play11:08

about the conversion Linker basically if

play11:10

you're using Google tag manager and you

play11:12

have Google ads tags inside of it then

play11:14

create the conversion Linker tag to if

play11:16

you found this video useful hit the like

play11:18

button below the video that will help me

play11:20

understand what videos do you like and

play11:22

what should I create in the future also

play11:24

if you want to learn more about Google

play11:25

tag manager or ga4 then subscribe to

play11:28

this channel my name is Julius this is

play11:30

analytics Mania and I'll see you in the

play11:32

next video

play11:36

[Music]

Rate This

5.0 / 5 (0 votes)

関連タグ
Google AdsConversion LinkerTag ManagerTrackingCookiesGCL IDAnalyticsCross-DomainServer SideUser Journey
英語で要約が必要ですか?