There are two types of synchronization:
Affise <-> Affise synchronization (so-called "Clone").
Non-Affise source type <-> Affise synchronization.
Below, you have a description of how the targeting is synchronized in both cases.
Targeting synchronization
To pull targeting information together with the offer, you need to set the rule value as First Sync or Always. If you don't want to receive targeting, select the Disabled rule value.
Non-Affise source - Affise
As the APIs of non-Affise sources are different, the API response parameters may also be different. So, there is synchronization of the targeting restrictions according to three scenarios, which depend on the API source structure:
If there is no targeting group in the API source offer, the countries are taken from all offer payments and displayed in the first general targeting group on Affise.
If there is any targeting group in the API source offer with any country (including All countries), then not only country but also OS and Device data are taken and put into your Affise offer in targeting group.
If there is no country in the targeting group in the API source offer, but there is OS and Device data, then the country is taken from the payments and put into your Affise offer in the targeting group.
Sync rules are used to manage synchronization frequency for specific offer fields on Affise, and in the case with targeting, the rule is used to manage synchronization frequency for Geo restrictions:
If the Traffic targeting is First Sync, then the relevant field is pulled to Affise offer the first time it appears in the source API response, synchronized with CPAPI, and is pulled to your Affise account. Despite all the changes made to your Affise offer, targeting is not updated anymore.
If the Traffic targeting is Always, then the relevant field is updated in Affise offer each time synchronization occurs.
If the Traffic targeting is Disabled, then the relevant field is never pulled or updated in Affise offer each time synchronization occurs, because the synchronization frequency is disabled.
🔎 By default, the rule set as Always. Read more about synchronization rules here.
Affise - Affise
There are the entities that are not pulled in the case of the Affise <-> Affise synchronization:
The Click-level Anti-fraud checkbox:
The Subs section:
Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].