With our server-side tracking solution we will help you get better insights in your fans’ online behaviour, so you know better how your marketing campaigns are performing and how they move through your ticketshop. As opposed to traditional client-side tracking (the well known pixels) there are multiple benefits to client-side tracking with our solution:
Cookies of tools like Meta (Facebook & Instagram) and Google Ads will be set as first party cookies instead of third party. Essential for browsers that already block third party cookies by default, like Safari and Firefox. But also for when Chrome starts blocking third party cookies in the near future.
Avoid adblocker detection, which can result in 10 to 30% more data.
Extend the cookie lifetime for Safari from a maximum of 7 days to 13 months.
All will contribute to more accurate data, which results in better attribution of your marketing campaigns.
We have made server-side tracking as easy as possible for you. You don’t have to set up your own servers or send requests to Meta and Google’s servers yourself. We will do this for you, without any costs for you! Follow the steps below to set up server-side tracking yourself and start making use of the benefits.
To benefit from everything server-side tracking has to offer, it is advisable to use your own domain. You can set that up as follows.
Before you can configure the Custom Domain in the backoffice, you need to set up a CNAME for server-side tracking with your own domain. The following steps are a general guide to achieve this. As this configuration is outside the Paylogic system, we can not help you with this.
Sign in to your domain host (DNS provider).
Go to your domain’s DNS settings.
Create a new DNS record with these values:
Name: The domain name you wish to use, e.g. sst.mydomain.com (note that usually you will only need to fill in the left-most part of the domain name). Important: For optimal use of server-side tracking make sure you use the same main domain for server-side tracking as for Shops. So for example ‘sst.event.com’ for server-side tracking and ‘shop.event.com’ for Shops.
Value: eub.stape.net
Type: CNAME
TTL (Time to Live): 3600 (one hour) is the recommended value, but this is at your discretion.
Make sure to save and/or apply your changes.
After having set up the CNAME(s), you can configure the Custom Domain(s) in the Paylogic backoffice. Follow these steps to set it up.
Go to the ‘Custom Domains’ menu under the Merchant settings.
Click ‘Add custom domain’.
You are directed to a new screen where you can see and set the following fields:
Allowed merchants: This determines on which account you can use the custom domain. By default the account you’re in, will be used. Adding accounts can only be done by your Client Success Manager.
Domain: Here you type the fully qualified domain name of the site you want to use (for example sst.domain.com). You have to provide the full subdomain and not only the main domain (so do not apply with example.com).
Type: Select ‘Server-side tracking’.
Status: this will always be ‘New’ and can therefore not be changed.
Once you have filled everything in, you save the form.
In the overview you now see the Custom Domain that you have requested. Our system will verify the domain with the CNAME that has been set up. Once this check is over and everything is good, the status will change to ‘verified’.
Once a Custom Domain has been verified, it can be used to configure in the Channel. Go to ‘Create > Sales Channels’ and select the channel you want to configure the Custom Domain on.
You can select a verified Custom Domain with the type ‘Server-side tracking’ for a shop in the ‘Custom domain for Serverside tracking’ dropdown setting.
Click ‘Save changes’.
The Custom Domain is now applied to the server-side tracking server!
By default Google Analytics 4 and Google Ads are running on server-side tracking, nothing you need to do for that. Additionally you can set up server-side tracking for Facebook. For Facebook follow the instructions in this article.