Release Notes 2026.10.22

New

✨ Integration Hub: Access Cleeng Reporting Data in Snowflake

Now you can query your Cleeng reporting data in a dedicated Snowflake account that Cleeng provisions for you. Connect your existing analytics and business intelligence (BI) tools and run your own queries, without requesting a data export.  

Key benefits

• No pipeline to build or maintain. The data arrives structured in an account that is ready to query.
• Combine reporting areas. Join the views in a single query, for example subscriptions, transactions and users, instead of matching separate export files. 
• Familiar reporting areas. The views cover the same six reporting areas as Analytics > Data Export.

Coverage

• Available for your production and sandbox environments.
• Reports included: User Report, Subscription Report, Pass Report, Transactions Report, Refunds Report and Gift Report.
• Data refreshes every six hours.
• Views are read-only.

What you need to do
The feature is available only on the Enterprise plan. 

To start, connect Snowflake Sharing in the Cleeng Dashboard and enter the email address that should receive the account credentials. Use the address of the person responsible for managing your data access, not a shared mailbox. For setup steps, see Connect Snowflake Data Share.  

To disconnect, contact Cleeng Support or your Account Manager.

Where to find it
Go to Cleeng Dashboard > Admin & Tools > Integration Hub > Snowflake Sharing.

Learn more

• Snowflake Data Share: access Cleeng reporting data in Snowflake
• How to understand exported data

Improvements

🚀 Transactional Emails: “Invoice” Email Renamed to “Receipt”

The “Invoice” email template in the Cleeng Dashboard is now called “Receipt”. Only the template name in the Dashboard changed. The email content and your on/off setting for this template stay the same.

Where to find it
Go to Cleeng Dashboard > Admin & Tools > Transactional Emails > Templates.

Learn more

• What emails are sent to my customers?

API Changes

🚀 Updated

Auth0 Integration

The Auth0 - Generate token endpoint now returns a specific HTTP status, error code and reason for each failure. You can now tell a data conflict from a service failure and decide whether to retry.

What has changed

• Data conflicts (such as duplicate external ID, email or Auth0 identity, or customer not found) return 409.
• Rejected customer data, such as an invalid email, returns 422.
• Service failures return 502 and timeouts return 504.
• Every error response includes a reason field.
• Field limits have been updated and are checked up front: 
  • firstName or lastName up to 50 characters with no hyperlink-looking substrings 
  • externalId up to 100 ASCII characters 
  • currency exactly 3 uppercase letters.
• A request body with trailing data after the JSON returns 400.

Successful responses don't change. For all codes and reasons, see Auth0 - Generate token.

What you need to do
If you use the Auth0 integration:

• Update your Auth0 Action's error handling to use the HTTP status and reason. 502 and 504 responses are safe to retry.
• If you monitor 500 responses from this endpoint, also monitor 502 and 504.
• Check that user data in Auth0 meets the new field limits. Values that exceed them now return 400 on every login.

  ->>><<<-

Click here to subscribe to our release notes emails and we will send them over to your inbox.