This Google Tag Manager Community template is available for the Eulerian Marketing Platform provided by Eulerian Technologies SAS (https://eulerian.com)
The dataLayer used is the one described in the official documentation of the Google Tag Manager Solution
For server-side integration please check the appropriate GTM Server-Side plugin
If you don't already have an account, you can try our freemium platform through Eulerian.IO to create a free account & declare your website, this allow you to have access to the trackingDomain.
-
go to you google tagmanager instance
-
go to the "Templates" section
-
look for the Eulerian Marketing Platform - GTM template in the gallery
-
create new template
-
the template is imported you just need to configure with the proper subdomain from the third-party tracking url
5.1 example : if you tracking domain is :
https://et1.eulerian.netthe trackingDomain is et1.eulerian.net5.2 example : if you tracking domain is :
https://io1.eulerian.netthe trackingDomain is io1.eulerian.net5.3 example : if you tracking domain is :
https://sdf475.eulerian.iothe trackingDomain is sdf475.eulerian.io -
save the template
-
trigger the template with custom page_view / remove_from_cart / add_to_cart / view_item / purchase / generate_lead.
-
publish the modifications -> you are now live !
The following global parameters are always provided to each call sent to us as long as they exists in the original datalayer :
- currency mapped to currency
- user_id mapped to uid
For each call we auto-copy all additionnal parameters of the event prefixed by gtm- for non-standard keys.
Standard call done.
If you have page_view events that are linked to another event_name you can provide a list through the similar_page_view configuration.
This configuration entry allows you to list all events that must be considered as page_view events.
For example: virtual_page_view,consented_trafic,hit_ok will all be considered as page_view events.
In case you do not have a page_view event, you can check the box in Advanced settings allowing a gtm.js event name to be mapped to a page_view event, that way you are still able to trigger calls to Eulerian Marketing Platform. Make sure that you link the event gtm.js to the tag to trigger it. If you have a page_view event do not enable this option as it can cause double-couting.
A transaction is registered in this case :
- transaction_id mapped to ref
- value mapped to amount
- items mapped to product array & product params are prefixed by ga-
Products listed in the items array are added to the current cart.
Products listed in the items array are removed from the current cart.
Product page is viewed and the first result of the items array is sent to Eulerian.
A lead is registered in this case :
- transaction_id mapped to ref, if not available a random ref is created
- value mapped to amount
- items mapped to product array & product params are prefixed by ga-
Custom events not listed above are directly sent to actions/goals for further processing in the platform.
As GTM can trigger multiple events and hence our tag it can result in multiple calls on our end that can inflate the stats.
To avoid this make sure :
- you only trigger the Eulerian GTM SS only for the event you want to track
- avoid multi-event call on a single page : page_view -> view_item -> user_engagement for example only trigger on view_item if exists for example.
We provide limited support through our free offering, if your setup is more complex we can provide consulting expertise and/or work with your expert agencies of your choice. This means that the current plugin works for most cases but not all cases, so please understand your own setup and make sure it makes sense regarding what we are collecting so that you can take the most of our platform. Enjoy !
Apache 2.0