Quiz: What Did You Learn?

Now that you’ve had a chance to learn more about this topic, let’s review what you should have learned with a short quiz. Select the best response to each question. When you've answered all the questions, select the submit button to check your answers.

What are some questions you should ask when analyzing your results and looking toward ideation from a winning variation?

Can we further optimize this page along the same trend?

Are there changes we made in our winning variation that kept it from being even more successful?

Could I apply this hypothesis elsewhere on my funnel?

Are there other sites or domains where we could test this idea?

1,3

2,4,5

1,3,4

1,2,3,4

Only site changes that have should be passed to the development team for implementation.

Reached statistical significance

Been tested and validated with data

Your full confidence in their effectiveness

Complete approval by your experimentation team

What impact can involving a developer in the experimentation process have?

Increase in the amount of time needed to plan your experiments

Decrease in the time it takes to translate successful changes to your live site

Slight increase in the effort it takes to set up a new experiment

They can help you design more impactful and efficient experiments

1, 2, 4

2, 3, 4

1, 2, 3

1, 2, 3, 4

Why is it important to have your developer write new code when implementing experiments rather than simply copying over and pasting the experiment code?

Developers need to understand and keep track of everything that’s being added to your website, so they should write new code in order to ensure that they are aware of exactly what is being added to the website.

If the code isn’t correctly aligned with your website, that code will often work just fine short-term, but in the long term, the strain of conflicting code can actually cause the website to go down.

It’s not necessary, actually. The experiment editor creates efficient code that can be directly implemented after an experiment wins.

When using the experiment editor, hundreds of lines of code are generated, some of which may be excessive in the long-term. This can cause flashing as the page loads, so having a developer implement more efficient code is necessary.