For the complete documentation index, see llms.txt. This page is also available as Markdown.

User identity

Decide which identifiers you collect, and therefore when two UserPoints become one person.

Your goal

Choose the identifiers you will send, understand how the platform links them into one view of a user, and know what happens when it gets that link right - or wrong.

Expected outcome

An identity model you can state in a sentence: which identifiers you collect, which of them merge UserPoints, and which registration systems and registries they belong to.

Why this is the decision that matters most

Identifiers do two things at once. They route incoming data to the right user, and they join data that arrived separately.

Consequences follow that are hard to reverse:

  • Any activity or import carrying an identifier is automatically related to the correct UserPoint. An activity using an identifier that does not already exist in the datamart triggers the creation of a new UserPoint.

  • When identifiers show that two UserPoints are the same person, the platform merges them - and a merge is not something you undo.

Identifiers versus content

It matters to distinguish nodes that identify a user from nodes that describe one. These are the types of user identifier:

Everything else attached to a UserPoint - activities, profiles, segments, choices - is describing content. Each of these objects is described in Understand mediarithmics standard objects.

Work through it in this order

1

Understand the graph and how merges happen

Before choosing identifiers, know what the platform does with them.

2

Choose your own identifiers

Account IDs from which systems, hashed emails with which function, which device identifiers.

3

Decide which third-party identifiers you need

Network IDs extend recognition beyond your own identifiers, and each one is integrated through a registry or a compartment.

4

Declaring associations, and knowing what to watch.

The prerequisites this section assumes

Identifiers only work if the container they belong to exists first:

Identifier family
Container
Where you create it

Account IDs, user-based network IDs

Compartment

Device and device-based network IDs

Device registry

Last updated

Was this helpful?