How to set up Memberstack checkout across different Webflow subdomains when pricing and member content are separated?
Hi everyone!
Could anyone help with this?
I have 2 WebFlow sites.
SITE A points to subdomain www.example.com (and contains all the sales and marketing)
SITE B points to subdomain hub.example.com (and contains gated content, available to paid subscribers)
I have been trying to install and configure Memberstack on the staging versions (not production versions, yet) of both sites, as follows:
- Added the MemberStack script code into the headers for Site A and Site B
- Added the Cross Domain Login script too (although unsure if necessary for my use case?)
- Added a MemberStack signup form (copied and pasted as a WebFlow component) into Site B with slug => /signup
- Added a paid Plan within MemberStack
- Added custom attributes ('name' and 'value') to the pricing button found on Site A => /pricing/product
I managed to get the process working when I confined everything to the SAME subdomain i.e. I added a temporary/test pricing page at hub.example.com/pricing. I was then able to click on a price, reach the signup page, make a test purchase, and then get re-directed to the chosen gated content. Great!
However, I can't get the process working when I move the pricing page to a DIFFERENT sudomain www.example.com/pricing. I am able to click on a price, reach the signup page...but when I click signup it no longer takes me to checkout. It seems as if the custom attributes are not being passed across the subdomains.
Ultimately, I just need my paid members to sign up and log in on the subdomain that contains my members-only content. Obviously Memberstack.io and app.memberstack.io are a great example of this -- so I am pretty sure (hoping!) that I've made a trivial error?
Thanks for any help on this!
Joff
Comments
2 comments
Hey Joff,
Thank you for posting. Without having your actual url I am unable to do any tests. This sounds like it could be an issue with not adding the memberstack install script on all the websites. Also when using cross-domain you will have to add the code to all of the domains especially the root domain.
Joff Hamilton-Dick Could you have your users do the plan selection and checkout all on the same domain? I can imagine issues popping up if you try to split that process across both domains. Once they are logged in / have the correct plans everything should be okay.
Please sign in to leave a comment.