Customer merging is an important feature that allows you to identify a single customer across multiple devices and browsers. When a customer visits your website using their phone and later through a PC for example, Exponea sees this as two separate customers with 2 different cookies. However, once he or she gets identified (after making a purchase or logging in) on both devices, these two customers will then be automatically merged into one, together with all their historic events. An event merge will be tracked. As the record is merged to one profile, duplicate profiles are avoided and instead, you achieve a coherent and reliable tracking of your customers.

Merging rules

  • No two customers can exist with the same hard or soft ID at the same time in the same project.
  • It is NOT possible to merge customer profiles with different hard IDs of the same type.
  • If there is a “clash” of identical soft IDs of the same type in two customer profiles with different hard IDs of the same type, then the soft ID is transferred (or “stolen”) from the “older” profile and will remain only in the “newer” profile. However, historic events are NOT moved from the “older” into the “newer” profile. This ensures the maintenance of your previous customer’s data.
  • Events are moved from source customers to destination customer (who's ID has a lower number and therefore higher priority)
    • Properties from source customers are added to destination customer
  • If destination customer already have property with given name it is replaced
  • The same rule that applies to properties applies also to assigned HTML campaigns
  • Latest communication overwrites the older one
  • Assigned ab tests are merged in reversed order (the ab test from customer with newer (larger) internal ID wins over the older (smaller) one)
  • add_first_session flag is set only if any of the customers has it set to True

'Merge' event

When the customer's IDs from multiple devices finally merge into one customer profile an event 'merge' is tracked with the following properties:

Attribute
Description
Example

source_internal_ids

Internal IDs of merged customers

["58244a8dfb6009d9d3213198", "5820734f83043485f66795eb"]

destination_internal_id

Internal ID of final customer

"5820734f83043485f66795eb"

original_external_ids

External IDs (registered, cookie) of merged customers

{"5820734f83043485f66795eb":{"registered":["bruckner@hu.com"]},"58244a8dfb6009d9d3213198":{"cookie":["c50961e7-9086-4169-8066-1ee47615108b"]}}

final_external_ids

External IDs (registered, cookie) of final customer

{"cookie":["c50961e7-9086-4169-8066-1ee47615108b"],"registered":["bruckner@hu.com"]}

Merging problem

There is a case when wrong people might be merged together. This could happen in the following situation: customers in your project do not have hard IDs. When a Customer 1 comes on to your website on the device of a Customer 2, the system does not recognize Customer 1 as a unique customer. Instead, it sees them as an additional soft ID that will be added to the soft ID of Customer 2. Only one customer profile remains then even though they are, in fact, two unique customers.

You can prevent this problem from happening by setting an email as a hard ID. If for some reason you want to keep email as a soft ID you must set some other hard ID. Thanks to this when Customer 1 comes on the device of Customer 2 the system recognizes that a unique customer (with unique hard ID) comes on the device of another unique customer (with another hard ID) and so the merging does not happen.

If you want to adjust the settings of your IDs you can do so if you have an instance admin access. Go to Administration -> Projects and you can adjust the identifiers.

Merging


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.