# Install the pixel
**What it does:** records which pages get visited, attributes them to the
campaign that brought the visitor, captures commerce events if your store emits
them, and — where it can — resolves an anonymous visitor to a person.
**Time:** one tag. The rest of this page is what it collects and how to control
it, which is the part worth reading before you paste it.
Every workflow and playbook on this site lists "the pixel live" as a
prerequisite. This is that step.
---
## The tag
```html
```
Put it in ``. `async` is deliberate — the pixel never blocks rendering,
and nothing on the page waits for it.
Your workspace ID is on the **Settings** page, and the wizard shows this snippet
with the ID already filled in.
### Pinning a version
`/signal-pixel.js` always serves the current release. If you would rather decide
when you move, name a version instead:
```html
```
A pinned URL never changes its bytes. We do not edit a released version, even to
fix a comment — if something needs to change, it becomes a new version and the
unversioned URL moves to it.
Pin if you have a change-control process. Otherwise use the unversioned URL and
get fixes without doing anything.
---
## Consent
**The default is to collect.** A tag with no consent attribute starts recording
on the first page load.
That is the right default for a first-party analytics tag on your own site in
the US, and it is the wrong default if you run a consent banner. If you do, say
so explicitly:
```html
```
With that attribute the pixel collects nothing — no page views, no commerce, no
identity resolution, and it does not even load our identity vendor's script —
until you call:
```js
window.geyseraSignal.grantConsent()
```
Call it when the visitor accepts. Anything that happened before the click is not
lost: page views and commerce events detected while waiting are buffered in the
browser and sent on grant. Nothing leaves the browser before that call.
To withdraw:
```js
window.geyseraSignal.revokeConsent()
```
That stops collection, stops identity resolution including any request already
in flight, and discards the identifiers — ours and our identity partner's alike.
A later opt-in starts a new anonymous visitor rather than rejoining the old one.
**One honest limit.** Our identity partner's script, if it had already loaded
before the visitor withdrew, stays loaded for the rest of that page — a
`