Time to read: 3 min.

The article covers the following topics:

How does Affise define click uniqueness?

Quite often, Affise clients are interested in what the difference between a click and a host is. A host is a unique click, while a click is any click.

In the statistics, clicks mean the number of all clicks, both unique and not unique.

Statistics _ Rocketcompany - Google Chrome 2022-06-21 at 11.50.26 AM

But how is click uniqueness defined in Affise?

Click uniqueness is defined in by:

  1. browser

  2. device

  3. date

  4. offer ID

In terms of Affise, clickid cookie is saved for 24 hours once a click is registered in our system.

This means that if a click comes to the tracking URL https://rocketcompany.g2afse.com/click?offer_id=1&pid=1 , we register it as a host and a click.

If the same user clicks the tracking URL

https://rocketcompany.g2afse.com/click?offer_id=2&pid=2 from the same browser & device within 24 hours, it will be a host and a click, because the offer ID is different.

If the same user clicks the tracking URL

https://rocketcompany.g2afse.com/click?offer_id=2&pid=1 from the same browser & device within 24 hours, it will be a click only, because the host was registered earlier.

There is an opportunity to send only hosts to the main tracking URL. Find more information here.

❗Note that the algorithm to define click uniqueness can fail to work if you use a tracking domain with the HTTP protocol. Since new browsers are more strict to cookies requirements, use HTTPS to make sure your clicks are defined the right way.

How does Affise define conversion uniqueness?

Three categories in the following scenarios define the uniqueness of conversion in Affise:

1) If a conversion has 'action ID' (i.e., conversion ID) value passed by the Advertiser via a postback, the uniqueness of conversion is defined by :

  1. goal - goal number or goal value (&goal)

  2. action ID - unique conversion ID in the advertiser's system (&action_id)

  3. offer ID - Offer ID

If you want to receive unique conversions for the same click ID, then you should add the parameter &action_id to the Postback URL. In that case, the uniqueness of the conversion would be determined by the conversion ID rather than the click ID, and the conversions would not be declined with the message "conversion exists".

Install Postback URL example with &action_id:

http://offers-rocketcompany.affise.com/postback?clickid={clickid}&action_id={adv-macro-for-action-id}

Event Postback URL example with &action_id:

http://offers-rocketcompany.affise.com/postback?clickid={clickid}&action_id={adv-macro-for-action-id}&goal={event-name}

❗ If the advertiser sends postbacks with different click ID, but the same action ID, conversions are not registered. The postback has status "2" and the comment "Conversion exists". The thing is that if the advertiser sends a value in &action_id= parameter, click ID will be ignored when defining the conversion uniqueness.

2) If conversion does not have "action ID" (i.e., conversion ID) passed by the Advertiser via a postback, the uniqueness of conversion is defined by:

  1. offer ID - Offer ID

  2. goal - goal number or goal value (&goal)

  3. click ID -unique click ID (&clickid)

❗ Find out more about the S2S Integration with Advertiser here.

You may also find the following articles helpful:


Should you have any further doubts or questions, feel free to contact the Support Team via [email protected] or your Dedicated Account Manager.

Did this answer your question?