AlleyTrak Version 5.173.0 Includes Cookie Consent Updates, Range Automation System Integration Updates, and More!

Cookie Consent Updates

We've introduced two new cookie consent utilities, which enables facilities to automatically grant or deny cookie consent when customers enter the booking workflow, based on information collected on the originating website. If for example, you have a cookie consent policy on your primary website that customers can accept/deny, you can inform AlleyTrak at the time the application initializes to mirror the incoming consent policy.

When linking customers to AlleyTrak, you can now include a querystring parameter to define if the customer has accepted or denied cookie consent. There are two optional parameters:

• consent == ‘granted' || 'denied'

• alleytrak_consent == ‘granted' || 'denied'

Range Automation System Integration Update

We've revamped our Range Automation System integration, which helps resolve an edge-case with how the RAS machines receive and transmit bay status details down to the bays. This update now more effectively ensures that bay updates (like bay extensions) are correctly updated for the expected duration, and prevents the bays from unintentionally shutting down due to a racing condition when the bay is recycling from active, to inactive, to active again.

Admin ‘Deposit Total' Defaults

We've how the default value for ‘Deposit Total' is defined for facility staff in the AlleyTrak admin panel. This parameter is tied to the payment amount, when facility staff are recording or processing transactions/payments.

We've improved how and what the default value is set to, which now correctly defines the deposit amount based on the event's payment policy. This will help reduce a few steps that facility staff had to take when commonly recording external transactions against the reservation/event.

We've also added new validation and user-prompts to help facility staff ensure that they are entering a correct/valid payment amount when recording external payments.