Setting up tracking

ticketmatic understands that ticket sales is your core business and that (e commerce) tracking is an important tool to increase your sales ticketmatic supports the two major web tracking tools google tag manager and facebook pixel to help you achieve this goal if you want something custom or have other tracking desires we also support custom tracking google tag manager google tag manager is a tag management system that allows you to quickly and easily update tags and code snippets on ticketmatics pages it's in an industry standard way to setup tracking you can find detailed information docid 2mebiiry wtpnswdclji facebook pixel the facebook pixel is an analytics tool that helps you measure the effectiveness of your facebook advertising you can find more info on setting up a facebook pixel docid\ jrjd7azaol7p0wflcn rj other trackers ticketmatic does not support other trackers on our ticketing sales pages to ensure that your data and your customer's data is secure trackers work by including code from a third party server in the pages your customers are visiting in general this has no adverse effect on your customers as only specific elements are tracked (for instance going to the next page) if a hacker should take control over the third party system they can track anything that happens on ticketmatic's ticketing sales pages if this happens the hacker has the ability to collect sensitive information from your customers this sensitive information can even include credit card information in specific cases as this is already happening on a daily basis throughout the entire web, for instance with the magecart campaign, we have decided to limit the number of client side trackers to google tag manager and facebook pixel if you want to go further than this, there is a possible to use custom tracking custom tracking ticketmatic keeps track of all operations (creating an order, linking a customer, adding/removing tickets, ) through the order log the orderlog thus contains all relevant information to analyze the behaviour of your customers without the need to add third party code to ticketmatic's pages by using the referral parameter in a link, everytime a new order is created with the specific link, the referral parmeter is stored in the order(log) this enables you to link a specific id on your end with a specific order inside ticketmatic whenever a customer leaves an online order, the order is removed after 15 minutes (this is the default value for this parameter and can be changed in the account parameters module) the orderlogs for this order stay available for at least 24 hours this enables you to ingest the order logs every couple of hours to keep track of the customer behaviour for example a custom tracking could work in the following way every time a link is shown on your website the \&referral=xxx parameter is added to the link the result is a link which looks like https //apps ticketmatic com/widgets/\<account>/addtickets?event=111111\&referral=xxx the xxx value is the id or code that enables you to link the specific customer to an order in ticketmatic every 2 hours the latest orderlogs are ingested via the api this is possible by using the export https //www ticketmatic com/docs/api/tools/export by relying on the fact that each orderlog entry is immutable and that it has an incremental id it's possible to implement an efficient synchronisation by only synchronizing newly created order logs the orderlog contains much more information than necessary so it's best to limit the orderlog types to type id description create order 18001 the order has been created and the model column will contain json that contains the referral parameter remove order 18002 the order has been removed and is thus no longer active this happens when a customer leaves the order confirm order 18006 the order has been confirmed it might be possible that the order has not been paid as a deferred payment method (bank transfer for instance) has been used it's thus possible that the contents (tickets, products) of the order will be removed in the future the model column will contain a totalamount parameter indicating the value of the order keep in mind that the totalamount can only be used for this orderlog customer linked ( 18007 ) a customer has been linked to the order the model column will contain a json object that has a customerid property indicating which customer has been linked order delivered 18014 the order has been delivered (through mail or via boxoffice) when this happens it's certain that the order has been paid keep in mind that this event can take place hours of days after confirming the order (for instance if the order has been paid through bank transfer) an example query that can be used with the export https //apps ticketmatic com/docs/api/tools/export is select id, orderid, typeid, model >>'totalamount' as totalamount, model >>'nbroftickets' as nbroftickets, model >>'referral' as referral from tm orderlog where typeid in (18001,18002,18006,18014) and id>n if you want to track when tickets and/or products have been added/removed you can also track the following orderlog types type id description tickets added 18003 tickets have been added the model column will contain json that has a tickets array where each ticket has an eventid and a price parameter enabling you to link to specific events tickets removed 18004 tickets have been removed the model column will contain a json object that has a tickets array where each ticket has an eventid to indicate which tickets are currently in the order products added 18020 a product has been added to the order the model column will contain an array products that contains the current products that are in the order products removed 18021 a product has been removed from the order the model column will contain an array products that has the current products in the order