40

Product Chaining

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.

Click Here to Leave a Comment Below 40 comments
Scott - November 18, 2010

Ravi, I really do need product chaining so I’m glad to see you are doing this. However, I have a bundle with Products A, B, C and D. How can I do this? I was hoping to use product chaining when I heard you were coming out with this, but limiting it to 2 products won’t work for me, unless I’m missing something. Thanks!

Reply
Veena Prashanth - November 23, 2010

Here’s how it will work:

You can have a rule that says if someone buys product A, give them access to product B, another rule that says if someone buys product A, give them access to product C.
One more rule that says if someone buys product A, give them access to product D.

Now if someone buys product A, they will have access to products B, C and D.

The chaining rules are applied to the ‘product that the user is purchasing’.

If you have these rules:
1) if someone buys A, give them access to B
2) if someone buys B, give them access to C
3) if someone buys C, give them access to D

Then if a user buys product A, they will only get access to product B and not to product C and D. It does not recursively apply the rules to the other products in the chain.

Makes sense?

Reply
Scott - November 23, 2010

Yes, it makes perfect sense now. Thanks for clearing that up. Off to set up my product chains 🙂

Reply
Kirk Ward - December 1, 2010

Can I add product chaining and then remove it, then add a different one and remove it.

I have products which are seasonal specials and want to add them to a standard product.

For example, in December I chain tax postcards to my standard product and allow them to drip out on calendar dates until the series is finished.

Then in April, I unchain the tax postcards and chain display ad artwork to my standard product.

Will the existing members have the new product in the chain added to their access, or will it only go to new members?

If it goes to existing memberrs, will drip days be calculated from the day the series is added, or from the members join date? (Meaning, can I use drip days or must they be calendar days?)

If “drip days,” then will the calculation be re-started each year when the specials are added?

Reply
Veena Prashanth - December 2, 2010

>> Will the existing members have the new product in the chain added to their access, or will it only go to new members << It will only go to the new members.

Reply
Kirk Ward - December 2, 2010

Well piddle.

Any easy suggestions on how to release seasonal products to existing members?

Reply
Veena Prashanth - December 2, 2010

Would have to be done manually for the existing members. You can select multiple users in the DAP Manage Users page and you can give selected users access to the new product by clicking on the ‘Give Selected User(s) Access to the Product…’ under Operations.

Reply
Kirk Ward - December 2, 2010

I can do that … until I can figure out an easier way.  LOL
Anyhoo, does I do it for the top level product or the chained seasonal product?

Reply
Veena Prashanth - December 2, 2010

If the existing users already have access to the top level product, then give them access to the  chained seasonal product. If the existing users do not have access to the top level product and the top level product also has product chaining defined for seasonal product, then you need to just give them access to the top level product and dap will automatically trigger the product chaining rule and give these users access to both top level and chained seasonal product. Hope this helps.

Reply
TheNightOwl - March 4, 2011

Hi Veena & Ravi

How does this feature work with a 3rd-party autoresponder?

For example:

* I have two products, ABC (free) and XYZ (paid).

* I’m using DAP/Aweber integration

* I have a rule set up in Aweber that says “Whenever someone subscribes to List-XYZ (for paid members), remove that lead from List-ABC (for free members)”.

Will DAP handle this?

Thanks,
TheNightOwl

Reply
Veena Prashanth - March 5, 2011

>>
* I have a rule set up in Aweber that says Whenever someone subscribes to List-XYZ (for paid members), remove that lead from List-ABC (for free members).

Will DAP handle this?
<< You have to setup a similar rule in DAP Product Chaining that says when someone subscribes to Product XYZ, automatically remove their subscription to Product ABC. The product chaining rule will take care of removing the user's access to free product in DAP when the user upgrades. You need to keep your aweber rule so aweber can automatically remove users access to free list when DAP notifies aweber of user's subscription to new/paid list.

Reply
Just me - September 14, 2011

I have a question. If someone subscribes to Product A (one month). Then, after times up, after he have to pay (automatically), he must enter to Product B. But only if he paid for this one, too. I cannot give access to Product B, if he didn’t paid for it.

How can I do this?

Reply
Veena Prashanth - September 14, 2011

You can try to setup both A and B as subscription products. Set up a subscription button to sell product A.
When you create the subscription pament button for A, set the intial payment (X dollars) to match the product A cost, and the recurring price can be set to match the monthly cost (Y dollars) of product B.

So the user will buy product A, then automatically a recurring profile will be set up to charge the user an initial amount of X dollars and subsequent recurring payment of Y dollars.

Setup a chaining rule that says, when a payment is received for product A, automatically grant access or extend access to product B. You will automatically keep receiving payments (via A) but user’s access to B will automatically keep getting extended via chaining.

Reply
Kristen - February 27, 2012

We have 3 products that are leveled. They’re called Standard, Premium, and Ultimate. I have them set up so that the Premium is the Standard plus a couple of extras and the Ultimate is the Premium plus a couple of extras. I figured out how to set up the chaining, but it looks like when someone buys Ultimate they receive 3 thank you letters with their password. Is there a way to correct that?

Reply
Veena Prashanth - February 27, 2012

The welcome email is configured at product level in dap.
If you do not want a welcome email with id/password sent, you can either remove the welcome email entirely from that product in dap (under dap products -> email notification tab) or you can update the contents of email and remove the part where the id/password in included.

Reply
Kristen - February 27, 2012

But if I remove the e-mail then people who purchase the lower levels won’t get an e-mail. It sounds like they’ll just have to get three unless I take out the chaining and just duplicate the protected pages for the different levels.

Reply
Mark - The Word Bay Guy - March 21, 2012

Going back to this email notification question – if you chain product B to product A, the welcome emails for both A and B get sent straight away, EVEN IF you set access to B to commence in, say, 5 days’ time.

The behaviour we really want is for the welcome email only to get sent once they actually get access, right? So do we do that by leaving the welcome message blank (under the Email Notifications tab for product B) and specifying an autoresponder message instead for day 1, basically saying the same thing (“You now have access…”). Will that autoresponder message then get sent on Day 5, as we want (since the chaining rule only begins access on day 5)?

Or should we do the same, except chain product B to A, but somehow set dripping to achieve the same?

I know I can test this stuff, but it’s a bit tricky with a live site and I would rather have it from “the horse’s mouth” what the best way is to implement this.

Reply
Veena Prashanth - April 23, 2012

>>So do we do that by leaving the welcome message blank (under the Email Notifications tab for product B) and specifying an autoresponder message instead for day 1, basically saying the same thing (“You now have access…”). Will that autoresponder message then get sent on Day 5, as we want (since the chaining rule only begins access on day 5)? << Yes, you are right. I have not tested it but yes, it makes sense to use autoresponder dripping for chained product to send welcome email ( if the access to chained product set to future ). This way the user will still receive the welcome email for chained product but ONLY when they actually receive access to the chained product in future.

Reply
Juan Sebastián - September 20, 2012

Hi Veena!

Well, I think you already answered this in the previous comments but still need some extra clarification.

I´m creating a product that has an initial payment of 97 dollars and a monthly cost of 17 dollars after the first month.

Question is…How can I do this? How can I charge 97 initially and create a profile for 17 dollars recurring payments?

Thanks a lot for your help. Very much appreciated 🙂

Reply
Veena Prashanth - September 20, 2012

Hi Juan,

You do not need product chaining for this. Just create a regular product in dap, click on the ‘price&recurring’ tab, and save it as a ‘recurring product’ with trial price set to $97 and recurring price set to $17.

Reply
Juan Sebastián - September 21, 2012

Lightning fast responses as always, the same great service we´ve all come to expect from you guys. Thanks for the answer. I found a lot of examples of this in the “Payment Setup Options” It´s done! LOL.

Thanks again!

All the best for you and your amazing family Veena 🙂

Reply
Veena Prashanth - September 21, 2012

Thanks Juan :).

Reply
John ODonovan - September 22, 2012

Kristen wrote:

#16 Kristen on 02.27.12 at 2:09 pm

But if I remove the e-mail then people who purchase the lower levels won’t get an e-mail. It sounds like they’ll just have to get three unless I take out the chaining and just duplicate the protected pages for the different levels.

Is there a way to fix the “multiple welcome email” issue that she is describing?

TYVM, John O’Donovan

p.s. loving DAP

Reply
Veena Prashanth - September 23, 2012

Hi John,

>>Is there a way to fix the “multiple welcome email” issue that she is describing? << Right now, there is no way to tell dap to NOT send welcome emails if the user is getting access to it in the chaining flow (without purchasing) but to send the welcome email if someone purchases the lower-level (chained product) directly. But it's a great suggestion. We will try to add this feature in dap 4.5 (release in about 4-5 months).

Reply
Joe - October 9, 2012

Veena,

I wanted to run an idea by you before I implement it on the site.

I offer language tutoring through a video membership site. The entirety of course takes a year to finish, one level per quarter. I offer monthly, quarterly, and yearly subscriptions.

So that I don’t have to recreate contentresponder for every subscription, I was thinking to create
one product for each level of the course, each level dripping lessons over 90 days. lets call them 1-2-3-4.

Then I was going to create 3 products with paypal buttons, monthly-quarterly-yearly, and chain each of those to the course levels. lets call them A-B-C, there is also free product D

Welcome emails to each level would be in the emailresponder dripped at day 01, day 91, day 181 and day 271.

Am I correct to think that this would work? So if someone was subscribed for a month, they would only get to day 30 (product A), then they cancel so product chaining kicks in and they go to free product D. If they were subscribed quarterly (product B), they get to day 90, recurring fees are charged, and on day 91 they get dripped email welcoming them to level 2. If they cancel at day 90, they get chained into free product D.

Will this work?

thanks for your help

Joe

Reply
Veena Prashanth - October 9, 2012

Hi Joe,

It might get confusing.

Actually i am not sure i understand the setup.

So you will have a total of 8 products ?

Product A, B, C, D (free) and the levels – 1, 2, 3, 4.

Products A, B, C are really dummy products with nothing dripped.

Anyone purchases say monthly subscription (product A), they get access to A but because you have chained A to 1-2-3-4, they get access to all 4 levels (products) …
But because of the content drip start / end setting under each level / product, the user can only access content based on their membership days in dap. For ex, a user who has been a member for less than 90 days, can only access level 1 (product 1) content because level 2/3/4 have content with drip start day > 90 days.

Is that what you are looking to do?

Reply
Joe - October 9, 2012

Veena, Yes that is what I mean.

Reply
Kristal - December 12, 2012

If I have lets say 4 products and 1 recurring product, and I set it up so that if someone buys the 1 recurring product, they also get access to the 4 other products… Is there a way for them to initialize the product drip for each product? I wouldn’t want them to get 5 welcome emails, then drip emails from 5 different products at the same time. They would want to go through each product one at a time.

Reply
Veena Prashanth - December 12, 2012

Kristal,
Dripping is a product level setting that once set by admin, cannot be changed in a chaining or other flows. Currently there is no way to avoid a welcome email.. but we will add a flag in the ‘chaining rules’ page so admins can specify if they want email sent or not for the chaining product in a future release of dap.

Reply
Kristal - December 13, 2012

Thank you, but I’m also worried about having all the products start up at the same time. It would be nice to have a feature, where they have to click on a “Start” or activate button for each product in order for the dripping to start, that way if they purchase more than one product, they can go through the content one product at a time if they wanted to.

If I offer all of my products as a free add on for the subscription service, they would get bombarded with emails from all of the other products, where they may not even want to use some of them.

Reply
João Diogo - January 18, 2013

Hi Veena.

I have a question about duplicate contacts. Let’s say I have several sub-brands of my brand. Each one has a free product that is a product launch funnel sequence that leads to a sale.

I want to have another free product that is a main list, where subscribers from all other products and funnel entrances get added.

So when user1 subscribes to the funnel in product1, he/she get added to main_list as well. I can do it with product chaining, no sweat.

Now let’s say that user1 subscribes to product2, again funnel form. If I have a chaining rule that add’s him/her to main_list, will he/she be added?

How does DAP handle this duplicate entrance? Will I have duplicate emails on a same list or is the second chain rule discarded?

Thanks, João.

P.S. main_list has no welcome email or any auto-responder whatsoever.

Reply
Veena Prashanth - January 20, 2013

Hi Joao,

>Now let’s say that user1 subscribes to product2, again funnel form. If I have a chaining rule that add’s him/her to main_list, will he/she be added? < < DAP will re-add user to the same product. DAP will treat it like a 'recurring payment' for the product, so the user's access to the product will be extended using the membership duration setting (in price&recurring tab in dap products page) upon each add to the same product via chaining. If it's a product where you give user forever access to product upon signup, then when dap re-adds user to the same product (via chaining or via regular registration), nothing will happen as the user already has full access to product. DAP only sends out welcome email during the first add. In users-> manage page, you can note down the current access end date, and then keep adding user to the same chained product (via add users page) and see how the access end date keeps extending upon each add, nothing else will change.

Thanks,
Veena

Reply
David M. O'Neill - November 2, 2013

If I sell a product with single opt-in and chain it to a free product that has a double opt-in, what happens in the email sequence that gets executed?

Reply
Aileen - December 4, 2013

Veena,
You answered this question:

>>Is there a way to fix the “multiple welcome email” issue that she is describing? <>But it’s a great suggestion. We will try to add this feature in dap 4.5 (release in about 4-5 months).<<

Was this implemented in 4.5? I am trying to work out what to do about product bundles… but don't want people to receive multiple welcome emails

Thanks.

Reply
Veena Prashanth - December 4, 2013

Hi Aileen,

No, we could not implement it in 4.5 but it’s high on our to-do list and hopefully we can implement it soon.

Thanks,
Veena

Reply
Veena Prashanth - December 4, 2013

>>If I sell a product with single opt-in and chain it to a free product that has a double opt-in, what happens in the email sequence that gets executed? << The user will receive welcome email for the single-optin product and the user will receive 'confirmation' email for the double-optin chained product.

Reply
Jordan - March 26, 2014

This product chaining feature is great! But I have a question..

Let’s say a user registers for a free product using a free sign up form generated by DAP (with some extra custom fields) and the account is created.

If that user later decides to purchase another product/level but the registration form for the paid product simply asks for full name, email address and payment details. Will DAP recognise the user’s name or email address and link the purchased product to his/her account + remove access to the free product they previously signed up for?

Or will DAP create a completely new account for the user?

Note: This entire scenario is assuming that the user was logged out of their account during the purchasing process.

Thank you

Reply
Veena Prashanth - March 26, 2014

>>Will DAP recognise the user’s name or email address and link the purchased product to his/her account + remove access to the free product they previously signed up for? Or will DAP create a completely new account for the user? << As long as the users enter the same email id, dap will recognize the user and dap will not create a new account. Thanks, Veena

Reply
Craig Grant - January 7, 2016

These instructions don’t include the following setting:
… with user’s access to chained product
set to start on…

Current Date (same date when user is added to source product)

Future Day #

* Enter # of “Days” to add to current date – Eg., 21
* Enter -1 if you want the “Access Start Date” of destination product
to match the “Access Start Date” of source product

A bit confused by the wording on this. My configuration in Free 7 Day Trial Period then manual offer to upgrade. If I have already set up a Free Product with a time limit of 7 days and then chain it to a Silver Paid Product, not sure what to enter in this field if I intend for the person to start paying the day they upgrade. Do I need to add anything here (select current date) or would I put 7 in this setting in product chaining if I intend for the user to be billed as soon as they upgrade to the paid package. Or is this setting putting a time limit on how long a user is allowed to upgrade (if it is I would not want to use this setting). Please let me know. Thanks.

Reply
Veena Prashanth - January 7, 2016

Craig,

Product chaining is internal to DAP. It does not integrate with any payment systems to upgrade/downgrade users.

Create two products – free and paid. Set the ‘access duration’ to 7 days for the free product in dap products page=>pricing tab.

Under the free product, set up an autoresponder email to automatically send out a manual upgrade offer on day 7. The email should send users to the paid product’s sales page.

Use product chaining to simply remove user’s access to ‘FREE’ product from DAP when they upgrade to the paid product. You don’t have to use product chaining for anything else in this scenario.

Thanks,
Veena

Reply

Leave a Reply: