This document provides answers to frequently asked questions about the Adobe Experience Cloud Device Co-op end-of-life (EOL) plan. When this plan goes into effect, Adobe will provide an advanced notice in the Experience Cloud release notes and the Priority Product Update.
The following is a list of answers to frequently asked questions about the Device Co-op EOL plan.
The upcoming changes in the AdTech environment are expected to result in Device Co-op becoming an obsolete solution in the coming years. Device Co-op is comprised mostly of third-party cookies and Google’s announcement that they will be blocking third-party cookies on Google Chrome by 2022 will diminish the effectiveness of Device Co-op. Chrome has ~65% of the browser market share and other major browsers have already implemented blocking of third-party cookies. Once Chrome blocks third-party cookies, the majority of third-party cookies will be blocked and Device Co-op will be rendered obsolete.
Sign-ups are ending to prevent risks of not meeting customer expectations due to the upcoming industry changes around third-party cookies. Device Co-op takes a few months to be prepared and another few months to extract value from the service. Any further sign-ups at this point could result in brands not experiencing the full value of Device Co-op.
Starting June 11, 2021, Adobe will no longer accept new sign-ups to Device Co-op.
Starting June 11, 2021, Adobe will no longer renew Device Co-op contracts. If you wish to continue using Device Co-op services, you may continue to do so under the current license terms until the program ends.
The Device Co-op program will end in 2022. The specific timing and date depends on when Google starts to block third-party cookies.
The following applications will be affected by the Device Co-op end of life procedures:
Audience Manager maintains integrations with third-party device graph partners including LiveRamp and Tapad, although you must establish commercial relationships with graph partners directly, in order to leverage Audience Manager.
There are no plans to modify the current Audience Manager Data Management Platform (DMP). However, the deprecation of third-party cookies will likely create scale challenges for most DMP users. To help customers evolve their data management practices, Adobe is encouraging the reduction of dependencies on identifiers that will face restrictions in the coming year. Marketing teams must build first-party data strategies focused on durable identifiers that include personally identifiable information (PII), which can be solved for with Real-time Customer Data Platform (Real-time CDP).
Real-time CDP reduces dependencies on third-party cookies and device IDs by expanding the set of identifiers available for audience creation to include PII. Foundational to Real-time CDP is Real-time Customer Profile, which brings together person attribute data with behavioral data in real-time and allows marketers to create rich audience segments with patented data governance controls. Like Audience Manager, Real-time CDP powers insights and personalization use cases, but also generates more granular person-level insights and can activate audiences to a broader range of destinations spanning advertising technologies and marketing technologies, including paid media, social media, email, and customer systems.
Real-time CDP will also include access to Adobe Experience Platform Segment Match (Beta), which allows brands to expand their own first-party data sets through partnerships and achieve improved insights and personalization.
There are currently no alternatives available for Target because Target provides a deterministic cross-device identity stitching capability known as
mbox3rdPartyId, which functions similarly to Adobe’s Customer ID. This capability allows Target customers to merge profiles and activity participation across Target tests and personalization being done in inbound channels.
Advertising Cloud customers will no longer be able to use Device Co-op for cross-device audience targeting and measurement. With Advertising Cloud, you will still be able to leverage Adobe’s Device Graph partnership with LiveRamp to continue to perform these functions to the extent of LiveRamp’s ability and scale. You must allow your campaigns that are using Device Co-op to end, and then either switch to the LiveRamp device graph provider, or no longer leverage people-based targeting.
Your existing Visitor ID Service implementation powers Analytics CDA. If your existing declared ID is a hashed email, this can be used to power the following capabilities:
For Audience Manager and Advertising Cloud users, the data from Device Co-op will not be available to be transferred to third-party graphs. Device Co-op data will only be migrated for Analytics Ultimate users using CDA with Device Co-op switching to Field-Based Stitching. All other solutions will not have their data migrated.
While adoption of other Adobe features is not mandatory, you should start the implementation of other features as soon as possible to allow time and appropriate coordination in advance of Device Co-op deprecation.
Adoption of other features is not mandatory. It is only recommended should you wish to continue addressing use-cases that were addressed by Device Co-op. If you choose to adopt other features, you must do so by 2022 (exact timing to be announced) before the Device Co-op program ends.
This will depend on the feature. For example, if an Analytics Ultimate customer using Cross-Device Analytics with Device Co-op needs to migrate to Real-time Private Device Graph or Field-Based Stitching, adoption will take some time.