# Does Google's Cookie Blocking Affect my Tracking?

With Google's [Tracking Protection](https://www.performancemarketingworld.com/article/1856390/googles-cookie-kill-off-finally-begins-12-marketing-experts-distorting-metrics-quitting-data-obsession) initiative which aims to restrict certain cookies in its Chrome browser, and Apple's [ITP](https://impact.com/partnerships/browser-news-what-is-itp-2-3-and-google-chromes-latest-on-tracking/) privacy feature doing the same in Safari, you might be wondering how these developments affect impact.com's tracking services. We're here to address your concerns by explaining how these initiatives impact our tracking services and what you can do to prepare for future changes in the world of tracking restrictions.

#### Why are 3rd-party cookies being blocked?

With online data privacy concerns becoming more prevalent, web browser providers are clamping down on cookies to prevent companies from tracking users as they browse the internet. Google Chrome is just one such browser that has introduced the deprecation of 3rd-party cookies. Many affiliate tracking providers traditionally used 3rd-party cookies to track attribution and ensure that partners were paid out for conversions driven. Tracking providers have since come up with new solutions to allow brands to continue tracking affiliate-driven actions.

#### What are 3rd-party cookies?

[Internet cookies](https://www.cookiepro.com/knowledge/whats-the-difference-between-first-and-third-party-cookies/) are files that collect data about a user's online behavior. 1st-party cookies enhance a user's experience on a single site and cannot share data beyond that site. An example in action is when your session is securely saved to a site so that you don't need to input credentials each time you visit the site. The cookie data is stored within the website domain, e.g., *acme.com*, and cannot be accessed outside of that domain.

3rd-party cookies, on the other hand, save data about a customer's activity across sites and share this data with an external entity. An example is when a tracking provider would traditionally track a customer's journey from a partner site to the brand sales page. With Chrome and Safari's restrictions on 3rd-party cookies, tracking providers no longer rely on 3rd-party cookie tracking to trace affiliate attribution.

#### Will this affect my tracking on impact.com?

Fortunately, impact.com no longer relies on 3rd-party cookie tracking with its Universal Tracking Tag (UTT), meaning that Google's latest iteration of Tracking Protection should not affect you.

Google's initiative does however have relevance to us at impact.com, as it illustrates the growing trend of web browsers posing restrictions on online tracking methods, and consequently, the methods available to affiliate tracking providers. To stay far ahead of the trend, impact.com recommends that you use our [server-to-server](https://integrations.impact.com/impact-brand/docs/api-tracking-integration) tracking services instead of UTT tracking (for more information on why to move away from UTT tracking, see the [Intelligent Tracking Prevention Explained](https://app.gitbook.com/s/b2rE79d9UhOKZQLgzSqx/what-would-you-like-to-learn-about/platform-features/working-with-brands/applying-to-brands/intelligent-tracking-prevention-explained) partner-facing doc).

#### Can I test my tracking against Google's restrictions?

Yes, it's possible to test if the absence of 3rd-party cookies hinders you from tracking an action. You can do this by enabling a [Chrome flag](https://developer.chrome.com/docs/web-platform/chrome-flags) and running a test action on impact.com:

{% stepper %}
{% step %}

#### **Step 1: Create a new Chrome profile**

This step protects the privacy of your personal or business profile.

1. Open Chrome.
2. In the upper-right corner of your browser, select your ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1183576591b45997efe4dc81a25024640591d02a%2F245137dc972a7a7f6165b59538fcdbac8fd5bd8fee4ba9f20c1a2982c5b58b57.svg?alt=media) **\[Profile] → Add Chrome Profile**.
3. Select **Continue without an account**.
4. Enter a **name** for your new profile and select **Done**.

   * Optionally, select a **profile photo** and **color scheme** to help you easily distinguish between your Chrome profiles.

   <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-21c7739a9c544ab95655501294ab0b63b31d055a%2F113139a03e3e0131485a95d8c33f09f51d395f2361842a5bb006c6acad1c5eca.png?alt=media" alt=""><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

#### **Step 2: Enable Chrome flag**

This step allows you to test Chrome's experimental feature of 3rd-party cookie phaseout.

1. Ensure that you're in your new Chrome profile, then type the following in the address bar: `chrome://flags/`
2. In the search bar at the top of the screen, type the following: `Test Third Party Cookie Phaseout`
3. Next to the search result, select **Disabled \[Drop-down menu] → Enabled**.
   * A banner will appear at the bottom of the screen prompting you to relaunch Chrome.
4. Select **Relaunch**.

   <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-6c796d137a6c72d74f80be3197011b34399036f3%2Fce71183d2b367c70d798933a95f62e713858a5b89d5ce00c470179d2370f63bc.png?alt=media" alt=""><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

#### **Step 3: Test your integration on impact.com**

This step allows you to test your impact.com tracking integration with the 3rd-party cookie phaseout flag enabled.

1. Reopen your new Chrome profile and sign in to your impact.com brand account.
2. Select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **Engage → Transactions → Test Actions**.
3. On the *Test Actions* screen, select **Start New Test**.
4. In the *Run Test* field:
   * Select **Start test in new window**.

     <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-a15e73a0e0055f350660130fc4038caefb1929dc%2F1f0abeab04938ebc0f6a02b0c8586e54807e6786b8d016f5f624ec8b5dd10324.png?alt=media" alt=""><figcaption></figcaption></figure></div>
   * Complete an action in the test window.
5. In the *Validate Actions* field:
   * Select **View my test action**.
     * If you see an action, it means that your integration supports tracking with 3rd-party cookies disabled.
   * The action should be visible within 30 minutes of running the test. To verify that all the data is correct, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-8ec3e877b1397045c61d394485e72ac4d93120ee%2Fc6ddb46c637059f06e86c790a911217a9428f5c47b5efef046f90555e85b03cd.svg?alt=media) **\[More] → View details**.
   * To change the test action's status from *Pending Validation* to *Successful / Failed*, select **Approve / Reject**.
     {% endstep %}
     {% endstepper %}
