The following are the steps to identify the visitors who visit your website from first-party cookies:

• Identifying visitors through a unique ID
• Sending the unique ID information to CDP
• Sending a customer feed with various customer attributes

Identifying visitors through a unique ID

If a visitor lands on your website from an external source, the source must send a unique ID for that visitor to your website. This can be sent in the redirect URL, cookie value, or any other web pass mechanism. You must store this unique ID on the website and persist it across the session cookie. Acquia recommends that you persist the unique ID information for a browser session.

Sending the unique ID information to CDP

After you receive the information from the external source, you must forward the same to CDP through the CDP WebTag library or DW Tracker API. CDP identifies the website visitors by leveraging this data. You must pass the unique identifier in the payload of the HTTP call based on the authentication status of your website visitor.

User is logged in to your website

customer:

{

SourceCustomerNumber: <Unique ID linked to the email value. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

UUID: <Unique ID. For example, 12345.>

Email: <Email used by the visitor to log in to the website. For
example, [email protected].>

*Other data points in this object remains same as desired*

}

event:

{

SourceCustomerNumber: <Unique ID linked to the email value. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

Email: <Email used by the visitor to log in to the website. For
example, [email protected].>

*Other data points in this object remains same as desired*

}

User is not logged in to your website

customer:

{

SourceCustomerNumber: <Unique ID. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

UUID: <Unique ID. For example, 12345.>

*Other data points in this object remains same as desired*

}

event:

{

SourceCustomerNumber: <Unique ID. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

*Other data points in this object remains same as desired*

}

Sending a customer feed with various customer attributes¶

The external source integrated with your system must send a customer feed with all the desired customer attributes. This helps CDP to build the customer profile. CDP can link the behavior from the website to the customer profiles built through the customer feed.

Sample explanation¶

Let us assume that CDP receives the following values:

CDP maps the preceding values from Customer feed - External Source to both SourceCustomerNumber and UUID.

This results in the following customer summary record:

First-party visitor identification

customer:

{

SourceCustomerNumber: <Unique ID linked to the email value. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

UUID: <Unique ID. For example, 12345.>

Email: <Email used by the visitor to log in to the website. For
example, [email protected].>

*Other data points in this object remains same as desired*

}

event:

{

SourceCustomerNumber: <Unique ID linked to the email value. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

Email: <Email used by the visitor to log in to the website. For
example, [email protected].>

*Other data points in this object remains same as desired*

}

customer:

{

SourceCustomerNumber: <Unique ID. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

UUID: <Unique ID. For example, 12345.>

*Other data points in this object remains same as desired*

}

event:

{

SourceCustomerNumber: <Unique ID. The format
of this parameter varies for each tenant. For example,
360profile_customer_13.>

*Other data points in this object remains same as desired*

}