Find where users get stuck in your Django site.

Add Cuttl to your base template

1. Sign in to Cuttl, or create a free account. Add your site with its domain. Open the site’s Install tab and copy the Cuttl Tag. It starts with <!-- Start Cuttl -->.
2. Open the template your other templates extend. It’s often templates/base.html.
3. Paste the Cuttl Tag inside <head>, between {% verbatim %} and {% endverbatim %}. {% verbatim %} tells Django to leave the Cuttl Tag exactly as it is.
   templates/base.htmlCopy

   <head>
       {# your other head tags #}
       {% verbatim %}
       <!-- Paste your Cuttl Tag here -->
       {% endverbatim %}
   </head>

4. Deploy.
5. In Cuttl, turn on Journey Insights for heatmaps and recordings, or Web Experiments for A/B tests. Admins can do it on the product’s page or in Settings → Plan & usage. A new workspace starts with both off, and until one is on, Cuttl keeps nothing from your site.

Check it works

1. Open any page of your live site in a browser.
2. In Cuttl, open the site’s Install tab. It shows when data last arrived, usually within a minute.
3. Nothing yet? View the live page’s source and search for app.cuttl.io to check the Cuttl Tag is there. Then check that the site’s domain in Cuttl matches the address in your browser.

Check on your deployed site. Cuttl only takes data from your site’s domain, so pages on localhost won’t show up.

Good to know

• If some pages use a different base template, add the Cuttl Tag there too.
• The Django admin uses its own templates, so your staff pages aren’t tracked.
• If your app sets a Content Security Policy nonce, add it to the script tag. The scripts Cuttl adds inherit it.
• To leave out your own sessions, open any page of your site once with ?cuttl_ignore=1 at the end of the address.