Personalize onsite experiences for unknown visitors using partner-aided visitor recognition

How to achieve the use case: Step-by-step instructions

Read through the sections below which include links to further documentation, to complete each of the steps in the high-level overview above.

Data management - Create an identity namespace, schema, and dataset to manage data attributes

In preparation for achieving the use case to personalize unauthenticated visitors’ experience, you must first set up the data management structure in Real-Time CDP to receive the incoming real-time event and audience qualification data.

Create Partner ID identity namespace

First, you need to create a partner ID identity namespace. Navigate to Customer > Identities in the left rail and then select Create identity namespace in the upper right corner of the screen.

Read more about how to create a partner ID identity namespace.

Create a schema

Next, create an Experience Event schema to hold the time-series data that you will later be collecting from your web properties, and make sure to use XDM ExperienceEvent as the base class for the schema. Read about how to create a schema using the Experience Platform UI.

As you create your schema and add field groups to to your schema, consider adding the Visit Web Page and Identity Map field groups. This is in addition to other field groups which are applicable to your digital property and data collection practices.

Additionally, you can create or re-use an existing field group and add it to your schema, to capture partner-provided insights about the visitor. Read how to create a field group and how to add fields to the field group. For instance, if you are expecting to personalize against partner-provided insights like age range, employment status, monthly spending power, or buying behaviors, have your field group include appropriate fields.

Assuming that the data partner provides a stable identifier for the visitor and you would like to bring that into Real-Time CDP, be sure to have an appropriately named field for the identifier in your custom field group. You should also mark the field as an identity in the identity namespace you created earlier. Remember also to enable the schema to be included in Profile.

Create datastream

As a first step in the data collection section, create a new datastream. The datastream is the foundation of how data is collected and correctly routed to the right Adobe app, in this case Experience Platform.

As you create the datastream, in the Event schema field, select the schema that you created previously.

Select the event dataset that you created earlier from the dropdown, check the boxes next to Edge Segmentation and Personalization Destinations, and select Save.

Note that you do not have to select a profile dataset in this scenario since you are bringing in event-based time-series data.

Create tag property

Think of a property as a container that you fill with extensions, rules, data elements, and libraries as you deploy tags to your site.

Navigate to Tags and select New property.

Fill in the required fields and select Save.

Get complete information about how to create a tag property.

Next, you must install various extensions within the property. Select your tag property and navigate to the Extensions section.

Notice that the Core extension is already installed. You must install two further extensions, as detailed in the next sections.

Install Web SDK extension

Note that this tutorial indicates how you can instrument your website with Web SDK. You can also use Mobile SDK on your app to personalize the experience to your app visitors.

In the screen to configure Web SDK, navigate down to the Datastreams section and provide information on the Experience Platform sandbox that you are using. Select the appropriate sandbox and the datastream created in the previous steps from the next dropdown. You can choose the same sandbox and datastream values for all other environments. Leave the other settings unchanged and select Save.

Get complete information on how to install Web SDK.

Install ID Service extension

Use the Experience Cloud ID Service extension to create a unique device-based first-party identity for visitors across all Experience Cloud solutions. Search for ID Service in the extension catalog, and install it. Keep all the default settings when installing the extension.

Set up environments

Next, head on over to the Environments section from the left-hand navigation. In this step, you must connect your website to the Adobe Edge Network to retrieve and deliver visitor information in real-time.

Select the box icon on the right for the development environment, and copy the standard version of the JavaScript code snippet that appears in a modal window.

You must add this code snippet to the very top of your website. As a result, your website will make a call to the Adobe Edge Network to retrieve JavaScript logic that will be loaded and executed on the page. This allows for functionality like visitor ID generation, data collection, and real-time experience personalization to work.

Set up data elements

Data elements are the building blocks for your data dictionary (or data map). A single data element is a variable whose value can be mapped to query strings, URLs, cookie values, JavaScript variables, and so on. Read more about data elements.

For the purpose of this use case, you must set up two data elements.

First, set up a partnerData element. Navigate to the Data Elements section and select Create New Data Element.

Name the data element partnerData, leave the extension value as Core, and set Data Element Type as JavaScript Variable. Enter partnerData in the field titled JavaScript variable name and select Save.

To set up the second data element, name the new variable pageVisit, set the Extension to Adobe Experience Platform and choose XDM Object as the data type.

From the schema, select the third-party attributes that correspond to the values that you are expecting from the data partner. Then, select the radio button titled Provide entire object. Select the icon that looks like a database and choose the partnerData data element that you created previously.

Set up rules

In the Rules section, you can configure your website to send a personalization request to Adobe with the attributes loaded into the data elements that you just created. Read more about creating rules.

Select Create new Rule. Name this rule Personalize and select the + sign next to Events. Select Page Bottom as the event and save.

Select the + sign next to Actions. Update the extension to Adobe Experience Platform Web SDK and set Action Type to Send event.

From the Type dropdown selector on the right, select web.webpagedetails.pageViews as the event type.

Select the database icon next to XDM data and select the pageVisit data element.

Scroll down the list of Action configurations and be sure to check the box titled Render visual personalization decisions. This is important to allow experiences delivered via Adobe Target or other similar products to be rendered visually on the web page. Select Keep Changes, and then Save the rule.

Set up publishing workflow

To deploy this configuration to the webpage, the next step is to build a library which includes the resources that you just created. Read more about setting up a publishing flow.

Select Publishing Flow and then Add Library.

Select Add all Changed Resources, give the library a name, set the environment to Development and select Save & Build to Development.