Use this link to share with your colleagues:
Using a Meta Pixel with the Public Ticketing Site: https://help.pm.leapevent.tech/a/1039973
PatronManager supports the use of a Meta tracking pixel for your Public Ticketing Site (PTS), so you can track and report activity with Meta's analytics.
Setting it up is easy! This article will help you:
- Create your Meta pixel with the correct URL
- Add it to PatronManager
- FAQs
Let's get started!
"Analytics? Tracking? What's this all about?"
If you haven't yet, we recommend starting with our All About Analytics on the Public Ticketing Site article -- it's a great place to get introduced to the concepts here, and evaluate your options.
When it comes to tracking page views, Meta doesn't play as nicely as Google Analytics with websites like the Public Ticketing Site. It can track visits to the ticketing site as a whole, and it can track purchases.
If you need more robust tracking, including individual page views within the ticketing site, we recommend using Google Analytics instead.
1. Create your Meta tracking pixel
Not sure what a Meta pixel is, or how to use one? You can read Meta's information about it here. If you have further questions, we recommend looping in your web developer or digital marketing agency.
Since we're PatronManager, not Meta, we can't help much with this part -- but here's a little info that may be useful. If you already have your Meta pixel ready to go, grab the pixel ID and skip to step 2!
1. Use the correct ticketing site URL
When setting up your pixel, you'll tell it which website you want it to track. Use the URL of your Public Ticketing Site, but stop after the "/ticket" -- don't include anything that might come after that in the URL. It should look something like this, but specific to your organization:
https://yourorganization.my.salesforce-sites.com/ticket2. Copy the pixel ID, not any other code
When you create your pixel, you'll have a few different options for putting it to use -- for example, you can view the full code, or email it to your web developer. We've simplified this part -- all you need is the pixel ID.
It'll be a string of numbers labeled "Pixel", and you'll find it in your Meta Analytics account under Data Sources.
2. Connect your Meta pixel to PatronManager
Once you have your pixel ID, it's time to hook it up to PatronManager.
2.1. Head over to PatronTicket Settings
You can get there from the PatronTicket Hub:
2.2. Click the "Site Analytics" link in the "Public Site Settings" section
2.3. Click the "New Site Analytics" button
2.4. Fill in the settings as indicated below
- Name it "Meta Pixel"
- In the Provider dropdown, choose "Facebook"
- In the Tracking ID field, paste your Meta pixel ID. If you're not sure what that looks like, try this tip in step 2
- For Status, you can choose between several options. Here's what each option means:
- Both: enables 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 can use it later if you want to "turn off" previously-connected analytics without deleting them from PatronManager entirely.
- Draft: enables tracking only on the draft version of the PTS.
- Published: enables tracking only on the published (live) version of the PTS.
- Save!
That's all there is to it! Now you can sit back and watch the tracking data roll in.
What tracking data does PatronManager send over?
PatronManager sends the data below to Meta. Each system has its own terminology, so you can see the Meta term on the left and the corresponding PatronManager term on the right.
| Meta | PatronManager |
|---|---|
| content_ids |
Event Instance ID |
| value |
Order Total |
| currency |
Org currency e.g. USD |
| contents |
For each Ticket Order Item: Event Instance ID, Item Price, Quantity, Ticketable Event Name & Event Instance Name formatted as follows:{ . "id": Event Instance Id, . "item_price": Price, "quantity": Quantity, "name": TicketableEventName - EventInstanceName } |
| content_type |
Always product
|
Frequently Asked Questions
As of mid 2024, Meta no longer supports domain verification for sites hosted on Salesforce (which includes all PatronManager client sites).
Meta's policies and pixel functionality have been changing rapidly since Apple's 2021 privacy updates; as of July 2024 it seems that you can still use your pixel on an unverified domain for some tracking, though you may not get as much detail. We are unable to provide support for non-PatronManager products.