We’re pleased to share the latest updates and improvements in Release 101 , designed to enhance tracking capabilities, improve consistency across modules, and resolve reported issues.
Please press control + shift + R to refresh your browser and see the latest changes.
Please see below the items included in release 80. Please read the release notes carefully and if you have any questions, please contact support in your region.
1. Google Tag Manager (GTM) Enhancements
We’ve added expanded tracking functionality within Google Tag Manager to provide more detailed customer journey insights.
New Action Types Added:
- Add to Cart
- Initiate Checkout
- Payment Confirmation
- Payment Successful
Additionally, GTM can now be configured at the event level within Event Build – Step 1 (Pixel Tracking), giving organisers greater flexibility and control over tracking setup per event.
Here is our detailed helpfile on Google Tag Manager: https://helpticketsearch.com/google-analytics/
2. New Event Scanning Setting (Transaction Date Based)
Introduced a new configuration option in Event Build – Step 1 under Options & Add-ons.
Applicable Regions:
- Malaysia
- Singapore
- Indonesia
When enabled, operators can scan tickets based on the transaction date, providing greater operational flexibility where this workflow is required.
Note: If you would like to activate this feature, please email our support team for assistance.
3. Pixel Tracking Help File
A direct help file path has been added to Event Build – Step 1 under Pixel Tracking.
This provides quick access to setup guidance and best practices, making configuration easier and reducing setup errors.
4. Membership & Module Image Display Fix
Resolved an issue where images in the following modules, were stretching when screen resolution changed.
- Memberships
- Merchandise
- Vouchers
Before
After
5. E-Invoice & Report Spelling Corrections
Fixed spelling and labelling issues affecting reports and E-Invoice emails:
- Perak was incorrectly displayed as Peravia
- Sarawak was incorrectly displayed as Sarande
- Malaysian (Nationality column) displayed an incorrect spelling
All values now display correctly across reports and email communications.