Customer ID maps export

This is for:


In this article, we’ll introduce you to our Customer Id maps export and how you can use it to get an insight into the mapping between the Qubit visitor Id and the observed login.

Reporting detail

This export type provides details of the mapping between the Qubit visitor Id and the observed login. If provided in the data layer, this mapping provides the user Id and user email.

As with all Qubit exports, you can specify the level of reporting detail to get a much greater understanding of reportables and focus on the details you’re really interested in.

For this export type, you can select:

  • A date range to include only data covering a defined period of time

  • Exclusion dates to exclude particular days or a period of time from the data

  • Dimensions which allow you to decide how to break down the data


  • To report users correctly, a user event must be emitted for each pageview while the user is logged in

  • User email and Id are taken from the user event (for example, ecUser, egUser, trUser). If email and Id are emitted in view, events, such as ecView, we can also get the data from this event

  • Only logged-in users with a non-null email address or Id are included

  • In the unlikely event that multiple emails or user Ids are associated with the same logged-in user the first time the experience was seen in the date range, we take the first values in ascending alphabetical order

  • Date is based on meta_recordDate, which is in the timezone configured for the property

info-icon Duplicate user and session events account for less than 1% of all user and session events.

Dimensions and outputs


Name Description Output

User Id

The observed user Id for the signed-in user


User Email

The observed user email for the signed-in user



Additional fields not included in the dimensions table above:

Field Description


The Qubit context_id