Identity Graph Resolution Linking Rules

[#1]

Objective of improvement:

When two users share the same device and the Identity Graph Linking Rule is applied, let the anonymous browsing events associated with the same ECID be assigned to both profiles, rather than only the last one identified.

Context:

• Applicant: The PL market, which seeks to implement specific use cases for SME.
• Example of use case:

• Offer leasing products or benefits by opening SME accounts to sme and/or individual profiles, if during anonymous browsing the user shows interest in SME products.

Current situation:

1. A user in Poland can have two profiles:

• Individual profile: customer_id=111, customer_type =ind (example).
• SME Profile: customer_id=222, customer_type=sme (example).
• Both profiles share the same ECID, as it is the same person using the same device.

1. Current problem with Identity Graph Linking Rule:

• Public browsing events generated with the same ECID are assigned only to the last identified customer_id.
• This means that:
• If the public browsing event is the trigger, only the customer_id of the most recently logged in client will be impacted.
• Public browsing events are assigned exclusively to that customer_id at this point, which makes us lose the opportunity to contact the other profile.

In order to impact both users, we need the ability to assign public browsing events to both profiles.