Follow this documentation page for Aweber-to-DAP integration only if you’re using DAP 4.3.1 or older.
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.
Now, if the flow is from DAP-to-Aweber, and are using email parsing to integrate DAP and Aweber, then your Aweber list will always be double-opt-in (as per Aweber policy, nothing to do with DAP).
But if you want your Aweber list to be single-opt-in, then you can use an Aweber signup form on your squeeze page (instead of the DAP sign-up form) and then have Aweber add users to DAP.
Please note that you cannot use this flow for Paid members – because paid members will need to have paid first, which means DAP needs to process their payment first, and if successful, it can add them to Aweber. So for paid members and paid content, always use the other DAP-to-Aweber flow.
But for free signups (say, like when you’re trying to build a list), you can add them to Aweber first using the flow explained below, just so you can take advantage of making your Aweber list single-optin, and then have Aweber add the subscriber to DAP on the other end. So this way, DAP can then create a free account for them, email them their login/password, and give them access to the “Free” content (that is, content available only to “Registered” users, so to speak), etc.
So here are the steps…
1. Go to DAP Dashboard > Products > Manage page.
2. Note down the Product Id of the product to which you want to sign-up the users (after adding them Aweber first, of course)
3. There is a file called dap-aweber.php in the dap folder. Make a copy of that file and call it dap-aweber-PRODUCTID.php.
Replace with the text PRODUCTID with the actual Product Id you noted in the previous step.
So in the example above, Product Id is 2. So the name of the file copy should be dap-aweber-2.php.
4. Open this file (dap-aweber-2.php).
The first line of code in this file looks like this:
$default_product_id = 1; //Change this to any product id from DAP
Change the part shown in bold below:
$default_product_id = 2; //Change this to any product id from DAP
Upload this file back to /dap folder on your site.
If your Aweber list is single-optin, then follow the steps below. If not, skip to “Aweber List Is Double-Optin” flow further below.
5. Now login to your AWeber account.
5A) From the “Current List” drop-down, select the list that you wish to sign up users to.
5B) Click on “Web Forms” in the menu at the top.
5C) Edit existing form by clicking on the name of the list.
6. On the next page – the list form generator page – click on ‘Go to Step 2’ towards the bottom of the page.
7. On the next, page….
7A) Click on the thankyou page dropdown and select ‘Custom’.
7B) 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 ProductId of the product you noted in step 2.
So, if the productId of the product in DAP is 2, then the thankyou page URL will be – http://yoursite.com/dap/dap-aweber-2.php
7C) Where it says “Pass Form Data”, check the check box so that Aweber can “Forward subscriber information to your thank you page” – which essentially is DAP, so that DAP can add the subscriber to your membership site.
That’s it!
In this flow, set up your Web Form as usual, with no DAP-specific settings required.
Only change required is in the Aweber list’s main “List Settings” page.
5. Now login to your AWeber account.
6. From the “Current List” drop-down, select the list that you wish to sign up users to.
7. Go to My Lists > List Settings
8. Go to “Confirmed Opt-In” tab
9. Scroll down to “3: Success Page“, and enter the URL of the special dap-aweber-2.php script (or whatever the file name is) you created back in Step #4 above.
Check the check-box that says “Pass subscriber info for personalizing this page”.
Ignore the comment that says “Not recommended for WordPress users”, because this is going to point to a DAP script, and not a WordPress page.
Click on “Save Settings”.
That’s it!
Now that you’ve set up DAP to integrate with your Aweber list (single- or double-optin), you may use the Aweber web form directly on your squeeze page for signing up subscribers (instead of DAP’s “Direct Signup Form”).
Now, every time a subscriber signs up via the Aweber form, they will automatically be added to DAP.
If your list is single-optin, then the subscriber will be added to DAP instantly after sign-up.
If your list is double-optin, then the subscriber will be added to DAP only AFTER they’ve clicked on the Aweber double-optin confirmation link.
In both cases, they will be redirected to the DAP Login Form.
You may also configure the DAP Product’s “Welcome Email” to send out the DAP email and password via DAP itself.
-OR-
You can leave the Welcome Email in DAP Product page as blank. And then configure DAP to generate a default password (DAP Admin > Setup > Config > Default Password) as shown below, and then enter that same pre-chosen password in to your very first Aweber follow up email that goes out to your subscribers, so that they can receive their dap id/password details directly from your Aweber list.
For more details about this default password, please see this post.
NOTE: If you want to send the subscriber to a different page (instead of the DAP login page) upon sign-up, then do this:
This way you can redirect users after they complete the Aweber signup, to a landing page of your choice.
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.
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.
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.
You already know that you can create a “My Content” kind of page within WordPress, that will list all products that a user has access to, and then each product will list the content that they currently have access to (content that has already dripped on them).
But this page is a full-summary of all products, all listed on one page.
Instead, if you wished to create product-specific download pages, where you create a separate page for each product, that lists all the content within just that product alone, then that’s where DAP’s “ProductLinks” Widget comes in handy.
Here’s how you set it up.
Replace the entire text <id> with the actual Product id from DAP (Products > Manage)
So, if the product’s id is 6 in DAP, then the merge code becomes:
%%PRODUCT_DETAILS_6%%
Save the page. And if you gave the page the title “Gold Membership Content”, then the permalink for this page will be:
http://YourSite.com/gold-membership-content/
NOTE: We do not provide support for server or domain moves as part of Standard DAP Support that you get with your purchase of DAP. Please see our Terms Of Support which explains why. If you want our help with moving a DAP installation, you may purchase Premium Support slots from http://DigitalAccessPass.com/buynow.php#store (see “Installations & Support” tab)
DAP does not store the domain name anywhere in the database. So if you want to move an existing installation to a new domain, the only place where you need to change your domain name in the DAP installation (if you’re moving across domains) is in the dap-config.php file.
Moving a DAP installation consists of basically moving the files, and moving the database. Only 2 components.
DAP allows you to easily import users in bulk from an external system or database.
Importing users in bulk is the same as adding users one at a time using the single-user-add feature. So whichever way you manually add users, DAP is going to all of the following…
When you do a single-user-add, all of this is done for that user in real-time. When you do a bulk-add, then all of the above happens for each user being imported, one at a time, when the DAP hourly cron job runs at the top of every hour. That’s the main difference.
1) You must have already created the DAP 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)
For doing a simple import of user data containing just email, first and/or last name, the format of data (per user, per line) should be like this:
Email,FirstName,LastName
Email and FirstName are mandatory. But LastName is optional. So your user data row could be just…
Email,FirstName
Example:
Joe@example.com,Joe,Customer
Jill@anothersite.com,Jill
Bob@another.com,Bob,Member
DAP will also allow bulk import of users with extended profile information. This includes their existing password and other profile data as detailed in this video (Bulk Add Users)
But please make sure you are using at least DAP v4.2.1 and LiveLinks v1.7, because what’s explained below is only available only since then.
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,Password,ProductName, Address,City,State,Zip,Country,Phone,Company, Flag (to indicate Paid or Free user), Access Start Date, Access End Date,UserName
Example:
joe@somesite.com,Joe,Member,test123,Example One-time Product,99 hill ave,Cityname,NY,10001,USA,,Plug and Play Inc,y,2011-03-16, 2012-03-15,JoeMember
The only required fields are Email, FirstName and ProductName. If you do not want to supply a value for any of the optional fields, but still wish to import certain others, then just leave those fields empty in the data row (but the commas should remain) as shown below.
Email,Firstname,,,ProductName,,,,,,,,Flag (to indicate Paid or Free user), Access Start Date, Access End Date,UserName
Create a file with the name /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, by visiting:
http://YourSite.com/dap/dap-bulkImport.php
Note:
* Replace “YourSite.com” with your actual domain name
* Limit the number of users you are importing with this method to not more than 500 users (rows) at a time. Otherwise the import may timeout, because the import occurs real time, because you’re running the script manually, and 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.
DAP is not an email service (like, say, Aweber).
DAP is just a script – a tool – like Microsoft Outlook or Thunderbird – that simply sends out email using your web host’s email server.
It is your web host’s mail server that actually sends out the email to the recipient. So once DAP notifies your mail server about a email that is to be sent, it has absolutely no control over what happens next.
It’s like when you put an envelope with a letter (regular mail) into the mailbox (post box). It is up to the Postal Service to actually pick up your letter, and deliver to the destination address. Your web host is like the Postal Service. If it doesn’t pick up and deliver the (e)mail, then DAP doesn’t have any say in it.
So if the emails that DAP sends out are not getting delivered to your recipients (or landing in the spam/junk folder of the recipient), there could be more than one reason for that.
DAP uses your web host’s email servers to send out emails.
Here are some ways to improve email deliverability and also avoid your email landing in the recipient’s junk/spam folder.
If you are on a shared host, you may even consider totally by-passing sending emails through your web host, and instead use DAP’s “SMTP” feature to send emails out through an external email system – like Amazon’s SES (Simple Email Service) , Gmail or AuthSMTP.com.
If Admin notifications are going out ok, but the welcome email to the buyer/member is not being delivered, then see Troubleshooting Welcome-Email Delivery
If yours is a new site setup, then this is usually because the hourly cron-job has not been setup.
However, if the emails were going out fine previously, and suddenly stopped going out, then it usually is because…
Steps to troubleshoot
If your inexpensive (read as cheap 🙂 shared web host is hosting a large number of sites on one server, and one of them knowingly sends out spam (or mistakenly gets flagged for spam), that will put the email deliverability of every web site on that server in jeopardy, because your site now shares the same IP address as that of an “alleged” spammer.
So your emails get sent to junk/spam folder by Gmail and Yahoo. Or worse, they just totally disappear into the ether.
Almost all shared hosts have hourly email sending limits. For example, DreamHost has an outgoing limit of 300 emails per hour. Which means, a total of only 300 emails can be sent out per hour through any web site hosted on DreamHost. All of the following count towards the 300 limit:
So do you see how quickly you can go over that hourly limit of 300 emails per hour?
But here comes the worst part…
Once you go over that limit, any emails that are actually sent by you or the scripts running on your site, will not actually result in any kind of error. The mail server will respond by saying that the email(s) has been sent successfully, but in reality, on the backend, it quietly “snuffs out” the email. Which means, it doesn’t go anywhere – just gets sent to a “blackhole”. So you keep thinking that you sent out the email. DAP keeps thinking it has sent out the email. But in reality, the emails never actually get sent.
This is the same as you actually putting your letter into the mailbox at the Post Office. But then, imagine this: The postal worker who comes to pick up your mail, quietly goes to the back of the post office and dumps it all into one giant trash can, and destroys all of the mail. So you’re thinking you actually mailed out that important check to pay your utility bill. But the utility company never gets your check, and they slam you with a late fee.
1) BEST OPTION: DAP + 3rd party SMTP service provider like Amazon SES, AuthSMTP.com or SMTP.com. (much less expensive than Aweber, and very reliable too)
2) DAP + Aweber (more expensive, very reliable)
3) DAP + Good web host (cheapest option, but can lead to mixed results – depends on your host).
You could always use DAP and external SMTP service provider like Amazon SES, AuthSMTP.com or SMTP.com to send out bulk mail through DAP while totally bypassing your web host’s email system. This is probably the first best option where DAP controls the composition and sending of the email, the 3rd party service controls the deliverability.
Next best option is using a service like Aweber or GetResponse.
And if you can’t afford even that, then simply use DAP on a good web host. We ourselves use just DAP and LiquidWeb’s email servers to send out emails to all of our users.
And DAP also has built-in job queues to schedule outgoing emails while also making sure that you don’t exceed your web host’s hourly email sending limits (dreamhost’s limit is 300 emails/hour, I think). We use multiple SMTP servers from our own other web sites, all combined to be able to send a few thousand emails per hour.
But even with a lot of planning, it is easy to go over the hourly limit.
So the next time you see in your Job Queue that emails were sent out successfully, but the recipient never received it, here are some things to check:
1) It landed in your recipient’s junk/spam folder. Ask them to whitelist or add your email address to their contacts list.
2) You have overshot the limit, so you would have to actually send out the email again.
3) Try to send out broadcasts during a low-traffic time – say like later in the night – when you’re not actively sending out emails, and using up precious email counts from that hourly quota.
http://DigitalAccessPass.com/documentation/?page=/doc/troubleshooting-email-delivery/
There are a few different reasons why this may not be working.
The DAP email-processing cron that processes the 1SC emails may not be running. Check your webhost control panel -> Cron job settings. Make sure dap-emailorder.php is setup to run once every 10 minutes.
The billing email id you have entered in DAP at Setup > Config > Payment Processing , should be entered into the “Order Notice Email – Primary Destination” field in your 1SiteAutomation/1Shoppingcart account, on the Setup > Orders > Notifications section. If by chance you enter it into the “Order Notice Email – Primary Destination” field, it WILL NOT WORK.
The DAP cron is running but 1SC payment notification emails are not reaching your mail server. Check the email account where you expect to receive your 1SC payment notification emails and see if the order notification email from 1SC is in that mail box.
The cron is running and the 1SC order notification email is reaching your mail server – but you did not configure the mail server settings correctly in DAP Dashboard -> Setup -> Config -> Payment Processing.
Email Server Where Order Emails Come In
Email Server User Name
Email Server Password
DAP only processes order notification emails that are in the “Unread” status, to prevent previously processed emails and other non-DAP emails from being repeatedly processed.
Also, if you “pop” off the emails from that mail box (means, your email client like Outlook or Thunderbird or Gmail is “removing” your emails from the server when it retrieves them), it means that when DAP logs in to that billing email address, there are no emails there to be processed – the mailbox is empty, or the 1SC payment notification emails have somehow gotten deleted from that mailbox.
So it is possible that DAP is able to connect to your email server, but DAP is not finding any “unread” emails. Please login to your email server and mark all the payment emails that you want DAP to process… as “unread”. And also make sure that your email client does not remove the emails from that mail box.
There might be a “Product Name” mismatch. The product name has to be EXACTLY the same (including case, spaces, etc) in both DAP as well as in 1ShoppingCart. So if you have created a product by name “Widget A”, make sure your 1shoppingcart product also has the exact same name “Widget A”.
If everything is setup correctly, DAP cron will run every 10 minutes and try to process all 1SC emails.
The next time the DAP cron will run (every 10 minutes), it will pick up all the unread payment emails from 1SC.
Welcome email is not getting sent.
Select the product, and make sure there is some text in the “Thankyou-Email Subject” and “Thankyou-Email Body”. Whatever is in these fields is what gets sent immediately after someone purchases that product (or right after you give them access from the backend).
Now go to DAP Dashboard -> Users -> Add .
Select the product and manually add user. Now see if the thankyou email gets sent to that email id. If it got sent, then your product setup is correct.
Also check the DAP Dashboard -> Orders . Search for all orders, look up the order for the particular user in question by email.
Check the payment status and make sure there is no error there.
If you did all this and things are still not working, please do this:
1. Set DAP Dashboard > setup -> Config -> Log Level -> Log All activity
2. Re-run the 1SC test purchase
3. Check the DAP Logs (DAP Dashboard > System > Logs) and send us the log text in there for troubleshooting by pasting it into a new support ticket.
Make sure you have set the thank-you message with the right merge tags for Email and Password.
First set DAP Dashboard > setup -> Config -> Log Level -> Log All activity
If you feel that the orders were not processed in dap, then just login to the 1SC email account where the sales/payment notification emails are sitting, and mark those orders/emails as UNREAD that you want dap to process.
Then manually run the cron script dap-emailorder.php cron by visiting the following link in the browser.
http://www.yoursite.com/dap/dap-emailorder.php
Replace yoursite.com with the name of your site.
It will just display an empty screen when complete.
Then check “Users > Manage” to see if user has been created.
– Veena Prashanth
If you have multiple products that have quite similar settings and content, you could save time by starting with just one product (either the lowest level, or the highest level), and then using the “Save As New” button to make an exact copy of that product, and then adding or removing content from this new copy to create new products.
So, let’s say you have say 3 membership levels: Silver, Gold and Platinum.
“Gold” will have all the content that “Silver” has, plus some more.
“Platinum” will probably have everything from “Gold”, plus some more.
So the way you could save time setting up all these 3 levels, is to either start with the lowest level, or the highest level.
Let’s say you start with the lowest level, “Silver”.
So create the “Silver” product fully, set up all the content dripping, email dripping etc.
And then once you’re done, while still editing the “Silver” product, click on the “Save as New” button (next to the “Save” button on the Product page).
That will create an exact duplicate of the “Silver” product – with all of its settings, content dripping and email dripping intact. And this copy will be called “Silver Copy” (just the text Copy added to the end). And this new copy will already be selected for you.
Now rename this new product from “Silver Copy” to “Gold”, save it, and then continue to add more content to it.
Then, finally, when “Gold” is fully ready, again do a “Save As New”, which would create a “Gold Copy” product.
Rename the “Gold Copy” product to “Platinum”, save it, and continue to add more content and emails to it.
Get the drift?
NOTE: On the flip site, you could also start by creating the “Platinum” product first, and then keep doing a “Save As New” and continue stripping out content to create the lower membership levels.
You wish to do what we call a “silent” import. Basically, you don’t want DAP to send out the instant “thanky-you” email to the users being imported.
You may want to do this, say, if you wanted to import a bunch of users into DAP first, without DAP sending them any kind of emails at all, do some preliminary testing, make sure their settings, product access, etc, are all correct, before notifying them of any changes.
1. Remove the “ThankYou-Email Subject” and “ThankYou-Email Body” from the Product into which you wish to import users. Save it in a text file for later, and save the Product.
2. Go ahead and do the bulk-add of users from “Users > Add > Bulk-Add Multiple Users To A Product”.
3. Wait for the DAP Hourly Cron to run and finish importing all users. Since the “ThankYou-Email Subject” and “ThankYou-Email Body” of the Product is empty at the time of import, DAP won’t send out those emails.
4. Once all the users have been imported, put back the “ThankYou-Email Subject” and “ThankYou-Email Body” text content, and save the Product.
OPTIONAL
5. At a later point, if you want, you can send out an Autoresponder email – or even better, a Broadcast email – with the merge codes for the email and password, if you want the newly imported users to get their passwords, or if you wish to notify them of anything at all (like the new system you’re using, their new account info, a general “what has changed recently” type of email, etc).