Entries Tagged 'Config' ↓
May 12th, 2013 — Access Control, Config, Customization, Setup
If you are using double-optin for your DAP product, then you would normally have entered the text %%ACTIVATION_LINK%% in your email body, which is replaced by a unique confirmation link specific to that user.
Normally, when that activation link is clicked, the user is redirected to your login page configured under Setup > Config > Login URL.
But if you wanted them to be redirected elsewhere to a page of your choice, then in your double-optin email body, where you normally enter %%ACTIVATION_LINK%% , enter this instead:
Where “http://link/to/landing/page/” is the URL where you want them to be redirected to after they click on the double-optin activation link.
January 13th, 2013 — Affiliate Program, Affiliates, Config, Email, Setup, Templates
Starting DAP v4.4, you can notify your affiliates with an automated instant email when they earn a commission for a lead and a sale.
In DAP > Setup > Config > (Affiliate Module) you can separately configure which emails to send (Lead, Sale):
And then on DAP > Setup > Templates page, you can configure the Subject and Body for both emails.
November 7th, 2012 — Affiliate Program, Affiliates, Config, Setup
Your DAP affiliate link (for DAP on your site, for your affiliates) by default will take the visitor to your home page.
If you wish to point this default landing page to some other URL – like, say, your squeeze page at http://YourSite.com/squeeze-page/ – then you can change this default landing page URL setting at:
DAP Admin > Setup > Config > Default Landing Page for Affiliates
Please note that this will change the landing page for ALL “default” affiliate links – except those using special redirection.
So it will affect all default affiliate links that look like this:
But it will not affect affiliate links where they’re already setting a special landing page, like:
September 23rd, 2011 — Affiliates, Cancellations/Refunds, Config, DAP, Examples, Paypal, Setup, Transactions
DAP offers a number of affiliate statistics on the “Affiliates > Reports” page.
Here’s how it looks as of DAP v4.2.1.
1) Email Id of Affiliate
This is the field where you would enter the email id of an affiliate, if you want to generate a report specifically for an affiliate. If you leave it blank, the report will include all affiliates.
2) “From” & “To” Dates
By default, if you leave these fields blank, then DAP will assume “today’s” date – i.e., the date whenever you’re viewing this page.
3) View Performance Summary
This is the most detailed report available. This is the report being viewed in the above screenshot. For a given time period, for a given number of affiliates (“all” affiliates if (1) is left blank above), it shows…
- Affiliate Id
- Full Name
- Email id
- Clicks generated during selected period
- Referrals generated (includes total of both Free and Paid referrals): If the referred member actually bought something, it constitutes a “Paid” referral. If they simply signed up, say, for your free newsletter or free report or free product, then it is counted as a “Free” referral.
- Commissions Earned: This is the actual amount credited to the affiliate’s account during the selected period
- Sales Generated: This is the amount of the actual sale (purchase) generated for your membership site.
- Earnings Per Click (EPC): This is an indicator of how well your web site is converting clicks into signups/members. So if an affiliate sent you 100 clicks (on their affiliate link), and 5% of them signed up for your “FaceBook Secrets” membership product by paying $10 each, it means a total revenue of $10 x 5 = $50. And if you were paying 30% affiliate commissions for the product, then the affiliate earned $15 in total.Total clicks sent: 100
Total affiliate earnings from those 100 clicks: $15
Earnings Per Click (EPC) = $15/100 = $0.15 – which means, 15 cents per click.The higher the EPC, the easier it will be for you to attract other JV partners and super-affiliates.
4) View Earnings Details
This shows the breakdown of each purchase referred by each affiliate. It’s a detailed view of the affiliate earnings, that lists each and every transaction (order) in the system that was referred by affiliates, all generated for the selected time period. It displays…
- Affiliate Id
- Full Name
- Email Id
- Product (name) that was purchased by referred buyer
- Referral Date (when affiliate was associated with buyer)
- Date/Time of actual transaction
- Trans Id: This is the transaction (order) id for the actual purchase
- Earning Type (L: Lead, S: Sale): Says what type of a commission credit it was – whether it was a “Pay Per Sale” credit or a “Pay Per Lead” credit.
- Id of User Referred: This tells you the actual user id of the buyer who was referred by the affiliate.
5) View Payments
This shows all payments made to affiliates during the period.
6) Refund Period
This is a config setting that you can change in Setup > Config. This is what drives which orders are picked up for affiliate payment. See this article for more details.
7) View Due Payments as of <date>
This is the MAIN button you should click to start the process of paying your affiliates each month (or however often it is that you pay affiliates). When you click this button, it will show you a report (see screenshot below) of commissions owed on all orders in the system UNTIL X days ago, where X is your “Refund Period”.
So if today is 10/01/2011, and you have a refund period of 60 days, then DAP will only consider orders prior to 60 days as of today. Which means, orders up to 08/01/2011 (of course, depending on how many days in a month, you may not exactly end up with 08/01/2011, because it goes an actual 60 days back from today – and sometimes, the report will stop at the 2nd or 3rd day of the month – like 08/03/2011. But that’s ok, don’t worry about it). You just focus on paying your affiliates on whatever day you wish to make the payment.
So when you click on this button, DAP will bring you a summary report of all affiliates, and how much they’re owed today, for all transactions referred by them as of 08/01/2011 (as per this example).
And when you click on the “Export These Affiliates For Payment” button shown in the screenshot above, DAP will select and mark those affiliates as being exported for payment.
And DAP will show you Paypal Mass-Pay Ready text report, with the affiliate info and the commission amount info already filled in and ready to go. If you’re paying via Paypal Mass-Pay, then all you need is this file. See this post for details.
NOTE: Being exported for payment doesn’t mean that you’ve actually paid them. Exporting affiliates for payment only means that DAP has now “set aside” those affiliates for payment, and you still need to tell DAP that you’ve actually paid your affiliates.
This is important, because you might export affiliates for payment on the first of the month, but it may take you a day or two (or 10) to actually make the payment – especially if you’re sending out Checks.
So once you’ve made the payment either through Paypal mass-pay, or by mailing your affiliates physical checks, then you need to tell DAP that you’ve actually sent out the payments, which is what you’ll do in the step below.
8 ) Mark Affiliates from <export> as Paid
This is where you will select the most recent export from the drop down (see #8 in first image at the very top), and click the “Paid” button. This is what actually lets DAP know that you’ve actually made the payment, and only after you do this, will the affiliates see the payment show up in the “Payments” section on their “Affiliate Info” page.
9) Archived Reports
This is just a report that shows you past commission payment exports.
July 22nd, 2011 — Access Control, Admin, Config, Customization, DAP, Examples, FAQ, Features, Merge Tags, Protecting Content, Protection FAQ, Setup
DAP has a very powerful, flexible and easy-to-use log in flow for your users and members.
- Log in from a dedicated log in page, or
- Log in from the login form on the side-bar, or
- Log in through the log in form shown on “Sorry, you don’t have access to this content. Please log in first…” kind of error messages.
And we call it the Smart Login, because the login process will work differently under different conditions, all designed to make the user-experience for your member more smooth and consistent with general login standards around the web.
So let’s see the various possible login locations in DAP.
But first, it is important to note that DAP has two main types of logins.
This is where it is considered a “generic” login by your member. For eg., a member came to your web site, and then just generally wants to log in to the member’s area – so they have no “context” – it’s NOT as if they were trying to view a specific page or post, got challenged with a login form, and then logged-in from there. That makes this a “Primary Login“.
Examples of this are…
a) Dedicated Login Page: You have a dedicated login page, like http://YourSite.com/login/ – which is what you’ve entered in to “Setup > Config > Login URL“. The body of this page has the DAP merge tag for the login form, which is %%LOGIN_FORM%%
b) Login/Logout Widget on the home page of your web site. This is also considered a primary login.
This is a login action that HAS “context”. Say, a member landed deep into your site (not the home page, not the dedicated login page) and were challenged by the “In Page Error Message” that says something like “Sorry, you must log in before you can view this content” and are presented with a login form right on that very same page. They were trying to read something before they were asked to log in first – which means, they must be returned to the same page they were trying to view BEFORE they were asked to login. So that makes this a “Secondary Login“.
Examples of this are…
a) Any custom “Error Page”, where you have inserted the DAP merge tag for the login form, %%LOGIN_FORM%%.
b) DAP’s “In-Page Error Message” which says “Sorry, this is private content – you must log in first before you can view this”.
Based on whether it’s a Primary Login or a Secondary Login, your member will be redirected to a different location.
1) If it is a Primary Login action, then…
a) They’re taken to the “Post-Login URL” if set at a Product-level AND they have access to just one Product.
b) They’re taken to the GLOBAL “Post Login URL” (under Setup > Config) if you have NOT set anything at a Product-level, OR if they have access to more than one Product.
This scenario is the only one where the Post-Login URL is ever used (whether it’s the Product-level or Global-level).
1) If it is a Secondary Login action, then…
They’re always redirected back to the same page they were on (or were trying to access) before they were challenged to log in first to view the content.
Primary Login is predictable, and you (the DAP Admin) control where they go right after they login.
Secondary Login depends on “context”, and they’re taken back to whatever page they were on, before they logged in.
July 18th, 2011 — Access Control, Admin, Config, Customization, Examples, FAQ, Feeds, Protecting Content, Protection FAQ, RSS Feeds, Setup, User Status
Once you protect a post in DAP, you can …
a) Make it completely disappear from your feed except for authorized users who have valid access to the post and are using a member-specific RSS feed URL
b) You can show a “Summary” of every post, by turning on sneak-peek and making sure you have inserted the “<!–more–>” tag entered into each of your posts.
Troubleshooting RSS Feeds
If your blog post is showing in its entirety in your feed, then….
1) You may not have protected the post in DAP at all, so it’s an unprotected post, which will (and should) show up in your feed
2) You have turned on Sneak-Peek and haven’t inserted the WordPress “more” tag (<!–more–>) into each of your posts. If you turn on Sneak-peek, then you must insert more tags into all posts. Also, if you have turned on Sneak-Peek, then you must also do this…
Go to “Settings > Reading” in WP admin, then set “For each article in a feed, show” to “Summary“.
If it is set to “Full text”, then it will show the full text in the feed, which is not what you want.
Custom RSS Feed Links For Members
Starting DAP v4.2, each of your members can now get their own unique RSS feed link that they can use with a feed reader (like Google Reader, FeedBlitz, iTunes, etc) to get a custom RSS feed with content that they’re eligible to view.
To give each of your members their own unique RSS Feed URL, just insert the following line of code into the top of the “Member Links” or “My Content” type page, or wherever you want your users to see their personalized RSS feed link…
If your blog is in the root…
If your blog is in a sub-folder (say “/blog”)…
The text %%ACTIVATION_KEY%% in the above URL will be replaced with their own custom key, like…
They can then copy that link, enter that into any feed reader, and it will show content specific to their account.
Custom Feed Link Security
Another useful feature we’ve added, is that the custom feed link also does IP count validation. So if they share the feed link with others, then after “X” unique IP login attempts (where “X” is configurable by you, the DAP Admin, in Setup > Config), their account will automatically get locked out.
February 28th, 2011 — Cancellations/Refunds, Config, Payment Integration, Paypal, Policy, Setup, Strategy, Transactions
There really is no one-size-fits-all when it comes to refund policies.
There are so many factors involved. The main one being, that Visa/Master/Amex/Paypal all give a buyer up to 60 days to ask for a refund, at least with most merchants.
Unless you’ve already negotiated the refund terms with your merchant account provider, and have both specifically agreed that there would be no refunds (like say, if you were selling an expensive item, like a car, or a boat, or a service), or that it’s only going to be a 30-day refund period, then you really have no control over the refund period. You just have to comply with at least the mandatory 60-day refund period required by the credit card companies.
So that brings us to the question:
How much should you set your refund period to be within DAP?
Now remember, it is this Refund Period setting (under Setup > Config > Advanced) that also makes affiliates eligible for payment.
So it really comes down to the question:
What is the waiting period for an affiliate to get paid for a referral?
Our recommendation: 60 days.
That’s because if you end up paying too soon (say like within 15 or 30 days), and then the buyer comes back and asks for a refund, now you’re out-of-pocket for the affiliate commissions that you have already paid on a purchase that you just refunded.
Now remember that when you do the actual refund within DAP, DAP will roll-back any commissions credited towards this purchase. If you have not yet paid your affiliates, then in the next report, it will ignore the refunded purchase, and will not calculate commissions on that purchase.
But if you have already paid your affiliates (like within 15 or 30 days after purchase), then DAP will include the negative commission in the next pay-period’s report. And any future commissions earned by this affiliate will be accordingly adjusted.
However, if the affiliate doesn’t refer any more members, then you have two choices at this point:
1) Ask the affiliate to pay back the over-paid commissions
2) Just swallow the loss, write it up to the cost of doing business, and move on.
September 2nd, 2010 — Access Control, Config, Examples, Protecting Content, Setup, Users
Creating 1 Single Login & Password For All Users
This is for when you don’t care about assigning unique usernames and passwords to your users, and would rather given all of your members (or site visitors) a single email id and password to log in to your membership site.
Here’s how you can do it:
- Most important: Go to Setup > Config > Advanced > “Max. # of User Logins From Different IP`s” and set it to a very high number – like 99999999. You’ll need to do this because everyone will be logging in using the same email/password, and you don’t want DAP to lock out the public account (you’re about to create below).
- Create a “public” user manually, with an email id like, say, “email@example.com” . DAP will assign a random password to the user (unless of course you have set the “Default” password in Config).
- Change this password also to something public – like ‘demo’
- Then if you don’t care about collecting anyone’s email id, then you could publish this info publicly on your web site
- But if you wish to collect people’s email id’s, and *then* give them this public email/password, then you can still sign them up using the “Direct Signup Form”. And in the welcome email, instead of sending them their own email id and password, send them the public email id and password.
August 24th, 2010 — Access Control, Config, Customization, LiveLinks, Protecting Content, Protection FAQ, Setup, WordPress
DAP has a feature called “Sneak-Peek” where you can show a part of your blog post or page to casual visitors (as well as to search engines like Google) and then when they click on the “Read more…” link, the protection will kick in for the rest of the post, and DAP will say something to the effect of “Sorry, you must be logged in to access this content. Please login below or click here to get access”.
And that error page will contain both the login form, as well as a link to your sales page. Of course, you can customize this error page to say whatever you want, but that’s another topic altogether.
Advantages of Sneak-Peek
Sneak-Peek allows you to show “teaser” content to potential members, instead of fully locking it up and showing just an error page. Using Sneak-Peek allows you to show some content to casual visitors in order to get them to subscribe to see the rest of the content, as well as keep some content open so that search engines like Google will have some content to index in their search databases, so that the open part of the content can show up in search results for potentially matching keywords, and bring you some free organic search traffic to your site.
How this works
WordPress has a feature called the “more” tag. Basically it is a bunch of text (<!–more–>) that you insert into your posts or pages. And WP will then break up your post right at the point where you inserted the more tag, and replace that tag (and everything that follows) with a “Read more…” link
Fig A: “More” icon in WP. Click to enlarge.
You can also insert the more tag in to your post or page, by clicking on the icon shown in the image above – that looks like two rectangles separated by a dotted line – on the WordPress page/post edit screen.
Of course, exactly what that “Read more” link will say (it could say, for eg., “Click here to read the rest of this post”) is determined by your actual WP theme.
Regardless of what it says, when you have a protected post, by default (when sneak peek is off) that post will completely disappear from your blog for non-members and those who are logged in, but don’t have access to it yet. And even to Google.
But if you insert the “More” tag in to all of your pages and posts, and in the DAP Dashboard, go to…
“Setup > Config > Advanced > WordPress Sneak Peek: Show snippets of post (upto the `More` break) even for protected posts?”
… and set the above setting to “Y” (for ‘yes’), then on your blog’s summary page (which lists all of your posts), all posts with the more tag (protected and un-protected will anyway show up to the more tag, but when someone clicks on the “Read more’ link, that’s when DAP’s security kicks in and if the user has access to that content, will show her the rest of the post. And if the user is either not logged in, or does not have access to that content (either access is yet to come because of the drip, or content has already expired), then it will show the appropriate error message.
WARNING: “Sneak-Peek” & “More” Go Hand-in-hand
If you turn on “Sneak-Peek” in DAP, then you MUST also insert the WordPress “More” tags into every one of your protected posts and pages.
August 23rd, 2010 — Access Control, Config, Customization, Products, Setup, Troubleshooting
DAP has 3 fields which are applicable at a Product-level. But if a content (page/post) is part of multiple products, then DAP can’t figure out which product’s field to use – so it falls back to the “GLOBAL” equivalent of that same setting under Setup > Config.
The 3 fields are…
- Post-Login URL
- Sales Page URL
- Error Page URL
All 3 of these have both a Product-level setting, plus a fall-back Global setting under Setup > Config.
1) Post-Login URL not redirecting to the right page
If the user has access to more than 1 DAP Product, then DAP cannot decide which Product’s Post-Login URL to redirect the user to. So it simply redirects the user to the global equivalent of that URL at Setup > Config > Post-Login URL (Global)
So if you’re testing the “Post-Login URL” field, make sure you create a test user with access to just that one product, and then log in as her and test.
2) Error Page URL not redirecting to the right page
If the content that user is trying to access, but is not eligible to access, is part of more than 1 DAP Product, then DAP cannot decide which Product’s “Error Page URL” to use. So it simply uses the global equivalent under Setup > Config > Error Page URL (Global)
3) “Sales Page URL” on error page not pointing to right URL
Lock message says “Sorry, this content is for members only. Click here to get access” but “Click here” points to my incorrect URL
If the content that user is trying to access, but is not eligible to access, is part of more than 1 DAP Product, then DAP cannot decide which Product’s “Sales Page URL” to show on the “In-Page Error Message” shown to the viewer. So it simply uses the global equivalent under Setup > Config > Sales Page URL (Global)
So make sure you have set up a URL in that field.
4) Clicking on a protected Category is not taking user to the correct “Error Page URL”
When you click on a category (instead of a single post), then because the category could contain many posts, each of which could be part of multiple Products. So DAP is unable to choose just 1 single Product from which to pick the “Error Page URL” and redirect the visitor to. So it just shows the error message with the padlock image, which can be customized. Click here for details.