FeaturesAgent RevenueHow detection worksStrategiesPricingFor agenciesBlogSign inStart free
FOR AGENCIES

For agencies that build stores, and agencies that grow them

Dev agencies build and run client stores. AEO and GEO agencies work on how clients show up in AI answers. Tactical does a different job for each, so each has its own section, its own proof and its own pilot.

Dev agencies ↓AEO agencies ↓

01Dev agencies: agent visibility on every client store

For e-commerce and WooCommerce agencies that build and look after stores: what AI agents do on each client store, what they bought, and a record of each agent order you can hand the client.

  • The agents on every client store: AI crawlers, verified against published IP ranges where a server-side install can check (the WooCommerce plugin, the Cloudflare connection or the Node middleware); agent browsers scored on behaviour, including the ones that never name themselves; and the visitors AI assistants send.
  • Agent orders, attributed: each order labeled an agent order, an AI-referred order or neither, including agent-checkout orders pixels never see. Agent orders and AI-referred orders are kept apart. Order data comes from WooCommerce today.
  • An evidence pack for every agent order: a PDF and a JSON record of the order, the session before it, the agent’s declared identity and the record’s own limitations, with no buyer name, email, address, IP or payment details in it. Something specific to hand a client when an agent’s purchase is disputed, charged back or returned. What’s in it.
  • Every client store in one account: add each store and switch between them. Each store has its own dashboard; there’s no combined cross-store report yet.
  • Installs you already know: the plugin from WordPress.org, one script tag, a one-paste Cloudflare connection, or middleware from npm.
  • Agent rules for client stores: drop protection and agent-checkout rules, coming. Join the Observe beta to try them on a client store first.

Coverage by platform

AI crawlers don’t run JavaScript, so seeing them needs a server-side install; order data comes from the platform, where it sends it. Every gap is footnoted:

InstallAI crawlersAgent browsersAgent orders
Custom / headless (snippet)
One script tag in the page head
—1✓—2
Custom + Node middleware
@tactical-app/agent-analytics on npm, plus the snippet
✓✓—2
Any site behind Cloudflare
One-paste Cloudflare connection, plus the snippet
✓✓—3
WooCommerce
Plugin from WordPress.org
✓✓✓4
Shopify
App from the Shopify App Store
—5✓—6
Shopify behind Cloudflare
The Shopify app, plus a Cloudflare connection
✓✓—7
  1. Crawlers don't run JavaScript. Add the middleware or a Cloudflare connection.
  2. A custom site has no order feed to Tactical yet.
  3. Orders come from the platform, not from Cloudflare; see your platform's row.
  4. From the order webhooks the plugin registers.
  5. Shopify gives apps no server-side request access, for every vendor. Put the store behind Cloudflare for crawlers.
  6. Needs Shopify order access, which the app doesn't have yet. Shopify's own Agentic report shows orders per AI channel.
  7. Needs Shopify order access, which the app doesn't have yet.

Proof: five ways stores handle AI agents, scored honestly · Who’s liable when an agent buys?

Put agent visibility on five client stores, free for 90 days.
Book a dev-agency pilotSee the five strategies

02AEO agencies: first-party proof for AI search retainers

For AEO and GEO agencies. Measurement only: what AI crawlers, agents and AI-referred visitors did on a client’s store, in a report with your agency’s name on it.

  • Co-branded AI Search Report: the crawler → agent → AI-referral → order funnel, top AI-read products and referral sources, exportable to PDF with your agency’s name and logo in the header (we set the branding up with you). Built for client QBRs.
  • Agent orders beside AI-referred revenue: agent sessions and agent orders are counted apart from AI-referred visits and the orders those people placed, and the two are never added together.
  • Ground-truth ROI: first-party, on-site numbers you can put in a retainer deck, for example how many visits AI assistants referred this month and what those visitors ordered.
  • Numbers that under-claim: crawler hits are marked verified only when the IP matches the operator’s published range, and orders from AI-referred visitors are attributed last-touch and labeled estimated.
  • Every client store in one account, one switch away. What each store can report depends on its platform: coverage by platform.

Complements your citation tools, doesn’t replace them. Citation trackers work from the outside: they check whether a brand is cited in AI answers. Tactical is first-party and on-site: it closes the loop to what happened on the store and to orders. Run both. Citation tracking tells you you’re in the answer; Tactical tells you what the answer sent you.

Proof: why Google Analytics can’t see this · how agent orders are attributed

Run a co-branded pilot on five client stores, free for 90 days.
Book an AEO-agency pilotWhy GA can’t see this

03Pilot and pricing, for either kind of agency

  • Free Command plan on up to 5 client stores for 90 days; Command includes the co-branded report.
  • About 10 minutes to install per store (WordPress plugin or one script tag). First store live on the call.
  • One 30-minute feedback call at day 30. That’s the whole commitment.
  • If it doesn’t earn its place with your clients, uninstall, and tell us why.
PlanWhat’s includedPrice
Agency bundleUp to 10 client stores · co-branded reports · multi-store view · direct line to the founderContact
Per-store à la carteStandard Scout / Radar / Command tiers, per storePublic pricing

Before the call: how detection works, and what it can’t tell you.

[email protected]
How detection worksDrop WatchAgent revenuePricingStrategies comparedPerformancePrivacyTerms