There are two methods to process postbacks and conversions that the system gets. They are synchronous and asynchronous processing. The latest processing method is asynchronous, that is a more effective and stable way to deliver postbacks and conversions to your Admin panel, and this is what is used by Affise.

Synchronous vs. asynchronous processing

In synchronous processing, the execution of each operation is dependent on the completion of the one before it. It means that to see a conversion in the Admin panel, the Affise system needs to do a whole set of checks, one after another, to decide whether a postback and conversion is successful or not.

In asynchronous processing, the execution of one operation isn't dependent on another. Postback and conversion checks for different parameters can run simultaneously.

Processing on Affise

Affise is using asynchronous postback and conversion processing, since it's the most effective way to process data for such high load services as Affise to keep supporting an almost unlimited number of requests.

To accept a postback or conversions, the system needs to check dozens of parameters like offer, partner ID, registration date, goal, etc. Synchronous processing can lead nowhere, as while checking is happening, there can be timeout or internal error.

Asynchronous processing 👍	Synchronous processing 👎
Not linked to other Affise services, processing is independent.	Linked to other Affise services (Admin panel, API, clicks, offers, automation, caps and other services responsible for traffic management).
The request is accepted disregarding any issues.	There may be a delay or internal issue which results into request abortion.
Each request processing is put into the dedicated queue for further processing. Upon receiving a request, Affise server responds with ‘status 1’ response. No matter of network throttling or server timeout settings, each request is collected and processed.	Each request is processed one by one, which may result in server response and timeout errors. Network throttling and server timeout settings directly affect postbacks processing capacity.
Can work with an unlimited number of requests.	Has limitations in capacity and scalability.
Saving traffic to the maximum.	Traffic may be lost up to 5-7% (due to data processing test).

Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].

Postback integration (S2S) (admins)

Affise postback URL parameters

Server postback errors

Server postbacks in statistics

Affise <-> Affise