Connector.wtf
UnclaimedConnect your ad platforms and e-commerce data to AI for instant, read-only insights.
Visit WebsiteFreeVisit Website
TL;DR - Connector.wtf
- Connects Google Ads, Meta Ads, LinkedIn Ads, and WooCommerce to AI assistants.
- Provides read-only insights into ad performance, wasted spend, and e-commerce data.
- Enables natural language queries for data analysis without spreadsheets.
Pricing: Free forever
Best for: Individuals & startups
Pros & Cons
Pros
- Simplifies data analysis by using natural language queries with AI.
- Consolidates insights from multiple ad platforms and e-commerce into one AI interface.
- Ensures data security with read-only access and encrypted storage.
- Eliminates the need for manual data exports and spreadsheet manipulation.
- Free to use, making advanced analytics accessible.
Cons
- Relies on AI assistant capabilities for interpretation and response quality.
- Meta Ads write capabilities require explicit approval, adding a step for changes.
- Some connectors like GA4 and HubSpot are listed as 'coming soon', limiting current scope.
Key Features
Google Ads MCP for performance analysis and optimizationMeta Ads MCP for reporting, ad creation/editing (with approval), and catalog managementLinkedIn Ads MCP for B2B-grade reporting and performance analysisWooCommerce MCP for revenue, orders, product, and customer insightsRead-only data access for all connected platformsNatural language querying with ChatGPT, Claude, and CursorEncrypted at rest data storageSupport for multiple WooCommerce stores
Pricing
Free
Connector.wtf is completely free to use with no hidden costs.
What is Connector.wtf?
Connector.wtf provides read-only Managed Connector Protocols (MCPs) that integrate various advertising platforms (Google Ads, Meta Ads, LinkedIn Ads) and e-commerce platforms (WooCommerce) directly with AI assistants like ChatGPT and Claude. This allows users to query their marketing and sales data using natural language, gaining insights into performance, identifying wasted spend, and comparing periods without manual data extraction or spreadsheet analysis.
The platform is designed for marketers, e-commerce managers, and analysts who want to leverage AI for quick, actionable insights from their ad campaigns and store performance. It emphasizes a read-only approach, ensuring that AI cannot make changes to campaigns or data, providing a secure way to analyze complex data sets and improve decision-making.
Reviews
Be the first to review Connector.wtf
Your take helps the next buyer. Verified LinkedIn reviewers get a badge.
Write a reviewExplore More
Connector.wtf FAQ
How does Connector.wtf ensure that AI cannot make unauthorized changes to my ad campaigns or e-commerce store?
Connector.wtf operates strictly with read-only API tokens for all connected platforms. For Google Ads and LinkedIn Ads, the OAuth scope is read-only, preventing any bid changes or campaign pauses. For WooCommerce, it requires API keys with only 'Read' permissions. Even for Meta Ads, where some write capabilities are available, any action that changes something requires explicit approval from the user within the AI agent.
Can I connect multiple WooCommerce stores to a single Connector.wtf account, and how does the AI differentiate between them?
Yes, you can connect as many WooCommerce stores as you want. The WooCommerce MCP exposes a
list_stores tool, allowing the AI to identify and select the correct store for your queries, or you can explicitly name the store in your prompt.What is the 'run_gaql' tool for Google Ads, and who is it intended for?
The
run_gaql tool allows advanced users to write and execute raw Google Ads Query Language (GAQL) directly through the AI assistant. This is intended for users who need highly specific or complex data queries that might not be covered by the standard pre-defined tools, providing maximum flexibility for data extraction.How does Connector.wtf handle the security and storage of my API keys and tokens?
For Google and LinkedIn Ads, Connector.wtf obtains a read-only OAuth token. For WooCommerce, it requires you to paste a Read API key. All sensitive credentials, including API keys, are verified, then AES-256-GCM encrypted at rest and decrypted only within server functions when an authorized request is made. They are never exposed to the browser after submission.
Source: connector.wtf