AI
AI Analyst
A check for material changes in leads, revenue, spend, CPL, ROAS and match rate, explained in plain language, and a chat about your reports.
Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.
Switching it on
- Off by default. Only the workspace owner can turn the AI agents on (AI Analyst page). They need the top plan, and the AI model key on OrcLink's server.
- HIPAA mode: they cannot be turned on until the owner records a BAA with the AI vendor (Anthropic).
The check for changes
- A fixed rule, no AI: the last 7 full UTC days against the 7 before, and the last 28 against the 28 before, for the workspace, each channel and the top 50 campaigns. A change counts when both sides have enough volume (at least 10 credited conversions, or 50 of cost), it is 25% or more, and it passes a noise test.
- It runs once a day while the scheduled jobs ai-analyst and jobs run (your OrcLink operator schedules them). With the agents on, the model explains the top changes.
What leaves for the AI model
- Aggregate tables only: rows by channel, campaign, campaign group or keyword, with counts and money per currency (never summed across currencies), at most 200 rows per table.
- A group with fewer than 5 outcomes is folded into one "Other" row. A line or total resting on 1 to 4 outcomes, or whose difference with the lines shown would, is sent without numbers.
- Never a person-level row, an outcome, click, session or visitor id, a hash, a page path or contact data. A name that holds an email address or phone number is hidden.
- HIPAA mode: generic stage labels, and campaign, group and keyword names only when the owner turned on "Include campaign names in data out" (else rows by channel only).
- Every request is checked before it is sent: if anything in it looks like an email address, a phone number or a 64-character hash, nothing is sent.
- Each call to the model is logged in the audit log (vendor, purpose, size, row count; never the content).
The number check
Every number in an answer must appear in the tables the model was given. An answer that fails gets one retry; if it fails again, the answer is not shown and the tables are. The tables are shown under every answer.
Known limit: numbers from two different tables (a channel total and campaign rows, two overlapping date ranges) can still be set side by side. The model is told never to compute numbers of its own, but this is not enforced beyond the number check.
Limits and retention
- At most 50 model calls per workspace per UTC day, and 20 chat questions per person per hour.
- A question that holds an email address, a phone number or a hash is refused before it is stored or sent.
- Chat is kept 30 days after each message; findings 90 days.
- Credited numbers are OrcLink attribution: a claim. Modelled models are never used here.