Time to read: 7 min.

The article covers the following topics:

By the policy conducted by Apple Inc. in 2021, it is prohibited for attribution platforms to store information, which could help to identify the end-user. As a result it becomes impossible to pass to the advertiser this information (in particular click ID, IP, User Agent) and as a result to get it back. The ordinary process of S2S conversions tracking in Affise has always envisaged the receiving of click ID via the postback link.

That’s why Affise offers a new system of conversions tracking, which is called Probabilistic Attribution.

In this article you'll learn how to get postbacks without click ID values there if you're integrated with Appsflyer as well as with other tracking/attribution platforms. You also can check out the article on integration with Appsflyer in particular.

If your advertiser uses one of the listed attribution platforms and it concerns Apple’s policy, it means you and all your affiliates should use Probabilistic Attribution.

Regular scheme

How it works on clicks level

Regular scheme is useful when the chain of traffic sources isn't long. You're integrated with Appsflyer and have not more than 4 traffic sources.

Step #1: You need to give the Affise tracking link to the affiliate.

You can use the parameters listed here to get some values if needed.

Step #2: Your advertiser should give you a link, which is to be put in the ‘Tracking URL’ field in the offer:

You can use the macros listed here.

❗ Technically it is possible to pass all information about clicks, which Affise stores, however it is important to remember that according to Apple's policy attribution platforms shall not store this data on their side. It means you still can send your IP, User Agent and other unique information to the advertiser, who uses an attribution platform, however he shall not store this information and you won’t be able to receive it via postback. As a result it is useless to pass it to him.

How it works on conversions level

The process of conversion tracking has many peculiarities in the case of Probabilistic Attribution.

Firstly you need to get a postback link here: Offers - Offer edit page - Postbacks tab:

Edit offer _ Rocketcompany - Google Chrome 2022-02-16 at 11.33.07 AM

The sample of the postback link for Appsflyer:


The sample of the postback link for other tracking/attribution platforms:


See the parameters for Probabilistic postback here.

Pay attention to the mandatory parameters, and to the ones for Appsflyer.

❗ If you don’t have both mandatory parameters in the postback link, then the conversion is not registered. You see ‘Status 2’ in the Server postbacks slice of Statistics:

Server postbacks _ Rocketcompany - Google Chrome 2022-04-25 at 6.00.15 PM

All conversions registered with the usage of Probabilistic Attribution have a relevant comment [Probabilistic Attribution]:

__demo.affise.com_statistics_conversions_date_from=2022-04-19&date_to.. 2022-04-25 at 6.02.48 PM

Sub8 scheme

If the whole chain of redirect is quite long and there are many traffic sources (affiliates), we suggest the following: use the {sub8} macro for the advertiser's tracking URL and &sub8= parameter for the Probabilistic Attribution postback.

Step 1

Receive the offer ID and affiliate ID via &sub8= parameter in your Affise tracking link:



  • &pid= - affiliate ID on your side

  • &offer_id= - offer ID on your side

  • &sub8= - parameter for receiving offer ID and affiliate ID of your affiliate's sources

  • {sub8} - offer IDs and affiliate IDs of your affiliate's sources

  • {offer_id} - offer ID on your affiliate side

  • {pid} - affiliate ID on your affiliate side

Step 2

Pass your offer ID and affiliate ID as well as the offer ID and affiliate ID your sub sources via {sub8} macro to your advertiser:



  • &pid= - affiliate ID on the advertiser side

  • &offer_id= - offer ID on the advertiser side

  • &sub8= - parameter for receiving offer ID and affiliate ID of your sources

  • {sub8} - offer IDs and affiliate IDs of your sources

  • {offer_id} - offer ID on your side

  • {pid} - affiliate ID on your side

❗ Keep the indicated order of macros in the advertiser's tracking link: &sub8={sub8}|{offer_id},{pid}. If you don't have sub sources, the order is: &sub8={offer_id},{pid}. If the order is incorrect, the system won't be able to extract the needed data on the postback level.

Step 3

Receive offer IDs and affiliate IDs of all traffic sources (including yourself) via your postback link:



  • &sub8= - your parameter to receive offer IDs and affiliate IDs of all your sub sources, including yourself.

  • {sub8} - advertiser's macro to pass this data to you.

Step 4

Pass the offer ID and affiliate ID of all your sub sources via {sub8} parameter in the postback link to your affiliate:



  • &sub8= - parameter of your affiliate to receive offer IDs and affiliate IDs of all his sub sources

  • {sub8} - your macro to pass this data to your affiliate

❗ If you use this scheme, no need to use &offer_id= and &pid= parameters in the postback link. You also can use all the macros and parameters suggested in the regular scheme, except these ones in the postback link.

We highly recommend setting local postback for your affiliates instead of the global one.

You can set the postback for the Probabilistic Attribution type of integration. Only conversions with this type of integration will be sent via the link, you've set up with the help of this option.

The example

The scheme: Affise client #4 -> Affise client #3 -> Affise client #2 -> Affise client #1 -> Appsflyer -> Affise client #1 -> Affise client #2 -> Affise client #3 -> Affise client #4.



Client #

Affise tracking link sample

Example data

Client #4



Client #3



Client #2



Client #1



Appsflyer receives




Client #

Affise postback link

Example data

Client #4



Client #3



Client #2



Client #1



Appsflyer sends




Probabilistic Attribution envisages several key peculiarities regardless of the scheme you use:

1) As there is no need to get a click ID via the Affise postback link, the conversion received via it won’t have the click ID.

__demo.affise.com_statistics_conversions_date_from=2022-04-19&date_to.. 2022-04-25 at 6.05.07 PM

However, it always has an action ID anyway.

How is it generated? There are two ways:

a) The advertiser sent some value to your &action_id= parameter - this exact value will be depicted in the ‘ID’ column in Conversions slice.

b) The advertiser didn’t send you his value. In this case, Affise will generate a specific number for this exact conversion. This value will be depicted in the ‘ID’ column (see the screenshot above).

2) If you use ‘Click&Impression session lifespan’ or ‘Minimal click&Impression session lifespan’ options:

Edit offer _ Rocketcompany - Google Chrome 2022-02-16 at 12.12.18 PM

Then you need to use the &timestamp= parameter to let the system get the time when the click was created. Otherwise, both options won’t work.

❗ The date and time should be passed in Unix format via this parameter.

There is a peculiarity when it comes to integration with Appsflyer: you need to use both parameters:

  • &timestamp - Time of click creation in Unix format.

  • &action_timestamp - Time of conversion creation in YYYY-MM-DD HH;SS format.

Both values are rounded down to the nearest hour on Appsflyer's side. It means there could be the following situation: click created at 14:00 and conversion created at 14.00, however the actual time is 14:15 and 14:55. Mind that when setting up Click session lifespan and Minimal click session lifespan options.

You can read about more points about Probabilistic integration with Appsflyer here.

3) If you would like to increase the security level of the tracking process, then you have to use only the ‘Allowed IP’ option:

Edit offer _ Rocketcompany - Google Chrome 2022-02-16 at 12.13.41 PM

This option is available on the advertiser’s edit page as well:

Edit advertiser _ Rocketcompany - Google Chrome 2022-02-16 at 12.15.00 PM

You can automatically add all IPs of Appsflyer by clicking on 'Add Appsflyer's server IPs' button. Nevertheless, you can insert all the needed IPs manually.

Secure postback code doesn’t work in case of the Probabilistic Attribution at all. The &secure= parameter doesn’t work for Probabilistic Attribution postback link.

4) ‘Unique IP only’ and ‘Reject not unique IP’ options don’t work in the case of Probabilistic Attribution.

5) When Probabilistic Attribution is used, the payouts selection is performed differently. There are three parameters for the Affise postback link, which help the system to select the appropriate payout:


Country where the conversion was made


OS of the end-user, who made the conversion


Sub2 value

If you have restrictions in relevant fields (‘Country’, ‘OS’, ‘Sub2’), then you have to use those parameters. Otherwise, the system will perceive information as ‘All countries’, ‘All OSes’, ‘All sub2 values’, which will influence the process of payouts selection.

It is possible to receive only sub2 value despite you might pass other subs to the advertiser via his tracking link. You have to use &sub2= parameter in the postback link if you have some relevant restrictions in payouts.

❗ We highly recommend not to use restrictions in other fields (‘Cities’, ‘Devices’, other subs), because the conversion may be declined otherwise.

You may also find the following articles helpful:

If you still have questions left on Probabilistic Attribution, feel free to address them to Affise Technical Support Team via [email protected] or contact your Dedicated Account Manager.

Did this answer your question?