Closed (fixed)
Project:
Promotion
Version:
5.x-1.7
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
6 Jun 2007 at 01:55 UTC
Updated:
2 Jul 2007 at 16:17 UTC
I am looking for a possibility to build a report to see how many users used one or another promotional code.
For example, I am sending one promo code to one audience type, but another promo code to another audience type.
This would enable me to assess effectiveness of marketing campaign.
If I could find API for this module - probably I would be able to generate this report by myself, but any other ideas of how to implement this would be greatly appreciated.
Comments
Comment #1
zostay commentedYes!
I have this very feature on my personal To-Do list, but haven't made it into a feature request here yet. I will need this in the next few weeks myself, but I'm not sure when I'll have time to get to it. A patch would be very welcome.
As of this release there is not much of an API yet and certain internals are in the midst of flux.
The only way to do this as is, would be to run a SELECT on the promotion_codes_users table for the promotion you wish to report on. Then, you could show the users along with the code_used, which is the column containing the actual code they submitted.
Comment #2
ivrh commentedThanks for the reply.
I will look into it tomorrow and get back with the result later on.
Comment #3
zostay commentedI haven't heard anything back on this, I'm going to need a report on this soon. Therefore, I'm going to start on this myself.
Comment #4
zostay commentedI've added an initial summary report to CVS:
http://cvs.drupal.org/viewcvs/drupal/contributions/modules/promotion/pro...
I will be adding the additional promotion code reports soon.
Comment #5
zostay commentedI've gotten the reporting pretty well finished. They don't include all the statistics I'd like yet, but the basic framework is there and ready to use. The most important information for my purposes (number of users using a report, in the last 30 days, last 7 days) are there. However, I still want more data and I think I may want a historical report in the future.
Comment #6
zostay commentedThese could use more work or a different set of fields, but the basic report is in place. The 1.7 release will be built momentarily. Additional requests for more features and such are welcome.
Comment #7
ivrh commentedMy apologies for being quiet. I am working on other things now and will contribute here as soon as I got thing up and running.
Comment #8
zostay commentedNo problem. Believe me, I understand. I'm only able to contribute to places that are a top priority and I can make the time to do it. I expect the same to be true for most folks.
Cheers.
Comment #9
(not verified) commented