Release 100 delivers a range of feature enhancements, and updates to the system including Facebook Server Side Tracking and the ability to add featured events to pre & post emails. Below is an overview of the key changes included in this release.
An important reminder that in release 99 Multi-Factor Authentication (MFA) was released. You can view the step-by-step guide for MFA here: https://helpticketsearch.com/multi-factor-authentication-mfa-setup-guide/
Below is an overview of the key changes included in this release.
1. Facebook Server Side Tracking
To enhance the reliability and efficiency of Facebook tracking, we have introduced an option that allows operators to add a Facebook Pixel token. This enables the configuration of Facebook server‑side Pixel Tracking at both the organisation level and the event level.
Facebook Server-side Tracking is a method that allows advertisers to measure the performance of their ad campaigns without the interference of browser limitations or privacy tools. Instead of placing tracking pixels and cookies directly in the visitor’s browser, the data is sent to a secure server, which then forwards it to Facebook.
This approach offers several advantages, including:
Full data ownership: Advertisers can decide which information is shared with Facebook, allowing for filtering, anonymizing, or limiting data to ensure better privacy and compliance with regulations like GDPR and CCPA.
More accurate data collection: It is less affected by browser restrictions, ad blockers, and privacy tools, making conversion tracking and attribution more reliable than with traditional client-side tracking.
Improved campaign optimization: With cleaner and more complete data, advertisers gain deeper insights into user behaviour and campaign performance, enabling them to optimize their Meta advertising strategies and increase their ROAS.
Privacy-friendly solution: Server-side tracking eliminates third-party cookies and processes data through a secure server, maintaining accurate tracking of Facebook campaigns and ensuring compliance with privacy regulations.
For businesses spending serious money on ads, server-side tracking directly impacts profitability. In modern digital marketing, accurate tracking is the backbone of profitable ad campaigns
Setting up Facebook Server Side Pixel Tracking in Facebook
Step 1: Generate a Facebook Pixel Access Token
- In your Facebook Business Account, Copy your Facebook Pixel ID.
- Go to the Data Set section and click Generate Access Token and copy the token.
Step 2: Configure Server-Side Pixel in TicketSearch
- Log in to TicketSearch.
- Navigate to Marketing > Pixel Tracking.
- Enable the option “Activate Facebook Pixel Tracking to track at Organisation Level?” Enter your Facebook Pixel ID from your Facebook Business Account (outlined in step 1).
- Enable the option “Activate Facebook Pixel Tracking at Server Level?”.
- A text box will appear, paste your Access Token from Step 1 available in your Facebook Business Account.
- As shown in the screen shot below, select the pixel tracking actions of where you would like the system to track actions such as ‘Buy Now’, ‘Add to Cart’ and click ´Save´.
- To enable event level Server Side Pixel Tracking, select ´YES´ for the option “Activate Pixel Tracking settings to track and adjust at Event level?”.
- Save your configuration.
Once this is complete, the system will begin sending Facebook triggers from the server at the organization level and will track Facebook Pixel events at the organisation level using the provided token.
Step 3: Enable Event-Level Triggers
- To enable tracking for a specific event, you must navigate to ´Events´ > Marketing and Social Menu > under Pixel Tracking, Enable Do you want to you want to activate Facebook Pixel?
- A text box will appear and enter your Facebook Pixel ID as explained in step 1.
- Enable ´Activate Facebook Pixel Tracking at Server Level?´ to ´Yes´
- A new text box will appear to enter the Facebook Pixel Token. Enter the token that was explained in step 1.
- Select the Pixel Tracking actions such as´Buy Now´, ´Add to Cart´ and/or Payment Successful.
- Click ´Save´to save your save your configuration.
Note:
If a server-side pixel is configured at the event level, it will override the organization-level setup. Only one configuration can be active at a time, and the event-level setup takes priority. This is important if you have promoters who want to track their events via pixels.It is important to also note that you cannot use both the standard pixel approach and server side tracking, you must select one or the other. If you select both, no tracking will occur. We are working on multiple pixel tracking as a priority as we see this as a beneficial enhancement.
2. Purchase date and time added under Paid Section in Confirmation email
We’ve just been made aware that the WA state Government has launched their Kids Access All Areas program which is a batch of vouchers that parents can claim to purchase tickets for children to access art programs across WA.
Some of the rebate claims have been denied because of the way the TicketSearch order confirmation displays the sale date.
To assist in the claiming process, the payment date and time have now been included in the confirmation, reservation, and refund emails, shown alongside the Paid By section as shown in the image below.
For transactions with multiple payments, each payment will display its corresponding date and time.
All timestamps follow the organization’s time zone. This enhancement requires no client-side changes, as the existing email templates will automatically reflect the update.
This will ensure customers who are screenshotting the order confirmation can capture the purchase date/time which they will need to verify their purchase. This is also a great enhancement for the system in terms of displaying all payments made grouped together in the paid by section for clarity where in particular for reservations, there could be multiple payments made across different dates.
3. Pre & Post Event email template enhancement- ability to add featured events
You can now allow for featured events to be highlighted within both pre‑event and post‑event reminder emails. This enhancement provides operators with greater flexibility in promoting key events to attendees.
To enable this option, operators can simply select the “Featured Event” radio button located under the Upcoming Event section within the Default Pre/Post Event Email template, accessible through the Tools and Templates > Email/Letter/SMS Templates area of the platform. Once activated, featured events will be prominently displayed in reminder communications, ensuring improved visibility and engagement. The system will automatically choose the earliest five events (Event 1 to Event 5), in chronological order.
4. When making ticket type inactive, new warning implemented if associated with event with specific status´s.
A warning message has been added when making a ticket type inactive from Events > Tools & Templates > Ticket Types, if the ticket type has been used in any event. There are three different warning scenarios depending on how the ticket type has been used:
- assigned only to past events
- assigned only to current/future events or
- assigned to both past and future events.
Clicking Yes in the popup will mark the ticket type as inactive. This is particularly important for current/future events where if you make the ticket type inactive and aren´t aware it´s associated to current selling event(s), it will no longer be available. We understand that multiple staff build ticket types and events and this clarity will help in not making the ticket type inactive.
For past events, in some instances, you may need to put it back on sale to them perform an exchange. If the ticket type was made inactive, it will not be available. We suggest if you receive the below message, you should not make the ticket type inactive.
Providing further clarity, we are providing 3 messages for past; future and both events so that clients can understand where these ticket types are associated.
Please note, the status of the event must be one of the following for the ticket type to be made inactive for the for the warning message to be shown.
- Active incomplete
- Active complete
- Active off sale
- Active live
If event has one of the below statuses, the warning message will not be shown.
- Inactive
- Deleted
- Archived
5. Dot in image update when there is only one image
Previously, when an event or module had only one image, a navigation dot was still displayed (highlighted by the red arrow in the image below) on the module detail page and in the popup that appears when clicking the module name.
These dots are intended to appear only when multiple images are available—one dot per image. We have now removed the dot when there is only a single image, both in the backend and in online sales process. Please refer to the before and after images below for comparison.
6. One Session (Date/time) rule via Events when marking as ‘Private’
We have implemented a new restriction in Step 3 of the Event Build process. If an operator attempts to mark a session as private while no other sessions remain active and non‑private, the system will prevent the operator from saving Step 3 as currently, such sessions are not available via the direct sales link. If you do have only one session active and want to make it private, simply head to step 1 of the Event build and check the ‘Private’ box.
In such cases, the following error message will be displayed:
“At least one session should be active and non‑private. If all active sessions are set to private, the event will not be available for purchase in sales, even via direct link.”
Please note, this message will be updated too:
At least one session should be active and not marked as private. If all active sessions are marked as private, this event will not be available to purchase via the direct sales link.
Where one session is available and there is the requirement to mark the session as private, click on step 1 and check the ‘Private’ checkbox at the top of the page to make that session only available via a direct sales link only.
This enhancement ensures that events always maintain at least one publicly accessible session, thereby preserving ticket availability and preventing accidental misconfiguration.
7. Currency Marker added in front of Suggested Values for Pay What You Feel
The currency symbol has now been added next to the suggested values for Pay What You Feel (PWYF) in the ticket type selection popup shown below.
Other PWYF flows such as GA events and the “Choose Seats for Me” flow already displayed the currency symbol. This popup for reserved seating events was the only place where it was missing. The before and after images below highlight the change. This update affects clients using PWYF with suggested values for reserved seating events.
Below displays the suggested values without the currency symbol.
The new update below displays the currency symbol, in this case being the $ sign before the suggested value, i.e. $5, $10 etc.
8. Online customisation > Companion Card holder additional information (Validation message overlap)
Previously, in online sales, when the Additional Ticket Information field had a long name, the validation message would overlap with other fields. Since the field name can be customized via Events > Tools & Templates > Ticket Types > Edit Ticket Type, some clients have quite long names. This issue has now been fixed.
Please see the before and after images below for reference.
Previously, in online sales, when the Additional Ticket Information field had a long name, the validation message would overlap with other fields. Since the field name can be customized via Events > Tools & Templates > Ticket Types > Edit Ticket Type, it could be quite long. This issue has now been fixed. Please see the before and after images below for reference.
9. Implementation of GA4 for Masked/Custom URL Site
GA4 tracking has now been implemented for masked URLs. Certain user interactions on TicketSearch pages were not tracked. GA4 tracking is now available for both masked URLs as well as unmasked (regular) TicketSearch URLs, ensuring accurate tracking of all user activity regardless of URL type.
A reminder to head to Marketing > Customise Your Domain to read about custom domains.
Example: If your company is named ABC, your current TicketSearch URL is: https://abc.sales.ticketsearch.com/
Through domain masking, we can transform it into a more branded and user-friendly URL: https://ticketing.abc.com/
10. Case Sensitive Weblinks Breaking – Order Confirmation Redirect
Previously, in online sales, if an Order Confirmation Redirect or Continue Shopping Redirect URL (configured via Settings > Organisation Settings > Step 3: Sales & Delivery > Shopping Cart) contained capital letters at the organization or module level—such as https://abc/349JTUIWRxgios0e—TicketSearch would convert the URL to all lowercase. This caused redirection issues due to case sensitivity. This has now been fixed and the system will use the URL exactly as provided without performing any conversion.
11. ´Fixed´- hiding section from platform customization that still displayed online
Previously, hiding the Contact Information section from the online checkout page (highlighted by the red arrow in the second image) in online platform customisation was not reflected in online sales.
This issue has now been fixed. When the Contact Information section is hidden through online platform customisation, the change will correctly reflect in the online sales checkout page. A reminder, you can update many areas of your online interface via Settings > Platform Customisation > Online Customisation.
12. ‘CKEDITOR table element has now be added
Previously, table creation was displayed to add into email templates but when added, the screen would go grey until you refreshed the page. We’ve added table options to the CK editor advancement.
When navigating to Tools & Templates > Email/Letter/SMS Templates > Edit any Email Template, go to the Message Text section and click the table icon. A popup will appear allowing you to define the table properties and click OK to create the table. Once the table is created, any information or tags can be added inside the table, as shown in the image below.
