How to integrate Memberstack with Webflow effectively while identifying and overcoming common challenges?
Hey everyone! 👋
Hope you're all doing well. I'm reaching out to gather some insights from your experiences. Specifically, I'm curious about the challenges you faced while integrating Memberstack with Webflow. What were some roadblocks or tricky parts you encountered?
Also, I'd love to hear your suggestions on how we can enhance this process for others. For instance, one idea we've been considering at Memberstack is to introduce a feature in test mode. This would allow you to click an icon at the bottom of the page, highlighting all Memberstack data attributes for easy identification and troubleshooting.
Your feedback is incredibly valuable to us, and it's a great opportunity for us to learn from each other and improve our workflow. Looking forward to hearing your thoughts and ideas!
Comments
7 comments
My only real "unexpected" moment with memberstack was when I finally became a paying member, the test mode in stripe only then added memberstack fees to my transactions, making all my prior projections wrong/invalid as test mode didn't account for the memberstack 4% until after I had that "plan" on my account. I basically spent half a day trying to figure out why the stripe amounts were reduced all of a sudden 😀
So my only advice, to avoid surpise pikachu faces, it might be worth considering including the memberstack fees into test mode before they become paying users, this makes the stripe transaction info usable for forecasting 🙂
I would like to have an event that tells me when memberstack first loaded. If possible returning the app and member object. I miss the onReady method of v1 😃
I know, I know. I can use the getMember method, but, sometimes I would like to keep requests at a minimum, and there's a memberstack request (the very first one) that I don't have access to. For me, it would be something good to have 🙂
ah! Thank you for your feedback. I agree. I will bring this up to the team!
for me personally there wasn't really any roadblocks or tricky parts. I think its pretty straight forward, the thing that frustrates me the most is webflow as a first time user of it. There's little bugs (especially the one where you click on an attribute and you didn't click off it and it wont let you open the attribute on a different element until you go back to the other one and unclick it again) and things about their ui that could be fixed and streamlined. 😂
I agree with this, my main issues while integrating memberstack into webflow have actually been with webflow. Either the attribute bug, the inability to copy paste a CMS ID (for some reason it wont let you copy????) along with a massive list of gripes with webflow's API.
Memberstack is honestly my "Gold Standard" and what I compare other companies and support experiences with.
It's why im a big fan of framer. Designing websites is so much more straight forward, fun, and efficient in it. Unfortunately its cms is bad and theres no api so you cant build more technical projects with it.
Thank you for sharing your valuable insights! I really appreciate the time you took to contribute your thoughts and experiences. I'll be reaching out to our contacts at Webflow to discuss your suggestions and feedback. However, it's important to remember that since Webflow is a separate entity, our influence over their processes and decisions is limited. Rest assured, we'll do our best to advocate for improvements that can enhance our integration with them. Your input is crucial in these discussions, so thanks again for helping us make a difference!
Please sign in to leave a comment.