Identity graph linking rules - Identity settings

Transcript

Hi, I’m going to show you how to enable identity graph linking rules in your sandbox. This feature helps data architects build quality identity graphs and customer profiles for Adobe Experience Platform applications like Real-Time Customer Data Platform, Journey Optimizer, and Customer Journey Analytics. I’m going to make a few assumptions. One, you already know how profiles are constructed from profile fragments and identity graphs. Two, you have permission to view and modify identity settings. Three, you’ve reviewed the other videos and documentation of the feature, and understand its impact on the formation of real-time customer profiles. Four, you’ve already experimented with this simulator to come up with rules appropriate for your platform implementation. You should have all of your namespaces and know their priority order, and know which ones need to be unique. You might want to keep the list handy in a separate document. Once you’re good with those four things, you’re ready to activate your rules in a sandbox, which I will now demonstrate. Navigate to Identities from the left navigation and select Settings. Here’s where you can sort your identity namespaces in priority order and choose the Uniqueness settings. Custom namespaces default to the top of the list. You can drag the namespaces up and down to reorder them in priority order. Check the Unique per graph boxes to indicate when each graph should only ever contain one identity value for those namespaces. In general, identity namespaces you can use to identify individuals should be checked as unique. Also, any unique namespaces should be at the top of your list. I don’t use the email and phone number namespaces in my Luma implementation, but they show in the list because they’re out-of-the-box namespaces included in every platform account. If you’re unclear on whether or not you actively use a namespace, review the Identity Count by Namespace report in the Identities dashboard. Device and Cookie namespaces display in this second section. These namespaces can’t be unique because it’s normal for profiles to have multiple device and cookie ID values. For example, if I log into your website from my work and home computers, I would have two ECIDs, one for each web browser. Again, all namespaces, including out-of-the-box namespaces you might not use, will appear Changing the priority of these device and cookie IDs impacts how the profile fragments of anonymous events are stored in the profile. Most of you will be best off by just leaving the default priority settings in this section. Now I’m ready to continue. When you turn the feature on, nothing instantly happens to your existing graphs. But once the settings have initialized, as new events come into the system and those events touch an existing graph, the graph may be split according to your new rules. And of course, brand new graphs will be created following these rules. Existing profile fragments will keep their primary identities, but primary identities associated with incoming experience event profile fragments will follow the rules configuration and use the highest priority namespaces identity as the primary. A good way to monitor the impact of the changes is to use the identity dashboard report, Graphs with Multiple Identities by Namespace. This report is updated every 24 hours, and you should see the number of graphs with multiple identities reduced for your unique namespaces as new events come in and graphs update. Another thing to be aware of, since the whole purpose of the feature is to prevent profiles from merging unintentionally, you should expect to see the number of profiles in your sandbox increase after you enable this feature. You can make changes to your configuration, which will take effect as new events enter the system. There’s no way to turn off linking rules entirely once it’s been enabled in the sandbox, short of resetting the entire sandbox. Once you’ve validated the configuration in the development sandbox, repeat the configuration in your staging and eventually production sandboxes. Thanks and enjoy the feature!