The golden path
Thirteen steps from signing up to a Purchase landing in Meta's Test Events tab — the same journey whether a person clicks it or an agent drives it.
Atribu connects your ad platforms (Meta, Google Ads), your CRM (GoHighLevel), your payment providers (Stripe, MercadoPago, Webpay) and your own systems, and answers one question: which ads produced real money. Then it sends that answer back to Meta so the ad platform can optimize on it.
Getting there is thirteen steps. This page is the map; every step has its own page with two tracks:
- In the app — the screens, the exact menu path, what you will see.
- With the API / an AI agent — the
curl, the SDK call, the MCP tool, and the hand-off pattern for the steps only a human can finish: give the user this URL, poll this handle.
Is an AI agent setting this up for you?
Then you have almost nothing to do. Step 2 is yours and it is the only one: your agent gives you a URL. Open it, create your account, approve. Come back. Everything before and after that is the agent's work — see the API quickstart or the MCP quickstart for what it is doing on your behalf.
Are you the agent?
Start at For AI agents — the bootstrap, the discovery documents, the readiness read, and the hand-off pattern, in one page.
The thirteen steps
| # | step | what has to be true at the end | readiness key |
|---|---|---|---|
| 1 | Discover | you know what Atribu does and which track you are on | — |
| 2 | Create your account | an Atribu account exists, email confirmed | — |
| 3 | Workspace and profile | one workspace, one profile per advertised business | — |
| 4 | Credentials | you hold a key or token that can act | — |
| 5 | Install the tracker | an event reached Atribu in the last 7 days | tracker_installed |
| 6 | Connect Meta and Google | a healthy ad-platform connection | ad_platform_connected |
| 7 | Connect your CRM | something tells Atribu when a lead or sale happens | crm_or_outcome_source_connected |
| 8 | Connect payments | cash can reach a conversion | payments_connected |
| 9 | Define conversions | one cash + attribution-eligible definition exists | conversion_definitions_valid, attribution_windows_set |
| 10 | Verify | a conversion has been credited to a touch | first_conversion_attributed |
| 11 | Send it back to Meta | a destination, a rule, and a test event Meta received | capi_destination_enabled, capi_rules_enabled |
| 12 | DPA and plan | the DPA is accepted and a plan is in place | legal_dpa, plan |
| 13 | What next | you find out when something breaks, without looking | — |
The readiness key column is not decoration. GET /api/v1/profile/readiness
returns exactly these steps, in this order, with a status and a next action for
each — so at any point you can ask the API where you are instead of guessing.
See Readiness.
Step 1 — Discover
You are here. Three things worth knowing before you spend the fifteen minutes:
- Only cash counts for ROAS. Atribu deliberately keeps pipeline value (a CRM's projected deal value) separate from money that actually arrived. Mixing them makes every ratio meaningless. See Revenue types.
- Attribution needs both halves. Ad platforms know the clicks; your CRM and payment provider know the money. Neither alone can answer the question, which is why steps 6, 7 and 8 all exist.
- Nothing here is a black box. Five attribution models, per-profile windows, and a coverage number that tells you what cannot be attributed. See Attribution models.
Machine-readable entry points, if you are a program:
llms.txt,
llms-full.txt,
the OpenAPI document, and the MCP
endpoint at https://mcp.atribu.app/mcp.
How long it takes
About fifteen minutes of clicking, then a wait. Spend and tracker data appear within minutes; attributed revenue appears when your first real conversion lands, which is your customers' clock rather than ours.