Master Data Management

Knowledge Center > Insights > Developer Reference > Master Data Management

Master Data Management

The quality of analytics data in Insights is only as good as the quality of the data that Insights receives. To avoid duplicate or incomplete data, you should understand master data management in Insights and ensure that data you send to Insights has the expected format. This enables Insights to correctly link together accounts, users, events, and sessions.

Account Data Management

The accounts in your Insights tenant correspond to the customer accounts in your Zuora tenant. For each Insights account, Insights automatically populates standard fields based on the data in your Zuora tenant. For example, the Zuora Account Number field in Insights contains the unique number that identifies a customer account in your Zuora tenant. See Insights Standard Fields for the complete list of standard fields.

You can use the Insights Batch API to send custom account data to Insights. Custom account data can be additional fields, such as engagement metrics, or logs of events that accounts have performed in your application. In custom account data that you send to Insights, you must identify the Insights account that each row of data relates to. Zuora strongly recommends that you use Zuora account numbers as unique identifiers in custom account data that you send to Insights.

See Insights File Format Guidelines for more information about the expected format of custom account data that you send to Insights.

User Data Management

Your Zuora tenant does not contain data about individual users within your customer accounts. This means that you must provide all the user data that you want to analyze in Insights. You can use the Insights Batch API to send user data to Insights.

If you want to send user data to Insights, you must have a authoritative source of data that Insights can create users from. The authoritative source must provide a unique identifier for each user in your application. Additionally, the authoritative source must identify the identify the Insights account that each user belongs to. Zuora strongly recommends that the authoritative source provides a Zuora account number for each user of your application.

Any other user data that you send to Insights must identify users via the same unique identifiers as the authoritative source of user data. This enables Insights to correctly match user data across different sources.

See Insights Standard Fields for information about the standard fields that Zuora can set up as a starting point for tracking user data in Insights. See Insights File Format Guidelines for information about the expected format of user data that you send to Insights.

Last modified

Tags

This page has no custom tags.

Classifications

(not set)