Conversions: tracking methods
RedTrack offers you the following methods of conversion tracking:
API conversion tracking method is based on the integration of the RedTrack API with the affiliate network. This is the most reliable conversion tracking method because it happens on the backend of both platforms. When a conversion occurs, the affiliate network infrastructure pings RedTrack with all the necessary information. However, since this method requires a lot more development work on both sides, it is not very common in affiliate marketing and not all the systems support it.
API method in a nutshell:
- It’s the most reliable method of passing the conversion. It does not need cookies to work.
- It’s a “set it and forget it” method. Once you complete the integration, you won’t need to configure anything. Conversions will be shared along with additional information such as payout.
- Can be challenging to implement.
These are the API-integrated offer sources/websites:
Server-to-server (S2S) postback is a very accurate method of receiving and sending conversion data. S2S tracking saves the information about the user ID directly to the server of an advertiser (offer provider), RedTrack, and Affiliate Network. When a user clicks on an ad, this click is recorded and gets a newly generated unique ID for this session. If a user buys or orders something on the offer provider’s side, RedTrack receives a message from the offer provider (affiliate network, advertiser) about the conversion that happened. This is a standard option available for everyone. No additional settings are required.
- It provides slightly accurate tracking and accurate statistics. This tracking method does not rely on cookies. Therefore, it works even if the visitor has blocked the collection of cookie data in their web browser. That is why it is considered one of the most reliable tracking methods
- Postback tracking must be supported by your affiliate network
How to set the correct S2S postback in RedTrack depends on the network you are using:
Conversion tracking using Pixel is the simplest and least accurate method. You place a piece of code (or script) on your “Thank you” page and each time the visitor opens this page, the conversion is fired with the help of the script. That means the same visitor can refresh the page and the pixel will then be fired once again so you may receive a duplicate.
- You can use it if the S2S option is not available
- It’s the ultimate solution when you don’t have many technical resources and have your own “thank you page”
- Pixel is simple and fast to implement and use, so there is no need to be a technical expert. You simply copy the pixel from the tracker and paste it into the code of the last page that the user sees after the conversion has occurred.
- Sometimes pixels may not work. One reason for this could be the user clearing the cache between clicking a link on the landing page and the actual conversion. In this case, the conversion will simply not be tracked
- Apple has implemented Smart Tracking Protection 2.0 in Safari, preventing websites from tracking user activity without permission. Right now, the website can request tracking permission, but the user must specifically register. Even if the user consents to be tracked by Safari on their own, after 30 days all data and cookies will be permanently deleted. In general, pixel tracking is a fairly complex process when working with Safari
- Google has announced that its Chrome web browser will no longer support third-party cookies from 2022, which will of course cause pixel tracking issues and make a simple pixel/script a solution only for the redirect tracking
Received conversions in reports
Campaigns table→ table settings→ choose all the custom conversion types you are using→ save the columns:
For more information go to Reports.