There are many reasons why an email is not delivered to the recipient.
And the list goes on!
That should give you an idea why email delivery is so tricky and complicated, which is what created a niche for the email delivery industry, and which is why companies like Aweber, MailChimp and GetResponse even came into existence and have thrived while charging a hefty fee for what you would think is the simple act of delivering email over the interwebs.
When you use DAP for sending out emails (whether autoresponder or broadcast emails), the “From Name” and “From Email” you set up in the DAP Config are used to send out the emails.
If you use your own web host as the “carrier”, then your web host’s email server is the one that carries the email and tries to deliver to the inbox of the recipient. And web hosts are generally not very good at the intricate science of email delivery, which is why if you’re going to use DAP, we recommend that you bypass your web host and have a third-party email system like Amazon SES deliver your emails.
Regardless of the carrier (web host, Amazon SES, AuthSMTP.com, etc), all bounced and undeliverable emails come back to the “From Email” that you have used under DAP Config.
DAP by itself does not do anything with those emails, as those emails don’t come back to DAP, but they go straight to the inbox of whatever “From Email” you have specified.
We will surely address this in the future. But for now, you will have to manually review those email bounces, see which one of them sound more serious (like, say, recipient email id not found, or domain no longer in use, etc), and then de-activate those email id’s from your DAP database.
When you use Amazon SES, Amazon by itself also monitors email id’s that have a consistent history of bouncing back, and will automatically suppress those email id’s and won’t even deliver email to those email id’s even if DAP did send the actual email to those id’s.
Or also called as network builder. And we introduced this feature in DAP v4.4.
We call it DAP “Upline” – basically a shortcode called [DAPUpline] that allows you (site admin) to display the person’s upline’s affiliate code to the person. So in effect, it is a downline builder.
1) John joins your site
2) John fills out profile with (say) his ClickBank nickname
3) John refers Adam
4) When Adam logs in, he sees affiliate link to some xyz third party product, but CB nick in the affiliate link is replaced with John’s CB nickname.
5) Adam fills out his profile with his own CB nickname
6) Adam refers Jill
7) When Jill logs in, she sees affiliate link to same third party product, but cbnickname is replaced with Adam’s CB nickname.
This can be done with any number of third-party programs, as long as the nickname can be easily replaced with the info provided by the upline affiliate.
DAP even takes this one step further.
When Jill joins through Adam’s DAP affiliate link, if Adam has not filled out his CB nickname in his profile, then the third-party CB link shows CB Nickname of Site Admin in its place.
So if an affiliate fails to claim his affiliate link, then site admin gets credit for it (and all such links).
Here’s the documentation for [DAPUpline]
Q: How to automatically add a new user in DAP to a 1SiteAutomation.com (1SA) list (or other 1Shoppingcart – 1SC – private label)?
A: Every list in 1SA/1SC gets a unique email id – like email@example.com ).
Add that to the “3rd-Party Notification Email Ids” field of the DAP product (under Products > Manage > “Notifications” tab)
And make sure you set the “Direct Subscribe” field in your 1SA/1SC list to be “On”.
DAP’s Amazon SES integration has been heavily tested, and we use it ourselves at DigitalAccessPass.com . So you can rest assured that there are no “bugs” of any kind.
Here are some troubleshooting steps if SES integration is not working even after you’ve followed the documentation exactly.
In this article, you’ll see how to integrate DAP with AuthSMTP.
DAP integrates with ClickBank “PitchPlus”, which is their 1-Click Upsell process.
So you can basically start by selling one front-end product, and then if your buyer purchases that product, you can then upsell them more products right after, and since they’ve already entered their payment information once, ClickBank remembers this information and allows them to purchase further products without having to re-enter all of the information again.
The basic idea is the same for DAP/CB integration, whether it’s one product, or multiple Upsell products .
You basically do a one-time set up of INS and the secret key as explained here.
Once that’s done, then for every Front-end product or Upsell-product, they are all integrated with DAP the same way: You just make sure the “Item Name” in CB and the “Product Name” in DAP both match, that’s it!
And for the last product in your upsell, be sure to point it to a static page containing a message like “Thank You, please check your email inbox for login details”.
And since CB notifies DAP separately for each product purchased, right then and there, if they end up buying 3 products during checkout (1 main + 2 upsells), then DAP will send the user 3 separate welcome emails. Of course, that’s optional – you don’t have to send out a welcome email for all products, but we highly recommend that you do.
Plus since they would be using the same email id for all 3 purchases, DAP will give them access to all purchased products under a single DAP account. So they need to log in to just one account to access content from all products that they just purchased.
You try to visit a protected page that you’re not eligible to view, and see an ugly page full of un-formatted links
Save, and that will no longer display the ugly error page going forward. Instead, it will redirect the user to the above custom error page.
You try to visit a protected page that you’re not eligible to view, yet you are still able to see all of the content. Or the page appears messed up with missing menu items or formatting issues.
WARNING: Gmail integration may not work for everyone. Many factors – including, but not limited to, your physical location, the location associated with your Gmail account, location of server, IP address, etc – appear to play a role in whether or not this will work for you with your Gmail account. So please note, that if it doesn’t work for you, then there isn’t anything the DAP team can do to overcome or “fix” that. It’s Google, after all. We don’t know what rules and monitoring they have in place for this. So, if Gmail integration doesn’t work for you, then you may want to consider Amazon SES integration, which has a 100% success rate with DAP users at this time.
To increase deliverability of your autoresponder, broadcast and instant emails (like “Welcome” email), you can make DAP completely by-pass your web host’s email server, and send emails out through third-party email servers, like Gmail or Amazon SES. This article is about setting up DAP to send out emails through Gmail’s email servers.
Before you start sending out mass emails through Google’s Gmail Servers, please note this…
Sending out emails through Gmail instead of your web host, will surely boost your deliverability, no doubt. But remember that Gmail is NOT meant to use for mass emails. It is not really meant to be used as a list service. Plus they have a very strict restriction of 500 emails per 24-hour period.
You exceed that quota even by one, and they probably will temporarily disable your Gmail account for about 24 hours. Sending a large number of un-deliverable emails (resulting in bounces) could also get your entire Gmail account permanently suspended. And if you lose your Google username, it may (no confirmation available) affect your other Google accounts too – like AdWords or AdSense.
Anyway, DAP has a round-robin emailing system – so you could set up and use multiple Gmail accounts – each with its own 500 email limit per day – and combine them to send out a larger broadcast. However, remember – we’re talking about Google here – which means they can suspend/cancel/delete your account for any reason at all, even more so when you’re going against their TOS.
So use Gmail with caution, and only for smaller lists. If you want a larger sending email limit, check out the DAP integration with Amazon SES which allows you to send out tens of thousands of emails a day.
You can hook up DAP to Amazon’s Simple Email Service (Amazon SES) and have all of your emails go through Amazon’s beefed up, high-performance, high-deliverability email servers.
The document below explains how to connect DAP to Amazon SES. (troubleshooting info for DAP/SES integration)
So if the server name displayed in your Amazon SES account is this…
…then the text you would enter into the DAP Email > SMTP page is this…
Watch this video for details:
DAP is so powerful and flexible, that you can sell access to your membership through different payment processors, all at the same time.
And we often get asked how to leverage different affiliate networks like ClickBank and JVZoo and Warrior Plus at the same time while making sure no affiliate commissions are lost, and every affiliate gets credited their commissions for sending potential buyers to your site.
1) If buyer arrives ONLY through DAP affiliate link, and ends up purchasing through ANY payment processor, then DAP affiliate will get credit.
2) If buyer arrives ONLY through CB affiliate link, and ends up purchasing through CB payment processor, but the buyer has a different DAP affiliate’s cookie from a link he clicked on at some point before (but did not purchase at that time, say), then both CB affiliate and DAP affiliate will get credit (double commissions on same purchase, but to two different affiliates).
If there’s no DAP cookie on his computer, then only CB affiliate will get the commission.
If the DAP affiliate “chains” two of his own affiliate links – his DAP affiliate link and CB affiliate link – like shown below, then same affiliate will get both CB commission as well as DAP commission. Again, double commissions but to same person.
3) If buyer arrives ONLY through JVZOO affiliate link, and ends up purchasing through JVZOO payment processor, but the buyer has a different DAP affiliate’s cookie from a link he clicked on at some point before (but did not purchase at that time, say), then both JVZOO affiliate and DAP affiliate will get credit (double commissions on same purchase, but to two different affiliates).
If there’s no DAP cookie on his computer, then only JVZOO affiliate will get the commission.
If the DAP affiliate “chains” two of his own affiliate links – his DAP affiliate link and JVZOO affiliate link – like shown below, then same affiliate will get both JVZOO commission as well as DAP commission. Again, double commissions but to same person.
To make sure that you’re not paying double-commissions on purchases, and also to make sure that sales don’t get lost between affiliate networks (and your affiliates losing their commissions in the process), you have to set things up the right way.
The main thing to do, is to create a separate set of the following for each affiliate network:
So the net effect of this, is…
If a CB affiliate sends traffic to a page, that page must have a CB buy link ONLY on that page. If you have, say, a JVZoo button on that same page, and the buyer buys through the JVZoo link, then the CB affiliate will get no commissions for that purchase. Which means, they will stop promoting your product because you’re basically funnelling off their visitors to a different affiliate network.
Similarly, the landing page for JVZoo affiliates must have only JVZoo buy buttons.
Landing page for a regular payment processor – like Paypal or Authorize.net – should have only a Paypal and/or Authorize.net buy button (and no CB or JVZoo buy buttons). In this case, for these products in DAP, you should set up an affiliate commission row on the “Affiliates > Manage” screen, so that your DAP affiliates can get credited for sales made through your regular web site.