Punchh Platform Release Notes - 01 April 2025 Deployment
The updates described in these release notes and the affected/linked documentation will not be available in the Punchh platform until the target deployment date.
Reporting and Analytics
Data Field Hidden on Campaign Performance Page
Within the Campaign Performance Page (CPP), under Campaign Audience vs. Control Group, Average Visit Frequency data is unavailable for long/perpetual or ongoing campaigns. The data field has been removed from the CPP for these campaign types instead of incorrectly populating as a zero. (Further enhancements are planned for 2025.) (EPS-9869, PDOC-2967)
See the following article for more details:
- Campaign Performance Page (Support Portal)
Redemption Data Export Correction
The Discount Amount field from the Redemption Data Export was prematurely removed in the March 18th platform deployment. This field has now been restored as of this April 1st platform deployment.
See the following article for more details:
- Data Export (Support Portal)
Webhooks
Issue Resolved for Favorite Locations
The issue of sending null values for favorite locations to mParticle was resolved through the default mapping configured for subscribed events within the dashboard without requiring any code changes. Additionally, a broader solution was planned for this release to prevent the issue from occurring altogether, ensuring that null values for favorite location attributes are not sent to mParticle, even without explicit mapping. (EPS-10055)
POS Integrations
Enchancement to Xpient POS Reference Numbers
To enhance consistency and prevent duplicate earnings when handling Xpient POS transactions, we are standardizing POS reference numbers to a minimum length of 10 digits. For a POS reference number with fewer than 10 digits, we will add leading zeros as needed. A POS reference number with more than 10 digits will be stored as is without modifications. Note: If Xpient modifies the transaction number structure for Olo (how and what Xpient sends to Olo, which Punchh then receives via webhook) or for Punchh (what Punchh receives from the POS), this solution may require further adjustments. (EPS-9971)