Hybrid setup

Step #1: Adding the collection tag to the web container

The first step consists in collecting the necessary information through the web container.

To do this, you will need to add the “Commanders Act – Data Saver 1.0” tag to your container, it will collect the information you need and store it for 24 hours on Commanders Act servers.

1)-In the Select step, select the “Commanders Act – Data Saver 1.0” tag and add it to your container:

2)-Configure your tag in the “Edit” step:

  • #STORAGE_KEY# corresponds to the reconciliation key to match data collected through the web container and that collected on the server-side (ex: user ID, basket ID…)

  • #DATA_KEYN# corresponds to the names of the variables that will collect and store information on the Website (ex: “order_id”, “cookie_vendor”…)

  • #DATA_VALUEN# corresponds to the variables’ value, e. information that was collected (ex: tc_vars[“order_id”]; a cookie’s value retrieved with and internal variable, etc…). In the following example, we wish to obtain the Order ID and the value of a cookie that was dropped by a partner solution. The reconciliation key that will allow to link Web data to that of the server side is the User ID. This is how you need to configure your tag:

  • #STORAGE_KEY# = tc_vars[“user_id”] (data layer variable)

  • #DATA_KEYN# = “order_id” or “cookie_vendor1” (needs to be typed because it is the variable’s name)

  • #DATA_VALUEN# = tc_vars[“order_id”] or the partner solution’s cookie’s name, collected with the tC.internalvars.get_cookie_vendor1

Note: The name of the partner solution’s cookie can be retrieved prior to this configuration (Options > Internal Variables):

Information collected by the tag will be stored on Commanders Act’s servers for 24h hours with this structure:

Reconciliation Key (user_id)












3) – Add, if need be, firing rules in the Rules step, then generate and deploy your web container.

Step #2: Declaring variables collected with the web container and reconciliation key in the external serverside variables

The second step consists in declaring variables retrieved with the “Commanders Act – Data Saver 1.0” tag in the “Server-side external variables” section. You will thus be able to map them with your server-side tags and send your partners values collected with your Web container.

1)- Go to the “Options” > “Server-side” > “External Variables” and click “Add variable” to add your data storage variables.

  • “Name” and “Parameter label” correspond to the name of the variable present in the #DATA_KEYN# field in the “Commanders Act – Data Saver 1.0 ” tag.

  • Remember to check the “data storage” box to specify that the variable retrieved from the Web database:

You will find the variable among those in the external variables list:

2)- Lastly, make sure that the variable serving as reconciliation key is indeed present amid your server-side variables. The “Reconciliation key” box must be checked:

Step #3: Mapping data storage variables in the serverside tags

The third step consists in mapping variables from the data storage within the server-side tag in the edit step, just as you would map a server-side variable. These variables’ names will be preceded by the “External Variables (data storage)” specification :

Step #4: Creating rules based on data storage variables

The fourth step (optional) consists in creating rules in terms of data saver variables. To do this, go to the Rules section. Two rule types can be defined based on data saver variables:

  • “If variable equals (based on saved Data)”: A tag executes if the “data storage” variable equals the specified valyue.

  • “If variable is not equal (based on saved Data)”: A tag executes if the “data storage” variable is different from the specified value.

When you are finished configuring the aforementioned elements, you can generate, test and deploying your server-side container.

Last updated