> 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/getting-started/the-loop.md).

# The loop in one page

How iCustomer Platform turns a goal into an outcome and back again: five steps, and an honest answer at every point it cannot advance.

Every marketing team asks the same two questions: am I winning, and what's my next move? Most tools answer half. Dashboards tell you where you stand and cannot act. Automation runs work and cannot tell you whether it helped.

iCustomer Platform closes that gap by running one loop, continuously, over your business:

```mermaid
%%{init: {'themeVariables': {'lineColor':'#98A2B0','edgeLabelBackground':'#E4EAF3','textColor':'#1f4f9c'}}}%%
flowchart LR
    G(Goal) --> K(KPI)
    K --> T(Target)
    T --> P(Play)
    P --> O(Outcome)
    O -. credited back through identity .-> T
    classDef box fill:#E4EAF3,stroke:#2966BC,color:#1f4f9c
    class G,K,T,P,O box
```

* **Goal**: one of [six standing GTM ambitions](/iharness/goals-kpis-targets.md), with one primary and up to two secondaries. The goal orients the whole loop. Every KPI is read in its service, and every decision is made to advance it.
* **KPI**: what your connected sources can actually read. Measurability is the definition: if nothing you've connected can compute it, it isn't a KPI for your workspace. This is why connecting a source doesn't just add data, it unlocks goals.
* **Target**: a number worth committing to, with a deadline, a guardrail that stops it being won the wrong way, and a checkpoint that tells you early if the plan is wrong. Achievability is part of the definition: a number nothing can reach isn't an ambitious target, it isn't a target.
* **Play**: a repeatable motion that moves a KPI. Several plays can move the same KPI through different mechanisms, which is why choosing one is a diagnosis rather than a lookup.
* **Outcome**: what actually happened, measured against what was expected. The difference between the two is what the system keeps.

## Why the loop closes

An outcome happens to one person or one account. A KPI is a number about a population. For an outcome to credit back to the target it served, the platform has to know that this person and that account are the same entities it was working on when it decided.

That's why identity resolution sits underneath everything rather than off to the side in data hygiene: it's the join that lets the loop close. When identity doesn't resolve, the outcome is still counted and still reported, credited to nothing, and said out loud. It is never quietly dropped.

## What you get

One loop, running over your business, returns four things:

* **A number worth committing to.** Targets are computed from what your connected data can read and what your plays can move, never guessed.
* **The right move, diagnosed.** The play that matches the cause behind a slow number, not a lookup from a menu.
* **A receipt for every action.** Why it ran, what it expected, and what came back, on record before it runs.
* **An honest answer when it cannot advance.** At every step the platform either moves forward or tells you exactly what is in the way and what would unlock it. Those moments arrive in [Pulse](/pulse/queue.md).

## The meta loop

Underneath the first, a slower loop runs and never closes: **outcome → evidence → better targets, better play choice.** The first loop runs in roughly 90 days. The meta loop runs across quarters, and it is where the compounding lives.

Concretely: when a target closes, the platform records what that play actually delivered in your workspace. Your own measured result then outranks any published benchmark the next time it sizes something. The bar moves as your business gets better, instead of the product going quiet after the first win. [The compounding loop](/measurement-and-outcomes/compounding-loop.md) follows the meta loop through measurement.

{% hint style="info" %}
The loop is continuous by design. Continuous, always-on operation over your managed audiences is a Team capability. On Free and Pro, the same loop runs on request.
{% endhint %}

## Where to go next

* [**Core concepts**](/concepts/core-concepts.md): the terms this loop is built from.
* [**System architecture**](/concepts/system-architecture.md): the five layers the loop runs on.
* [**Data flow and trace spine**](/concepts/data-flow.md): how a single event travels.
* [**Plans**](/getting-started/plans.md): what each plan unlocks.


---

# 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/getting-started/the-loop.md?ask=<question>&goal=<endgoal>
```

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