August 16th, 2010 — Admin, Affiliates, ClickBank, Config, Customization, Merge Tags, Setup
There are many reasons for wanting to do this.
1) You simply don’t wish to let people know that you have an affiliate program – maybe it is so that you don’t want to confuse the mom-and-pop niche that you are in with crazy words like “Affiliate” and “Commission”
2) You deliberately want to disable certain users from using the affiliate link, and not award them any commissions, even though they know what that link is.
3) You are using a 3rd party affiliate service – like ClickBank – and don’t want to use DAP’s built-in affiliate program.
At this time, you cannot really do (2). There is no way to stop DAP from tracking an affiliate’s referrals and not tracking their earnings. Only work-around right now, is to simply not pay them at all, for whatever reason (you better have a very good reason, if not it could be legal trouble for you).
Here’s how you can do (1) – which essentially works for (3) also.
A) If you are using the default dap/index.php as your members’ home page, then all you have to do is to go to…
Setup > Config > Advanced > “Should Affiliate Section be displayed on User `Home` Page? (If using ClickBank, set this to `N`)”
And set it to “N” (for “No”).
That will essentially “hide” the affiliate section from showing up on the default DAP home page.
B) If you are not using the default dap/index.php, and are putting all of the DAP member content (like User Profile, User Links, Affiliate Details) etc right into your WordPress blog, then just skip the Affiliate Details part, and don’t create a custom page for Affiliates within your blog. If you don’t create the page, then they won’t see it, that’s all.
NOTE: If you don’t want anyone to get any commissions, also make sure that you don’t set up any commissions on the “Affiliates > Set Commissions” page.
So basically, in both (A) and (B), you are essentially “hiding” the affiliate program details, and not really disabling it.
In a future version of DAP, we will have the ability to selectively turn off an individual’s ability to use their affiliate link, so DAP will completely ignore all referrals from the affiliate, and won’t track anything from them.
August 15th, 2010 — 3rd Party Integration, 3rd Party List Integration, Aweber, Config, Email, Examples, Features, Merge Tags, Personalization, Setup, Users
Starting DAP 3.8, DAP has a new feature where you can ask DAP to always generate a pre-chosen, default password of your choice for all new members.
So all new users will be assigned the same default password, which they can of course change as soon as (or any time after) they login.
This is especially helpful for new users, if instead of DAP, you want a third-party service like Aweber to send out the new member’s “Welcome Email” which contains their email and password.
Since DAP is unable to pass the randomly generated password to Aweber, instead, you can setup a default password by going to
Setup > Config > Advanced > “If you want DAP to generate a default password for all new users, enter it here. If not, leave blank”
So if you set this password to say, “changethis“, then DAP will give out the same password to all new users.
Then, in the welcome email you configure at, say, Aweber, you would put the Aweber merge code for email id, and then enter this pre-selected password (because you already know what it is) into your Aweber email, like this:
Hello {!firstname},
Welcome to Example.com. You may log in to your member’s area at:
Email: {!email}
Password: changethis
Thank you,
- Admin from Example.com
And if you ever change the default password in DAP, don’t forget to also change it in your welcome email at Aweber (or 3rd party email service).
Also, don’t use the default password in any subsequent emails, other than the Welcome email (very first email sent to member through Aweber), because the member may have already changed their password by then.
WARNING: You must have also set up DAP/Aweber integration first before you attempt to do this.
July 26th, 2010 — Activation, Aweber, Customization, Email, Setup, Uncategorized
Subscriber Flow
The flow of subscriber in this model, is “FROM Aweber TO DAP“. User gets added to Aweber first, then arrives at DAP via Aweber “thank you page”, at which point she gets added to DAP.
If you are looking for the other way, i.e, “FROM DAP TO Aweber”, then click here.
How it works
If you use email parsing to integrate DAP and Aweber, then the Aweber list will always be double-opt-in.
But if you want your Aweber list to be single-opt-in, then you can use the Aweber webform (instead of DAP sign-up form) and follow the steps below to integrate DAP with Aweber.
1. Go to DAP admin panel -> manage products page.
2. Note down the product Id of the product to which you want to signup the users.
3. There is a file called dap-aweber.php in your /dap folder. Make a copy of that file and call it dap-aweber-<productId>.php. Replace <productId> with the product Id you noted in step 2.
If the productId = 2, then you will end up with a file called dap-aweber-2.php.
4. Open this file (dap-aweber-2.php), and change this line:
$default_product_id = 1; //Change this to any product id from DAP
So, in this example, change it to:
$default_product_id = 2; //Change this to any product id from DAP
Upload this file back to /dap folder on your site.
3. Now login to AWeber, select your single-opt-in list in AWeber -> Webform -> click on ‘Go to Step 2′ towards the bottom of the page.
http://screencast.com/t/ZTE0MDhhYTY
Click on the thankyou page dropdown and select ‘custom page’.
Set the thank you Page URL to http://<yoursite.com>/dap/dap-aweber-<productId>.php
Replace <yoursite.com> with the name of your site. Replace <productId> with the product Id you noted in step 2.
4. Use the Aweber web form for signing up customers (instead of dap direct signup form).
That’s it.
Everytime a users signs up via the aweber web form to your site, they will automatically be added to DAP.
You can configure the welcome/thankyou message in DAP to send out the dap login id and password
OR
You can leave the welcome/thankyou message in DAP empty. Configure DAP to generate a default password (DAP Admin -> Setup -> config -> Advanced) as shown in the screencast below and set up an autoresponder in Aweber so when the users signup via the Aweber form, they can receive their dap id/password details via Aweber directly.
http://screencast.com/t/MjY0NGI3
July 20th, 2010 — Customization, Merge Tags, Setup
When you use the merge tag %%LOGIN_FORM%% in a WordPress page, the tag is replaced by a login form that your member can use to log in to your membership site.
If you wish to customize the look & feel or text of the form, then rename the file…
wp-content/plugins/DAP-WP-LiveLinks/DAP-WP-LoginForm.html
To…
wp-content/plugins/DAP-WP-LiveLinks/customDAP-WP-LoginForm.html
Basically you are adding the text “custom” to the beginning of the file name, that’s it.
And this new file will also reside in the same directory.
Once you have this new file in the directory, DAP will ignore the old, default file, and will only use your new custom version.
July 19th, 2010 — Access Control, Examples, Products, Setup
Product Bundling
Any time someone gets access to PRODUCT A (either through direct signup, manual admin add, or purchase), then you can automatically give them access to PRODUCT B. And you can select whether they get PAID access to PRODUCT B or not.
Similarly, when someone is removed from PRODUCT A, you can also tell DAP to automatically remove their access to PRODUCT B.
Very useful for bundling products.
Product Access Automation
User signs up as free user to PRODUCT A.
Later on, user buys PRODUCT B (which is, say, paid version of PRODUCT A).
If you set up Product Chaining, then you can automatically remove them from PRODUCT A when they purchase PRODUCT B. So when you send an email to all PRODUCT A users asking them to purchase access to PRODUCT B, then you won’t be sending emails to those who have already purchased PRODUCT B.
Click on image below to open full size in a new window.

July 9th, 2010 — Access Control, Config, Customization, Examples, Products, Setup
Starting DAP v3.8, we have a new feature called “Product-Specific Details“.
This feature basically allows you to put all of the Product-specific details (including links available to the member as part of that Product) on a specific WordPress page.
Here’s how it works:
1. Go to DAP Dashboard > Products > Manage
2. Select the Product for which you wish to generate the Product-specific details page. Note down the Product Id (it’s a number as shown below)

3. Create a new WordPress Page – give it any title you want. Put in the text…
%%PRODUCT_DETAILS_<insert-product-id>%%
So in the above example, since the Product Id is “1″, the merge code becomes:
%%PRODUCT_DETAILS_1%%

Publish the page.
4. When you view the page, it will show the product’s details.

That’s pretty much it as far as creating the Product details page is concerned.
Where to use this
Starting DAP v3.8, you can now take the permalink for this above page and enter it into the “Logged-in URL” field of the Product. This field is basically for specifying a Product-specific URL for showing users right after they login. So that way, when someone purchases this product, and logs in to your membership site, instead of showing the default member details page, you could show them just a product-specific page.
July 4th, 2010 — Affiliates, Cron, Transactions, Troubleshooting
1) Affiliate was not credited with a sale
There could be many reasons for why the affiliate was not credited to the sale.
1) Buyer didn’t click on any affiliate links before purchasing the product
2) Buyer did click on an affiliate link, but somehow (intentionally – or not) cleared her cookies before buying the product
3) Buyer hasn’t yet logged in to their DAP account after purchase
4) The hourly cron job on your DAP site hasn’t run yet (hourly cron has to have run *after* the buyer has logged in to their account)
5) You have not set up any affiliate commissions for the Product on the “Affiliates > Set Commissions” page
2) Manually credit an Affiliate with a sale
Right now, there’s no way to do this via the DAP Dashboard. We will include this in a future release.
3) Affiliate Program Life Cycle
- You have already set up a “Per Sale” commission for the Product being purchased.
- Visitor clicks on affiliate link and affiliate cookie is set on her computer
- Visitor goes on to buy the product
- Visitor gets welcome email and logs in to your member’s area: This is when the affiliate is actually credited with the referral. So it is critical that if you’re testing the affiliate program, make sure you log in to the new member’s account. At the time of this login, the only thing that happens is: a) DAP notes down that this buyer was referred by this affiliate. b) If you have set up any “Per Lead” commission, then this lead commission amount is credited to the affiliate’s account. So if the affiliate were to log in to his account at this point, they would just see that they have gotten the “Per Lead” commission credited to their account.If there is no “Per Lead” commission, then nothing is credited to Affiliate account at this point. So if the affiliate were to log in to his account at this point, they would see no referrals yet.
- At the top of the hour after the buyer has logged in to their member’s area, the DAP Hourly Cron runs. It sees that Buyer X has been referred by Affiliate Y. It also sees that no commissions have yet been paid for the purchase. So it looks up your Affiliate Commission Structure (that you have previously set up on “Affiliates > Set Commissions”), calculates the commission to be paid (“Per Sale Fixed” or “Per Sale Percentage”), and then credits affiliate’s account with that amount.
- If the affiliate were to log in to his account at this point, they would just see that they have gotten the “Per Sale” commission credited to their account.
June 29th, 2010 — Admin, Cancellations/Refunds, ClickBank, Integration with Shopping Carts, Payment Integration, Paypal, Paypal Website Payments Pro, Subscription, Transactions, User Status, Users
The question
How does a customer, once they have signed up and become a member, cancel their membership (or get for a refund)?
Cancellations
If it’s Paypal, they could go into their Paypal account, and cancel their subscription themselves.
If it’s ClickBank, they can log in to their CB account, and cancel their subscription themselves.
If it’s any other payment processor or cart – like 1SiteAutomation.com, Authorize.net, Paypal Payments Pro, etc – then they have to ask you (the membership site owner) to cancel.
Refunds
Except with CB, in all other cases, they have to ask you for a refund
What Next For DAP Admin?
If it’s a cancellation, then DAP already does “Pay As You Go” processing – which means, their account will automatically expire at the end of the current recurring period (eg., end of current month).
If it’s a refund of just one recurring payment, then you can go into the “Users > Manage” screen, search for the user, and do a “Rollback Access for Selected User(s) to the Product by 1 Recurring Cycle“.
If it’s a refund of the entire purchase, then make sure you “Remove” user from product.
Also see: Cancellations & Refunds
June 27th, 2010 — Activation, Admin, Control Panel, DAP, Database, Installation, Setup, Web Hosting
Here’s how you can move an existing DAP installation from one host – or domain – to another.
- Log in to your web hosting control panel, go to “phpMyAdmin”, select your WordPress database (which is where the DAP tables are also installed, by default)
- Do an “Export” of just the DAP tables. Select the “SQL” option and select “Save as File”. All DAP database tables start with the text “dap_”. Save this file on your desktop – let’s say you call it “dapexport.sql” (it could also be “dapexport.txt” – does not matter what the exact extension is – .txt or .sql).
- Make a back up of the dap-config.php file (located in the “dap” directory on your old site/domain) on your desktop
- At your new site, install WordPress
- Copy the database info from your new blog’s “wp-config.php” to the “dap-config.php” file stored on your desktop.
- Then log in to your web hosting control panel of your new site, go to “phpMyAdmin”, select your WordPress database, go to the “SQL” tab, open the export file from above (dapexport.sql), copy the contents, paste into the SQL tab and hit “Go”. All dap data from your old site is now on your new site.
- Upload all dap files to your new site (don’t do full installation – just upload the files).
- Also upload the LiveLinks files to wp-content/plugins/ .
- Upload the new dap-config.php file from your desktop to the “dap” folder on your new site.
- Log in as WP admin, and activate the LiveLinks plugin. It should give you a warning that DAP is already installed. That’s ok, that’s what we want it to say.
- That’s it. DAP is now moved over from your old site to your new site.
- Log into your DAP Dashboard using your old DAP admin login info, and you’re all set.
June 25th, 2010 — 3rd Party Integration, 3rd Party List Integration, Examples, Products, Setup, User Status, Users
DAP allows you to import users in bulk from an external system or database.
Pre-requisites for Importing Users
1) You must have already created the Product into which the users will be imported
2) The user list has to be in a CSV (comma separated) format (one user per line), with the exact format being:
Email,FirstName,LastName
LastName is optional. So your user list could have just
Email,FirstName
Example:
Joe@example.com,Joe,Customer
Jill@anothersite.com,Jill
Bob@another.com,Bob,Member
How to do the actual import

1. Go to Users > Add > “Bulk-Add Multiple Users To A Product”
2. Paste your CSV list into the large text area
3. Select the Product into which you want to import the users
4. Check the “Mark Users as Paid” checkbox if you want them to have “Paid” access to the content (just as if they are actual paying members). If you don’t check it, they will all have access as a “Free” user (instead of a “Paid” user), which means they will only have access to content within the Product that you have marked as “Free”.
5. Click on the “Bulk Add Users” button.
That will first save this entire list as a CSV file in your /dap/admin/bulk folder on your site.
And then, the next time the Hourly cron (dap-cron.php) runs, it will add them one by one to the product, and send them emails as per your Product set up.
So if your Product has the “Thankyou-Email” subject and body filled out, it will individually send out each of the users that thankyou email.
DAP will also allow bulk import of users with their existing profile
This includes their existing password and other profile data as detailed in this video.
Bulk Add Users
Pre-requisites for Importing Users with their existing password and profile
1) You must have already created the Product into which the users will be imported
2) The user list has to be in a CSV (comma separated) format (one user per line), with the exact format being:
Email,FirstName,LastName
Email,Firstname,Lastname,Password,ProductName,
Address,City,State,Zip,Country,Phone,Company,
Flag to indicate paid or free user
The only required fields are Email and Firstname. If you do not want to supply a value for any optional field (say Lastname), then just it empty as shown below.
Email,Firstname,,Password,ProductName,
Address,City,State,Zip,Country,Phone,Company,
Flag to indicate paid or free user
Example:
you@yourdomain.com,joe,,test123,Example One-time Product,99 hill ave,cityname,NY,12345,USA,,DAP,y
you@yourdomain-1.com,joe1,smith,,Example One-time Product,99 hill ave,cityname,NY,12345,USA,,DAP,y
How to do the actual import
Update the /dap/bulk/importusers.csv file so it has the users you want to import in the format specified above.
Run this script on your browser to complete the import. Replace yoursite.com with the name of your site.
http://www.yoursite.com/dap/dap-bulkImport.php
Note: Try to limit the number of users you are importing with this method to 50-60 users at a time otherwise the import will timeout as the import occurs real time (not via cron).
If the user already exists in dap, then the script will just skip that user and move on to the next user in the bulk add list.