Attribution Methods Across InOne

Prev Next

Attribution methods and frameworks show us how we calculate the output of any campaign (e.g., an OnSite campaign, a Web Push notification, an App Template, an App Push, an Email, an SMS, a WhatsApp message, or an Architect journey). This guide aims to provide a general terminology and to answer the following questions:

General Terminology

Attribution TypeAims to show whether a product uses a view-through, click-through, or unique revenue method of attribution. It is mainly concerned with what action the user has to take in what duration, so the campaign has the revenue attributed to it.
Re-eligibility DurationRe-eligibility Duration refers to the time interval after which a user becomes eligible again to be assigned to a variant group of the same campaign. Re-eligibility is triggered based on user interaction, not just by viewing the campaign. If a user sees a campaign but does not click or close it, they might still see the same variant again in later sessions, even before the re-eligibility duration ends.
Goal Conversion DurationThe time interval starts after a user interacts with a campaign for the first time. This interaction can be viewing or clicking a campaign based on the attribution type set for conversions. During the time interval you set, when your goal is achieved, the campaign will be logged as a conversion.
Re-eligibility Duration After ClickIs used in cases where the user viewed the campaign and clicked on it but did not close the campaign.
Re-eligibility Duration After CloseIs used in cases where the user viewed the campaign and closed it.
The attribution model does not have attribution between channels. For example, if a user clicks an Email and a Web Push notification in the same duration and makes a conversion, the conversion is attributed to both the Email and the Web Push notification.

Only in Architect, the last click is attributed to the last channel activity. Also, no attribution happens between journeys. For example, if a user receives an email from Journey A and receives another email from Journey B, clicks both emails, and makes a purchase, we see one conversion for Journey A and one conversion for Journey B.
Read more on Goal Durations.

How do re-eligibility durations work (view options)?

The diagram below shows the campaign eligibility (re-eligibility) duration, re-eligibility duration after click, and re-eligibility duration after close. These durations apply to the OnSite products.

  • If a user views a campaign but does not interact with it, the same variant may still be shown to the user in future sessions.
  • If a user views a campaign and clicks but does not close it, the "re-eligibility duration after click" setting is applied.
  • If a user views and closes a campaign, the "re-eligibility duration after close" setting is applied.

How does Goal Conversion work (goal attribution window)?

The diagram below shows an example of a goal duration or attribution window. 

  • The user views the campaign and makes a purchase.
  • The user views the campaign, clicks it, and makes a purchase.
  • The user views the campaign, closes it, and makes a purchase.

In the above cases, the revenue is attributed to the campaign if the attribution window includes all the steps passed through (between view and purchase events).

Overall Revenue Uniqueness & Cross-Campaign Attribution

The following table summarizes whether each product attributes conversions across campaigns and whether revenue shown on the product’s Overall Analytics page is unique (de-duplicated).

ProductIs there attribution among campaigns?Is the revenue in overall analytics unique?
SMSLast clickYes
WhatsAppLast clickYes
ArchitectJourneys: No
Channels: Yes (Last click/view)
No
EmailNoYes
OnSiteNoYes
App PushNoYes
App TemplatesNoYes
Web PushLast clickYes
Smart RecommenderLast clickYes
Eureka-Yes
While some products (e.g., Email, OnSite, App Push, App Templates) may attribute the same purchase to multiple campaigns at the campaign level, they still display unique conversions and revenue on their Overall Analytics pages.

What are the default re-eligibility durations for Insider products?

OnSite Products

You can customize the re-eligibility and goal conversion durations for each OnSite product, template, and campaign as per the following methods:

  • Session-based duration: If the session ends, the user can still view the campaign; however, their actions will not be counted as a goal conversion.
  • Day-based duration: User actions are counted as a goal conversion within the defined day interval.

OnSite products utilize both view-through and click-through attribution, depending on the selected goal.

  • If the goal is Purchases, the goal conversion is tracked based on view-through attribution.
  • If the goal is Purchases from Clicks, the goal conversion is tracked based on the click-through attribution.
By default, the re-eligibility of a campaign is based on the number of views the campaign receives.

Messaging

Re-eligibility is not applicable to most messaging products as they are single campaigns, and users will not be exposed to them for an ongoing duration.

ChannelsCampaign Re-eligibilityDefault Re-eligibility DurationGoal Conversion DurationDefault Goal Attribution WindowAttribution TypeClick Attribution Window
Email--Customizable7 days after clickClick-through-
SMS--Customizable14 days after clickLast Click-
WhatsApp--Customizable14 days after clickLast Click-
Web Push--Customizable14 days after clickLast Click-

Conversions for Web Push, SMS, and WhatsApp campaigns are attributed using the last-click model. This means that only the last eligible campaign clicked within the attribution window will receive credit for a conversion.

- If a user clicks multiple campaigns across Web Push, SMS, or WhatsApp before making a purchase, the conversion will be credited only to the most recent eligible campaign.
- If no campaign qualifies within the attribution window, the conversion will not be attributed.
Note: Attribution works within each product (Web Push, SMS, WhatsApp) separately. There is no cross-product attribution. For example, a WhatsApp campaign and an SMS campaign do not affect each other. However, multiple WhatsApp campaigns can influence attribution among themselves.

The default re-eligibility duration applies only to Trigger Web Push. It is 14 days by default and can be customized.
The Email channel uses two types of attribution: Click-through and the last click model. The revenue is tracked based on click-through model for individual campaign analytics, while the revenue is attributed based on the last click model for overall email analytics. The overall revenue is tracked based on the last campaign the user clicked before their purchase. Thus, the overall revenue becomes unique. Read more on Email Conversion Tracking.
To track conversions, Email campaigns require a click event after the user opens the email. The goal conversion duration starts when the user clicks the link within the email content, but not after they open the email.

Mobile Products 

The table below displays the details of the re-eligibility and goal conversion for the mobile products.

ChannelsIs Campaign Re-eligibility customizable?Default Re-eligibility DurationRe-eligibility TypesIs Goal Conversion Duration customizable?Default Conversion DurationAttribution TypeDisplay Options
One-Off PushesNo--Customizable6 hoursView-through & Click-through-
Automated PushesCustomizableClosedAfter ViewCustomizable6 hoursView-through & Click-through-
App Templates & SurveyCustomizableClosedAfter ViewCustomizableSession-based & Duration-basedView-through & Click-throughCustomizable
App SurveyCustomizableClosedAfter ViewCustomizableSession-based & Duration-basedView-through
Customizable
The re-eligibility duration is disabled by default. If enabled, the default value is set to 1 hour. However, the duration can be customized with daily or hourly values.

You can use the Display Options, App Templates, and App Survey to configure delay duration, recurring display rules, priority, and frequency capping to show your campaign in a single session.

Smart Recommender

Smart Recommender has different attribution models for the OnSite Analytics and Smart Recommender Analytics pages.

OnSite Analytics Page

The attribution model on Onsite Analytics acts similarly to the model of the Onsite products. This page focuses on the overall performance of the launched Smart Recommender campaigns. The metrics are attributed to the campaigns. For example, revenue is attributed to the campaign if a user purchases any item after viewing the Smart Recommender campaign.

Smart Recommender Analytics Page

This page aims to measure the performance of the recommended products and algorithms. That's why the metrics are attributed to the products. Campaign performance is tracked based on a product level. For example, the revenue is attributed to the campaign only if a user purchases a product recommended in the campaign.

All metrics are based on a 7-day cookie duration. This means that once a website user views and clicks on a product from the recommended products, tracking begins with this click event. If the user views and clicks a product, and makes a successful purchase within the next 7 days after this click event, this transaction is counted as a conversion.


Attribution TypeCampaign Re-eligibilityDefault Re-eligibility DurationRe-eligibility TypeGoal Conversion DurationDefault Goal Attribution WindowGoal Conversion Window starts with
Onsite AnalyticsView-through & Click-throughCustomizableSession-basedAfter view, After click, After closeCustomizableSession-basedImpression
Smart Recommender AnalyticsDirect Click-ThroughCustomizableSession-basedAfter view, After click, After closeCustomizable7 daysViewable impression
Both analytics pages consider impressions for the goal conversion attribution windows. However, the impression is tracked differently for each. Once a user views the page where the campaign is located, this view is counted as an impression for OnSite Analytics. However, the user must see the Smart Recommender campaign in their viewport for the view to be counted as an impression for Smart Recommender Analytics. The latter is a more discrete measure of whether an end user actually sees a given campaign.
- View-through is a successful purchase within a defined timeframe after a user is exposed to a campaign.
- Click-through is a successful purchase within a defined timeframe after a user is exposed to a campaign and clicks it.
- Direct click-through is a successful purchase within a defined timeframe after a user is exposed to a Smart Recommender campaign, clicks it, and purchases the item they click in the Smart Recommender. Direct click-through is used only in Smart Recommender Analytics.

Architect

The Architect has a journey-based attribution model with multiple channels and touchpoints with users. It offers two attribution models:

  • Last Click Attribution for Click-through Report Type: Conversion is attributed to the channel/campaign that the user clicked last, provided the attribution window has not yet passed. Click actions are taken into account for Email, Web Push, SMS, WhatsApp, App Push, In-App, and OnSite channels.
  • Last View Attribution for View-through Report Type: Conversion is attributed to the channel/campaign that the user viewed last, and the attribution window hasn’t passed yet. This view corresponds to different actions for each channel: Open for Email, Open (Read) for WhatsApp, View (Delivered) for Web Push and App Push, Delivered for SMS, View (Impression) for InApp and OnSite.

When you visit any analytics page, you will see Click-through Report Type metrics by default. You can change it from the dropdown at the top.

You can set different attribution windows for view and click-through attribution within the Launch section. The default values are 14 days for click-through and 3 days for view-through. These windows are journey-based.
You can select any event or any attribute change as a conversion goal. The source of the event can be App, Web, or Upsert API. You can define up to 10 goals. While selecting a goal, you can also specify the values of the event parameters of the respective event. The purchase event is tracked by default.
Here are some examples of the conversion goals that you can set: add to cart, sign up, purchase of any items under the Shirts category, purchase of any product more than $100, and SMS opt-in attribute changes from false to true.
You might find the following pages useful: User Eligibility, Journey Goals, Architect Analytics Dashboard.