Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

1

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.

2

Add it to your site

Paste it into your site's <head>, 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.

3

Confirm traffic

Back in Visitor Intelligence, confirm the pixel is receiving traffic. That's it.

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.

Visitor resolution draws credits only when a resolve succeeds; per-action rates are in Billing. The pixel is available on all plans, and seeing visitors by name is included on all plans, Free included.

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 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.

Outside the app

Visitor events can be viewed outside the app via API and MCP as well.

PreviousYour stack
NextDestinations vs live channels

Last updated