Home
Offers & Tracking
Attribution Models
Choosing Between First Touch & Last Touch Attribution
Choosing Between First Touch & Last Touch Attribution

SERIES:

Choosing Between First Touch & Last Touch Attribution

This article clarifies the difference between First Touch and Last Touch attribution methods, explaining how each attributes conversions to partners based on the initial or final click (or impression) before a conversion, and details how to configure these settings at both the offer and advertiser levels.

Overview

First Touch and Last Touch are Attribution Methods associated with each Offer. In this article you’ll learn all about their inner workings.

Note First Touch vs Last Touch Attribution only works when using Javascript SDK or HTML Pixel as the Offer’s Conversion Method. Learn more about Conversion Methods here.

Understanding The Concepts

Last Touch (Default)

Last Touch attribution is when Everflow attributes the conversion to the Partner who drove the last click before the conversion took place.

How It Works

With Last Touch Attribution (default), the conversion will be attributed to the last Partner to drive the consumer to your site or Offer (via click or impression). It assumes that last exposure was the deciding factor that drove the conversion. This is best used when you have shorter sales cycles or believe the final touchpoints correlate most to driving conversions, so you can optimize towards placements, ads, keywords, etc. that directly preceded purchases or sign-ups. However, it fails to account for assisting factors earlier in the buyer's journey and risks only optimizing bottom-funnel tactics.

⚠️ Video player not ready. Try clicking again or refresh the page.
0:00 Attribution Models Overview
0:25 First Touch Attribution
1:02 Last Touch Attribution
1:40 Choosing the Right Model
2:18 Configuration in Everflow

First Touch

Attribute the conversion to the Partner who drove the first click before the conversion took place.

How It Works

The First Touch Attribution Method utilizes cookies to track the origin of a conversion. Upon the initial click or impression, a cookie is placed on the user's browser and persists for up to 90 days, or until deleted. If this cookie remains present when a conversion occurs, the originating Partner associated with the cookie is credited with the conversion, regardless of whether a different Partner delivered the most recent click or impression.

A Practical Example

__wf_reserved_inherit

Let’s take a potential buyer for Nike’s Offer named Mike. Here’s some facts:

  • Mike makes multiple clicks that lead him to the same offer
  • Each click was made via a Tracking Link that was associated with a different affiliate
  • For each click, Everflow generates & stores a Transaction ID in a cookie within the browser
__wf_reserved_inherit

Eventually the last click on Day 4 in the example above, leads to a conversion, which in this case was a sale. The conversion script ends up reading all the cookies stored above and passing on the Clicks (& Impressions) information on to Everflow’s server.

From there, Everflow will do the following:

  • If the attribution for this Offer was set to Last Touch, the conversion would be attributed to the Partner (Affiliate) associated with Click 3.
  • If the attribution for this Offer was set to First Touch, the conversion would be attributed to the Partner (Affiliate) associated with Click 1.

How To Configure Attribution Method

On The Offer Level

To configure the attribution method at the Offer Level, please complete the following steps:

Navigate to Offer → Manage Click on the Offer you’d like to edit On the General card → click Edit Navigate to the Attribution tab Choose either First Touch or Last Touch Attribution Click Save
__wf_reserved_inherit

On The Advertiser Level

To configure the attribution method at the Advertiser Level, please complete the following steps:

Navigate to Advertiser → Manage Click on the Advertiser you’d like to edit On the General card → Click Edit Choose either First Touch or Last Touch Attribution Click Save
__wf_reserved_inherit

How Everflow Decides Which Attribution Setting Applies

You can set an Attribution Method in more than one place, at the Offer Level and at the Advertiser Level. Because of this, Everflow follows a clear priority order based on which identifier the conversion script passes:

When aid (Advertiser ID) is used, Everflow applies the Advertiser Level attribution method (First Touch / Last Touch). When oid (Offer ID) is used, Everflow applies the Offer Level attribution method (First Touch / Last Touch). If both oid and aid are passed, oid prevails.

Example

Consider an Offer configured as follows:

Click Tracking = JavaScript SDK Advertiser Level attribution = Last Touch Offer Level attribution = First Touch The conversion script passes aid (instead of oid)

Question: For a conversion with multiple clicks, does Everflow use the First Touch or Last Touch setting?

Everflow uses Last Touch, because the script passes aid, so the Advertiser Level setting applies. In this scenario it does not matter whether the click came from the JavaScript SDK, and it does not matter which platform generated the conversion script. What matters is that the conversion is cookie based.

The Click Resolution Order

The first stage of any conversion is finding the click associated with it. This resolution logic only comes into play when multiple Transaction IDs are found in the cookie, or when none are found. If there is only a single Transaction ID in the cookie, the steps below are not relevant, since there is only one click to attribute to.

When there are multiple (or no) Transaction IDs, Everflow tests the following steps in order and stops as soon as a click is found:

If oid was passed and is valid, check the Offer attribution settings (First Touch / Last Touch) and find the first or last click accordingly. If aid was passed and is valid, check the Advertiser attribution settings (First Touch / Last Touch) and find the first or last click accordingly. If neither oid nor aid was passed, but the transaction is cookie based and Transaction IDs exist in the cookie, default to Last Touch. Try to find the click using the fingerprint (when the conversion comes from the SDK and a fingerprint is available). If an email was passed, try to find the click based on that email. If none of the previous steps succeed, check whether the conversion can be attributed via coupon code.
Note The default platform configuration is always Last Touch, and this is not currently configurable. Support for changing the platform default is planned for the future.