Documentation
Integrations overview
What connects, what each connection unlocks, and what works with no connection at all.
Connections use your own accounts through a one-time OAuth grant. We never post, send or write from a shared Ansengine account.
| Connect | Unlocks |
|---|---|
| Google Search Console | Search wins, prompt seeding from real queries, sitemap and URL tools. |
| Google Analytics 4 | AI referral sessions and conversions, revenue by page. |
| WordPress or Webflow | Export drafts to your CMS, and publish live behind the two-click confirm. |
| Gmail | Send outreach pitches from your own mailbox, so the From is you. |
| Reddit or LinkedIn | Place approved answers from your own or your client's account. |
| HubSpot or Salesforce | Push leads with their AI-source evidence attached. |
| Slack | Drop and lead alerts where your team already works. |
| Zapier, Make, Google Sheets | Fan events and exports anywhere else. |
Works with a domain and nothing else
Measurement, the retrieval view on consumer ChatGPT, the ranked fix queue, the client report link and receipts all work with no connection at all. Connections add the acting and the attribution, not the measuring.
AI traffic and crawler logs
First party: which AI crawlers and agents read which pages, how sure we are who each one was (signed, IP, user agent only or inferred), and which AI assistants send people back. It reads your own request logs, so it needs one connection: a log drain from your hosting platform or a small collector in front of your site. Vercel, Cloudflare, Netlify, AWS CloudFront, Fastly, Akamai, Google Cloud, WordPress and Kinsta each have a guide, Next.js and Node get a middleware, and anything else posts to the REST endpoint. See the AI traffic page.