Step 13 — What next
Setup is not a state you reach; it is one you keep. How to find out something broke without looking.
A finished setup decays. An OAuth token expires, a developer strips the UTMs off a landing page, a CRM pipeline gets renamed, a Meta dataset is replaced. None of those announce themselves in a dashboard that keeps rendering numbers — they announce themselves as numbers quietly getting smaller.
Three habits, in order of value:
- The setup-status strip. It stays on the dashboard, driven by the same readiness checklist. A connection that flips to reconnect required shows up there before it shows up as missing revenue.
- Data quality, weekly. Attribution coverage and UTM health are the two numbers that move first when instrumentation breaks.
- Scheduled reports. A report that arrives every Monday is also a liveness check: the week it looks wrong, something upstream changed.
Stop polling. Subscribe.
curl -sX POST https://api.atribu.app/api/v1/webhooks/subscriptions \
-H "Authorization: Bearer atb_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/atribu",
"providers": ["atribu"],
"events": [
"connection.reconnect_required",
"connection.revoked",
"recompute.completed",
"conversion.attributed",
"export.completed",
"export.failed",
"profile.freshness.changed"
]
}'The providers list is the part people miss
Every platform lifecycle event carries the provider atribu, not a channel. A
subscription whose providers list does not include it receives none of
them, whatever its events list says. The connector's real provider rides in
data.provider.
Then keep a much smaller loop:
GET /api/v1/profile/readinesson a schedule — adegradedstep is a broken connection, and itswhyalready says which and what to do.GET /api/v1/profile/freshnessbefore drawing a number you are about to act on.- Verify the HMAC signature on every delivery before trusting it, and use
POST /api/v1/webhooks/test/{id}to prove your verifier works before real traffic depends on it.
What to do with the setup now that it works
- Read what earned the money. Overview for the KPIs, breakdowns for the cuts, customer journeys for the individual story behind a payment.
- Compare attribution models.
GET /api/v1/attribution/modelsputs all five side by side. If last-touch and first-touch disagree sharply, your funnel is longer than one click. - Act on it. Recommendations are the AI media buyer's suggestions, applied through one audited write spine with a rollback.
- Report it. Reports for the client-facing artifact, with a share link that needs no login.
Adding the next profile
Steps 5 through 12 are per profile. An agency onboarding a second client repeats them — which is exactly why the agent track exists: the second time through should be a script, not an afternoon.