Can server-side tracking reduce the impact of a consent banner?
Adding a consent banner to your website can affect tracking and marketing performance. When visitors decline cookies or other tracking technologies, some data is no longer available to analytics and advertising platforms, leading to fewer recorded conversions and limiting the information available to you.
While server-side tracking does not eliminate the need for user consent, it can help you reduce the negative impact of consent banners without bypassing consent. There are several methods that allow you to make the most of the data you are legally allowed to collect, improve tracking reliability, and gain greater control over how information is processed and shared.
How to reduce data loss without compromising on consent
1. Understand consent modes
If a visitor declines consent, you can’t collect or forward any of the data that requires their consent. However, there are different ways to configure consent management. For example, Google Consent Mode offers two approaches:
- Basic Consent Mode: Google tags are blocked until the visitor grants consent. If consent is denied, no data is sent to Google through those tags.
- Advanced Consent Mode: Google tags load even when consent is denied, but adjust their behavior according to the consent state. They can send cookieless pings that Google uses for conversion and behavioral modeling.
Clever use of the Advanced Consent Mode can help fill in some measurement insights through modeling. It doesn’t recover actual data from users who declined, but rather produces estimates based on patterns from consenting users and the cookieless pings. Always be sure to review its implementation against applicable privacy requirements and with your legal team. Learn more in our guide on Google Consent Mode V2.
2. Use the Consent Parser variable
The Consent Parser variable decodes Google Consent Mode v2 information from the gcd parameter of an incoming GA4 request in your server container. It makes consent states available as variables in sGTM. Server tags can then fire according to each visitor's actual choices instead of being blocked wholesale.
3. Data Store
Stape’s Data Store solution can keep a visitor's consent state with its timestamp and policy version. Later backend events (CRM, webhook, offline) can then check that stored consent before going to destinations. Please keep in mind that it counts toward your subscription’s usage quota.
4. Google Consent Mode Listener tag
The Google Consent Mode Listener tag pushes a stape_consent_update event to the dataLayer when consent changes. It ensures that your tracking setup always uses the latest consent state and prevents tags from firing (or not firing) based on outdated consent values. For instance, you can use it to fire tags once a visitor accepts consent later in their journey on your site.
5. Cookie Keeper
The Cookie Keeper power-up restores first-party cookies that Safari ITP would expire after 7 days. It can restore first-party cookies that would otherwise expire early under browser restrictions, such as Safari's Intelligent Tracking Prevention (ITP), helping maintain more consistent identifiers and attribution data. Though it addresses browser limits, not the consent banner, it’s an important part of the equation if you wish to preserve as much user data as possible.
Was this article helpful?
🍽 Table of content:
Comments