Connect Your Data Sources to Cogny Cloud

Cogny has no data of its own. Every insight, report and ticket is built from what you connect here. This page covers the order to connect in, what each source unlocks, and the settings that decide how autonomous the agent may be with each tool.

Where

Settings → Data & Integrations → MCPs For Cogny. Each integration is an MCP server (the protocol Cogny and AI agents use to call tools). The page has four parts:

Cogny Managed MCPs, grouped by category. This is the catalog: Ads, SEO & search, Analytics, E-commerce, CRM, Email & marketing, CMS & content, Dev & build tools, Community, Data & infrastructure, Billing & payments. At the top are the built-in tools you can toggle: image generation and media analysis, Brave web search, and Ahrefs domain rating.
Custom APIs for internal systems.
Wish for an MCP: paste a link to any tool's API docs and Cogny researches it. If it can be built unattended, it is queued for the coding agent and you hear back within about a minute.
MCP Servers: add any standard remote MCP server by URL, for tools Cogny does not ship.

Connections are either OAuth (click, sign in, approve) or an API key you paste from the tool's own settings. A handful must be connected in the dashboard rather than by an agent: Shopify, X Ads and Apple Search Ads.

After connecting a server, open it and use Discover Tools so Cogny reads the tool list. Until then the agent cannot see what the integration can do.

The order that works

Connect in this order. Stop when you run out of tools you actually use; do not connect platforms you do not run.

1. Google Search Console

The most important source, and free. It is the organic search-term feed behind the SEO and content loop: which queries you rank for, on which pages, with what click-through rate. Title and description rewrites, content gaps, cannibalisation and the Search Intent Playbook all read from it. You do not need a paid SEO suite. Search Console plus Bing Webmaster Tools cover what the agent needs.

2. Google Analytics 4 and Google Tag Manager

GA4 is the funnel: sessions, landing pages, events and conversions. Tag Manager lets tickets fix tracking without a developer. Cogny does no tracking of its own; it reads yours. If GA4 does not record your lead or purchase event, connect it anyway, and make fixing that the first ticket.

For deeper analysis, link GA4 to your workspace's BigQuery project. In GA4 go to Admin → BigQuery Links and add the project shown under Settings → Data & Integrations → Data Sources. Use the free direct link. Two things to know:

Export data starts flowing 48 to 72 hours after linking and does not backfill history. Data accrues from the day you link.
Metric definitions that query BigQuery cannot be built until data has landed.

3. Google Ads

Connect it even if you spend little or nothing. Historic search terms show what people typed before converting, and Google Ads is the fastest way to test a new keyword. Connecting it with Search Console unlocks the Search Intent Playbook, which finds converting paid terms with no matching organic page and creates the page.

4. Bing Webmaster Tools

Free, and worth five minutes. It is the only source that reports AI citations inside a search engine (Copilot and, through the Microsoft partnership, a proxy for other assistants). Verify the domain, submit the sitemap. Provisioning takes about 48 hours.

5. Your site

The agent executes content and page tickets against your site, so this connection decides how much it can ship.

A code repository on GitHub (Next.js or similar) gives the most. Connect it under Settings → Cogny Code → Coding Agent. Tickets become pull requests with preview deployments. See the coding agent.
Shopify works well: the API covers products, guides, metadata and blog posts.
WordPress works for drafts. The API does not allow everything, so posts land as drafts you publish, and some schema fixes are manual.
Webflow, Framer, Sanity, Ghost, Contentful connect with a key and support drafting and, in most cases, publishing through the CMS.
If your CMS is locked down, a common pattern is to route one path (for example /blog) to a separate code project the agent can fully control, while the rest of the site stays where it is.

Meta Ads, LinkedIn Ads, TikTok Ads, Snapchat Ads, X Ads, Bing Ads, OpenAI Ads and Apple Search Ads. Connect the ones with spend. Each unlocks an optimisation audit template and campaign execution. Cogny uses its own developer access with each platform; every write is approval-gated and logged. Organic social posting is not available through these connections, because the platforms do not allow the same app to do both paid and organic.

7. E-commerce, CRM, email, revenue

E-commerce (Shopify, WooCommerce, Wix, Abicart, Litium): revenue and product data, and the E-commerce Performance Signals template.
CRM (HubSpot, Upsales): lead quality and pipeline, and the B2B Sales Pipeline template. Matching site events to CRM outcomes works by timestamp, and better if you pass the same ID through both.
Email (Klaviyo, Mailchimp, Brevo, MailerLite, Rule, Get a Newsletter, Drip, Braze, Symplify): the Email Marketing Optimization template.
Revenue (Stripe, RevenueCat, Fortnox): subscription and profit signals.
Community and support (Discord, Crisp): conversation mining for objections and content ideas.

Tool permissions: how autonomous each integration may be

Every connected server exposes a list of tools. For each tool you choose one of three settings:

Setting	Meaning	Default for
Auto-approve	The agent may call it without asking	Read tools: list, get, search, run report
Ask first	The action becomes a ticket or an approval prompt	Write tools: budgets, bids, status changes, campaign creation, sitemap changes
Blocked	The agent never sees the tool	Anything you want off the table

Keep the defaults at first. Loosen specific write tools later, once you have seen twenty tickets and know what you would have approved anyway. The YOLO settings build on these permissions: a ticket can only auto-execute if every tool it uses is read-only or explicitly granted.

All writes through any integration are recorded in the MCP write ledger, under Settings → Automation, so you can audit what changed and when.

Bring your own data

Settings → Data & Integrations → Bring Your Own Data creates a dataset and a storage bucket in your workspace's BigQuery project and lets you upload CSV, JSON or Parquet files as tables. Use it for order exports, CRM extracts, lifetime-value lists or offline conversions. Exclude sensitive personal fields such as national ID numbers and phone numbers before uploading. Anything in the project is available to the agents in chat and reports.

Verify the setup

Run the Connection & Setup Verification template once from the Reports page after connecting. It probes every connected source and reports what is reachable, what returns data and what looks misconfigured. Run it again whenever you add or change a source.

Common problems

"Unverified app" or blocked OAuth. Google Workspace admin policy. Click through the advanced link, or have your admin allow the app. For Meta, invite Cogny to your Business Manager.
BigQuery link fails right after granting access. Cloud IAM permissions take a few minutes to propagate. Retry shortly.
An old BigQuery link on the GA4 property. Delete it and re-point it at the workspace project.
The integration is connected but the agent says it has no tools. Open the server and click Discover Tools.
Reports look empty on day one. Expected. Data accrues from the connection date; BigQuery exports start after two to three days.
Duplicate or legacy conversion tags inflate conversions and can make the agent over-invest. The Data & Tracking Quality template finds these; fix them before scaling paid.