Overview
What are Triggers?
From Google Tag Manager Help:
“Tags fire in response to events. In Google Tag Manager, a trigger listens to your web page or mobile app for certain types of events like form submissions, button clicks, or page views. The trigger tells the tag to fire when the specified event is detected. Every tag must have at least one trigger in order to fire.
Triggers are evaluated when code on the page or app is executed, and associated tags are fired or blocked when the trigger conditions are met.”
What are Variables?
From Google Tag Manager Help:
“A variable is a named placeholder for a value that will change, such as a product name, a price value, or a date.”
ACME Custom Triggers & Variables
The Google Tag Manager (GTM) Tenant Setup covers custom triggers and variables ACME supports that are recommended to configure in Google Tag Manager. This document serves to explain each of these with examples.
Additional Helpful resources
• Google Tag Manager Debug Mode
ACME Custom Triggers & Variables Explained
VirtualPageview
Triggers when pages are rendered/viewed without a standard browser page load, such as the checkout cart and event forms.
Example: Checkout Cart
• Page Title: “Your Order”
• Event Action: “Calendar::DateSelected”
• Event Category: “Calendar”
• Event Label: “Feb 14, 2020”
Example: Event Form
• Page Title: “Response Forms”
Interaction Trigger
Triggers when a user performs a tracked interaction on a page. The examples below are currently supported by ACME:
Example: Visitor clicks “Tickets” for the event “Admissions”
• Event Action: “Add”
• Event Category: “Event”
• Event Label: “Admissions”
Example: Visitor selects a date on the calendar
• Event Action: “Calendar::DateSelected”
• Event Category: “Calendar”
• Event Label: “Feb 14, 2020”
Example: Visitor clicks “Join” for a membership
• Event Action: “Membership::Join”
• Event Category: “Membership”
• Event Label: “Contributor (5a0530ddf71d1a05637a5cec)”
Example: Visitor selects a different membership offering in the cart
• Event Action: “Membership::Offering::Select::Contributor”
• Event Category: “Membership”
• Event Label: “Two year::Contributor”
Example: Visitor continues to a different step in checkout
• Membership
◦ Event Action: “Step”
◦ Event Category: “Checkout”
◦ Event Label: “MemberInfo”
◦ Checkout Step: 2
• Payment
◦ Event Action: “Step”
◦ Event Category: “Checkout”
◦ Event Label: “Payment”
◦ Checkout Step: 3
• Review
◦ Event Action: “Step”
◦ Event Category: “Checkout”
◦ Event Label: “Review”
◦ Checkout Step: 4
Example: Visitor taps to complete checkout
• Event Action: “Checkout”
• Event Category: “Checkout”
• Event Label: “Order (100114511)” (Note: This is the Order Number)
• Checkout Step: 5
Example: Visitor receives confirmation of order completion
• Event Action: “Purchase::Complete”
• Event Category: “Purchase”
• Event Label: “100114511” (Note: This is the Order Number)
• Order Id:
“100114511”
• Note: A single item purchased will be returned in this payload. It is important to check the Product Triggers to see each unique item purchased (see below)
Product Trigger
Triggers when a product is successfully purchased. If multiple items are purchased, you will see multiple Product triggers returned with the confirmation page.
When it comes to Events, we track both the sales at the Event level and the Item level. This gives you the flexibility to track revenue both per Event (e.g. all "Admissions" event revenue) and per Ticket type (e.g. all "Adult" ticket revenue") or Add-on (e.g. all "Audio Tour" add-on revenue).
Note: When calculating total revenue for an Event, keep in mind that the price of tickets and add-ons are already subtotaled at the Event level.
Example of a Standard Event purchase
- 2 Adult Tickets ($10 each)
- 1 Child Ticket ($5)
- 2 Audio Tour Add-Ons ($1 each)
- Event Level
- Product Category: “Standard/Event"
- Product Id: <EVENT ID>
- Product Name: “Sailing”
- Price: “27.00”
- Item Level - Ticket
- Product Category: “Standard/Ticket”
- Product Brand: “Sailing”
- Product Id: <TICKET ID>
- Product Variant: “Ticket”
- Product Name: “Adult”
- Price: “10.00”
- Quantity: “2”
- Item Level - Ticket
- Product Category: “Standard/Ticket”
- Product Brand: “Sailing”
- Product Id: <TICKET ID>
- Product Variant: “Ticket”
- Product Name: “Child”
- Price: “5.00”
- Quantity: “1”
- Item Level - Add-On
Product Category: “Standard/Add-on”
Product Brand: “Sailing”
Product Id: <ADD-ON ID>
Product Variant: “Add-On”
Product Name: “Event Add-On”
Price: “1.00”
Quantity: “2”
Note: For General Admission Events, all of the above is the same except the Product Category will say “General Admission" instead of "Standard" (e.g. General Admission/Event)