> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/collect-users-from-a-tagged-page.md).
# Collect users from a tagged page
Build an audience from whoever loads a page, using a mediarithmics pixel.
## Your goal
Collect an audience defined by a single criterion - "loaded this page" - without writing a query or knowing your schema.
## Expected outcome
A [Pixel segment](/audience-and-activation/build-your-audiences/segment-reference/segment-types/pixel-segment.md) that fills itself with every user that hits the pixel you placed, and empties itself on the default lifetime you set.
## When this is useful
* A page whose visitors matter but whose meaning is not in your schema - a campaign landing page, a pricing page, a specific article.
* An audience you need before the schema work to express it properly is done.
* A partner or agency page you want to collect from without changing your data model.
## Prerequisites
* The ability to place a snippet on the pages concerned - directly, or through a tag container.
* A view on how long a user should stay in the audience, which becomes the segment's default lifetime.
## Steps
{% stepper %}
{% step %}
### Create the segment
In the segment creation wizard, select **User Pixel** under *Other segment types*.
{% endstep %}
{% step %}
### Name it and set its lifetime
Give it a name. Fill in the optional fields - in particular the **default lifetime**, which is supported on this type and is what stops the audience growing indefinitely. See [Segment properties](/audience-and-activation/build-your-audiences/segment-reference.md#segment-properties).
{% endstep %}
{% step %}
### Save and collect the snippet
Click **Save**. A code snippet appears at the bottom of the configuration page.
{% endstep %}
{% step %}
### Place the snippet
Paste it on the pages whose visitors should join the segment.
{% endstep %}
{% endstepper %}
## Verification
The segment appears in **Audience > Segments** with the type `Pixel`, and its user count starts rising after the pages carrying the snippet get traffic.
## Limitations to plan around
* **The criterion is the placement.** A pixel segment can express exactly one thing - that the pixel loaded. Anything conditional needs a [Query segment](/audience-and-activation/build-your-audiences/segment-reference/segment-types/query-segment.md) instead.
* **Consent applies.** If the audience will be activated, attach the processing activities to the segment. Pixel segments do support user choices, unlike Campaign, Lookalike and Edge segments. See [Enforce compliance on your audience](/audience-and-activation/build-your-audiences/enforce-compliance-on-your-audience.md).
* **A blocked tag collects nothing.** As with any client-side collection, an ad blocker or an opt-out through your CMP means the snippet does not run.
## Related pages
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/collect-users-from-a-tagged-page.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.