<h1 id="heading-creating-a-new-netlify-site">Creating a new Netlify Site</h1>
<p>Create a site on Netlify from a GitHub repo allow to trigger a deployment on repository update</p>
<h1 id="heading-creating-branch-deploys">Creating branch deploys</h1>
<p>Netlify settings to deploy all branches</p>
<h1 id="heading-creating-and-configuring-split-tests">Creating and configuring split tests</h1>
<p>“<a target="_blank" href="https://docs.netlify.com/site-deploys/split-testing/">Netlify's Split Testing</a> allows you to silently serve different versions of your sites to your users without compromising performance which would prejudice your test results.”</p>
<p>“The way that this happened on Netlify, it's thanks to <a target="_blank" href="https://www.netlify.com/products/edge/">Netlify Edge</a>, which allows us to run a thin layer of logic right out on the edge nodes of the CDN that can shape the traffic from one branch to the other depending on rules that we create. Let's go and create some of those rules now.“</p>
<h1 id="heading-adding-branch-information-to-analytics">Adding branch information to analytics</h1>
<p>Add snippet code for Google Analytics about the BRANCH variable</p>
<h1 id="heading-opt-in-betas-with-branches-and-split-testing">Opt-in betas with branches and split testing</h1>
<ol>
<li>Set up a split test with two branches as 100% and 0%</li>
<li>Setup script to create a cookie with “nf_ab: BRANCH_NAME” + reload</li>
<li>When the user clicks, thanks to the cookie, Netlify will guide the traffic to the specific branch.</li>
</ol>
<h1 id="heading-resources">Resources</h1>
<ul>
<li><a target="_blank" href="https://explorers.netlify.com/learn/split-testing-with-netlify">Netlify explorers resources</a></li>
</ul>


# Creating a new Netlify Site 
Create a site on Netlify from a GitHub repo allow to trigger a deployment on repository update

# Creating branch deploys
Netlify settings to deploy all branches

# Creating and configuring split tests
“[Netlify's Split Testing](https://docs.netlify.com/site-deploys/split-testing/) allows you to silently serve different versions of your sites to your users without compromising performance which would prejudice your test results.”

“The way that this happened on Netlify, it's thanks to [Netlify Edge](https://www.netlify.com/products/edge/), which allows us to run a thin layer of logic right out on the edge nodes of the CDN that can shape the traffic from one branch to the other depending on rules that we create. Let's go and create some of those rules now.“
# Adding branch information to analytics
Add snippet code for Google Analytics about the BRANCH variable

# Opt-in betas with branches and split testing
1. Set up a split test with two branches as 100% and 0%
2. Setup script to create a cookie with “nf_ab: BRANCH_NAME” + reload
3. When the user clicks, thanks to the cookie, Netlify will guide the traffic to the specific branch.

# Resources
- [Netlify explorers resources](https://explorers.netlify.com/learn/split-testing-with-netlify)

Netlify Explorers

⚙ Split testing with Netlify

Creating a new Netlify Site

Creating branch deploys

Creating and configuring split tests

Adding branch information to analytics

Opt-in betas with branches and split testing

Resources

LPM Blog

Léo-Paul's Blog