Step 1: the data foundation
To start using revenue attribution, the source from which the revenue information should be taken must be in place. Here you will need a one-to-many data table that contains data on purchases, subscriptions or other types of revenue.
This table can be setup to fit your organisation’s needs but will have to contain two fields in order for it to be used to calculate revenue attribution:
A field that contains the monetary value associated to the row. This column must be of the type number
A column that contains information on the time of when event associated to the row took place. This column must be of the type timestamp
Step 2: mapping the table
Once the table has been configured with the necessary fields, we need to map the table so that the system knows what to use for the calculation.
Open the revenue table page in settings (Settings → Revenue attribution → Revenue table)
Choose the desired one-to-many table, as well as the fields contain information on time and value
(optional) if you know only select rows added to the chosen table should qualify for revenue attribution, you can create a filter by using conditions to target these specific rows. Rows that do not meet these conditions will not be part of the revenue attribution calculation
Step 3: configuring events and windows
The last part of the setup process is to select what events in which timeframes should have revenue attributed to them.
Open the revenue events and windows page in settings (Settings → Revenue attribution → Revenue events and windows)
Select the events that should qualify for revenue attribution and the attribution windows in which each event is eligible. The attribution window looks back from when the revenue occurred (one-to-many table field mapped to time)
Step 4: gaining insights
Once you have completed the previous steps, revenue will be calculated each time a new row is added to the one-to-many table. You will then be able to see revenue attribution metrics inside the dedicated Flow revenue attribution report and in flow insights.
Note: For an introduction to revenue attribution, see Revenue attribution