Ubercart Affiliate
SiteMaster.Serv... - November 27, 2008 - 20:36
| Project: | Affiliates |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Can you please include:
1. The ability to "flag" a visitor using a cookie, so that their return-visits can be tracked, based on which affiliate link they came from.
2. It will then be very useful to be able to pick up their "recorded" affiliate-link id on their return (stored as a Tag?).
3. Adding a Trigger/Event for workflow purposes for a hit on an affiliate link
4. On registration of the visitor, linking the new user to the affiliate user (Or does this module take care of that already?).
It's awesome news to see an Affiliate module being worked on again. THANKS!
PS: The Ubercart Affiliate Module lists some great features to consider for future.
ServeLime
#1
a Cookie for returning visitors would be nice...
#2
#3
I'm going to be giving this more thought tomorrow as i feel this feature request points toward some great ideas.
Please feel free to elaborate on your ideas though. When it comes to discussing new ideas you can't be to verbose
or state something to clearly. If you see how something should work in your minds eye then share your ideas completely
by giving step by step , point by point narrative of exactly what you would like to see implemented.
Best, Paul
#4
Taking a look at the User referral module ..
http://drupal.org/project/referral
#5
@kbahey
It looks as though "affiliate referral" information should be drawn from the union of the affiliates and the user referrals modules working together. Can i get your thoughts on this issue before i continue working on this .
Best, Paul
#6
Question for the original poster: with item #4, are you suggesting that when a new user who followed an affiliate link registers, that new user should be added to the existing user's Buddylist or User Relationships?
I, for one, vote against that if that is the idea (or at least vote that it is an option that can be disabled). The Invite module does that and that's fine when it's a direct invite, but I wouldn't necessarily want random users who followed a link to be added as a buddy/friend.
Maybe I am misunderstanding?
#7
Apologies for only now responding.
[Background:]
I did research on the UberCart Affiliate, Affiliate, Affiliates and User Referral modules, from which resulted the (new) features (missed User Relationships).
There are commercial applications of Affiliation which requires handling events, tracking user activity, tracking referred hits to hosted links.
[Module Co-operation/Re-use:]
I'd recommend co-operation with (at least) the developer of the Ubercart Affiliate & Affiliate modules (integration/.awareness + separation of functionality ?).
Maybe the Affiliate aspects should be separated from the Ubercart purchase-management aspect.
[Answer the above question:]
Buddy list - Definitely not, as I agree it's not appropriate
User Relationships is appropriate - it definitely makes sense to define an "Affiliated to" relationship using that module, to be used for this purpose.
[Expanding my previous post:]
1+2:
This is required to provide a "relationship-link" back to the affiliate for all activity generated by the affiliated visitor/user (e.g. for repeat purchases) {see Ubercart Affiliate module}
Cookie: Enables affiliation of unregistered visitor to be "remembered"
3+4:
It's important to be able to Trigger Actions/Workflow Events/Rules, based on an any of the following:
a. Landing on an Affiliate link page (e.g. to place the Visitor's tag in a NodeQueue, Welcome page redirect, Tracking Advertising clicks, etc.)
b. Assigning an Affiliate Cookie
c. Registering as user from an Affiliate Link
d. Purchasing/Registering for an event as affiliate visitor/user (implies new checks in those environments)
4: It is important to be able to link the newly registered user to the Affiliate, for future tracking of the relationship. (E.g. "My Affiliates" View)
Again, having a Trigger available when the linking occurs would be highly desirable.
[Summary of Stakeholders & Functionality areas:]
Thinking about it, maybe what we are seeing here is the emergence of separate aspects of Affiliation...
a. Affiliate: Tracking & Compensating for activity related to them + Reward Management (% of sale, Userpoints per link click/new-Affiliate user/etc.)
b. New-Affiliate (Affiliee?): Registration and Tracking of their activity
c. A user can be both an Affiliee & Affiliate (multi-level type relationships) - Level (depth) in the Affiliate structure
d. A User can have multiple affiliations (complex case, to be addressed last - requires knowledge of affiliation programs)
Functionality:
1. New-Affiliate Registration & Relationship establishment with Affiliate (Cookie, User Relationships)
2.1 New-Affiliate Link Handling (Events; Logging stats/date-time + "origin" of hits)
2.2 New-Affiliate Link Tracking (Stats, Views)
3.1 New-Affiliate Activity Handling (Events; Logging in NodeQueue, etc.)
3.2 New-Affiliate Activity Tracking (Stats, Views)
4.1 Affiliate Compensation administration (measurement + threshold + value earned)
4.2 Affiliate Activity Reporting & Compensation (Stats on activity, reporting on "Value earned")
5.1 Definition & Administration of an Affiliation Program (Name + Status + Root-Code)
5.2 Reporting on an Affiliation Activity (activity generated per month/Affiliate to-date/this-month)
5.2 Reporting on an Affiliation User Growth (new users generated per-month/Affiliate to-date/this-month)
Hope this clarifies what I was so cryptically asking - (items 1-3 above) ;)
Thank you for considering these features. ;))
#8
Just wanted to say a big thanks now for looking into this and for your detailed report . I hope to get to this v.soon
Best, Paul
#9
I think ill get to this tomorrow :-)
#10
Replies ..
"Maybe the Affiliate aspects should be separated from the Ubercart purchase-management aspect."
Would you consider discussing your findings with the Ubercart project maintainer as i'm not familiar with this
module a this time.
1+2:
This is required to provide a "relationship-link" back to the affiliate for all activity generated by the affiliated visitor/user (e.g. for repeat purchases) {see Ubercart Affiliate module}
Cookie: Enables affiliation of unregistered visitor to be "remembered"
.. Is now implemented in the development branch. The User referral module creates the cookie
4: It is important to be able to link the newly registered user to the Affiliate, for future tracking of the relationship. (E.g. "My Affiliates" View)
.. Is now implemented in the development branch. The Affiliates module makes use of the User referral module to implement this feature
3+4:
It's important to be able to Trigger Actions/Workflow Events/Rules, based on an any of the following:
a. Landing on an Affiliate link page (e.g. to place the Visitor's tag in a NodeQueue, Welcome page redirect, Tracking Advertising clicks, etc.)
b. Assigning an Affiliate Cookie
c. Registering as user from an Affiliate Link
d. Purchasing/Registering for an event as affiliate visitor/user (implies new checks in those environments)
.. I need to give this some thought. Would welcome further discussion.
#11
Have a look at the Ubercart Affiliate module: http://drupal.org/project/uc_affiliate2
It achieves many of the business requirements I listed previously:
I strongly recommend co-operation between these 2 modules to establish an awesome combination. ;))
Thank You for your hard work on this important module.
#12
I have installed ubercart on a clients site recently so now have a good understanding of how this module work. I shall take a look at this module in the near future and report back.
Best, Paul
#13
An issue with ubercart affiliate module is that there is no userpoints integration.
Chris