We have an issue when implementing amember and clickbank. The current process amember uses is not ideal for implementing a one-time offer, as well as the flow in which users sign up is not ideal. As far as flow... We would like to go straight from the sales page to Clickbank, and THEN to the amember registration page. Rather than from the sales page to amember reg. page then to Clickbank. This tends to scare off customers as it is not the "usual" process in which they are comfortable with. As far as we can see there is no way to do this. As far as implementing one time offers... Keeping in mind the desired flow as described above, there is a problem. The ideal flow for the upsell would be: salespage > clickbank > one time offer page > clickbank (to purchase OTO) > amember registration page. Considering that you must create two products, one for the front-end and one for the upsell, wouldn't the buyer have to create two different accounts or is there a way to, when they register after purchasing the upsell, also automatically register them for the front-end product as well? So for example, they would go to the sales page and decide to purchase the front-end product. They would then complete the front-end product purchase via clickbank. Next, they would be redirected from CB to the upsell/one-time offer page. The person decides to purchase the OTO as well and goes to CB to complete purchase. They are then redirected from clickbank after payment is successful, to the amember registration page. Ideally, the person should be signed up for both products (fully integrated with CB) once they complete the amember registration process, since they did purchase both products. So, if they cancel the upsell product they are still able to access the front-end product. How is this process possible? I've tried to explain it as carefully as possible here. I can follow up with clarifications if necessary. Thanks for your support,
This would be a nice option to have in aMember. I suspect you'll have to hire a dev. to customize aMember. aMember wasn't designed to work the way you're describing.