Device registries
Create or subscribe to a registry for every device and network identifier you intend to ingest.
Your goal
Make sure every device or network identifier you are about to send has a registry to be stored in, before the data arrives.
Expected outcome
Each identifier type in your integration is backed by a registry that exists, is linked to the right datamarts, and - where required - is enabled on the channels that will send it.
What a device registry is
In each datamart, all device information is stored in a device graph. Device technical identifiers in that graph are always related to a registry: the place where identifiers of a given kind are stored. Device-based network IDs work through registries for exactly this reason - each device is assigned a registry where its identifiers are kept.
Registries are related to organisations, and are managed in Settings > Organisation > Device Registries.
Registry types
There are several registry types, and what you can do with a registry depends on its type.
INSTALLATION_ID
One registry is created per site on which the installation ID feature is activated.
MOBILE_ADVERTISING_ID
Mobile advertising IDs that can be shared across editors - for instance Android Advertising IDs (AAID) and Apple Identifier for Advertisers (IDFA).
MOBILE_VENDOR_ID
Mobile IDs that can only be shared among apps of the same developer account - for instance Apple Identifier for Vendors (IDFV).
TV_ADVERTISING_ID
Registries referring to smart TVs and TV boxes: AAID on Android TV and Android boxes, IDFA on Apple TV, Amazon Advertising ID on Fire TV, Tizen Advertising ID on Samsung Smart TV, and similar.
NETWORK_DEVICE_ID
IDs that are device-related and managed by third parties - for instance ID5 or First-ID.
CUSTOM_DEVICE_ID
Your own device identifier, for instance a first-party cookie that you generate.
MUM_ID
"mediarithmics User Mapping Identifier". This type and the single registry it contains host the mediarithmics third-party cookie (vector_id) and references to partners' third-party cookies, until their deprecation.
IP_V4_ADDRESS_ID
IPv4 addresses. Can be generated automatically when IP address auto-capture is activated on a channel.
IP_V6_ADDRESS_ID
IPv6 addresses. Can be generated automatically when IP address auto-capture is activated on a channel.
What you can create, and what you subscribe to
Create your own registry
MOBILE_VENDOR_ID, CUSTOM_DEVICE_ID, IP_V4_ADDRESS_ID, IP_V6_ADDRESS_ID
Subscribe to an existing registry
The other types
Nothing to do
INSTALLATION_ID registries are created and removed automatically by the platform
You can set an expiration duration for identifiers stored in registries you created manually. It applies only to identifiers captured after the expiration duration is set.
Set up a registry
Activate ingestion on your channels
Some device registry identifiers require channel configuration updates before tracking with them works properly on your sites. IP address auto-capture, for example, is activated on the channel and generates the corresponding IP registry.
See Channels.
What happens when identifiers meet
When two device technical IDs are associated, their device points are merged. This happens when user activities are captured with multiple identifiers, and when the identifier association feature is used.
If the device points involved are linked to different UserPoints, merging device points also triggers a merge of the UserPoints.
Verify
Every identifier type your integration sends has a registry that exists.
With several datamarts, each registry is linked to every datamart that needs it.
Channels that must send a registry-based identifier have been updated accordingly.
After the first data arrives, device identifiers appear on your UserPoints rather than being dropped.
Related pages
Last updated
Was this helpful?