Share this article with your colleagues using the link below.
How to Use Google Tag Manager with the Public Ticketing Site: https://help.pm.leapevent.tech/a/1039326
Your PatronManager system contains a plug-and-play Google Analytics 4 integration to automatically send information like Page Views, Purchase, Add to Cart, Remove from Cart, and View Item directly to Google Analytics. If your digital marketing team or web developer prefers to collect different or more granular data, PatronManager's Google Tag Manager (GTM) integration allows for more customizable analytics.
Google Tag Manager is somewhat complicated, and isn't for everyone. Keep in mind that our support team won't be able to help set up or troubleshoot Google Tag Manager, so if you're not comfortable with HTML, Javascript, or setting up tags to fire triggers, head over to our article on Google Analytics 4 to learn about our standard integration.
What tracking data does PatronManager provide?
In addition to things like page views, PatronManager sends eCommerce data to Google Tag Manager for purchases.
Google terms are on the left, PatronManager terms on the right:
Order details:
ID = Order Number
Revenue = Order Total
Tax = Sales Tax Total (if applicable)
Shipping = Delivery Fee
Item details:
Product Name = Ticketable Event Name & Event Instance Name
Product ID = Event Instance ID
Category = Ticketable Event Type (Tickets, Subscription, Membership)
Product Variant = Allocation & Price Level
Coupon = Discount Code Name
Quantity = Quantity
Price = Item Total
PatronManager's Custom Events
PatronManager sends three custom events to GTM:
- appStarted: This fires when a user first lands on the Public Ticketing Site and it finishes loading.
- pageView: This fires every time a new page is viewed. Simultaneously, the "url" data layer variable is updated with the URL of the page being viewed.
- purchase: This fires once the payment has been processed, and is also when PatronManager pushed the eCommerce payload to the data layer.
If you're not fluent in implementing these kinds of custom events or these terms aren't familiar to you, Google Tag Manager might not be the right fit. We can't provide assistance for setup or troubleshooting; so if you're encountering issues that you can't get past, check out our standard Google Analytics integration for our standard plug-and-play option!
How to Connect Google Tag Manager to PatronManager
To connect your GTM account to PatronManager, you'll enter your GTM-ID into PatronManager's ticketing settings by following these steps.
1. Head over to PatronTicket Settings
You can get there from the PatronTicket Hub:
2. Click the "Site Analytics" link in the "Public Site Settings" section
3. Click the "New Site Analytics" button
4. Fill in the settings as indicated below
- Name it "Google Tag Manager"
- In the Provider dropdown, choose "Google Tag Manager"
- In the Tracking ID field, paste your Google Tag Manager ID. (Enter the full ID, beginning with "GTM-")
- For Status, you can choose between several options. Here's what each option means:
- Both: this option will enable tracking on both the draft version and the live version of the Public Ticketing Site.
- Disabled: your analytics will not work if you choose this option, but you could use it later if you wanted to "turn off" previously-connected analytics without deleting them from PatronManager entirely.
- Draft: this option will enable tracking on ONLY the Draft version of the Public Ticketing Site.
- Published: this option will enable tracking on only the published (live) version of the Public Ticketing Site.
- Save!
Using custom HTML tags with GTM and PatronManager
GTM allows you to use custom HTML tags to gather more customizable analytics by injecting HTML into the Public Ticketing Site. Most PatronManager organizations don't need this extra layer of customization, and it's not something we typically recommend.
PatronManager blocks code injection by default, because injecting HTML into your PTS can be risky. Poorly formatted code can break your site, and a bad actor with access to your GTM account could use it to inject malicious code.
If you want to use custom HTML tags, you will need to sign a waiver acknowledging that you're aware of the risks involved with injecting additional code into the ticketing site, and that you understand you're responsible for maintaining it. If this is something you require, submit a support request through the Client Community and we'll send over the paperwork to unlock this option for you.