> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/integrations/events-and-pixels.md). # Events and pixels Install the pixel, what it captures, how visitors resolve to real accounts, and how consent works. The pixel is how the platform sees your site: who visits, what they look at, and which campaigns brought them. It is available on every plan, and it is the first-party signal that feeds identity, scoring, and attribution. ## Install the pixel {% stepper %} {% step %} ### Copy your snippet Go to **Settings → Visitor Intelligence** and copy your workspace's snippet. It is one small async script tag carrying your workspace id. {% endstep %} {% step %} ### Add it to your site Paste it into your site's ``, or add it through your tag manager. One snippet covers every page. A static-tag variant is available for sites with strict content-security policies. {% endstep %} {% step %} ### Confirm traffic Back in Visitor Intelligence, confirm the pixel is receiving traffic. That's it. {% endstep %} {% endstepper %} ## What it captures Page views (including single-page-app navigation), referrers, UTM parameters, scroll depth, and device basics. Form submissions are detected so a visitor who fills in an email becomes known. Your own site can also call `window.aloop.identify()` and `window.aloop.track()` for custom events (the tracker keeps its original `aloop` namespace; it is the same platform). ## How visitors become accounts Anonymous visits resolve to real people and companies two ways: a form email ties the visitor to a contact, and reverse-IP resolution ties the visit to a company. Resolution is retroactive: once a visitor resolves, their earlier anonymous activity is re-attributed to the same identity. {% hint style="info" %} Visitor resolution draws credits only when a resolve succeeds; per-action rates are in [Billing](/settings/billing.md). The pixel is available on all plans, and seeing visitors by name is included on all plans, Free included. {% endhint %} ## What you get back Once the pixel is live, each resolved visit returns four things: * the **account** (and, where a form ties it, the person), resolved to its immutable ID, * the visitor's **full activity**, including earlier anonymous sessions re-attributed to the same identity, * a **FIRE score movement** where the visit carries intent, with the reason attached, * and the **credits drawn**, charged only because the resolve succeeded. Resolved accounts appear in [Audience](/audience/building-audiences.md) under **Hot lists**, the system-built lists, as **Identified visitors**. Visits that do not resolve cost nothing and stay counted as anonymous traffic. ## Consent The pixel does not decide consent; your consent banner does. Wire the snippet into your consent management platform so the pixel loads only after the visitor consents, the same way you gate any analytics tag. If you use HubSpot's or another CMP's banner, load the pixel in the consent-granted callback. Consent and suppression flags then flow through everything downstream; see the [Security model](/security-and-compliance/security-model.md). ## Outside the app Visitor events can be viewed outside the app via [API](/settings/api-keys.md) and [MCP](/iharness/bring-your-own-agent.md) as well. --- # 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://docs.aloop.icustomer.ai/integrations/events-and-pixels.md?ask=&goal= ``` `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.