Checker
Affise Checker is a tool to check redirects of Affise tracking URLs and advertiser tracking URLs (whether links redirect to App Store/Google Play Market). With the Checker, you can use flexible settings to adjust checking the way you want. Also, you can manage your offers to understand the flow of traffic. The tool allows you to analyze the statistics on redirects and optimize the tracking process. Unlike the testing tool, Affise Checker can check any links with any additional parameters.
💰 Affise Checker is available by request. Contact your Affise account manager to get the feature.
Affise provides two ways of checking links: automatic checking and manual checking.
To find the Affise checker, go to the Checker section.
⚠️ You need the following permissions to work with Affise Checker:
Automation > Affise checker > Write.
Automatic checker
If you don’t want to spend time checking tracking links, use this tool. The system performs the test automatically, according to the conditions you set up.
To work with the Automatic checker, go to Checker > Automatic. On this page, at first, you see the following:
You can learn about the advantages of Automatic checker usage, pricing, and terms and conditions. You can start a free trial period by clicking Start free trial.
All available settings are:
where:
Automatic checker enabled: you can enable or disable the automatic checker.
Advertisers: you can add advertisers whose offers you would like to check. It is not possible to set up several rules for different advertisers.
⚠️ You need the following permissions to add advertisers:
Users > Advertisers editing > Affise checker > Write or Read.
Hops limit: it's possible to set redirects limit. If the limit is exceeded, the test is considered failed.
⚠️ The number of hops ≠ the number of links. Hops are redirects from one link to another. For example, there are three links, but two hops (1 → 2, 2 → 3).
Interval: you can set the frequency of tests: 1, 4, 8, and 24 hours.
Action: you can just check offers, and also pause and disable offers, that have an unsuccessful check result.
Only CPI: you can test only CPI offers (offers, where the CPI checkbox is active in Offers > a certain offer > General).
During the check, the system takes advertiser tracking links of all active offers of the selected advertisers. Each number of selected hours, the system checks whether the link reaches the Google Play Market or App Store.
The system looks at the first general targeting group in every offer to create (to emulate) a click. The settings considered are the following: GEO & OS (the very first OS setting).
⚠️ Automatic checker ignores macros presented in the advertiser tracking URL.
For example, there is a link:
https://google.com?click={clickid}&pid={pid}&ip={ip}
Checker sees it the following way:
https://google.com?click=clickid&pid=pid&ip=ip
⚠️ The system successfully checks the HTTP 302 type of redirect. There can be issues with other types.
Test results
The test is successful if Google Play Market or App Store is reached within the number of redirects you set up. The test is failed if Google Play Market or App Store is not reached or the number of redirects exceeds the number you set up.
You can see the results at three places on the Admin panel: Offers, Dashboard, and Statistics.
Results in Offers > offer list:
You see the results of the last four checks. Green is a successful result, and red is unsuccessful. The numbers mean the hop at which the link led to the target market, or the failure occurred. If you hover the cursor over the unsuccessful result, you can see the reason for failure.
You can filter offers by the checks result and hops.
Results in Statistics > Affise Checker:
You can use the following filters:
Indicate a time range: up to 90 last days.
Select the timezone.
View results by certain advertisers.
⚠️ You need the following permissions to view advertisers:
Users > Advertisers editing > Affise checker > Write or Read.
You can use the following widgets:
Top advertisers per failed checks: up to five advertisers with the highest number of failed checks. The X-axis shows the number of checks.
Top advertisers per successful checks: up to five advertisers with the highest number of successful checks. The X-axis shows the number of checks.
Checks by hops: the percentage of checks with a certain number of hops (the system counts both successful and failed checks).
Checks by results: the percentage of checks with successful results, and different reasons for failed checks.
The table:
The total daily number of checks and hops.
The hops/checks ratio.
The total daily number of checked offers.
The total daily number of offers with failed checks.
The percentage of offers with successful/failed checks.
Results in Dashboard > Advertisers top (successful checks)/(unsuccessful checks).
You can see the following widgets:
Top five advertisers with the highest number of offers, who passed the test.
Top five advertisers with the highest number of offers, who failed the test.
You can use the time range: Today, This month, Last month.
Change Log
Each time you change the settings of the automatic checker, the relevant record appears in the Change log.
Here you can filter by the date and users who changed the settings.
🔎 If you see the Can’t fetch change log message, it means you have AdBlock or similar plugins turned on. Please turn it off for a while.
Manual checker
This feature allows you to check manually the Affise tracking URL (or any other link) for a certain offer under certain conditions (GEO, OS/Device, OS version).
You can use the manual checker for free for ten tests per day for all users. If you want to extend the limit, please contact your Affise account manager.
All available settings are:
Link: the link you want to check. It starts the further chain of redirects.
Operating System: you can select the OS, you want to check for the offer.
OS Version: you can select the OS version, you want to check for the offer.
Country: you can select the country you want to check for the offer.
City: you can select the city you want to check for the offer.
You can also test an advertiser tracking URL in Offers > a certain offer > Tracking. The manual checker opens on a new browser tab.
Test results
If the link that you check is invalid, you get a notification. The link is considered invalid if it doesn’t begin with https(s)://www.
In the manual checker, the default number of hops is ten. If the tool doesn’t reach the app market in ten hops, the test is failed.
You can see the results of the test right in the manual checker window:
The green indicator means the Affise tracking URL leads to the offer.
The gray indicator with the message means the test failed. In the message, you can see the reason for failure.
Reasons for failed tests
In case of unsuccessful test results, the automatic or manual checker shows you one of the following messages:
Redirect URL returned bad status: while redirecting, the Affise checker got a status other than 200 (it could be 404 or 400, for example). This error means something is wrong on the advertiser side, not on Affise.
Redirect chain didn't lead to target market: at the end of the test, the system didn’t reach the market.
For example, you set up the limit of ten hops, and on the sixth one you got to some website, and there are no further redirects at all.
It can happen if your advertiser has targeting restrictions on their side, which are not met by Affise Checker. As a result, the system was redirected to the trafficback.
The time limit for redirecting from one link to another is seven seconds. If time is exceeded, you get this error.
Hops limit exceeded: the number of hops is exceeded. For example, you set up the limit of ten hops. After the tenth one, the system didn’t reach the market. Probably, if you set up more hops, it would have reached the market eventually.
Redirect URL is insecure: while redirection, the system faced the HTTP connection, which interrupted the entire chain of redirects.
⚠️ The system deletes the test results in seven days if there are no new results.
Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].