Follow

Mistargeting As a Reason Why Clicks Go To Trafficback: What To Check?

Time to read: 10 min.

topic.pngThe article covers the following topics:

If you receive unwanted traffic, you can redirect it to the Trafficback (Fallback) link. Different links can serve as Trafficback: 

  • Affise tracking link
  • Affise Smartlink
  • Third-party link
  • Disabled page

Wherever unwanted traffic goes, you can track whether it goes to Trafficback in the self-titled slice of Statistics:

mistargeting.png

Mistargeting is the spreadest reason why traffic didn't reach the offer. It means click was sent and it does not match targeting restrictions of the offer, there were no suitable targeting groups, or traffic is blocked by the enabled 'click-level antifraud' checkbox in the offer settings. You can see the exact reason why traffic went to the Trafficback link in case if it didn't meet targeting restrictions.

Possible reasons:

  • Mistargeting: Click-level antifraud
  • Mistargeting: IP
  • Mistargeting: Sub1 & sub2
  • Mistargeting: Sub
  • Mistargeting: Sub is empty
  • Mistargeting: Mobile carriers
  • Mistargeting: Brands
  • Mistargeting: Browsers
  • Mistargeting: OS
  • Mistargeting: Connection type
  • Mistargeting: Devices
  • Mistargeting: Cities
  • Mistargeting: Regions
  • Mistargeting: Country

It is a priority list. If a click didn't meet several elements of a targeting group, it won't be recorded for several reasons. Instead, the reason will be depicted according to this list.

But how to find out the exact value of why traffic went to Trafficback instead of the offer? In this article, you will learn how to do it.

Mistargeting: Click-level Anti-fraud

Click-level Anti-fraud option is located here:

CLAFbutton.png

The setting will block proxies (i.e send to trafficback or preview URLs based on the offer’s settings) that are known to be problematic based on the global Digital Elements database. It means that clicks went to Trafficback because they were made with the help of a proxy or VPN.

If you see this reason in Trafficback statistics, do the following:

  1. Go to Trafficback slice of Statistics and check how many clicks went to Trafficback due to this reason (Mistargeting: Click-level Anti-fraud). 
  2. Go to Countries slice of Statistics and check how many clicks came from forbidden countries (either country you didn't specify in the Targeting groups) - they're shown in the Trafficback column.
  3. Compare both values you've got and you'll understand which countries the end-user made clicks from using proxy/VPN.

import.png It is needed to understand, that the number of clicks in the Countries slice can be bigger than the number of clicks in the Trafficback slice under 'Mistargeting: Click-level Anti-fraud' reason. Why: because Affise also registers clicks came from forbidden countries, which were made without usage of proxy/VPN. They're depicted in Countries slice together with clicks made with the usage of proxy/VPN. Here you can learn how to check 'Mistargeting: Country' reason.

The example: the offer has Sweden, Switzerland, and Belarus as allowed countries, but in Statistics, there are clicks under 'Mistargeting: Click-level Anti-fraud' reason:

CLAF.png

Countries slice looks like this:

VPN.png

You also can use a filter by affiliates or drilldown report:

country_slice_mist.gif

When you've understood who sends VPN/proxy traffic, you can contact this affiliate directly.

Mistargeting: IP

IP whitelist/blacklist is located here in the Targeting group:

IPMis.png

If you inserted IPs to the whitelist to allow a certain country/region/city, then you can do the following:

1) Check which country/region/city they belong to. In order to to that please refer to the Technical Support team via support@affise.com or the life-chat. Our specialists will help you to define which country/regsion/city do this IP belong to according to the data base (called 'Digital Elements'), used by Affise.

2) When you found it out, check the Countries slice of statistics: number of clicks in Trafficback column. All countries which those IPs don't belong to are the reason why clicks went to Trafficback. 

If you inserted IPs to the blacklist to exclude a certain country/region/city, then you need to proceed with all the steps above, but in this case, clicks in the Countries slice mean that IPs in the blacklist belong to these particular countries.

In the case of regions/cities, you have to clarify it directly with your affiliates, because we don't store data on clicks gone to Trafficback according to their cities and regions.

Recommendation: if your goal is to limit countries, then it is better to use the 'Countries' field in the Targeting group. Then you won't need to use IP checkers. Use the 'Exclude' flag if you want to receive traffic from all countries except the mentioned ones. 

Mistargeting: Sub1&Sub2, Sub, Sub is empty

All three options are located here:

TraffStats.png

Here you can read more about how to set up targeting restrictions by subs. 

Affise doesn't store sub-values of click, which went to Trafficback, however, there is a workaround:

  • To ask the affiliate to give you Affise tracking URL in the way how it is installed on the affiliate's side. If the reason is 'Mistargeting: Sub is empty' or if the affiliate sends you fixed values instead of macros, then you can check whether the link contains forbidden pair of subs, forbidden sub-values, or empty subparameter.
  • To go Statistics and compare the date you've received with the data your affiliate passed to you:
    • Go to Custom slice of Statistics and tick the relevant subs (sub1-sub8) as well as clicks:

mistart_custom.png

    • You also can get a click log in detailed Statistics on clicks. Where to get it: Statistics - Daily slice - click on the hyperlink on the number of clicks. Remember that a click log can be hardly loaded when it comes to a high number of clicks, and the data they might include: once you're facing difficulties with loading the click log, use a smaller timeframe.

Here you can see all the information about clicks, including the one passed by the affiliate. 

clicklog.gif

Whichever slice of Statistics you use, don't forget to use a filter by offers/affiliates.

    • Then export the data to an Excel file. It is better to export one file per one affiliate. Then you can request a click log from the affiliate's side and compare values on both sides. The affiliate's file should contain values, which didn't come to Affise.

Mistargeting: Mobile carriers, Brands, Browsers, Os, Connection type, Devices, Cities, Regions

Since Affise doesn't store all relevant data on click, which went to Trafficback, we recommend you to check it directly with your affiliates. You can request a click log from his side and compare the data from it with your Targeting restrictions in the offer.

import.pngIn the case of regions/cities, it is needed to remember, that Affise defines both ones when clicks are being registered on the platform. Affise uses the Digital Elements database to define a certain region/city. As a result, there might be a situation when while comparing data from the affiliate's file and Affise file you'll see only allowed regions and cities. However, it doesn't mean that Affise defines those in the similar way how the affiliate does. For example: if you see Moscow in the affiliate's file and this city is allowed in your offer, it means Digital Elements defines it as some other city in Affise.

Also remember, that Mobile IPs tend to change locations every week. This is also why Affise doesn't make manual updates to mobile IPs since one user can have one IP in one state during a week, and then another user can have the same IP in an entirely different state/region the next week. This is just the nature of mobile networks and how they operate.

Mistargeting: Country

This option is located here:

country.png

If you see this reason in Trafficback statistics, do the following:

  1. Go to Trafficback slice of Statistics and check how many clicks went to Trafficback due to this reason (Mistargeting: Country). 
  2. Go to Countries slice of Statistics and check how many clicks came from forbidden countries (either country you didn't specify in the Targeting groups) - they're shown in the Trafficback column.
  3. Compare both values you've got and you'll understand which countries the end-user made from forbidden countries.

You also can use Drilldown report to look through the data separated by affiliates:

country_slice_mist.gif

Make sure you don't have the Click-level Anti-fraud option turned on in the offer. In this case, clicks, which came from unwanted countries and were made with the usage of proxy/VPN will be depicted in Countries slice as well, but the reason in Trafficback statistics will be 'Mistargeting: Click-level Anti-fraud'

import.png Remember, that Affise uses the Digital Elements database to define a certain country. As a result, there might be a situation when a certain country is defined as Russia in Affise, but on the affiliate's side, it is China. It is an ordinary situation.

General Recommendations

  1. Before you start checking cases with Trafficback statistics, you need to know for sure which Targeting group was chosen by the click. If it was a personal Targeting group, then don't forget to use a filter by affiliates while checking Statistics. Here you can read more about targeting group selection.
  2. User Affise tracking URL as a trafficback. For example, you have offer #1 and offer #2. Make the Affise tracking link to offer #2 as a Local Trafficback link to offer #1. In this case, you will be able to track absolutely all values which were the reason why clicks went to Trafficback: just check the data on offer #2. Check this article out to find more details. 
  3. Use custom statistics. It might be more convenient for you to check data in the format of Custom slice. Possible useful flags are:

ticks.png

 

article.pngYou may also find the following articles helpful:

If you still have any questions left on the Trafficback feature, Trafficback statistics, feel free to address them to Affise Technical Support Team via support@affise.com  as long as to contact your Dedicated Account Manager.  

Written by Lizaveta Talkachova 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.