Overview

Sona's Attribution Reporting settings tell Sona which data defines a customer and where revenue comes from. These two definitions anchor every attribution report, so setting them once means every downstream report counts customers and credits revenue the same way. This guide walks through each part of the page: the Customers definition, the Revenue definition, the conditions that narrow each one, and calculated metric columns.

When to use Attribution Reporting settings

Use Attribution Reporting settings when you need to:

Tell Sona which data source and identifier represent a customer.
Choose the timestamp that marks when a record became a customer.
Point Sona at the field that holds revenue, and the date that revenue should be attributed to.
Narrow either definition so only a subset of records counts.
Derive custom report columns such as ratios, blended costs, or ROAS.

Prerequisites:

Access to Workspace Settings in Sona.
At least one connected data source or report that contains your customer and revenue records.

Getting to Attribution Reporting

Open Workspace Settings.
Select Attribution Reporting in the settings sidebar.
The breadcrumb at the top of the page confirms you are on Workspace Settings › Attribution Reporting.

Note: View Setup Docs in the top right opens the full setup documentation in a new tab.

Step 1: define your customers

The Customers card defines how Sona identifies and counts customers. It has three fields:

Data Source: the report or connected object that holds your customer records.
Customer Identifier: the field that uniquely identifies a customer, such as Email.
Customer Timestamp: the date field that marks when the record became a customer, such as Became a Customer Date.

Pick an identifier that is present and consistent on every record. If the identifier is missing or formatted differently across sources, records will not join to the same customer.

Step 2: define your revenue

The Revenue card configures revenue tracking for attribution. It has four fields:

Data Source: the report or connected object that holds your revenue records.
Customer Identifier: the field used to match a revenue record back to a customer, such as Email. Use the same identifier you chose for Customers so revenue lands on the right customer.
Revenue Identifier: the field that holds the revenue amount, such as Total Revenue.
Revenue Timestamp: the date the revenue should be attributed to, such as First Conversion Date.

Revenue can come from a different data source than customers. The Customer Identifier is what ties the two together.

Step 3: narrow a definition with conditions

Each card has its own definition row beneath the fields, labelled Customers Definition and Revenue Definition. Click Add Condition to limit which records the definition includes.

Conditions are useful when only part of a data source should count, for example excluding internal or test records from your customer count.

Customers and Revenue each have their own conditions, so you can filter one without affecting the other.

Step 4: add calculated metric columns

The Calculated metric columns section lets you derive custom columns from your report fields, such as ratios, blended costs, or ROAS.

Click Add Metric to create a column. Once defined, it becomes available as a column in your attribution reports alongside the fields it was derived from.

Saving your changes

Your changes are not applied until you click Save in the bar at the bottom of the page. Because these definitions anchor every attribution report, saving a change updates how customers and revenue are counted across your reporting.

Key concepts and best practices

Define once, report everywhere: the Customers and Revenue definitions are shared by every attribution report. Changing them here changes every report that depends on them.
Match your identifiers: use the same identifier field on both cards so revenue records join to the customers they belong to.
Choose timestamps deliberately: the Customer Timestamp decides when a customer is counted, and the Revenue Timestamp decides which period revenue lands in. Mismatched choices are the most common cause of reports that look off by a period.
Keep conditions minimal: add conditions only to exclude records that genuinely should not count, such as test or internal data. Over-filtering silently shrinks every report.
Review after source changes: revisit this page whenever you connect a new data source or change how your CRM records customers or revenue.

FAQs

What do the Customers and Revenue definitions control?

They tell Sona which data defines a customer and where revenue comes from. Every attribution report is built on these two definitions, so they determine how customers are counted and how revenue is credited across your reporting.

Why does the Revenue card have its own Customer Identifier?

Revenue can live in a different data source than your customer records. The Customer Identifier on the Revenue card is the field Sona uses to match a revenue record back to a customer, so choose the same identifier you used on the Customers card.

What is the difference between Customer Timestamp and Revenue Timestamp?

The Customer Timestamp is the date a record became a customer, such as Became a Customer Date. The Revenue Timestamp is the date revenue should be attributed to, such as First Conversion Date. They can be different fields, and each one controls the period its data appears in.

When should I add a condition to a definition?

Add a condition when only part of a data source should count, for example to exclude internal or test records. Customers and Revenue have separate conditions, so filtering one does not affect the other.

What are calculated metric columns for?

They derive custom columns from the fields already in your reports, such as ratios, blended costs, or ROAS, so you can see a derived figure as a report column instead of calculating it yourself. Click Add Metric to create one.

Workspace Settings: Attribution Reporting