Skip to main content
A service which provides subscriptions is nothing without its upgrade flows. Usually using upgrade modals Often hard coded and never changing Businesses are always changing their pricing and offerings but the upgrade flows are often hard coded and never changing. The core piece of an upgrade flow is the payment source collection Traditionally, this process is done in a separate page, but with the Checkout Experiences, you can easily collect payment sources in a modal or inline on your page. Optimise conversions by creating experiences which match the action the user was going to take. Checkout Experiences
  • configuration
  • a/b tests
  • custom triggers

​
Steps to create a checkout experience

  1. install sdk
  2. create a checkout experience
  3. define trigger
  4. Define conditions
  5. define first a/b test
plandalf.dispatch("my-custom-event-name")

​
Decide on the experience trigger

  • “on button click”
  • “on page load”
  • “on page exit intent”
  • “on page scroll”
  • “on DOM element clicked”
  • “a custom event”

​
Tell us conditions & plans

Plandalf can show the new experience based on combinations of conditions such as:
  • “if user does not have a plan”
  • “if user has a specific plan”
  • “if user has a specific email domain”
  • “is user on a free plan”
  • “is user a customer or not”
Need different conditions? We can add them easily.

​
Decide % of users that will see the new experience

We will input this for you - this is a condition. Can we explain how that would work? How do you test experiences. a/b testing, making changes
  • A/B testing
  • Security
Every account comes with two keys: one for live and one for sandbox. You can test your integration on the sandbox client and then switch to the live client when you are ready.
  • Use “sandbox” users to test your integration risk-free with 100% coupons
  • Use “live” users to test your integration with real users

​
Conditions

ScheduleQuantity SubscribedToProduct SubscribedToPlan HasEntitlement ProductSubscriptions