Update: Since version 1.2 (June 2025), the Server-Side GTM template supports hybrid tracking. If you also use a client-side container, we strongly recommend adding our client-side fallback tag to improve tracking performance. Server-side only setups may underperform by 15–20% compared to traditional tracking pixels and our hybrid solution.
This article explains how to implement the Daisycon conversion tag using Server-Side Google Tag Manager (ssGTM). It assumes your tagging server is already set up and that relevant website data (such as event variables) is available in your GTM workspace.
Note: This guide is intended for users with a technical background. For standard client-side tracking, please refer to Implementing the Conversion Pixel.
Useful resources
-
Don’t have a tagging server yet?
Start with the official setup guide: Google Tag Manager – Server-side setup -
Need to send data from your website to the tagging server?
Follow this guide to forward events from your frontend: Send data to your server-side container -
Looking for an introduction to server-side tagging?
Read more here: Analytics Mania – Introduction to ssGTM, Simo Ahava – Server-side GTM guide
Getting started
If you’ve used our client-side GTM solution before, the process will feel familiar. The key difference is that server-side tracking no longer relies on browser-based click data. Instead, we capture the Daisycon Click ID (DCI) via a URL parameter and store it in a first-party cookie.
Step 1: Add the page view tag
Start by adding the server-side tag template:
- Open GTM Server-Side, go to Templates, and search the Community Template Gallery for "Daisycon Conversion Tag Server-side (Synergy/Hybrid)".
- Add the template to your workspace.
Next, create a new tag using this template:
- Select Page view as the event type.
- Set your preferred log type for troubleshooting or live operation.
Configure the tag to extract the DCI value from landing page URLs and store it in a cookie:
- Use any URL parameter name, such as
dci. - Inform your Daisycon contact of the chosen parameter, to ensure it's included in campaign URLs (e.g.
&dci=%DCI%). - Specify your domain for the cookie, in the format .yourdomain.com.
The page view tag also captures the gclid (Google Click ID), but only if the click can be confidently verified as originating from a Daisycon campaign. This requires either a valid dci parameter or utm_source=daisycon in the URL. This functionality helps future-proof your setup for changes in Google Shopping or Google CSS campaigns that rely on parallel tracking, where the redirect process may no longer be directly tied to the original affiliate click.
Trigger configuration
Ensure the tag fires on every landing page using the Page View – All Pages trigger.
Step 2: Add the conversion tag
Once the DCI is stored, create a conversion tag using the same template:
- Select Conversion as the event type and set your logging preference.
- Enter your Daisycon campaign ID (e.g.
12345) and as many transaction data variables as necessary. - For hybrid tracking, populate Synergy Reference with a persistent transaction identifier (e.g.
{{Transaction ID}}). Ensure this matches your client-side Synergy Tag.
Trigger configuration
Server-side tags don’t have direct URL access. Use a Custom Event trigger configured to your frontend’s conversion event, like purchase.
Final steps
Save your tags, triggers, and publish your GTM changes.
Notify your Daisycon contact when live to verify and test your implementation.
Conclusion
The Daisycon server-side conversion tag in GTM provides reliable tracking by capturing the DCI and GCLID to ensure accurate attribution, even under evolving parallel tracking conditions. Always pair it with the client-side Synergy Tag for optimal hybrid tracking performance. Remember to clearly communicate your URL parameters with Daisycon, configure triggers appropriately, and verify all variables for seamless implementation.