How to improve the configuration of a LinkedIn-sponsored Stape server container

Once your server container is created through LinkedIn Campaign Manager, your Conversions API connection is established. To improve data quality and make use of the features included with your LinkedIn-sponsored container offer, consider the following steps in your Stape container:

When creating your Stape container, we have already provided you with a randomized technical domain (for example, wjzsdfvom.us.stape.io). You could use it as a tagging server URL, but it’s recommended to use a custom domain. 

When your tagging server is situated on the same domain as your business website (e.g., if your website is example.com, then your tagging server URL could be sst.example.com). In that case, your cookies will be considered first-party, which bypasses ITP limitations of browsers like Safari and significantly increases the cookie lifetime. 

With a LinkedIn-sponsored Stape server container, you can configure a custom domain automatically or manually. You can enter a domain name, either use the No CDN or Own CDN option (Stape Global CDN is unavailable to LinkedIn-sponsored server containers), as well as configure advanced settings. 

It’s highly recommended to enable Custom Loader as part of your server-side tracking configuration. This power-up minimizes the impact of ad blockers on your GTM and GA4 scripts. It routes requests through a path that turns all cookies first-party, increasing their lifetime.