The terms that decide whether a tool can actually do what you need, defined plainly. Each one says what Growomat does about it and links to the surface that does it, because a definition with nothing behind it is a description of somebody else's product.
An open protocol that lets an assistant call an external service's functions directly, instead of you copying data between two windows. A server exposes typed tools; a client connects to it and can then read and act through them. Growomat runs a hosted MCP server covering every ad platform on your account, over OAuth, with each tool marked read-only or destructive so a client can tell a report from a deletion before it runs one.
The MCP server, the platforms it covers, and how to connect itSending a conversion back to the ad platform after it happened somewhere the platform could not observe: a deal closed in a CRM, a subscription that survived a trial, a refund that reversed a sale. Without it the platform optimises on the last thing it saw, which is usually a form submission rather than money. Growomat imports these against the click that produced them, so a campaign's reported return is built from what actually happened rather than from what was countable at the time.
Conversion tracking and the import pathA Google Ads feature that matches a conversion using hashed first-party details when the browser no longer carries a usable click identifier, recovering conversions that would otherwise go unattributed. Growomat exposes the leads variant, per conversion action. It is a Google Ads feature and not a general one, so it is worth checking against the platforms you actually run.
What Growomat does on Google AdsHow long after a click a conversion still counts as caused by it. Set it short and long consideration cycles look unprofitable; set it long and you credit campaigns for sales they only brushed against. Each platform enforces its own limits, and Growomat clamps a requested window to what the platform will actually accept per conversion type rather than silently sending a value that gets rejected or reinterpreted.
Conversion actions and their settingsSpending a monthly budget evenly rather than exhausting it in the first fortnight. Growomat compares month-to-date spend against your cap every few hours and adjusts daily budgets proportionally to stay on track. It is advisory arithmetic about money not yet spent, which is a different job from the brake below.
Autopilot, and what it is allowed to changeHow large a step a bid moves in one adjustment, as a percentage of the current bid, rather than how often it moves. A high velocity reacts quickly and overshoots; a low one is stable and slow to find a price. Growomat applies the step in either direction, refuses to raise a bid past your maximum cost per click, and will not lower one below a floor.
Autopilot, and what it is allowed to changeA reactive stop based on money already spent, as opposed to a cap that refuses a change which would spend too much. Growomat compares real month-to-date spend against the limit you set and pauses when it is past it. Preventive caps and advisory pacing both look forward; this one looks at what left the account.
Autopilot guardrailsA machine-readable declaration of what one ad platform's adapter can and cannot do, versioned alongside the code. It matters because the platforms genuinely differ, and the alternative to declaring the differences is discovering them during an export. Growomat validates a campaign against the manifest of the platform you are sending it to, so an unsupported setting is reported before anything is sent rather than after.
How a campaign reaches a platformAn edit that exists in Growomat and has not been sent anywhere. Campaigns are created and edited locally and stay paused there; pushing them to a live ad account is a separate, explicit step. This is what makes it safe to let an assistant draft and revise: a conversation can change a great deal and still spend nothing until you push it.
The path from draft to live