How to deploy the Tag Manager script - Adobe Launch

To conclude the installation, you need to deploy the Tag Manager script. This consists of adding the script in your Adobe Launch and configuring it.

This guide explains how to deploy the Tag Manager script on your site through Adobe Launch.

Before starting, please make sure the Preload script is in place. The Preload script is used to guarantee that your cookies are always up-to-date when the page loads.

The process

It is assumed that an existing Adobe Launch implementation is in place on the website and configured as required: https://docs.adobe.com/content/help/en/launch/using/intro/get-started/quick-start.html

1. Create Adobe Launch rule

Once logged into your Launch Property, create a new Rule by clicking "Add Rule" under the Rules tab. 

Give the Rule a name, e.g. "Cookie Saver".

In the Events selection, select "Core - Library Loaded (Page Top)". 

For the Actions selection, choose "Custom Code".

In the Action configuration for your Custom Code, select "Execute globally" in order for Cookie Saver to function properly. 

Give the Action a name, e.g. "Cookie Saver script".

In the code section of your Custom Code action, insert the Cookie Saver code that can be copied from your Cookie Saver account. See Cookie Saver scripts.

Note: Remember to remove the comments and <script> tags (or select HTML when configuring the Custom Code action).

2. Configure, add cookies and deploy

Immediately following the Cookie Saver script, initialize, add your cookies and start the service.

If you need only a very basic configuration, please, check out our ready-for-use quick start code. Otherwise, we recommend you to proceed as described.

First, Cookie Saver should be configured to your domain. In most cases, the following will suffice:

acq("init", {
    "endpoint": "INSERT ENDPOINT"
});

 Where:

• "endpoint" is the NS domain that you have chosen to use with Cookie Saver (e.g. for cookiesaver.io we have chosen to use fpc.cookiesaver.io).

More information on the initialization can be found here. 

At this point, cookies can added one-by-one. In most cases it is enough to add the name of the cookie and the wanted expiration.  

acq("addCookie", {
    "name": "INSERT COOKIE NAME",
    "expirationDays": INSERT EXPIRATION DAYS
});

Where:

• "name" is the exact cookie name (e.g. for Google Analytics its "_ga")
• "expirationDays" is the wanted expiration in days. E.g. for Google Analytics its two years, equal to 730 days.

If you are struggling with this step, you can read more about different configuration possibilities when adding cookies. 

If you have no idea about which cookies to save, you can start by identifying which cookies that have been affected by ITP. You can also read more about how to configure and add platform-specific cookies. E.g. Google Analytics cookies, Facebook cookies, and Google Ads cookies.

Lastly, after you added the cookies that should be saved, the script should be started by adding the following:

acq("start");

Complete example

This is what a complete configuration can look like when including cookies for Google Analytics (_ga), Adobe Analytics (AMCD_DE7...), Facebook (_fbp, _fbc) and our Cookie Consent.

What´s next?

Congratulations! You have now completed the installation and should have Cookie Saver up and running. 

Validation

As a last step, you may want to check that everything is working correctly and implemented lawfully. To do so, please, visit the Validation section.