Purpose of Declared ID Targeting

Some browsers, and most mobile devices, do not accept third-party
cookies. This makes it difficult to retain information about site visitors or
assign persistent IDs. To resolve this issue, Audience Manager uses DIL to let
you pass in declared IDs on an event call. Also, a declared ID can act as a
universal ID that applies to the same user across all the solutions in the
Experience Cloud. The following table describes the
ID targeting/matching process:

Process

Description

Event Call

To work, you need DIL and the
Experience Cloud ID service code on the page. DIL gets
declared IDs from the
setVisitorID function provided by the
Experience Cloud ID service and passes that on to
Audience Manager.

Match ID

Audience Manager attempts to match the client and visitor ID
with a corresponding ID in our system. If a matching ID does not exist,
Audience Manager creates a new ID and associates it with the client and visitor
ID.

Note: The most recent mapping is used if your ID maps to more
than one Audience Manager ID.

Return ID

Audience Manager writes its synchronized ID to a first-party
cookie (or other addressable storage space) in the client domain or
application.

Subsequent Event Calls

Additional event calls read the Audience Manager ID from the
client's domain and send that to Audience Manager.

To get started, you need to configure the
Experience Cloud ID service and DIL across the pages
on your site that you want to use for data collection. See
DIL create and
Declared ID Variables.

Audience Manager can pass
in a declared ID opt-out alongside an Audience Manager UUID in the URL.

The declared ID opt-out is
stored in the Profile Cache Server (PCS) on a per-partner basis. There is no
platform-level opt-out using declared IDs. Additionally, Audience Manager opts
the user out from that particular region on the edge (the opt-out does not
cross DCS regions).

See
Data Privacy for more
information about opting-out of data collection.

Declared ID Opt-Out Examples

You can make a declared ID opt-out requests with the
d_cid and
d_cid_ic key-value pairs. The legacy parameters like
d_dpid and
d_dpuuid still work, but are considered deprecated.
See
CID Replaces DPID and DPUUID.
In the examples,
italics indicates a variable placeholder.

These methods still work but are considered deprecated. This
information is provided for legacy purposes and reference. Legacy opt-outs
include:

Opt-Out (Deprecated)

Code Sample

d_uuid only

http://domain/demoptout.jpg?d_uuid=AAM
ID

Partner level opt-out

http:///demoptout.jpg?d_dpuuid=user
ID&d_dpid=data provider ID

A partner level opt-out gets stored for the latest mapping
of this
dpid +
dpuuid pair to an AAM UUID. If there is no
previously existing mapping, Audience Manager checks whether the request
contains an AAM UUID in the cookie, and if it does, uses that for storing the
opt-out. Otherwise, Audience Manager generates a new AAM UUID and stores the
opt-out under it.