-
Can 2 experiments share the same variables? If yes, under what conditions?
-
Changing distribution back to what it was after setting a winner
-
Days Since Sign Up
-
Does the getRunningExperimentsAndVariations block get called even with a failed/timeout response?
-
Experiment behaviour when setting winning variations
-
Experiment Distribution Logic
-
For a new build we just switched the default value of our variable to be FALSE (previously TRUE). Would this cause any issues for the experiment?
-
For A/B experiments, any plans for showing statistical significance of results and how many users are required to reach significance? Similar to how other A/B testing tools display results
-
For any experiment that already has a winning variation assigned to it, is it still possible to restart it but with a different distribution?
-
For users who have previous versions of my app and don’t have code variables, will they be accounted for?
-
Getting Code Variables/Code Blocks to show up in the Taplytics Dashboard
-
I have a bunch of repeated elements and I don't want to manually select each and every one of them. Is there an easy way to select them all?
-
I have two experiments we want to run on our initial signup screen - do we have to wait until the first experiment is done in order to begin the second one?
-
If I change the value of a code variable of a variation while an experiment is running, how soon does it come into effect? Anything I should consider?
-
Is it safe to not target a specific version of the app where older versions of the app don't have experiment variables?
-
New custom data field - Dashboard logic
-
Reaching Statistical Significance while running A/A tests
-
Removing/Deleting Code Variables
-
Running Simultaneous Tests
-
Segmentation for targeting a specific country, region, or city
-
Send Custom Events Using Taplytics API
-
Setting up Experiment Segmentation and Distribution
-
Statistical Significance Calculation
-
Using the Taplytics Experiment Rollout feature
-
We have users who switch devices (use both iPhone and iPad). Under no circumstance should a user see the baseline on his iPhone and the variation on his iPad. Is there a way to do this with Taplytics?
-
What happens during an experiment if there's bad connection with Taplytics' servers ?
-
What happens to variables, code blocks, and experiments when you want to start a new project?
-
What if I don't want to set a goal for an experiment?
-
What is the maximum number of experiments I can have running at any given time?
-
When choosing segmentation for app version comparisons, such as greater than or equal to, how do they account for strings? e.g. is 3.11.0_stage >, <, or = 3.11.0?