Discount codes
How to usage history and reporting
Each code can carry usage count and usage history so teams can measure adoption and audit redemptions. Usage history can include booking references, customer identity context, transaction date, and discount amount, making the page useful for campaign analysis as well as configuration.
Each code can carry usage count and usage history so teams can measure adoption and audit redemptions. Usage history can include booking references, customer identity context, transaction date, and discount amount, making the page useful for campaign analysis as well as configuration.
Usage history and reporting
Each code can carry usage count and usage history so teams can measure adoption and audit redemptions. Usage history can include booking references, customer identity context, transaction date, and discount amount, making the page useful for campaign analysis as well as configuration.
- Use usage count for fast volume checking.
- Use usage history when you need to see where and when a code was redeemed.
- Use export when stakeholders want the promotion data outside the platform.
Tips
- Decide the targeting and stacking rules before publishing the code, because those are usually more important than the discount percentage itself.
- Use date, time, and day restrictions intentionally for demand shaping instead of only thinking about the discount amount.
- Review usage history after launch so campaigns can be adjusted before they overrun margin or underperform.