MetaKeys in the Application

It is possible to create a MetaKey type in the UI as part of configuring a Signal, but the scenarios where you want to do that are rare.

In almost all cases, you will create the MetaKey types with the API as part of setting up events. Application users will see evidence of MetaKeys, but they don't create, manage, or delete them through the UI.

The following sections show you where you see MetaKeys in the application.

Company Profile

Use these steps to see the Company ID MetaKey on the Company Profile:

  1. Go to the CSM Workspace and open the Company whose MetaKey you want to view.
  2. Click the Company name in the upper left-hand corner.

The Company profile appears:

The CompanyID MetaKey for this Company appears under the MetaKey heading on the left. Below that are the AltKey types available for this company and their values. If you have combined this Company, then you can see the CompanyID MetaKey values for the combined Companies under the Other MetaCX IDs heading by clicking Show All Identifiers.

Signals Setup

When you're on the Fields step of creating a Signal, you see both AltKeys and MetaKeys.

The event fields that come into a Signal can be named anything. For example, every one of your business systems could name the ID field CompanyID. As shown above, though, it's essential to know which system's Company ID the data contains in order to find the correct mapping in the mapping table.

To prevent mix-ups, MetaCX does not attempt to guess or match the field names with an AltKey. Instead, you explicitly define which product's AltKey the ID field maps too. To help you make sure you're choosing the right AltKey, the screen shows the MetaKey that the AltKey maps too.

If the AltKey that you're mapping to doesn't yet exist, you can configure the Signal to a new one here. In the rare case when neither the AltKey nor the MetaKey yet exist, you can configure the Signal to create a new one of those as well.

Important: Use the new MetaKey option with caution! You cannot map existing records to a MetaKey that you create this way. If you have existing records related to an entity represented by this kind of MetaKey, use the API instead.

Dimensions Explorer

If you create a Metric using Signals with more than one MetaKey, then you can use the Dimension Explorer to pivot the data in the Metric based on those MetaKeys.

For example, you might set up a MetaKey to identify users and another MetaKey to identify device types (laptop versus mobile). When looking at the login Metric for a Company, you view the Login data by user, and pivot the data to see it by device type.

- Next in this series 'Creating MetaKeys with the API'

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.