Customers

Customers and their events are the principal entities around which Exponea's tracking and analysis capabilities are built. You can learn the basics about these entities in the Customers and events article.

This article will explain how to access the single customer view in Exponea and the accompanying features for managing your customer database.

Accessing the database and basic features

To access your customer database, go to Data and Assets > Customers. You will see the full list of all your customer profiles. Here you can look for a specific customer using the search function or by using the customer and event filter. The search function will only search through attributes that are visible in this list view. You can edit which attributes you want to see and make searchable by clicking on the cog wheel icon in the top right corner of the table.

Download or delete multiple users

You can export the list of all / filtered customers and their selected attributes into CSV by clicking on the three dots in the top-right corner. You will be prompted to select which attributes you want to download.

You can also delete all your customers here. If you want to delete a customer, hover with your mouse over the row with that customer and click on the bin icon that will appear on the very right side. If you want to delete a customer attribute, go to the Data Manager.

Downloading customers for a specific segmentation

If you want to download customers for a specific segment:

  1. Go to the Customers tab. There you can download customers data by default, or you can narrow it down.
  1. To narrow it down by a segmentation, go to add filter condition and click on Customer tab; choose a segmentation you wish to narrow down by, and set a segmentation which you want to download the data for.

Managing customer profile

After clicking on a customer profile, you will open the single customer view. Section "Overview" will be opened, where you can see all the basic information about the customer together with their most important recent actions. Click on the three dots in the top right corner if you want to manually add an event for this customer, download all their data in a JSON format, anonymize or delete the customer.

Overview tab

This section provides you with a basic overview of the user grouped in several sections.

Basic information:

  • Contact information (attributes email, address, and phone are displayed if available)
  • Personal information (attributes gender and birthday)
  • Selected predictions and segmentations (go to the "Properties and events" tab to see all)

Profile

  • Items viewed (count event view_item for the last 30 days)
  • Purchases (count even purchase for the last 30 days)
  • Revenue (count event purchase > total_price for the last 30 days)

Below, you can see additional information, such as the last purchase and campaign received. If you use recommendations and have an active model running, you will also see what products would be displayed to this customer. You can switch between different recommendation models by clicking on its name.

Properties and events tab

On the left side, you can see the full list of identifiers and attributes. In the screenshot above, they are grouped as "Basic information", "Demographics" (and more groups continue out of the picture). This grouping reflects the structure set in the Data Manager, which is completely customizable there. Note that you can also edit the property values for the specific customer when you hover over them. Similarly, the delete button only clears the value of the attribute for that specific customer. If you want to erase a whole attribute from Exponea, you can do so in the Data Manager.

Customers can have various types of attributes (and all of these will be displayed on the left side):

Types of attributes

Identifiers

  • Soft and hard IDs to identify unique customers

Static attributes

  • these are usually set from the SDK or are updated through imports
  • attributes that don't change often (e.g. first_name, last_name, email, subscription status

Aggregates

  • calculated for every customer in real-time from events belonging to a given customer

Segmentations

  • calculated in real-time
  • when customer belongs into a certain segment in a segmentation, the segmentation will be available to use as their attribute

Expressions

  • calculated in real-time
  • these attributes are derived from the existing ones through custom Expressions

Predictions

  • calculated in real-time
  • click here to learn more about predictions.

On the right side, you can see the full history of all events performed by this customer. Click on an event to expand all its attributes and values tracked. You can search by event name using the text search on the right side, or you can use the filters to search for an event using specific criteria.

Consents tab

Here you can monitor and manage consents manually for every customer. Read more in the Managing consents in customer profile guide.

How are customers created

Exponea automatically creates a customer record for every first-time visitor of your website on their device, thereby triggering Exponea's initialization code. This process creates a hard identifier (usually called registered) and an identifier cookie that allows Exponea to track the customer, including their subsequent actions and sessions. The nature of the hard identifier depends on how your project is integrated. It's usually the user's email address or some internal ID your company is using. You can also create new customers by importing them or manually from the customers list view.

There are situations where Exponea creates several customer records for a single customer, for instance, when a customer browses your website using multiple devices. Exponea automatically merges these records when matching identifiers are provided (for example when the customer logs in their account from the other device).

Updated 5 days ago

Customers


Suggested Edits are limited on API Reference Pages

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