ÃÛ¶¹ÊÓƵ

Getting Started with Profile Merge Rules getting-started-with-profile-merge-rules

To create Profile Merge Rules, review and complete the steps in each of the procedures described in this section.

Create a Cross-Device Data Source create-data-source

To create a cross-device data source, go to Audience Data > Data Sources > Add New and complete the steps for each section described here. Administrator permissions are required to create or edit a cross-device data source.

Data Source Details details

To complete the Data Source Details section:

Data Export Controls export-controls

Data Export Controls are optional classification rules you can apply to a data source and destination. They prevent you from sending data to a destination when that action violates a data privacy or use agreement. Skip this section if you do not use Data Export Controls.

Data Source Settings settings

Data Source Settings section provides multiple options, but these 2 are important for creating a cross-device data source:

The text fields associated with these settings let you rename the Data Source with an alias that appears in the Profile Merge Rule options. For example, if you add an alias to Use as Authenticated Profile, that name appears in the Authenticated Profile Options list. If you add an alias to Use as a Device Graph, that name appears in the Device Options list.

Create a Profile Merge Rule create-profile-merge-rule

To create a Profile Merge Rule, go to Audience Data > Profile Merge Rules > Add New Rule and complete the steps for each section described here.

You can create up to 3 merge rules after setting up a cross-device data source. You get access to a 4th Profile Merge Rule (All Cross-Device Profiles) if you sign up for People-Based Destinations.

Administrator permissions are required to create, edit, or delete a rule. All users can view and use existing Profile Merge Rules.

Prerequisites: A cross-device data source is required to build a Profile Merge Rule. See Create a Data Source.

Basic Information basic-info

To complete the Basic Information section:

Data Export Controls data-export-controls

Data Export Controls are optional classification rules you can apply to your Profile Merge Rule. They prevent you from sending data to a destination when that action violates a data privacy or use agreement. Skip this section if you do not use Data Export Controls.

Profile Merge Rule Setup profile-merge-rule-setup

To complete the Proflie Merge Rule Setup section:

Considerations for ÃÛ¶¹ÊÓƵ Campaign Destinations using Cross-Device IDs as User ID Keys considerations

In late 2019, we have release a series of Profile Merge Rules enhancements to improve the accuracy of batch files generated using cross-device IDs. These enhancements will be strictly honored in your Audience Manager instance starting Monday, March 16, 2020. Consquently, segments mapped to a destination using a cross-device IDs will stop producing exports in some Profile Merge Rules configurations.

To ensure the correct integration between your Audience Manager instance and destinations using cross-device IDs, such as ÃÛ¶¹ÊÓƵ Campaign, make sure you meet the following requirements:

Configure Merge Rule Code configure-merge-rule-code

Follow these instructions to set up the ÃÛ¶¹ÊÓƵ Experience Platform Identity Service, DIL, and mobile SDK code to work with your merge rules.

Prerequisites

You must set up a cross-device data source and profile merge rules before completing these procedures.

For ÃÛ¶¹ÊÓƵ Experience Platform Identity Service Customers id-service-customers

The ÃÛ¶¹ÊÓƵ Experience Platform Identity Service and the latest version of DIL are recommended when working with Profile Merge Rules. However, you don’t have to use the ÃÛ¶¹ÊÓƵ Experience Platform Identity Service to work with this feature. If you’re just using DIL, see the legacy DIL section below.

Configure the Set Customer ID Function

When working with the ÃÛ¶¹ÊÓƵ Experience Platform Identity Service, the setCustomerIDs function passes declared IDs to Audience Manager. To use a profile merge rule, you must modify setCustomerIDs to use the integration code specified when you created a cross-device data source. For example, say you’ve created a cross-device data source with the integration code my_datasource_ic. To pass in a declared ID, you would add the integration code to the visitor ID function as shown in the modified code sample below.

Generic code sample

visitor.setCustomerIDs({
  "userid":{
      "id":"12345",
      "authState":Visitor.AuthState.AUTHENTICATED

Modified code sample

visitor.setCustomerIDs({
  "my_datasource_ic":{
     "id":"12345",
     "authState":Visitor.AuthState.AUTHENTICATED

For more information, see Create a Cross-Device Data Source and Customer IDs and Authentication States.

Configure DIL.create function

The latest versions of DIL now automatically pick up the declared ID from the visitorService function in DIL.create (see Declared ID Variables). Check your DIL.create function to make sure this is set up properly as shown in the code sample below.

var vDil = DIL.create({
   partner:"partner name",
   visitorService:{
      namespace:"INSERT-MCORG-ID-HERE"
   }
});

In the namespace key-value pair, the *MCORG* variable is your Experience Cloud Organization ID. If you don’t have this ID, you can find it in the Administration section of the Experience Cloud dashboard. You need administrator permissions to view this dashboard. See Administration: Core Services.

Configure SDKs

See the Configure SDKs section below.

Legacy DIL legacy-dil

If you’re not using ÃÛ¶¹ÊÓƵ Experience Platform Identity Service yet, you really ought to. But, we understand that moving to new code requires careful thought and testing. In these cases, check your DIL.create function to make sure this is set up properly as shown in the code sample below.

DIL.create({
   partner: "partner name",
   declaredId:{
      dpuuid: YOUR_DPUUID,
      dpid: YOUR_DPID
   }
});

For more information, see the legacy DIL section in Declared ID Variables.

Configure SDKs configure-sdks-legacy-dil

Check the methods in your SDK code that let you pass declared IDs from Android and iOS mobile devices. The variable names for the Android and iOS code libraries are the same:

 public static void setDpidAndDpuuid(String dpid, String dpuuid);

 AudienceManager.setDpidAndDpuuid("myDpid","myDpuuid");

See also, and .