Leanplum glossary

term definition
A/B Testing A/B testing is a type of test in which your users are separated into groups (variants) and each group is served a different experience. The control group is served the default experience while the variant(s) is served the alternate experience. The variant(s) is then compared against the control with metrics/goals to establish the winner.
A/B Testing Goals The goals are success measurements used to determine the winning variant of the test. The individual goals are used for the time estimate for the test to reach statistical significance. Any ratio or percent available in the metric catalog can be used as a goal.
Active Mode Active status is when an a/b test or messaging campaign has been created and published live to the targeted users.
Admin Dashboard The Admin Dashboard allows you to manage your apps, users, and test devices. Leanplum provides user permission settings to ensure that users in your organization have access to the appropriate apps and abilities within your account.
App ID This is the ID applied to your application in Leanplum that tells us which dashboard the data is applied to.This key is used in your Leanplum integration.
App Settings Page The App Settings page allows you to create and delete apps, and adjust all app settings. An app will be tied to whichever team you create it under, and all team members from that team will have access to it.
Calendar UI The calendar UI provides a comprehensive view of scheduled push notifications on a monthly calendar. The UI provides visibility into how often users are being communicated with and which messages are being sent.
Content Read-Only Key This key is used when retrieving information about your tests and messages from Leanplum with our API. It is specific to your app in the Leanplum dashboard. See our available content read-only methods.
Control Group The control variant is what will be used to compare your result against in the A/B test. If testing a variable, the control will be the override value on the Variables Dashboard. If no override has been set, it defaults to the default in the code value.
Data Export Key This key is used when exporting data from Leanplum with our API. It is specific to your app in the Leanplum dashboard. See our available data export methods.
Development Key This key is used to tell leanplum to send the data to the development/test pipeline. This allows the data to be processed real time as well as to viewed in the debugger for validation. It is specific to your app in the Leanplum dashboard. See our available development methods.
Distributor Toggle The distribution toggle allows you control the portion of users randomly assigned to each variant in the a/b test.
Draft Mode Draft status is when an a/b test or messaging campaign has been created but not published live to users
Element Selector For the UI editor, this allows you to select any element from your interface here. The selected element is highlighted in purple.
Finished Mode Finished status is when an a/b test or messaging campaign has been published and completed.
First Time User A first time user is a user who has installed the app and opened it (initializing Leanplum) for the first time. This is defined in Leanplum as users with 0 sessions prior. If the user installs the app but does not open it, they will not count towards the first time user analytic.
Immediate Sending A delivery type that sends messages to users within the next several minutes.
Impression Criteria The impression criteria defines when a user is counted towards the analytics of the test. By setting an event as the impression criteria, the user will not count in the analytics of the test until they fire the event selected.
In-app Messages A type of message displayed to its targeted users at a chosen place within the app.
Lifecycle Engine The lifecycle engine is used to create an automated messaging campaign that sends users a series of messages based on past behavior. A trigger/event is defined that places the user in the campaign as well as a trigger/event is defined that takes the user out of the campaign, i.e. the campaign objective.
Magnet The magnet icon controls the “stickiness” of your test. As a default, the magnet is turned on and lit blue. This means that even if a user no longer matches the initial targeting criteria, they will continue to be part of the test. You can turn the icon off, which will turn the button grey and will remove users from a test if they no longer match the targeting criteria.
Manual Sending A type of delivery that allows apps to send messages using the REST API.
Message Actions Performs an in-app action that may not display a message, such as sending the user to a specific url (in-app or external)
Metric Catalog The metric catalog appears when you click the + tile in analytics or attempt to add a goal to an a/b test. These are all the metrics that are currently being tracked for the application and can be selected for analytics. For a full description of metrics, click here.
Newsfeed A type of message that sends to an inbox contained within your app that Leanplum manages for your users to revisit.
Paused Mode Paused status is when an a/b test or messaging campaign has been published live to the targeted users but subsequently paused.
Preview Panel The preview panel will display the message on the viewer to the right side as one would see it on their device.
Production Key This key is used to tell leanplum to send the data to the production/live pipeline. It is specific to your app and Leanplum dashboard. See our available production methods.
Push Notifications A type of message that is sent to your users while they are not in the application.
Returning User A returning user is a user who has installed the app and has had at least 1 session prior. On the day that they are viewed as returning user, it will be their 2nd or greater session.
Scheduled Sending A delivery type that results in users receiving the message on the day and time option selected. There are several time options that Leanplum provides.
Statistical Significance Significance represents the likelihood that when Leanplum identifies a winning variant, it is in fact a winning variant. If you choose a higher significance, you reduce the risk of a false positive (i.e. concluding your goal was reached when in actually was not), but your experiment will need to run for more time. Our defaults of 80 percent power and 95 percent significance works well for most applications, and we recommend you only change them if requested by your data science team. We calculate significance with the Welsh T-test.
Status Indicator This icon tells you whether the test is active (green) or paused (gray), in draft mode (pencil icon) or finished (checkered flag). By clicking on the bubble, you are presented with these options.
Targets The targets allows you to select groups of users based on attributes about them or actions they have taken. You can use targets in a/b tests and/or messaging campaigns to focus on specific users. For a full list of targets and their definitions, click here
Team Management Page The Team Management page allows you to edit your account settings, create, edit, or delete teams, and add or remove team members. All apps in Leanplum belong to a team, and all users that are members of a team have access to all apps that belong to that team.
Test Devices Management Page The Test Devices Management page allows you to manage which devices are registered as development devices. To add a development device, either run a development build of your app on your device, or find an existing user via the Users dashboard and click Register next to the device.
Time Estimator The time estimator gives an approximation of when the test will reach statistical significance. If the test is estimated to take a long time to complete, you can alter several things in your test to help minimize the time estimated. The key things that impact the test time estimation are: 1. The goals selected 2. The targets selected 3. The number of variants in the test.
Triggered Sending A delivery type which users must complete the selected action in order to trigger the push notification to send at the desired time delay after said action has been completed.
UI Editor The UI Editor allows you to modify the appearance of any static screen within your app on the fly, without having to re-submit your app to the App Store. You can change any visual element; some examples include swapping out an existing image for a new image, changing the color, size, and placement of any button, and changing text.
Variable A variable is anything in the app that you may want to swap in and out on the fly or A/B test. This can be a line of text, an image, a layout file or a new feature. Once a variable is coded in and sync’d on Leanplum, you can change the default as you like without having to resubmit to the app store.
Variable Default in Code This is the default that the user will see should no change be made to the variable. The value listed here is what the developer coded in as the default.
Variable Overrides The variable override is where you input the change in value/experience that you want the users to see as opposed to the default.
Variant The variant is the change that you are making in the test and comparing with that of the control. Simply click on the value in the variant and change it to the desired option that you want served to your users in the test.
Visual Element Editor In the UI editor, this allows you to make changes to the selected element here. Your options will vary depending on the type of element you sent.
Webhook A type of message that sends through another service, such as an email provider.

Was this article helpful?
Have more questions? Submit a request