Identity Graph Linking Rules
Introduction
With Adobe Experience Platform Identity Service and Real-Time Customer Profile, it is easy to assume that your data is ingested perfectly and that all merged profiles represent a single individual person through a person identifier, such as a CRMID. However, there are possible scenarios where certain data could try to merge multiple disparate profiles into a single profile (βgraph collapseβ). To prevent these unwanted merges, you can use configurations provided through identity graph linking rules and allow for accurate personalization for your users.
ο»Ώ
Shared device
There are instances where multiple logins can occur on a single device:
- Family computers and tablets: Husband and wife both login to their respective bank accounts.
- Public Kiosk: Travelers at an airport logging on using their loyalty ID to check in bags and print boarding passes.
- Call center: Call center personnel log in on a single device on behalf of customers calling customer support to resolve issues.
More details are available in the product documentation.
ο»Ώ
Demo scenario available in DSN Public projects
The Identity Graph Linking Rules feature has been enabled in all Public project sandboxes. You can review and repeat the following Halliby example in other Public project sandboxes:
ο»Ώ
How do you configure Identity Graph Linking Rules on your Experience Platform sandbox?
1 - Prerequisites
- The feature is currently in Limited Availability. You should verify if your IMS organization is part of this group.
- Ensure the permission "Manage - Identity settings" has been added to your AEP Role.
2 - Configuration Steps
The Luma presets have been updated to support the Identity Graph Linking Rules feature. Changes were made to the AEP schemas and the data collection property template. Below are the steps to configure it on your sandbox:
QUICK SETUP β LUMA BASIC
- Select your Environment and the Luma Basic preset
- Click on Start and enter a Workspace name e.g. Luma Basic - IGLR test
- Note: The name has to be unique, as Data collection does not allow duplicates.
- Once the installation process is complete, click on Close
- Note: Please update the DX Demo Mobile App to the latest version if required: https://dsn.adobe.com/installο»Ώ
EXPERIENCE BUILDER β UPDATE DATA COLLECTION INTEGRATION
- Open the newly created Workspace
- Edit the new Luma Web project
- Navigate to the Integration tab
- Select the suggested data collection property
EXPERIENCE PLATFORM - IDENTITY SETTINGS
β οΈ This feature cannot be disabled once configured.
- Navigate to your sandbox Experience Platform Home screen
- Click on Identities in the menu (Customers > Identities)
- Click on Settings in the top right
- Accept the Limited Availability terms if requested
- In the Person namespaces, check the Email identity type
- Click on Next then click on Confirm
Do you need assistance? Request help here.
4 - Demo flow
- Browse a few pages anonymously
- Go to the registration - to create a profile or sign-in page - to log in with your existing profile https://dsn.adobe.com/web/[project-id]/registrationο»Ώ
- Browse again a few pages while authenticated
- Show John's identity graph ("ECID XXX is tied to John")
- ο»Ώ
- Then go to https://dsn.adobe.com/web/[project-id]/sign-in or register to create a new profile and log in using another email (Jane). DO NOT click log out. If you do, ECID will be reset, and therefore, you cannot showcase feature
- Browse while authenticated
- Show Jane's identity graph ("ECID XXX is now to Jane"), The profile viewer will show updated values against this ECID
- ο»Ώ
- Now the ECID has transferred from John to Jane...but what about the events? who is associated to what event?
Show profile behavior:
- Go to AEP β Profiles and select "No Stich Merge Policy"ο»Ώ
- Go to John's profile - the one you created first in demo part 1 -> you should only see John's authenticated browsing activityο»Ώ
- Go to Jane's profile -> you should only see Jane's authenticated browsing activity - the first event would probably be registration/sign inο»Ώ
- Go to ECID profile -> you should only see unauthenticated activity on ECIDο»Ώ