...
Change the value of the 'type' parameter to 's'.
Add a parameter called 'cli' to make sure the ID of the click can be transmitted. You can transmit one or multiple click Ids here. To learn how the system will perform attribution and how you can control attribution with multiple click IDs, please read the article Working with the clickId.
If you do so, you conversion code will look more or less like this:
| Code Block |
|---|
https://marketing.net.advertiser.com/ts/i12345678/tsa?typ=s&tst=!!TIME_STAMP!!&trc=default&ctg=Request&sid=&cid=!!convId!!&orv=!!ordValue!!&cli=!!clickID!!&orc=EUR |
If you want, you can add any parameters that can be added to regular conversion codes. When you are applying server to server tracking, you might find it necessary to overwrite rating values by using the corresponding parameter. If so, please make sure you add the magic key to the conversion code as well. If you do so, the conversion code will look more or less like this:
...
When you are done, scroll down the page and click on the button 'save' in the right lower corner.
Device Id on server to server conversions
Server to server conversions themselves do not contain device information so the device id of the most appropriate touchpoint is applied on them to be used in reports.
Optional you can provide the appropriate device id using a parameter called 'device_type' set to one of supported device id values: “mobile“, “tablet“, “desktop“
Implementing the code
When you have configured the conversion code and added all the parameters you need, the code is ready for implementation in the external system. How this needs to be done will depend on the demands of the external system you use. Please make sure the code is triggered unconditionally.
...