> For the complete documentation index, see [llms.txt](https://keak.gitbook.io/keak-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://keak.gitbook.io/keak-docs/getting-started/quickstart/installing-the-keak-tracking-pixel.md).

# Installing the Keak Tracking Pixel

The Keak Tracking Pixel is a small JavaScript snippet that enables Keak to display variations to your visitors and record conversion events. **You only need to install it once per website**, and it will power all current and future tests on that domain​

{% embed url="<https://www.youtube.com/watch?v=brJS9WEKezQ>" %}

**How to install the pixel:** After you launch your first test in Keak, you’ll be provided with a unique script tag (your tracking pixel). Include this script on your website’s pages, ideally by pasting it into the global `<head>` section of your site’s HTML​. This ensures the script loads early on every page for reliable tracking. Most developers will add the pixel code to a site-wide header or template so it’s included on all pages. *(For example, on Shopify you would paste the code into your theme.liquid header, or on WordPress into the global header.)*

Once added, the pixel will **asynchronously load a tiny library** of functions that listen for visitor actions and enable Keak to swap in content variations when a test is running​

&#x20;The script is lightweight and optimized for speed, so it won’t bog down your page load times. Placing it in the `<head>` ensures maximum compatibility and that visitors are tracked even if they leave the page quickly​.

**Note:** If you need help installing the pixel on popular platforms, refer to our integration guides for step-by-step instructions (e.g., how to add the script to Shopify or Webflow). Once the pixel is in place, you do **not** need to reinstall or change it for each new test​ - it remains the same and will work for all tests on that domain.

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Shopify Guide </td><td><a href="https://keak.com/shopify">https://keak.com/shopify</a></td><td><a href="/files/R5UHELWyCIHZuIS7jP86">/files/R5UHELWyCIHZuIS7jP86</a></td></tr><tr><td>Framer Guide</td><td><a href="https://keak.com/framer">https://keak.com/framer</a></td><td><a href="/files/7Bby07Om6b8nwRRqKxED">/files/7Bby07Om6b8nwRRqKxED</a></td></tr><tr><td>Webflow Guide</td><td><a href="https://keak.com/webflow">https://keak.com/webflow</a></td><td><a href="/files/gXRXPGWcatNBUSnv65KS">/files/gXRXPGWcatNBUSnv65KS</a></td></tr><tr><td>Wordpress Guide </td><td><a href="https://keak.com/wordpress">https://keak.com/wordpress</a></td><td><a href="/files/RkfvwG33fnV67cLhSWqY">/files/RkfvwG33fnV67cLhSWqY</a></td></tr><tr><td>Squarespace Guide</td><td><a href="https://keak.com/squarespace">https://keak.com/squarespace</a></td><td><a href="/files/Pddhm9vywhuV9R2XpU4V">/files/Pddhm9vywhuV9R2XpU4V</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://keak.gitbook.io/keak-docs/getting-started/quickstart/installing-the-keak-tracking-pixel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
