Leanplum's user guides and developer documentation.

Leanplum Documentation

Leanplum's user guides, SDK setup, API docs, and more resources are here to help you get the most out of A/B testing, Campaigns, Messaging, and Analytics.

Testing and QA best practices

How to QA your changes and set up your app for success

At Leanplum we like to test everything, which is why we have tools that help you preview messages, A/B tests, variables, and other changes to your app.

You can also implement a QA process for your team to test and preview content in Leanplum before sending it to your users. Read on for a brief overview of your tools for testing content in Leanplum.

Development and production mode

In general, development mode is for internal testing, and production mode is for a live environment with real users. Once you implement the Leanplum SDK, you can switch between development and production mode by running a build of your app with either the development or production API key in place.


Use the correct keys

Never use a development key in a live production build. Our development key uses an open socket (for real-time analytics), which could noticeably degrade your app's performance. Additionally, any user data will be lost as it is not captured in analytics.

See Use the right API keys for more about using development and production mode.

Creating a test app

Most testing is done in developer mode, but you may want to test a few things in production mode as well. Creating a separate testing or "staging" app for your team allows you to test changes in production without adding risk or accidentally sending content to your real users.

You can add a new app and access your Keys from the App settings page.


Name your staging and live apps clearly

For example, if your app is called "Plums," then in Leanplum you could name your apps "Plums Production" and "Plums Staging."

Feel free to create as many test environments as you want — leanplum does not limit the apps you can have in your dashboard.

See more on setting up separate staging and live environments

Team roles and permissions

Setting up different permission levels for each Leanplum user can also refine your testing process. For example, some team members need to send messages to your app users, but you may not want your whole team to have that ability. You could give some users "Viewer" permission for messaging in Leanplum.

Admins have full access to all areas of Leanplum.

Either choose a pre-set role from the Team page, or create custom roles and permissions to specify how much access each person has to different areas of Leanplum.


Total separation for teams on different apps

If your organization has multiple different apps in Leanplum, you may want to limit certain team members to only have access to one app. Contact your CSM for help setting up your organization by app.

You could give your whole team access to your staging app, but only give a select few members editing access in production.

Updated about a year ago


Once you are comfortable with your QA process, it's time to start testing out your content in Leanplum.

Previewing content in Leanplum

Testing and QA best practices

How to QA your changes and set up your app for success

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.