The cumulative exposures graph: Inflection points and flattened slopes

This article helps you:

  • Interpret the meaning of an inflection point in your cumulative exposures graph

  • Determine why you're seeing a flattened slope

Inflection point

Sometimes, lines will have an inflection point caused sudden increase or decrease in the count of exposures per day.

image2.png

You can see here that on February 27, the slope of all three lines changed a bit, from around 70 users per day per variant, to about 100 users per day per variant. (Note that the slope can also flatten after an inflection point.)

There are several reasons why this could happen:

  • Traffic was increased to your experiment
  • Traffic allocations were increased for each variant (If you had increased traffic to a single variant, then only one line would show this inflection point)
  • Targeting criteria was changed (i.e., originally you were targeting users from California, but then decided to target users from California and Florida)
  • There was some external event (like an increase in the advertising budget or the release of a new feature, that could have driven more users to your experiment)

Settings changes during a live experiment

You should not change settings for traffic or traffic allocations to variants in the middle of an experiment. Doing so can introduce Simpson’s paradox into your results. If you have changed the traffic allocation, we suggest you restart the experiment by choosing a new start date. Avoid including any users who were already targeted.

Note

Likewise, you shouldn’t change the targeting criteria during an experiment because the sample is then not representative of what would happen if you rolled out a variant to 100% of your users. Instead, consider gradually increasing traffic to the entire experiment, or doing a gradual feature rollout instead of an experiment.

For example, imagine that in the first week of your experiment, you target only Android users, and your experiment is seen by 100 of them. The following week, you change the targeting criteria to include iOS users, and your experiment is seen by 20 of them.

So far, your experiment has been seen by 220 users after two weeks; 9% of them (20/220 = 1/11 = 9%) are iOS users. However, when you release your experiment to 100% traffic, you discover the true percentage of iOS users is actually 16.7%. In this case, we are underestimating the effect of iOS users. If the experiment shows a positive lift for Android users but a negative lift for iOS users, you may be rolling out a feature based on what you think is a positive experiment, but it is in fact a negative.

Consider changing the experiment's end date

Once you have answered the question of why the slope changed, consider whether the end date of the experiment should be adjusted. With more traffic, you’ll reach statistical significance faster. If you are getting less traffic, you will reach statistical significance more slowly.

Flattened slope

image3.png

Focusing on the data from March 4 to March 11, the graph is fairly flat. This indicates that very few new users were added to the experiment during that time period. Potential explanations include:

  • You’ve run out of users to add to the experiment
  • There is a bug in the sending of exposure events
  • Your product’s usage is strongly affected by seasonality

You can see a strong illustration of that last bullet point in this hourly chart:

image7.png

Between March 21 at 7 pm and March 22 at 9 am (the rightmost section of the graph), very few users were exposed to this experiment. But just before that, starting at around 5 am, a large number of users were exposed. Yet on the left hand side of the graph, the pattern is one of users slowly trickling in. When you consider that this experiment is run by an online gambling company, it makes sense that there would be these spikes in traffic when they run their jackpots.

Was this page helpful?

Thanks for your feedback!

May 21st, 2024

Need help? Contact Support

Visit Amplitude.com

Have a look at the Amplitude Blog

Learn more at Amplitude Academy

© 2024 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.