CorpusIQ is now live in the ChatGPT app store.
Find CorpusIQ in ChatGPTConnector directory
CorpusIQ is now live in the ChatGPT app store.
Find CorpusIQ in ChatGPTConnector directory
Connect HubSpot, Google Ads, Meta Ads, GA4, Klaviyo, Slack, Gmail, and Drive through read-only external-source retrieval tools. Ask any question across every client account in plain language and get cited answers. No dashboards, no exports, no SQL.
Read-only access · 30-day free trial · Cancel anytime
Real questions that take an analyst an afternoon and CorpusIQ seconds.
HubSpot, Google Ads, Meta Ads, GA4, Klaviyo, Mailchimp, Slack, Gmail, Drive. CorpusIQ reads across the agency stack and answers per client, not per platform.
Ask if any client's project notes drifted from the signed SOW. The assistant pulls Drive and Slack and tells you which clients are running over scope, before write-off.
Cross-channel paid spend (Google + Meta) against revenue per client (HubSpot + invoiced amount). One question, one cited answer, no spreadsheet stitching.
Hours logged plus billable rate against retainer fee. Spot the underwater client before next month's invoice goes out.
An agency should not need a separate login for every client it manages. For Google Ads, connect one agency-controlled Google identity that sits above a manager account. CorpusIQ then reads the client accounts linked beneath it, including accounts sitting under a sub-manager.
Ask for one client by customer ID and CorpusIQ resolves the manager account that query needs. You do not manage that plumbing by hand.
Also called an MCC. It is a separate account built to sit above client advertiser accounts. An ordinary advertiser account does not turn into one.
Something like ads-reporting@youragency.com, held by the agency rather than one employee. It has to be a real user that can complete Google sign-in, not a group or a forwarding alias.
Each client advertiser account sits directly beneath the agency manager account, or beneath a linked sub-manager. A pending invitation is not an active link.
Google Ads roles inherit down the hierarchy. Read-only access is enough, and CorpusIQ exposes read-only reporting tools whatever the role says.
Clients keep their own access throughout. Linking an advertiser account to a manager account does not remove the client's own users, and a client administrator can unlink the relationship later. Your staff keep their personal Google users for day to day work in Google Ads. The connected identity is only the one CorpusIQ reports through.
Run a non-marketing services firm? See other vertical playbooks. Sell on Shopify? Start here for Shopify. Looking at this by function instead? See the operations team view.
Solo $29.95 per month, Team $109.95 per month. All 40+ connectors included. 30-day free trial. Cancel anytime.
Start free trialHubSpot, Google Ads, Meta Ads, Google Analytics 4, Klaviyo, Mailchimp, Slack, Gmail or Outlook, Google Drive or OneDrive or Dropbox, Google Sheets, Airtable, QuickBooks. 40+ live connectors in total; agencies typically wire 6 to 9.
Yes. Ask in plain language: 'show me Acme's spend vs revenue this quarter,' or 'summarize every Slack thread mentioning Beacon this week.' The assistant scopes to the client by name across every connected tool.
HubSpot reports stay inside HubSpot. CorpusIQ pulls from HubSpot plus Google Ads, Meta Ads, GA4, Klaviyo, Slack, and Gmail in the same question. Cross-tool answers without exports or BI tooling.
Yes. CorpusIQ uses read-only external-source retrieval per tool and respects whatever access the connected identity already has. For Google Ads the cleanest pattern is one agency-controlled identity sitting above a manager account, so client passwords never change hands.
No. For Google Ads, connect one agency-controlled Google identity that holds access at the manager account level. CorpusIQ discovers the client accounts linked beneath it, including accounts under a sub-manager, and works out which manager account a given query needs. Logging out and reconnecting per client is not how it is meant to work.
Two ways round it. Link the advertiser account into your manager hierarchy, or have the client grant your designated agency identity direct access to that one account. A CorpusIQ connection authenticates a single Google identity, so it only reads accounts that identity can reach. If neither option is open, contact support before you onboard that account, and never send passwords or OAuth codes.
Sign in to Google Ads as the connected identity and check the account is visible there. If it is missing in Google Ads it will be missing in CorpusIQ. Reconnecting OAuth does not repair an unaccepted manager link or a missing Google Ads role, so fix the hierarchy or the access in Google Ads first, then ask CorpusIQ to list accounts again.
No. It reads account, campaign, ad group, ad, keyword, search term, geographic, device, and demographic performance data. It does not create campaigns, change bids or budgets, pause ads, accept manager links, or change user permissions. Those stay in Google Ads.
Direct MCP does not retain raw customer files or full connector response payloads. Local AUDIT logs record raw query text and tool parameters plus bounded result summaries; the Azure Log Analytics workspace retains those logs for 30 days. Optional indexed search has a separate lifecycle. Authorized source context is sent to the selected AI client, whose plan and settings govern conversation handling.
30-day free trial. Cancel anytime.
Skills, cross-tool patterns, and connector setup pages most relevant to operators on this surface.