OneTag

How does OneTag work ?

The OneTag is placed on the web containers of your site. They send your events with all the required data to our servers from where they are redirected, in server-side and automatically, to the partners of your choice.

If the data goes through the Commanders Act servers, does that mean you store it ?

The data remains on our servers only as long as it needs to be formatted and processed to be sent back to your partners.

What do I have to do to make this work ?

1. One OneTag per event

   It is necessary to put a OneTag by event to track (the templates of tag are in the TagCo library).

   It will map the variables required for the partners without having to worry about the differences between the partners.

2. One Base Tag and one connector per partner

   For each partner we will add its library in a web tag and a connector per partner (FB, GA, AT, etc.)

   The connectors consist of simple fields to be filled with the partner id, a token, the privacy category id of the partner.

3. One deployment and it's ready :)

But... for privacy, if the OneTag remits data for partners of different privacy categories, how do I categorize my OneTag ?

OneTag has a technical and functional role of collecting user consent and acting as a data carrier.

It is at the connector level (server side) that the partner's category id will be compared to the consent collected by the OneTag in order to allow or prevent the data to be sent to the partner.

OneTag can therefore be classified as either functional or technical in your CMP.

OneTag has a technical and functional role of collecting user consent and acting as a data carrier.

With Enterprise Tag Management, you don't have to do anything ! The container code automatically retrieves the category ids consented by the user and injects them directly into the OneTag events.

If you don't have TRUST it's not a problem ! You just need to add a property to your events that will retrieve the ids consented by your CMP.

Do I need to know how to code to install OneTag ? If I don't know how to code, how do I do it ?

By default you don't have to code anything!

OneTag are pre-templated in the TagCommander bookstore.

You will only have to map your tags (i.e. select variables in dropdown menus) and fill in ids on the partner connectors.

Some customizations may require some adjustments to the code. In general, it's quite simple to set up.

What if I need to customize my OneTag ? What customizations can or should I do ? Is it complex to customize ?

The OneTag is designed to send standard events (page view, add cart, purchase, etc.).

However, customizations are possible:

• custom event name

• custom variable name

• custom event filter

• custom consent id

These customizations require only a simple addition of properties to the OneTag, i.e. a short line of code.

Details of these customisations are available in our documentation.

If I already have partner events in client-side won't they duplicate the OneTag ?

Sending events on the serverside allows you to avoid sending them on the clientside.

However, if you want to keep both setups, that's not a problem. In this case the events will be deduplicated on the partner side and the event server will even be able to add to the amount of browser events received.

In order for the server and browser events to be deduplicated, they must have the same event id.

That's why when the OneTag is triggered, an event id will be generated automatically.

A slight adaptation of your partner events in Clientside will have to be done so that they get, in a property, this same event id. A short line of code is all it takes.

What do you recommend ? server-side only ? Client-side only ? Both ?

Several setups are possible.

Server-Only: You only send your events in serverside.

Advantage --> This setup has the advantage of minimizing hits and server calls.

Redundant Setup : You send your events to server side and to clientside. This requires a common event id for both server and browser events. OneTag allows this.

Advantage --> The events server will bring an increment to the amount of events received.

Disadvantage --> This setup is optimal but more expensive.

Borwser-Only: This is the classic setup. No need for OneTag.

Disadvantage --> in the sense taken towards a cookie-free world this type of setup risks to be quickly obsolete.

How can you guarantee the protection of personal data with OneTag ?

In addition to automatically retrieving the user's consent, the OneTag embeds in each event, at your convenience, the user-properties available in your datalayer.

On the CA server side, user-properties are automatically and without exception, hashed in SHA256.

Can we use OneTag on GTM ?

Yes !

We have a template of OneTag for GTM.

This template allows the sending of standard events but also the sending of custom events.

If you want to install the OneTag yourself, is it possible ? Do you have a doc ?

Everything is documented so that you can be autonomous.

Here is an example of the OneTag events reference document

See our documentation here :

https://community.commandersact.com/platform-x/developers/tracking/events-reference

How can I be sure of the quality of the events sent by the OneTag ?

The quality of event mailings is measured according to 3 criteria:

• The amount of server events compared to browser events

• The deduplication of events

• The gain of data embedded in the events (user-properties in particular)

For this we recommend a server-side + client-side setup for a sufficient period of time to be able to compare event feedback and evaluate this quality.