Analytics Settings

​

Overview

The Analytics Settings page lets you configure attribution, personalisation exposure and custom tags for your company. Use tags to qualify Branches and segment Analytics. Access it from the Settings link in the Analytics sidebar navigation.

​

Attribution

Attribution decides how much revenue your Reelevant workflows helped generate. Here you choose the model, the lookback windows, and the data source. See Attribution for a full explanation.

​

Attribution model

The model decides how credit is shared between the interactions that led to a purchase.

​

Lookback windows

The lookback window is the time before a purchase during which an interaction can earn credit. You can set a different window for each interaction type.

​

Configuring attribution

1. Navigate to Analytics > Settings.
2. Choose an attribution model.
3. Set the lookback windows for each interaction type.
4. Choose your data source (web tracking or customer purchases).
5. Click Save.

​

Personalisation exposure

These two thresholds decide which customers count as personalised in the Customer Impact dashboard. That dashboard and Adoption are both in beta and enabled on request, so you may not see them yet. Customers above zero but below these thresholds count as neither personalised nor non-personalised. They stay out of the comparison.

1. Navigate to Analytics > Settings.
2. Scroll to Personalization exposure on the General tab.
3. Set the two thresholds, or leave them empty to keep the defaults.
4. Click Save changes.

​

Tags

Tags give each Branch controlled labels that your team can use consistently across Workflows and Analytics. Each tag contains a tag key (the label to organise) and a list of values. For example, Campaign objective can contain Acquisition and Retention. Only custom tags appear in this tab. Reelevant-managed tags are not editable.

​

Understand cardinality

Cardinality controls how many values from one tag key can be assigned to the same Branch. It does not limit how many values you create. Most downstream means closest to the Output Node. Imagine one Workflow qualifies Campaign objective: Acquisition before a second Logic Node. A later qualification on the same final Branch assigns Campaign objective: Retention. Analytics uses Retention because it is closer to the Output Node. With Multiple cardinality, both values remain attached to the final Branch.

​

Create a tag key

1. Navigate to Analytics > Settings.
2. Select Tags.
3. Click Add tag.
4. Enter a unique Name.
5. Add an optional Description to help teammates use the tag correctly.
6. Choose Single or Multiple under Cardinality.
7. Click Create tag key.

Tag key names must be unique. The platform ignores capitalisation and leading or trailing spaces when checking names.

​

Add values

1. Find the tag key.
2. Click the plus icon beside Values.
3. Enter a unique value name and an optional description.
4. Click Add value.

Value names must be unique within their tag key. You can expand Values to review every available choice. The platform also ignores capitalisation and leading or trailing spaces when checking value names.

​

Edit or delete tags

Use the pencil icon to change a tag key, its description, or its cardinality. Expand Values, then use each value’s action icons to edit or delete it.

​

Use tags in Workflows and Analytics

Created tags become available when you qualify a Branch. Users select controlled values but cannot create new ones there. In Analytics, use tag keys and values to filter results or compare performance across your qualification choices.

​

What’s Next?