Tracking clicks by node author
fortressgame - September 13, 2006 - 20:35
| Project: | AdSense |
| Version: | 5.x-3.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
Description
it's sort of been asked for, in a different way, maybe.
i'd like to be able to assign each author a channel. authors are paid flat rate per piece written, so we are not revenue sharing or using their google id. instead we use our google id and just assign each one a channel so we can track how effectively their writing generates revenue.
Basically would need a 'adsense channel' field in profile to be read by adsense module and used on authors' posts.
it seems like i can use something like [adsense:468x60:1:2] but the last part, the channel, needs to come from the extra field in the profile of the user.
i think i can do it myself but it would be great feature to have in the module.
#1
So, you want a channel per user, so you can track them in your Google adsense account.
OK, sounds like a good idea.
However, this is something that you as the site owner have to do, first in your Google account, then for each user's profile to plug that value there. Then you hope that the users do not change it themselves by mistake or something. This does not scale as well. If you have say 50 users, it is sort of managable. If you have 200 users, it is hard, but maybe doable. If you have 500 users, you run over the number of channels that Google provides you.
Not trying to shoot it down completely, but pointing out potential problems with this design.
At some point when I get time, I like to have an adsense API, where other modules can give a different adsense ID, or channel or what have you ... this way, plug in modules can do whatever you want.
#2
To keep users from accidentally changing their channels, you could create a role and configure channels for all the users with that role on the settings page.
#3
#4
I don't think this is possible with the new Ad code which relies on ad slot.
Setting to postponed until a conceptual solution can be found.
#5
It's actually the same problem as always. The only difference being that the site admin had to create different channels per user and now he has to create different ads (so that he can obtain a different slot ID for each user).
Of course, this means that the system would have to store per user a slot ID. If this solution is beginning to sound like what would have to be done to solve the Revenue Sharing with the new code, it's because it's just a simple variation of it. In this case, the publisher ID of the site would be used and not a per-user publisher ID. Of course, forcing the site admin to start creating the ads for each user is even more annoying than the already annoying solution we have 'designed' for the new code sharing.
I very much doubt any site admin willing to share with more than 2 users will be able to stand it. We'll keep it postponed, but I am guessing that with the current Google AdSense code, this will never get used, even if we do it.
João