Safari Intelligent Tracking Prevention Policy and DYID Retention

About the ITP Policy Issue

The Dynamic Yield script generates and manages a unique ID for each user visiting your website, enabling you to keep track of visitors. This script relies on localStorage and cookies for storing this value on the user's browser. To ensure the continuous valid functionality of Dynamic Yield for users visiting your site via Safari, an implementation adjustment is required on your side as described in the next section.

Apple ITP 2.3, released in September 2019, forces an expiration of 7 days upon third-party cookies and localStorage. Other browsers are likely to follow suit in the future.

If a returning Safari user does not visit your website for 7 days or more, the DYID value stored in the browser expires from both localStorage and the cookie. This prevents Dynamic Yield from accessing this value, and views the user as if they are visiting your website for the first time. The implications include targeting limitations due to historic behavioral data, audience membership data, and affinity data becoming inaccessible to Dynamic Yield.

What you need to do

To overcome this ITP limitation, the DYID cookie must be set by the backend application serving your website on your domain. Cookies set this way are considered first-party cookies, and are therefore not affected by ITP and can have a longer expiration period. 

1. When a user visits your site, a request is sent from the browser to the backend application serving your site. For returning users, the request includes the _dyid cookie (together with all other first-party cookies).
2. Upon receiving this request, within your backend application, duplicate the _dyid cookie value into a new cookie. Use the key _dyid_server and return the new cookie as a response header for this request, setting a 1-year expiration date. This sets the _dyid_server cookie as a server-side first-party cookie in the user’s browser, which is not affected by the cookie expiration enforcement (as recommended by the ITP policy). 
3. Our script then uses the _dyid_server cookie as it runs on your page. As a result, no returning-user data is lost, even if the user has not visited your site for over 7 days.

 The flow:

1. A visitor enters your website.
2. Your server gets a request to return a web page from the browser. Requests from returning users include the _dyid cookie.
3. Your application server does the following steps:
   1. Checks if the _dyid cookie was sent in this request.
   2. If it is, it duplicates it to a new _dyid_server cookie. 
   3. Set it as a response header, with a 1-year expiration date. This sets it as a server-side first-party cookie in the visitor’s browser (the _dyid cookie continues to be returned, this should not change).
4. Your website visitor sees the rendered content of your website.
5. Note that if you have enabled the Active Cookie Consent mode, it is important to wait for the consent object and act upon its result - otherwise, you might write cookies for opt-out users.

How to duplicate the cookie 

Let’s say the value of the _dyid cookie is 7237284912004766755. Duplicate the cookie value into the new _dyid_server cookie, and set the expiration to 1 year by setting 31556951 as the max-age attribute value.

The result would be the following cookie: _dyid_server=7237284912004766755;max-age=31556951

Code examples

As a reference, we’ve added a few code snippets for commonly used platforms and programming languages for implementing this solution. 

>>> curl -v http://yoursite.example.com --cookie "_dyid=-3233584359067736988"                                                                                                                                                                                                                                                                                        19:55:13
*   Trying 172.217.18.4...
* TCP_NODELAY set
* Connected to yoursite.example.com (172.217.18.4) port 80 (#0)
> GET / HTTP/1.1
> Host: yoursite.example.com
> User-Agent: curl/7.64.1
> Accept: */*
> Cookie: _dyid=-3233584359067736988
>
< HTTP/1.1 200 OK
< Date: Mon, 30 Mar 2020 16:55:16 GMT
...
< Content-Type: text/html; charset=ISO-8859-1
...
< Set-Cookie: _dyid_server=-3233584359067736988; expires=Wed, 29-Apr-2021 16:55:16 GMT; path=/; domain=.google.com; Secure

// need cookieParser middleware before we can do anything with cookies
app.use(express.cookieParser());
 
app.use((req, res, next) => {
  if (req.cookies._dyid) { // if this is a returning user and the DYID cookie exists
    const dyid = req.cookies._dyid;
    res.cookie('_dyid_server', dyid, { // store a new server-side cookie named "_dyid_server" with the DYID value
      expires: new Date(Date.now() + 31540000000000), // Set a 1 year expiration for the new cookie
    });
  }
  next();
});

...
dyid_cookie = request.COOKIES.get('_dyid') 
if dyid_cookie is not None: # if this is a returning user and the DYID cookie exists
    set_cookie(‘_dyid_server’, dyid_cookie, 31540000000000) # Store a new server-side cookie named "_dyid_server" with the DYID value
...

<?php
if(isset($_COOKIE['_dyid'])) {
 $dyid_cookie = $_COOKIE['_dyid']; /* if this is a returning user and the DYID cookie exists */
 setcookie('_dyid_server', $dyid_cookie, time() + 31540000000000); /* expire in 1 year */
}
...

Validating the implementation

This procedure checks that a server-side cookie called _dyid_server is created with the same value as the _dyid cookie, but with a one-year expiration date. It can be done on any browser, but we used Chrome in this example:

1. Open a new browser and navigate to any page in your website that has the Dynamic Yield script. 
2. Open Chrome's developer tools (Press Command+Option+J (Mac) or Control+Shift+J (Windows, Linux, Chrome OS). 
3. Go to the Network tab. Click the Preserve Log checkbox and then click Clear ⊘ .
   
4. Refresh the page. Select the first request with the URL of your site (a), and look at the Header tab (b).
   
5. Verify that the value of _dyid_server is the same as the value of dyid.
   The value of the _dyid_server cookie is in the request header. You can also find the value of dyid in the Request Headers section of the Headers tab under "cookie:" (the first field). If the values match, your solution is verified. 
   

Limitation

• Campaign targeting conditions that are based on cookies affected by this update may not function as expected. This includes the New User (first session), cookie, and elapsed time conditions.