Attribution model

What is attribution model and when to use it

• Attribution is a set of rules that determine whether a target action occurred as a result of marketing campaigns and, if so, which ones.
• A Goal is a desired customer action. Campaigns are launched to increase the performance of this metric. A goal can be set as an order in any status and touchpoint.

Attribution allows you to evaluate the effectiveness of channels and campaigns in meeting your goals, allowing you to make decisions on how to allocate the marketing budget across different activities.

Attribution model

We use the last-non-direct-touch attribution model - the order is attributed to multiple touchpoints based on the last indirect interaction within each channel group (campaigns, website forms and pop-ups, In-App).

Meaning, that If there were several campaign interactions before the order, the order will be attributed to the last campaign within each channel group (campaigns, website forms and pop-ups, In-App) using the following rules:

• Attribution model measures which campaigns the customer clicked last across all communication channels, except for SMS, you can track clicks or deliveries based on the settings.
• The order is attributed to a campaign when:
  • The order matches the settings (status and first action touchpoint) determined by the selected goal;
  • Number of days passed between the campaign interaction and the order first action is less than specified in the attribution settings;
  • There are no other website visits apart from direct ones (entering a link in the address bar or clicking from bookmarks) between the campaign interaction and the order first action.
• Orders are not attributed:
  • To campaigns excluded in the attribution settings;
  • To lead generation forms and pop-ups;

Attribution settings

Go to Settings → System → Goals and attribution settings and ****select tab Attribution:

• Attribution window (1 to 30 days) - maximum number of days between campaign interaction and order first action.
• Do not attribute goals to campaigns - transactional or other campaigns that do not affect conversion rate and should not take over revenue from other marketing campaigns. For example, an SMS with an authorization code at a checkout or double opt-in email.
• Goal settings are on the next tab:

Every project has an automatically created default goal ”Orders” that includes orders in status categories “Placed”, “Paid”, “Delivered” across all touchpoints. You can create up to 5 goals selecting the desired category status and touchpoints.

Update schedule:

• Last 30 days' data — daily by 09:00;
• Last 2 years days' data — every Monday by 09:00 if a new goal is created or an attribution is edited.

Where to find attributed revenue

Reports

Attribution allows you to evaluate the effectiveness of channels and individual campaigns in meeting goals, and based on the results - to allocate the advertising budget.

• Goals report - lets you track your goals and the impact of channels on goals. Choose a revenue driver to see the attributed revenue to every channel.

• Campaigns report - ****lets you see how each campaign impacted a chosen goal.

• Website campaigns report - ****lets you see how each notification campaign impacted a chosen goal.

Filters

Filters can be used to select specific orders attributed to campaigns.

• Filter “Associated with campaign”:

• Filter “Associated with flow”:

Export

When you add an attribution flag to the export settings, campaigns that triggered the conversion are added to the file.

Why data from an external analytics system might not match data from Maestra reports

1. The external analytics systems might not account the fact of cancelations and returns of orders, i.e. statistics is generated based on the order value immediately after the order is placed. In Maestra you can configure the exclusion of such orders through setting up goals - in this case they are not included in reports and not accounted in the final revenue.
2. If the loyalty program is connected, you need to compare the amounts that are transferred to Maestra and to the external analytics system: the cost of the order with promotions is transferred to Maestra, other systems may have other settings.
3. If the loyalty program is connected, you need to compare the amounts that are transferred to Maestra and to the external analytics system: the cost of the order with promotions is transferred to Maestra, other systems may have other settings.
4. If the difference is significant, then there may be possible issues in the integration, namely with the installation of the tracker, or fake orders (an order for a large amount of money, much beyond the average check). You need to make sure that Maestra tracker is installed on the website.
5. If there are fewer orders in Maestra than in the site database or transferred to GA, you need to check the integration on the project - that order data that is transferred to GA is transferred to Mindbox, and vice versa. Check that there are no order placements that Maestra does not know about (calls of order placement/change operations are not transferred to the project), for example, the order placement comes from a popup, data is transferred to GA, but the operation for data transfer to us is not configured.
6. In Maestra, you can limit the attribution window - orders that are placed after a specified number of days will not be included in the campaigns' report. An external system may not have such restrictions or they may have other values.