Arlo can send order related information through to Google Tag Manager, allowing you to manage and deploy marketing tags (snippets of code or tracking pixels) on your checkout without having to modify the actual code. Tag Manager can then be connected to other systems, allowing you to send Arlo transaction data to your various marketing and reporting systems.
- Go to your Arlo platform Settings, and under Marketing, choose Google settings.
- Toggle on the Enable Google Tag Manager option
- Add your Google Tag Manager container ID to the Tracking ID field. You can get your container ID by going to your admin page in Google Tag Manager.
- Press Save and close or Save to save your changes.
When Tag Manager is enabled, 'events' get fired as a registrant moves through your checkout process. These events contain information which can be accessed by Tag Manager and used to create variables, triggers, and tags. For more information regarding how to set up and use Tag Manager, see their help center. Below are the events that Arlo fires:
When a registrant first enters the checkout the ‘arloCheckoutStarted’ event is fired. This includes the course code allowing you to analyze results on a course level. The 'checkout' variable lets you know which registration method the registrant is using ('quick' for quick registration and 'order' for order process).
If the registration method is Order Process, at each page/step of the checkout the ‘arloCheckoutStep’ event is fired. This event includes details about which step of the checkout the registrant is on (‘cart’, ‘billinginfo’, ‘review’, or ‘finish’). This allows you to report on where people are getting to in your checkout process and where they might be dropping off.
Once the registrant has successfully registered, the ‘arloCheckoutFinished’ event is fired. This event includes more details about the order including the overall order value, currency, region, and expected payment method.
Purchase event (ecommerce):
If ecommerce via Tag Manager has been activated, the Purchase event (eCommerce data) is fired at the same time as the ArloCheckoutFinished event, so when the registrant has successfully registered (i.e. when they press Submit in the checkout).