10
DAP can only protect content on the same domain where it is installed.
So, if you install DAP on SiteA.com, then DAP can only protect content (blog posts/pages and files) on SiteA.com.
If you install DAP on subdomain1.SiteA.com, then DAP can only protect content (blog posts/pages and files) on subdomain1.SiteA.com.
DAP on SiteA.com cannot protect content on SiteB.com.
DAP on SiteA.com cannot protect content on subdomain.SiteA.com.
Similarly, DAP installed on subdomain.SiteA.com cannot protect content on the main domain, SiteA.com
Now, let’s say you own a network of web sites, some sell a product, some sell a membership course, some sell a physical product, and some just exist to build a list.
So let’s say you have 10 sites in all.
And you want someone who’s an affiliate on Site A, to be an affiliate for all ten, and be able to get commissions if the person he referred goes on to purchase a product from any of your 10 web sites.
Yup, DAP can handle that. And here’s how…
Configuration #1
Summary: Parent.com has DAP. Your sales pages are all on different sites, like ChildA.com, ChildB.com and ChildC.com. But all buy buttons point right back to the main DAP site (Parent.com) and that’s where all buyers from all child sites are eventually added to, regardless of where the sale was initiated from. So all members are actually created on Parent.com, and that’s where everyone would log in to access the member content.
1) Install DAP on your main “Parent” site where you have all of your content that needs to be protected/delivered. Make sure all of your content for all of your sites is on this main “Parent” (hub) site.
2) You can then have multiple “Child” sites – completely different domains from your parent site – which are basically just “sales page only” sites. Of course you can have a wordpress blog on each of them and have as much content as you want. Just put the main content to be delivered on the Parent site.
2A) On each of these child sites, you can use any DAP-supported payment processors to sell your products. So for eg., on one “child” site, you can use ClickBank, on another, you can use Paypal, on another you use e-junkie, etc.
3) All buyers end up with an account on your “Parent” site, which is where they get to access their content too. You can set up multiple blogs on one site for different look & feel for all of your various products, and deliver content from the specific blog for the specific product. DAP can support multiple blogs on one site, so that’ll work fine.
4) Since all of your actual products are on one DAP installation, your affiliates can use the same affiliate link for promoting all of your “child” sites. Which means, anyone buying any product across your network, will result in a commission for your affiliate
5) Since all of your users are in one database, email marketing also becomes extremely simple. You can send autoresponders & broadcasts all from within DAP
6) And anyone purchasing any product across your entire network, instantly and automatically becomes a “global” affiliate – which means they can straightaway start promoting any of your web sites. So if your parent site is Parent.com, and you have 3 child sites called childA.com, childB.com and childC.com, then your affiliates’ global affiliate link would be:
http://Parent.com/dap/a/?a=1234
Now if they wanted to promote childA.com, they just use the redirection feature of DAP like this:
http://Parent.com/dap/a/?a=1234&p=www.ChildA.com
Or if they want to point to a specific page on childA, they can do this:
http://Parent.com/dap/a/?a=1234&p=www.ChildA.com/specificpage.php
or
http://Parent.com/dap/a/?a=1234&p=www.ChildA.com/blog/specific-post/
Plus we’re coming up with a “N”-tier affiliate program in 4.0, which will make it even more powerful when you club it with the ‘global’ concept explained above, as every new member becomes a global affiliate, and will also get multi-tiered commissions across ALL purchases across ALL of your child sites.
DAP now supports Coupon codes – which again means your global affiliate will be able to use coupon codes for any product across your network. So the extensions are unlimited, and the possibilities are infinite.
Configuration #2
Summary: There’s only one site – Parent.com. That’s where DAP is installed. All child sites and content for those sites, are created in “sub-folders” on the same Parent.com site.
Parent.com has “dap” in its root folder.
Parent.com/site1/ is a blog for Site 1 which has all of the content for whatever is being sold on Site 1. Sales page can be the root of the “site1” blog itself, or in a separate WordPress Page on that blog.
So you will have one blog per site, each installed as a separate WP installation, in sub-folders of Parent.com.
Parent.com/site1/
Parent.com/site2/
Parent.com/site3/
Parent.com/site4/
Each of the above blogs should have their own copy of the “DAP-WP-Livelinks” plugin.
But only one installation of the “dap” folder itself. DAP is in root.
Parent.com/dap/
The blogs must be in sub-folders of the main domain – they may not be in sub-domains.
So, in a nutshell…
- DAP enables to you have one, large, global “store”.
- This is also your content and affiliate hub, while unifying and standardizing content delivery for all of your products,
- This gives your members a “Single Sign-on” facility, where if they log in to your “Hub Store”, they basically never have to log in again
- All of the content can be made available from one “Content Delivery” site
- Your affiliate program goes “Global” – which means if you’re an affiliate for one site, you can promote all sites and all products in the network using just one affiliate link. Which will help you recruit more affiliates, and help get them excited about promoting your network sites.
what i wish to do is have a central dap install,
that looks after all my sites and affiliate programs,
of course i would like different site members to access the down load they bought in they same style of the site they bought
i would like different site members to access the affiliate programs that they enrolled in affiliate program ,
but also let them taste my others,
so each product wold have its own tools affiliate links,
my current set up is a hep desk in my root folder, as that is generic name which will work for all my products,i wold then like to deliver products within this system so each has its own download pages , in its own styleall im asking is do i need 10 wp blogs to do this or just one or none
can blogs and pages be sub-domains or only folders ( you answered this in your last post )thanks for your help |
Response Time: 37 Minutes |
Mon 10 Jan 2011, 18:36pm |
|
» Reply by: Ravi Jayagopal |
|
Here’s how you would do it…Parent.com has “dap” in its root folder.Parent.com/site1/ is a blog for Site 1 which has all of the content for whatever is being sold on Site 1. Sales page can be the root of the “site1” blog itself, or in a separate “WP Page” in that blog.So you will have one blog per site, each installed as a separate WP installation, in sub-folders of Parent.com
Parent.com/site1/
Parent.com/site2/
Parent.com/site3/
Parent.com/site4/
Each of the above blogs have their own copy of the “DAP-WP-Livelinks” plugin.
But only one installation of the “dap” folder itself. DAP is in root.
Parent.com/dap/
Each of the blogs may not be sub-domains – must be sub-folders. |