The following is a general reference for placing pixel code within Theatre Manager so that they appear on the appropriate web pages. | |
For employees of MogoArts, your pixels have been used in web pages at a number of Theatre Manager venues. Please refer to Mogo's internal corporate Wiki Pages that describe your internal processes for Theatre Manager. An image has been provided. | |
Variables can be used within pixels to get actual cart values. |
The general steps for implementing pixels are:
Pixels:
Mogo, Facebook, or Google pixels can be placed in Company Preferences->Web Listener tab as required to accomplish what you want without needing to edit any web pages. You can also edit web pages directly if you have unique requirements. | |
Conversion pixel codes imbedded in iFrames are not allowed by the Credit Card PCI Council on web pages due to a security risk called Click-Jacking (effectively a man-in-the-middle attack vector).
If the MOGO pixel provided is with an iFrame, please inform them to give you one that is javascript. For your own safety, Theatre Manager web pages do not support embedded iFrames because the PCI Council forbids it. |
A tracking code added to the Header or Footer field in Theatre Manager should be visible in the source code of all pages on the ticketing site. Code added to the Checkout field would be visible on the final page of the sales process. A sample link would be:
This is not an endorsement of pixels from MogoArts. |
We have seen MogoArts' internal documentation wiki. We are not sure of the exact web page, we believe it is called 12_44_43-Vendor - Ticketing Wiki - Google Sheets2222. It contains instructions that look like the image below.
** NOTE: All field references need to be added to the pixel code using <field> tags. An example would be
<field>SCH_ORD_SEQ</field> |