Time to read: 15 min.

The article covers the following topics:

Integration Test with Affiliates

Integration test can help you to check whether you set up all the links correctly and whether all redirects work well.

Integration test with Affiliates could be done in two ways:

  • Via the Testing link tool

    The Testing link tool is faster and easier, it allows you to perform a test in a few clicks. But it can be used only in cases when you need to perform the test for the default goal value ‘1’ and you don’t need to use any other additional parameters. Also, conversion’s GEO might be defined as the Netherlands, as servers that support the Testing tool are located in this country.

  • Manually

    Manual test gives more variability. You are able to perform the test for different goals, sub-accounts, etc.

Choose the way that you find more suitable for you, considering these 3 cases in which only Manual way of testing can be used:

  1. You would like to perform a test with sub-accounts in the offer.

  2. You would like to perform a test for the offer with not default goal value.

  3. You would like to perform a test with the usage of additional parameters in the postback link.

The integration test includes two general steps:

  • Tracking URL work: you check whether an affiliate's tracking link leads to your tracking URL.

  • Postback link work: you check whether you receive information about conversions consistently and without errors.

What to begin with?

Whichever way of integration test you choose, the beginning of the integration process will be the same.

1. On the offer’s preview page, choose the needed Affiliate and click the Generate button to get the tracking link:

2. Update the tracking link with Affise parameters and Affiliate’s macros.

❗ Once you'd like to omit targeting restrictions set in your offer, you can generate a test link with a special parameter &sub1=testofferlink.

3. Optional. If you use a tracking domain that allows both HTTP and HTTPS protocols, enable Use SSL option to have https://, and disable it to have http://.

The generated tracking URL will look the following way:

https://rocketcompany.g2afse.com/click?pid=2&offer_id=896&sub1=testofferlink

This will help you to test how clicks are generated for a specific offer omitting the targeting restrictions you have in the offer's settings.

If you have some subs in the whitelist, you can add them to the link like this:

https://rocketcompany.g2afse.com/click?pid=2&offer_id=131946&sub1=123&sub6=456

❗ You can add sub parameters only while performing the Manual test.

Give the generated link with the &sub1=testofferlink parameter to the affiliate to let him set it on his side.

4. The affiliates should perform two steps on their side:

a. To set the postback and update it with Affise macros (Affise macros for affiliate’s postbacks can be found in the Affiliate panel - > Profile - > Postback information).

b. To give you the test link.

Make sure the link that your affiliate gave you leads to an Affise tracking link. To find it out use Affilitest or Affise Checker.

5. To proceed with the integration test, do one of the following:

Tracking URL test

Test via Affise Testing links tool

To use Testing tool, you need to get a Read permission for Clicks list in Users -> User management -> A certain user -> Statistics -> Clicks list:

How does the Testing links tool work? The tool emulates click and conversion.

  1. It takes the affiliate’s link, which should lead to Affise tracking link.

  2. It takes generated clickid, then takes default Affise postback:

    http://rocketcompany.affise.com/postback?clickid={clickid}

  3. It replaces the {clickid} macro with the generated clickid value in the clickid= parameter.

Perform the following steps:

1. Go to the Affiliates section - > Testing links and enter the affiliate’s test link in the Affiliate outer link field.

2. Click Run.

When a test is run, you will see whether a test was successful or not:

a) If a test is successful, you will see the following message:

It means that a click and conversion were successfully generated, and the related conversion for the mentioned above clickid can be checked in the Conversions slice of statistics.

b) If a test is not successful, you’ll see one of the related messages:

  1. Click not created - ‘click not created’ message means that there are some targeting restrictions set in the offer on the client’s side or the client’s affiliate side. All the targeting restrictions should be switched off during the test. This error can also mean that the tested link doesn't contain parameters/values for affiliate ID or/and offer ID.

  2. Not found tracking URL - ‘not found tracking URL’ message means that the Testing links tool cannot find Affise link in the chain of redirections. Use redirections checker, for example, Affilitest to check the chain of redirections. Affiliate’s testing link should redirect to Affise tracking URL at 1st instance, and no additional redirections should be in-between. Ask the client to get back to the Affiliate and ask them to set the correct redirection.

  3. Wrong URL - ‘wrong URL’ message means that the wrong/incorrect link is used for a test purpose. Most likely it does not have HTTP/HTTPS protocol or it contains a space in between any symbols. You need to get back to the Affiliate and ask him to check the link and redirections set.

  4. Occurred Error - 'Occurred error' message means the same that 'Wrong URL' message means: the wrong/incorrect URL is used so it does not redirect to Affise tracking URL. You need to get back to Affiliate and ask him to check the link and redirections set.

❗ Make sure that the link itself is valid; otherwise, you’ll see the related message that the link is not valid.

Manual test

You can easily perform the Manual test yourself at any time without the help of Support Team by following the steps:

1. Choose one of the following ways:

  • Affise Manual Checker

    Put the affiliate's link to the Link field, adjust the country, Operating System, and OS version in case, if you don't want to get rid of targeting restrictions. Click Check.

    You will see a 24-symbol Affise clickid value and the URL it's redirected to (you can find more information about Affise Manual Checker here).

  • Affilitest

    Put the affiliate's link to the relevant field, adjust country, device (OS) in case, if you don't want to get rid of targeting restrictions. Click Submit.

    You will see a 24-symbol Affise clickid value and the URL it's redirected to.

2. Put the Affise’s postback link to the browser address bar, replace the {clickid} macro with the clickid value that you got in the previous step.

You can also add additional parameters to the link.

❗ Keep in mind that if you want to use the additional parameter, you need to put some value after that (like &sum=150). If you leave it like &sum={some_macro} no value will be displayed in the conversion. You will see the {some_macro} value in Statistics instead.

If you want to perform a test for not default goal value add &goal=goal_value_from_the_offer

Ex.:

https://offers-rocketcompany.affise.com/postback?clickid=5ec3c7ba4a4f2b00012aa72b&goal=registration

Read more about goal tracking here.

If you want to perform a test with the usage of additional parameters add the additional parameter. Let’s suppose you would like to use the &sum= parameter

Ex.:

https://offers-rocketcompany.affise.com/postback?clickid=5ec3c7ba4a4f2b00012aa72b&sum=150

Fire the link by pressing Enter.

Once firing the link you will see 'status:1' which means that postback was fired successfully:

It also can be checked in the Statistics - > Server postbacks:

If status:2 is received, find a related error message in the following guide and steps to update the integration. Find out more about how to take the S2S Integration test with Advertiser here.

If you see ‘Status 1’, it means you can go to check whether the postback was sent to the affiliate.

Postback link test

If the test is successful, after a tracking URL test you will receive a postback automatically. You need to check its status.

Go to the Affiliate postbacks slice of Statistics to check whether the affiliate’s postback was sent:

  • HTTP code 200 means that a postback was successfully sent and received by the Affiliate’s server:

  • Any other HTTP code response means that there is ‘something’ on Affiliate’s side that prevents from accepting Affise postback. Check the affiliate's postback settings on your side and make sure that the set up is correct. If a postback is set up correct from your side, contact your Affiliate directly to find out the roots of the occurred error. You can read more about HTTP status codes here.

What should I do if Affiliate's postback is not sent at all?

If a postback was not sent to the Affiliate's once checked in the Affiliate postbacks section, proceed with the following actions:

1) Check if a postback is set up for the Affiliate on the affiliate's edit page (Affiliates section - > Affiliate Management - > Find specific Affiliate - > Edit).

2) If a postback is set, check postback's setup:

Check whether a local postback for a specific offer or a global postback is set up for a specific affiliate. Do not forget to re-check the status, goal of the generated conversion and status, goal, and the type of integration of a postback set up for the affiliate. Make sure that they are the same. Find more details on the logic of sending affiliate's postbacks here:

You may also find helpful the following articles:


If you feel like there are some questions left upon the S2S Integration Test with Affiliate, feel free to address them to Affise Support Team via [email protected] or your internal live-chat as long as to contact your dedicated Account Manager.

Did this answer your question?