Skip to main content
Deutsch Français Nederlands

Implementing Daisycon conversion tag in Server-Side Google Tag Manager

  • Updated
This article explains how to implement the Daisycon conversion tag using Server-Side Google Tag Manager (ssGTM). It covers adding a page view tag to capture the click ID (DCI), storing it in a first-party cookie, and setting up a conversion tag with a custom event trigger. This guide is intended for users with a technical background and provides references for setting up a tagging server and sending data from the website.

This article explains how to implement the Daisycon conversion tag using Server-Side Google Tag Manager (ssGTM). It assumes your server-side container 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 those with a technical background. For standard pixel-based 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 we no longer rely 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

This tag captures the click ID from the landing page URL.

  • In GTM Server-Side, go to Templates and search the Community Template Gallery for "Daisycon Conversion Tag Server Side".
  • Add this template to your workspace.

Import the Daisycon Conversion Tag Server-side template from the Community Template Gallery.

  • Create a new tag using this template. Set the tag type to Page view.
  • Choose your logging preference (recommended for troubleshooting).

In a server-side setup, tags cannot access browser data. To track the click, include a Daisycon Click ID (DCI) in your URL parameters. You can use any parameter name.

Please share the parameter name with your Daisycon contact, so this parameter is included in all campaign materials. For example, if the parameter is dci, campaign links will contain &dci=%DCI%.

You also need to store the DCI in a first-party cookie. Specify the domain where the cookie should be stored, usually your own website’s domain. Use the format: .yourdomain.com.

Configure the Page view tag with DCI parameter and cookie domain.

Trigger configuration

This tag should fire on all landing pages. Use the Page View – All Pages trigger.

Set the All Pages trigger for the Page view tag.

Step 2: Add the conversion tag

Once the DCI is stored, you can add the conversion tag.

  • Create a new tag using the same Daisycon Conversion Tag Server Side template.
  • Set the tag type to Conversion.
  • Set your logging preference.
  • Fill in required values (such as campaign ID) using static values or GTM variables. Your Daisycon contact can provide the campaign ID.

If you haven’t set up variables yet, refer to the second link under "Useful resources".

Fill in the campaign ID and other parameters in the conversion tag.

Trigger configuration

Normally, the Daisycon conversion tag fires on the thank you page. However, server-side tags do not have access to the page URL.

Instead, use a Custom Event trigger. Set the event name to match your conversion event, such as purchase or conversion.

Set a Custom Event trigger with the name 'purchase'.

Final steps

Save both tags and triggers, then publish your workspace changes.

Let your Daisycon contact know once the tags are published, so they can perform the necessary tests and verify the implementation.

Related articles