> For the complete documentation index, see [llms.txt](https://docs.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.icustomer.ai/ireveal/poc.md).

# 30-day POC

The 30-day iReveal POC: discover, deploy, evaluate, on your traffic, with full decision rights retained throughout.

iReveal proves itself on your traffic, not in a demo. A POC runs 30 days on your site and ends in a joint review against success metrics you agreed to before anything went live. Until that review, nothing is committed.

{% stepper %}
{% step %}

### Week 1: Discovery

A tag audit of your site, a walkthrough with your privacy or legal team where your jurisdiction calls for one, and success metrics fixed jointly. Data processing terms are signed before any live data moves.
{% endstep %}

{% step %}

### Week 2: Deploy

The tag goes live and resolution starts, hosted or against your own warehouse, in the data plane your compliance posture requires. Consent gating is wired to your banner from the first event; see [Consent](/ireveal/consent.md).
{% endstep %}

{% step %}

### Weeks 3 and 4: Evaluate

Resolved accounts flow daily while the evaluation runs. The POC closes with a joint review of what iReveal found against the metrics agreed in week 1.
{% endstep %}
{% endstepper %}

## The ground rules

* You retain full decision rights throughout.
* No commitments before the joint review.
* Consent first: capture is gated by your banner from day one, and no automated individual decisions are made about the people identified.

## What a good POC measures

The point is not traffic counts; analytics already gives you those. A POC is judged on what was previously invisible: how much of your anonymous traffic resolved to real accounts, which of those accounts your team would actually want, and what came of the ones you acted on.

## What you get back

Thirty days in, you hold four things:

* a **resolved-account list**, built daily from your own traffic,
* the **resolution rate** on your site, measured, not estimated,
* **outcome evidence** for the accounts you acted on, joined end to end,
* and a **joint review** against the success metrics you set in week 1, before anything was committed.


---

# 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.icustomer.ai/ireveal/poc.md?ask=<question>&goal=<user_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.