Conversions Import Service

The service accepts three GET parameters:

1. clickid - it can be received via {clickId} holder from our system and should be forwarded back to our system.
2. payout - the conversion value in $, fractional number is possible, separator is a dot. For example: 1.5.
3. type - conversion type, three options are available: goal1, goal2, goal3. A user can forward up to 3 different conversion types. Example: registration -> goal1; sale ->goal 2, etc.

To import conversions, they should be sent to the domain http://conv.adxadserv.com/ using the GET method.

An example of how a complete request should look like:

http://conv.adxadserv.com/?clickid=d94ff74f-ea02-4153-ac04-111119!44117&payout=1&type=goal3

How to set up.

Step 1: Adding ClickID token of ADxAD to the traffic source template in a tracking system.

Therefore add {clickid} token to the template and set it equal to any token of the tracking system:

Now a token of ADxAD can be used appropriately.

Step 2: Receiving ClickID from ADxAD in the tracking system.

Therefore {clickid} token has to be added to the click url in the ADxAD campaign settings interface:

Now after a click happens, ADxAD system will replace the token with the internal clickid and the tracking system will be able to recognize the click ID of the external system.

Step 3: Setting up the postback url.

Therefore the postback url of ADxAD has to be added to the postback section of the tracking system.

The ADxAD postback url:

http://conv.adxadserv.com/?clickid=%insertyourtoken%&payout=1&type=goal3

%insertyourtoken% has to be replaced with the token of the tracking system, which will forward ADxAD clickID into the ADxAD postback URL.

Payout = put here a value of a single conversions which will be postbacked.

Type = put here the type of conversion (goal1/ goal2/ goal3 are the possible options).

How a ready-to-go integration should look like on the tracking system side:

The integration is done.