Report to track coupon/discount code usage by month or year

A report showing which coupon or discount codes were used in bookings for a selected month or year would be very helpful.

We use unique coupon codes for social media campaigns and influencer/affiliate partnerships, and we need to know which codes were used, how often, and in which bookings. This helps us:

• Track marketing performance and ROI

• Pay accurate commissions to partners and influencers

Suggested columns:

• Coupon code

• Guest name

• Booking ID

• Stay dates

• Comission 

A built-in report or filter would save hours of manual work and give property managers clear insight into which marketing efforts are actually working. If you also work with influencer or affiliate codes, please vote. This would really help all of us track marketing results better.

Hi Denise,

I believe everything you're looking for, and more, can be found in the Line Item Pivot report. You can export it to Excel to filter as you see fit!

[This topic has been merged with another topic (Reports for Discount/Promo codes used). All unique votes have also been merged.]

Hi, 

I think I'm doing it wrong, because it doesn't show which discounts were used. And it would be very useful to be able to filter by discount coupon; it would be much easier.

Hi Denise,

The Line Item Pivot should show you separate columns for each discount, and the discount amounts. You should see those columns titled as the Description of said discount. For example, if you have code FAM123 and the Description for that discount is "Friends and Family", the column on the LIP that will reflect it will say "Friends and Family".

I'll ask our Support team to send you some screenshots in the ticket you have open with them.

The Product team has reviewed your feedback, and we'd ask that you submit a new Feature Request specifying that you're looking for a dedicated report that only contains the information you're looking for, since the Line Item Pivot includes more than what you're after in one report.

This request here was interpreted as having meant that this information did not appear on any OR reports, which is why it was merged into a similar request.

Thank you!