Managing Profiles and Integrating Custom Attributes

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください

Overview

The User Profiles and Account Profiles pages contain enriched data on the users and accounts interacting with your product.

These profile pages integrate attributes extracted from collected events with information from third-party sources. Examples of these attributes include a user’s first_seen timestamp and an account’s account_id. Together, they help create comprehensive, centralized profiles.

These enriched profiles enable more precise segmentation and deeper analysis of user behavior, helping you identify patterns over time, track key cohorts (for example, users active after six months), and guide product decisions and engagement strategies.

Profiles

User and account profiles are generated from RUM events collected through the RUM SDK. Use datadogRum.setUser to set user attributes and datadogRum.setAccount to set account attributes.

User profiles are grouped by the user_id attribute, while account profiles are grouped by account_id.

You can also customize these pages by adding attributes that matter most to your team. See the Custom Attributes section to learn how to tailor profile data to your needs.

User profiles

The User Profiles page lists the users who are interacting with your application. You can select a user to view detailed insights into their activity, including their most visited pages, frequent actions, and session history.

A view of the User profiles page.

Use the session history to identify moments of frustration and follow the View Analytics links to explore the related analytics.

Explore the user profiles page and its session history.

Each profile has attributes to help you better segment your users. You can conduct a full-text search or sort and filter based on any of these attributes. You can also customize this page with attributes relevant to your analytic needs. See the Custom Attributes section to learn how.

List of user profile attributes
User ID REQUIRED
type:string
A unique user identifier.
User Email
type:string
The user’s email address.
User Name
type:string
The user’s full name.
First Seen
type:timestamp
The date of the user’s first session.
Last Seen
type:timestamp
The date of the user’s most recent session.
First Seen Application
type:string
The ID of the first application the user accessed.
Last Seen Application
type:string
The ID of the last application the user accessed.
First City
type:string
The city of the user’s first session.
Last City
type:string
The city of the user’s last session.
First Seen Country
type:string
The ISO code of the country for the user’s first session. The country’s code is saved in the backend and the country’s name is displayed in the UI.
Last Seen Country
type:string
The ISO code of the country for the user’s last session. The country’s code is saved in the backend and the country’s name is displayed in the UI.
First Region
type:string
The region of the user’s first session.
Last Region
type:string
The region of the user’s last session.
First Device Type
type:string
The device used in the user’s first session (for example: desktop, tablet).
Last Device Type
type:string
The device used in the user’s last session (for example: desktop, tablet).
First OS Name
type:string
The operating system of the user’s first session (for example: Windows, iOS).
Last OS Name
type:string
The operating system of the user’s last session (for example: Windows, iOS).
First OS Version
type:string
The OS version of the user’s first session.
Last OS Version
type:string
The OS version of the user’s last session.
First Browser Name
type:string
The browser used in the user’s first session (for example: Chrome, Safari).
Last Browser Name
type:string
The browser used in the user’s last session (for example: Chrome, Safari).
First Browser Version
type:string
The browser version from the user’s first session.
Last Browser Version
type:string
The browser version from the user’s last session.

Account profiles

The Account Profiles page surfaces a list of the organizations interacting with your application.

A view of the User profiles page.

Each profile includes four default attributes to help you identify and track account activity over time. These default attributes are:

  • account_id
  • account_name
  • first_seen
  • last_seen

You can customize the Account Profiles page to include additional attributes, giving you the flexibility to tailor the view to your observability and product analysis needs.

Use custom attributes to enrich profiles

Join the Preview!

Custom Attributes is in Preview!

How to configure custom attributes using integrations

Use integrations to automatically import custom attribute data into profiles. This data is synced on a regular schedule, reflecting the latest values from the source system to ensure that profiles remain up-to-date and accurate.

On the Integrations page, you can explore the integrations that are compatible with custom attributes.

On this same page, you can select the Custom Attributes tab to view imported attributes for user and account profiles.

See the integrations that are compatible with Product Analytics.

To import attibutes from an integration such as Salesforce or Snowflake, select the Add Attributes button and choose whether the attributes are for user or account profiles. Then, follow the prompts to:

Add new attributes using to enrich your profiles.
  1. Choose a source of the data to be imported.
Choose a source of the data to be imported.
  1. Select the table containing the desired user data, then select the join keys to merge the table with your profiles.
select the data to be merged with your profiles.
  1. Choose which attributes from the integration to add to your profiles.
Add new attributes using to enrich your profiles.

How to configure custom attributes using reference tables

Importing custom attributes from a reference table follows the same steps as importing from an integration. The exception here is to select the reference table tile in step 1.

Choose the name of the reference table from which to import your data.

How to query your custom attributes

You can filter these custom attributes throughout the product analytics platform without needing to first add them to a segment. For example, you can create an analytics chart to view a time series of all users originating from a specific org_id.

Query your custom attributes in an analytics chart.

Further reading

お役に立つドキュメント、リンクや記事: