Review our Taplytics Glossary for a better understanding of the terminology used on our platform and our documentation.
A QA and experimentation function which allows the Taplytics Dashboard to connect in real time to a development or production device, allowing you to make static copy or image changes without the need for a release using the Visual Editor.
The version of your app users would see if there were no a/b tests (the control over the variation). Typically setup to be the same experience as Default value.
Taplytics code which wraps around single or multiple elements for testing with dynamic content or to be used outside of a release schedule. Simply put, it is a bundle of code that can be set to turn ON or OFF.
Taplytics code which allows for dynamic testing within your app. For example, testing different variations of an onboarding or checkout flow.
The Taplytics platform’s interface, where you can navigate through different projects, experiments, push notifications, and feature flags.
Percentage of users who will be in baseline and variation(s).
The actions that are logged to track user behaviour to evaluate the success of the variation(s) over the baseline.
Allows you to control the percentage of users in each variation who will be exposed to the element(s) being tested.
Track the conversions on any number of metrics to measure the impact/success of the variation(s) over the baseline.
Refers to the specific environment that experiments are launched from. Each has its own unique SDK and API keys. Clients can have as many as they like; typically, we see one for Staging and Production. Most clients use iOS and Android within the same project.
User Segment (audience)
A specified group of users who will be included in the test.
Taplytics code which wraps around specific element(s) for testing with dynamic content or to be used outside of a release schedule. Can be a String, Number, Boolean or JSON.
Shouldn’t be the same as Default value. It refers to the updated version(s) of the app/webpage that shows the modified element(s) which are being tested.
Used together with Advanced Pairing, this tool allows you to select and edit static UI elements (copy and images) within your app to launch tests outside of a release cycle without touching your actual codebase.
Updated about a year ago