Connect Henneth to the stack you already run.

Brings AI-agent (bot) traffic into Agent Analytics. Two ways to connect, run either or both. Neither sends human visitor traffic or request bodies to Henneth.

export default {
  async fetch(request, env, ctx) {
    const ua = request.headers.get("user-agent") || "";
    const bot = ["GPTBot", "ClaudeBot", "PerplexityBot", "Google-Extended"].find(b => ua.includes(b));
    if (!bot) return fetch(request);            // human traffic: nothing is sent
    const response = await fetch(request);
    ctx.waitUntil(fetch(HENNETH_WEBHOOK_URL, {
      method: "POST",
      headers: { "X-API-Key": HENNETH_API_KEY, "Content-Type": "application/json" },
      body: JSON.stringify({ bot_name: bot, path: new URL(request.url).pathname, method: request.method,
        status: response.status, user_agent: ua, ip: request.headers.get("cf-connecting-ip"),
        country: request.headers.get("cf-ipcountry"), timestamp: new Date().toISOString() }),
    }));
    return response;
  },
};

For enterprise customers on Akamai, Henneth ingests AI-agent traffic through DataStream 2. Akamai pushes CDN request logs to Henneth over HTTPS; Henneth keeps only known bots. Your property configuration and content are not touched.

Connect a Google account to put Playbooks to work across Sheets, Docs, Gmail, Google Analytics 4 and Search Console. Write Lens results into a Sheet, draft a report in Docs, email a summary, or pull GA4 data into a workflow. The Impact page reads revenue through its own Google Analytics connection, listed separately on the Integrations page.

# requested Google OAuth scopes
userinfo.email  userinfo.profile
spreadsheets                # Sheets read / write
documents                   # Docs read / write
gmail.send  gmail.readonly  # send + read email
drive.metadata.readonly     # list file names for the picker only
analytics.readonly  webmasters.readonly   # GA4 + Search Console, read-only

Two ways to connect. Sign in to Slack and pick the channels Alert Center posts to, or paste an incoming webhook for a Playbook step to post through. Either way Henneth only posts.

A Playbook step posts an Adaptive Card to a Power Automate or Azure Logic Apps webhook you control.

Connect your Shopify store so the content and findings Henneth already produces land in the store instead of in an export. Every write is a draft you approve first, and nothing goes live on the storefront without you.

Technical findings such as a robots.txt rule blocking GPTBot, a missing sitemap or a schema error need a developer. Connect Jira and Henneth opens them as issues in your project, then follows whether they were closed.

Read-only. Henneth reads what Search Console knows about a page and sets it beside its own findings: a page losing citations in AI answers, and whether Google is showing it less too.

Read-only. Henneth reads your campaign results and real search terms, and sets them against the prompts it tracks: the queries where you are missing from AI answers, and what you pay for them on Google today.

For stores that export Google Analytics 4 or Merchant Center to BigQuery. Henneth runs its own saved, parameterised queries over your dataset: AI-sourced sessions that became orders, and conversion per product. You connect the dataset, nothing more.