Quote:
|
Originally Posted by The Ghost
I don't think it is a TMM (NATS) question persay, but more one for programs who have gone from one affiliate management system to another. It would be interesting to hear MANSION's take on it as well, and insight from the actual programs that have done this transition. A list of those programs would be a good start.
As I stated earlier, we went with NATS from day one to avoid any future integration problems such as this. Better to have it clean and working well the first time through. I know the information for affiliate referrals in NATS is stored in a database and not accessable through the NATS admin.
A list of referrals would have to be accumulated and imported, but it seems as though it would be a large task to check the original referrals from CCBill or what have you, then check to see if any of those affiliates signed up again to the new system. And if the referrer has signed up to the new system as well.
Not saying it is impossible, but it seems like something that would be incredibly difficult for a program to keep track of. It may be something where an affiliate might lose all referrals the new referrals, unless they know their specific referred accounts. The old account would still be active until those rebilling members/links become unused.
Great business thread After Shock Media. This one will be bookmarked.
|
Just saw this thread hence my late response. Since we are mentioned specifically I will answer albeit it being a Nats thread.
I will go into a transition from CCbill specifically since that is what the discussion is about.
When we import affiliates from CCBill:
1. We first get a list of the affiliates with all their info and import them in MPA3. We keep track on the old CCBill affiliate id for each affiliate we import, so we can cross-reference later when we convert the link codes, which link for which MPA3 webmaster is
2. We create new sub accounts in CCBill and set them in MPA3, so these accounts can be used for the new signups only - the one that go through MPA3. The old sub accounts stay, and any recurring memberships the client already has will rebill in the old sub accounts. This way it will be clear that the payout generated in the old accounts is for the rebills of the old sales and this payout is not paid via MPA3.
3. We set the old sub accounts to redirect all the incoming traffic to the MPA3 tracking script, and also pass all the link parameters to the MPA3 tracking script. This includes the affiliate id, sub account id, etc.
4. A massmail is sent to the affiliates, with their MPA3 login information, so they can login and check their stats in MPA3.
How it works:
When an old CCBill link is used, it is redirected to the MPA3 tracking script, MPA3 checks the passed parameters, queries the database and finds out which MPA3 webmaster (imported from CCBill), matches the CCBill affiliate id passed to the tracing script. It also checks the sub account id, so it can be clear what site is the hit for.
Then the tracking script translates this information into MPA3 parameters and redirects the surfer further to the tour page. If the surfer signs, the affiliate that sent the surfer is credited for the sale.
Webmaster referrals: CCBill affiliate export contains referral webmaster for each webmaster. At the time of the import, the MPA3 script is checking for each imported affiliate which webmaster has referred him and assigns the affiliate under that affiliate.
--- This will work the same way if we import from a competing product, processor, etc.
