Google Tag Manager - Server-side

No technical skills required.
This documentation also applies to solutions like AddingWell, Stape, etc., which uses the GTM-Server Side platform.


1. Retrieve your 3rd party data collection domain


1.1 Example: If your data collection domain is:  https://et1.eulerian.net , the targetHost is et1
1.2 Example: If your data collection domain is:  https://io1.eulerian.net , the targetHost is io1


2. Connect to your GTM Server Side interface





3. Check your data collection


Log in to your interface to check if your data collection is activated.Your installation is now complete! Party Popper



Special case of multiple clients


You may have configured multiple clients in your GTM Workspace; for example, you might have this list of clients:

https://slite.com/api/files/aX4ZBo47S46ed4/Screenshot%25202025-07-11%2520at%252014-46-57%2520Google%2520Tag%2520Manager.png?apiToken=eyJhbGciOiJIUzI1NiIsImtpZCI6IjIwMjMtMDUtMDQifQ.eyJzY29wZSI6Im5vdGUtZXhwb3J0IiwibmlkIjoiNGRDdVg3VVp3VFZ1X1UiLCJpYXQiOjE3NjUwMjQ4MTgsImlzcyI6Imh0dHBzOi8vc2xpdGUuY29tIiwianRpIjoieFVlRC1ZTHowRTRMMUIiLCJleHAiOjE3Njc2MTY4MTh9.HF0TTzx5Ikg1WH0mN2NvJR_VE3SN7J31PYGSb1OKMm0

In order for Eulerian to collect data correctly, it is necessary to ensure that the client collecting said data, sends it correctly to the Eulerian server-side connector. To do this, it is necessary to modify the triggers and add the GA4 client from which the data will be retrieved as a clause. This is very simple to do by configuring this trigger (you will then need to delete the old triggers):

Once that is done, check in the Preview section that access is triggered correctly and publish your changes.


Going further



1. Configure the consent method:


1.1 Simple setup: activate the GTM SS Eulerian template only on your consented traffic. To do this, check the "All traffic is consented" box.

1.2 Advanced Setup: activate the GTM SS Eulerian template on all your traffic and retrieve consent signals via your CMP.
1.2.1 Consent via pmcat by providing the list of consented categories for the current call
1.2.2 Consent via TCF, in this case the TCString must be provided via a custom variable


Learn more (developer documentation)

The following information is useful for understanding how the events and data in the GA4 DataLayer are associated with the data in the Eulerian DataLayer.


What events are being measured?

Global Data
The following global parameters are always provided to each call sent as long as they exist in the original datalayer:
  • page_location mapped to url
  • page_referrer mapped to rf
  • screen_resolution mapped to ss
  • ip_override mapped to ereplay-ip
  • user_agent mapped to ereplay-ua
  • client_id mapped to euidl
  • currency mapped to currency
  • user_id mapped to uid
  • user_data.sha256_email_address mapped to email

For each call, we automatically copy all additional event parameters prefixed by ga-

page_view event
Standard call made

Purchase event
A transaction is recorded in this case:
  • transaction_id mapped to ref
  • value mapped to amount
  • items mapped to the product array & product parameters are prefixed by ga-

add_to_cart event
The products listed in the items table are added to the current cart.

remove_from_cart event
The products listed in the items table are removed from the current cart.

event generate_lead
A lead is recorded in this case: the transaction_id is mapped to the ref; if not available, a random ref is created.
  • value mapped to amount
  • items mapped to the product array & product parameters are prefixed by ga-

Personalized Events
Custom events not listed above are sent directly to actions/objectives for further processing on the platform.

WARNING
By configuring server-side data collection like this, you will lose all access to the initial web browser. This means that certain features of the Eulerian Marketing Platform will not be available due to the server-side integration, including but not limited to:
Heatmap
TMS on the client side
Identity synchronization for IdGraph, CookieSync, etc.
Real-time access to the user's current status via the client-side JavaScript API
Privacy Sandbox Integration
Client-Hint Management