[Wishlist] Get full query url parameters from the Stripe Completed

• 

  Tyler Bell

  • May 15, 2024 16:44
  • Official comment

  Rokas Judickas Petr Musil
  
  The after-checkout redirect now includes the price id from Memberstack and Stripe. 🎉

  https://xxx.webflow.io/<redirectURL>?forceRefetch=true&fromCheckout=true&msPriceId=prc_abc&stripePriceId=price_123

• 

  Duncan from Memberstack

  • March 19, 2024 16:26

  Tyler Bell would it be "easy" to include the price ID in the return params?

  1
• 

  Rokas Judickas

  • March 20, 2024 08:39

  Please! This feature would literally fix all the problems with conversion tracking! 

  2
• 

  Petr Musil

  • Edited March 23, 2024 15:48

  Hi Guys, I am setting up a basic conversion tracking of the purchases made trough MS/Stripe.

  Before we start begging for features, I suggest Memberstack DOC should be updated. There are contradicting statements about what is returned in current version of MS after successful checkout - here in this thread and in this one:

  https://docs.memberstack.com/hc/en-us/community/posts/13145950998939-Tracking-Conversion-Rates

  As of my quick testing on the STANGING, the app currently return the following:

  https://xxx.webflow.io/<redirectURL>?forceRefetch=true&fromCheckout=true

  I don't want to conduct testing on my live site, as I will probably run into the issues with Stripe testing and their Service Agreement, which prohibits testing using real credit cards https://docs.stripe.com/testing?locale=en-GB

  So could we add a new page into the DOCs V2 that describe some basics about Purchase/conversion tracking in MS and include what params are returned in both STG and PROD environments?

  I believe there is no such article (did not find it) if yes I am sorry.

  From there we can then iterate to some enhancements if guys from MS will be willing to :-)
  Without DOCs it is just a guessing on both sides and waste of time (IMHO).

  All the best,
  Petr
  CTO, Šikulio

  3
• 

  Josh Lopez

  • April 04, 2024 16:29

  Hi Petr Musil,

  Thanks for reaching out and for the insightful feedback on our documentation. I totally get how crucial it is to have clear and precise information, especially when it comes to understanding what data you can expect after transactions.

  We want to make sure we get it right, so I’d love to dig a little deeper into the specifics of what you need. Could you elaborate on the discrepancies you’ve found in our current docs? Additionally, it would be super helpful if you could list the exact parameters and types of information that you believe should be included in our new documentation for both staging and production environments.

  Your expertise as a CTO is incredibly valuable to us, and I want to make sure we address your concerns thoroughly. Once we have a clearer picture, we’ll be in a better position to update our documentation to be more helpful for you and all our users.

  Looking forward to your reply!

  0

Please sign in to leave a comment.