The Daisycon Synergy Tag is a lightweight client-side tag designed to work alongside the server-side conversion tag. It enables more reliable hybrid attribution by sending a transaction-level reference from the browser to Daisycon. This reference must match the value included in your backend conversion call.
Note: This tag must be used in combination with the Daisycon Server-Side Conversion Tag. It does not track conversions on its own.
When and why to use this tag
In hybrid tracking setups, the primary identifier for attribution is the Daisycon Click ID (DCI). However, in cases where the DCI is not available in the backend, the Synergy Tag ensures that the transaction can still be linked to the correct affiliate click by providing a unique transaction reference.
- The
Synergy Reference
must be unique per transaction, such as an order number or cart ID. - This same value must be passed in the
Synergy Reference
field of your server-side conversion tag.
How to implement the Synergy Tag
Step 1: Add the template to your GTM container
- Open your GTM web container (client-side).
- Go to Templates and search the Community Template Gallery for Daisycon Synergy Tag (Server Side/Hybrid fallback).
- Add the template to your workspace.
Step 2: Create a new tag
- Go to Tags > New.
- Select Daisycon Synergy Tag (Server Side/Hybrid fallback) as the tag type.
- Fill in the following fields:
- Program ID: The Daisycon campaign ID (e.g. 12345).
-
Reference: A GTM variable that returns a persistent transaction reference, e.g.
{{Order ID}}
or{{Cart ID}}
.
Step 3: Set the trigger
- Trigger the tag on your confirmation page or at the first moment the reference becomes available.
- This is often a Page View or Custom Event trigger tied to order completion, cart creation, or session start.
How it works in combination with the server-side tag
The Synergy Tag sends a transaction-specific reference from the browser to Daisycon. When your backend sends the server-side conversion call, it must include the same value in the Synergy Reference
field.
If the DCI is missing in the backend (e.g. due to cookie restrictions or user privacy settings), Daisycon can still attribute the conversion using the reference, provided it was received earlier via the Synergy Tag.
The Synergy Tag is privacy-friendly: all order data is sent through the server-side conversion call and does not touch the client browser.
Best practices
- Use a persistent and unique identifier per transaction, such as an order ID or cart ID.
- Fire the tag only once per transaction, preferably as early in the order process as possible.
- Verify that the same reference is included in both the Synergy Tag and the server-side conversion call.
- Always fire the server-side conversion tag for every conversion, without applying deduplication or attribution rules on your end.
Conclusion
The Daisycon Synergy Tag strengthens hybrid tracking setups by providing a browser-based reference that supports accurate attribution even when the DCI is unavailable server-side. Always use this tag together with the server-side conversion tag and ensure both share the same transaction reference to enable reliable fallback attribution.