Documentation
Ask AI
Cited answers on attribution, delivery, forms, content, and tracking health. Pause/boost apply is in Attribution — not MCP.
Ask AI answers questions about your attributed revenue, destination delivery, and on-site behavior — citing the same data Attribution and Experience use. Open it at Ask AI. Feature key: ai_analytics (also shown as Intently AI).
It does not invent credit percentages or invent a custom “intent score.” Answers ground in stored events, attribution models, ROAS, and delivery proof.
Pause or boost recommendations with Apply pause / Apply +20% budget live on Attribution (Meta, Google, Microsoft — confirm required). Ask can surface weak-ROAS campaigns; write-back is not performed through Ask or MCP.
What you can ask
Starter categories (availability depends on what you capture and your plan):
| Family | Examples |
|---|---|
| Attribution & revenue | Top channels by attributed revenue; paid vs organic; why Direct gets credit; weak-ROAS next checks |
| Delivery proof | Destination success rate; which routers fail; capture vs delivery |
| Forms | Field abandonment; completion rate; started-but-not-submitted forms |
| Converters | What converters do differently; engagement gaps |
| Content | Engagement score distribution; reading time; content types |
| Tracking health | Empty logs; setup next steps |
You can type free-form questions. Prefer specific, measurable asks (“Which form field abandons most?”) over vague ones (“How is the site doing?”).
How grounding works
- Your question is matched to aggregations Intently already computes (events, attribution summary, spend/ROAS, delivery rates).
- The answer cites those surfaces — model, lookback, channel, destination — rather than guessing.
- Optional date range on the Ask page scopes the analysis window.
- Threads and history live under Ask so you can reopen prior exchanges.
Launching Ask from Attribution or Experience can pass page context (cohort, channel, gap) so the first answer stays on that investigation.
What Ask needs from Tracking
| Question type | Turn on under Settings → Tracking |
|---|---|
| Attribution / ROAS | Snippet + conversions (and spend sync for ROAS asks) |
| Forms | Form vendor tracking (+ field metadata when available) |
| Content / engagement | Content Intelligence + sections for content context; Engagement Tracking under Ask depth for visitor engagement scores (scroll / active time; off by default) |
| Delivery | At least one destination configured and sending |
Thin capture → thin answers. Ask depth is optional and counts against your plan’s monthly events — see Ask depth.
Limits (today)
- No saving answers as dashboard widgets or scheduled digests
- No MCP write tools (pause/scale ads) — MCP is read-only; see MCP server
- Pause / scale on Attribution is a separate product action, not an Ask write-back
Practical checklist
- Confirm events in the Event log and conversions on Attribution
- Enable Content Intelligence + forms for form/content Ask; enable Engagement Tracking for visitor engagement score questions
- Import spend before asking ROAS questions (Ad spend & ROAS)
- Use starters first, then refine with a date range
Next
- Experience — on-site gaps Ask often cites
- Tracking — capture depth
- MCP server — same grounding in Cursor / Claude