Google Analytics (GA) can be linked to Google Ads. A GA custom dimension can be used as the basis of a GA audience. Therefore, with GA linked to Ads, this approach can be used to add or remove visitors from remarketing lists for search ads segments (RLSA) in Ads.
In this article:
Add a Set Data Value extension scoped to the Tealium Collect tag to set the variable
ga_cid to the GA first-party visitor cookie with the leading part removed. This allows AudienceStream to identify the same user as the tag.
The code snippet is:
The first step is to create the event and visitor attributes to capture the client ID coming in from the Tealium Collect tag.
Next, create the Google Analytics connector.
Depending on the nature of your use case, you may be able to reuse the same custom dimension for multiple audiences, as long as the audiences are mutually exclusive (for example, a progression). If they are, then you can duplicate step 3 above for each audience involved. If they are not, then you probably want the GA custom dimension to be set to a different value when the visitor leaves the audience. In this case, duplicate step 3, but set the Trigger to “Left Audience”
You do this under in the Admin section of Google Analytics under “Audience Defintions, Audiences”
This can be done using Charles Proxy or a similar tool. You need to be able to see the cookies that are set and sent (Chrome Dev tools no longer shows you this in all cases). The chain of redirects below is an example. Your exact behavior might be different, but the important thing is that redirects are happening.