Bare in mind, this is just an example of how we could set up these events. You can use any other naming conventions when setting up the events in GTM. Full list of events that we send to GTM, with their data, can be found here: https://wiki.advbet.com/admin/online-platform-cms/google-events?s[]=slipbuy
These Data layer variables are used to pass data that comes from our app and are mapped within the GTM ecosystem to pass data to GA.
To set up a trigger, we need to use the event name from the Events section. This is how login event looks after we finish the set up:
To receive all events from our app, we need to create triggers for all events from the Events table.
Additionally to all triggers, we can set up routing trigger, to track pageviews in GA. The set up for this trigger should look like this:
The event according to the table in the Events section sends Category, Action and Label data. So in this case:
{{ Google Analytics Settings }}
in Google Analytics Settings sections
* Tag data should be set up according to the Events table. For instance, if event does not send Label data, we should leave Label field empty. Same goes for other fields.
Router tag is set up a bit differently from other events, and the tag set up should look like the one below:
Event name | Category | Action | Label | Value |
---|---|---|---|---|
registrationInit | YES | YES | NO | NO |
registrationConfirmationKey | YES | YES | NO | NO |
registrationFinished | YES | YES | NO | NO |
login | YES | YES | NO | NO |
logout | YES | YES | NO | NO |
slipBuy | YES | YES | YES | NO |
depositSuccess | YES | YES | YES | YES |
withdrawalSuccess | YES | YES | YES | YES |
myAccountMenuDepositButtonClick | YES | YES | YES | YES |