What the product is made of: Lia, Relay, the Media library, App Tools and the MCP. Jump to a feature and see the real screen.
Ask about your numbers in plain language and get the answer built from your live account. Ask for a change and Lia asks before she makes it: born paused, applied on your Yes, undoable.
Spend, leads, CPL, creatives, audiences, delivery. No exports, no stale dashboards.
The exact diff and estimated reach above the input, answered Yes, Yes to all or No. A launch can come as one plan instead.
Born paused, turning on is its own question, one-click undo, no delete in the write layer at all.
What GitHub did for code, Relay does for Meta traffic: every change is an event with an author, a diff and a thread. From Liaison, from Ads Manager, from Meta itself.
Every row says which tool made the change: Liaison, Ads Manager, or Meta.
Rollbacks are events too. The team sees the fix the same way it saw the mistake.
Projects list, tap into the feed, long-press a change for the menu.
Your uploads and the account's existing Meta images and videos, in one picker inside the chat. Build from a reference, swap the media, keep the structure that already converts.
The "in 3" chip means the file already runs in three ads. You see what is working before you reuse it.
Meta media needs no upload: Meta already holds the file. Video streams in chunks.
Images dedupe by content hash. The same file never lives twice.
Every Liaison screen as a standalone app: Overview, Ads, Creatives, Audience, Leads, plus Tasks, Canvas and Storage. The same screens Lia mounts next to her answers, gathered in one launcher.
Meta Ads through the official API with approved advanced access. The MCP gateway brings your ads to Claude and any MCP client: same ownership walls, same journal, same Yes before a change.