We value your unique insight into our products and services and often receive ideas and feedback from our community in a variety of ways. To streamline this process, we’ve created an idea bank where you can post product suggestions, vote for those most important to you, and add comments to existing ideas.
Specifically regarding membership promotions. The discount report is just not enough, especially since it does not include back office transactions. Ideally it would be nice to pull a query that shows who renewed with a discount, what promo was used, when they renewed and at what level they renewed. It is important to be able to track who is renewing in which cycle to target renewal efforts.
Six years later, this bug has still not been fixed.
KB 195895
Agree!!
"Data is just data until it can be compiled and analyzed; only then is it information. If the data is there, but inaccessible, it has no value. Blackbaud has sold us on the value, but is not delivering."
I went through the trouble of creating a membership promotion with separate promo codes to be able to track if the member joined from an email or mailing, only to find out later when running reports that you cannot isolate the promo codes.
Please see every response below on this issue; i am in agreement that we should be able to see what specific code was entered by a constituent.
Very surprising and disappointing that this is not a canned report by now.
2016 -> 2023. Very surprised this hasn't been corrected.
Come on Altru, do better! This should be such a basic thing.
I have a promo code for corporate sponsors and community partners to attend an event for free. I can't pull a list of who actually redeemed this promo code! This should be a basic, easy report or query to pull. Blackbaud needs to address this asap.
I've spent the last 3 hours trying to build an ad hoc report to find out that it is not possible. I'm highly disappointed in this as it is a very basic function. Work on reporting needs to be done asap.
I agree with all the comments below! My favorites:
"It is completely asinine to not be able to report on promo codes. What is the point of creating codes and having people redeem them if we can't see who they are? This is a basic functionally. And the fact this was first posted in 2016 and STILL hasn't been fixed, is even more frustrating. Do better, Blackbaud."
"Yet another "feature" that doesn't actually deliver the value it promises. Why even offer the multiple code option if the only data we can actually access is the discount name itself?"
"This is honestly an unbelievable oversight. This needs to be fixed."
"Data is just data until it can be compiled and analyzed; only then is it information. If the data is there, but inaccessible, it has no value. Blackbaud has sold us on the value, but is not delivering."
This feature is absolutely necessary! Please add it. Why have a promo code if we can query on who used it?!
I woud like to have this feature added
It is completely asinine to not be able to report on promo codes. What is the point of creating codes and having people redeem them if we can't see who they are? This is a basic functionally. And the fact this was first posted in 2016 and STILL hasn't been fixed, is even more frustrating. Do better, Blackbaud.
Yet another "feature" that doesn't actually deliver the value it promises. Why even offer the multiple code option if the only data we can actually access is the discount name itself? At least make this clear so that we don't invest a lot of time and energy into a code program that we cannot measure the efficacy of.
This is a basic need for tracking discounts. How do I know which group is most responsive to an offer if I can't track the specific code? I know I could set up a new offer every time I offer one but then we would end up with a huge list of one time only offers. Thank you for considering fixing this very basic data need.
Yes, if you won't fix it, at least make it clear at the TOP OF THE KB that you cannot do this AND REMOVE THE PROMOTION CODE FIELD from the Query options. Seriously, why is a field that you can't query on even present?!
Would be a very helpful tool.
Very necessary indeed.
We need this!
Yes!