How to set up Impact server to server conversion tracking

Using affiliate marketing to bring in revenue for your company is a great idea. On the other hand, if done correctly, it is also a good method for affiliates to monetise a website which may be quite profitable.

Affiliate conversion tracking has grown difficult as a result of cookie restrictions, Apple's Intelligent Tracking Prevention (ITP), Firefox's Enhanced Tracking Protection (ETP), and ad blockers. Because of this, you might want to think about server-side affiliate tracking.

Here we will discuss the Impact server to server conversion tracking: how to set up the tag and how it works. 

Stape created an Impact tag to submit events that you would like to report on and potentially pay partners for.  Conversions come in many different forms, with sales, leads, and subscriptions serving as common examples. 

Using server Google Tag Manager, you configure the Impact tag that sets first-party cookies. These cookies can not be blocked because they have first-party status. Which result in more accurate data.

The other benefit is improved pagespeed. When you implement Impact tag on server side the tracking code is reduced which means faster loading time of your site. 

Besides that, data that this tag gathers is under your control. Client-side tracking has the potential to collect more data than you authorized. For instance, it may scrape personally identifiable information (PII) from your users, which is against GDPR and your privacy statement. But here, on server side, you have total control over what information was provided.

1. Create and set up a server Google Tag Manager container. 

2. Send data to the server GTM container. In these blog posts: Google Analytic 4 and Data Tag/Data Client, you can find the description on how to send data to ss GTM.

3. Download Impact tag from GitHub -> Open templates sections in the server Google Tag Manager container -> Click New. Or add it from the Community Template Gallery.