01
Unified performance data
Shopify, Meta, Google, and Klaviyo normalized into one model. Revenue, spend, orders, campaigns, flows, and cohorts line up on the same dates and currency.
§0 AI-native reporting for ecommerce operators
Kreel connects Shopify, Meta Ads, Google Ads, and Klaviyo, normalizes the data, and gives your AI agent the context to analyze performance, explain what changed, and produce client-ready reports.
Run
/kreel:weekly-report demo-brand Reads
Shopify + Meta + Google + Klaviyo
Returns
Analysis, creative insight, reports, and next actions
Connects to
Works in
*via custom GPT until OpenAI ships MCP
§1 The problem
Your numbers live in Shopify, Meta Ads, Google Ads, and Klaviyo. To explain a single week, someone exports four dashboards, screenshots the charts, drops them in a spreadsheet, and reconciles the figures by hand before any thinking starts. Every report begins from zero.
Today · scattered sources
With Kreel
One AI-ready context
§2 What you get
Kreel gives your AI the operating context behind your store, already normalized and ready to reason with.
01
Shopify, Meta, Google, and Klaviyo normalized into one model. Revenue, spend, orders, campaigns, flows, and cohorts line up on the same dates and currency.
02
Data shaped for a language model: compact, labeled, consistent. Your agent reasons instead of parsing raw API dumps.
03
Creatives, campaigns, and keywords with the metrics to explain what's working, what's fatiguing, and what to brief next.
04
Battle-tested report and analysis skills you run in the AI you already use. Recurring reviews take one prompt.
§3 Workflows
Revenue, spend, blended efficiency, and what changed, with next actions.
Shopify · Meta · Google · Klaviyo
Top and fatiguing creatives by CTR, hook rate, and CPA, with what to brief next.
Meta · Google
Flow and campaign performance, AOV lift, and cohort retention.
Klaviyo · Shopify
Where the next budget should go by marginal efficiency across channels.
Meta · Google · Shopify
A plain-language monthly summary: results, drivers, and the plan.
All platforms
§4 Example output
Reports are one visible output of the data layer. Ask for the weekly view and your agent can return narrative takeaways, source metrics, and next actions from the same cross-platform context.
Example command
kreel run weekly-report --client demo-brand --range last_7d
Weekly report
Revenue
Orders
MER
Email revenue
Revenue rose while blended efficiency softened. Meta contributed the largest week-over-week swing, Klaviyo flows lifted AOV on the ad-push cohort, and Google stayed efficient but concentrated in brand search.
Source context
Shopify orders, Meta campaigns, Google campaigns, Klaviyo flows, customer cohorts.
§5 Creative
Every active creative with its spend, ROAS, revenue, CTR, and CPM, tagged by hook, format, audience, and product. Your agent reads the same view to explain what's driving results and what to brief next.
§6 Try it · live
Routed through a real agent against a demo workspace. The agent gets compact ecommerce context instead of raw dumps from separate tools.
— Demo Brand, last 7d
§7 The data layer
One API key, four platforms, every agent. We ingest through OAuth, keep the platform data synced in Kreel, normalise it across clients, and serve it to whatever you already use.
§8 Skills
Every Skill was battle-tested on real client work before it shipped. Run them in the agent you already use.
weekly-report ~2 hrs Full client report, ready to send.
meta-health ~30 min 7-day Meta Ads health check.
anomaly-detective ~1 hr Spot spend anomalies before your client does.
creative-brief ~45 min Auto-generated agency creative brief from performance.
crm-calendar-planner ~2 hrs Interactive email content calendar.
budget-advisor ~1 hr Where to shift spend this week.
ad-pack-builder ~1 hr Copy pack from a folder of creatives.
monthly-report ~3 hrs Tabbed HTML dashboard for client delivery.
§9 Safety
Kreel is an analysis and reporting layer first. At launch it reads your data to explain performance and draft reports. It does not edit campaigns, change Klaviyo flows, update Shopify products or discounts, or touch customer data. Connections use scoped, read-only OAuth you can revoke anytime.
§10 Why not just connect every MCP?
Pulling ecommerce performance through separate tools means asking Meta, Google, Shopify, and Klaviyo for each date range one by one. Kreel does that work in the data layer, then returns the compact answer your agent needs.
Typical MCP stack
meta.get_insights(last_7d)
meta.get_insights(last_30d)
google.get_campaigns(last_7d)
shopify.get_orders(last_7d)
klaviyo.get_flows(last_7d)
More tool calls, repeated date logic, platform-specific field names, and a bloated context window before the agent can reason.
Little room left for synthesis, recommendations, or a client-ready report.
Kreel
kreel.get_performance({
client: "demo-brand",
range: "last_7d",
include: ["shopify", "meta", "google", "klaviyo"]
})
More of the window stays available for analysis, narrative, and next actions.
Shopify orders, customer cohorts, ad spend, campaign performance, and Klaviyo flows arrive together, already shaped for an LLM.
§11 How it works
OAuth Shopify, Klaviyo, Meta, and Google in minutes. No passwords, read-only by default.
One key per workspace. Looks like kreel_live_… Scoped to that workspace only.
Claude Desktop (one-click extension), Claude.ai (connector URL), Claude Code (kreel auth login), or the CLI directly.
§12 For builders
Under the report layer is a compact schema for orders, customers, campaigns, flows, and cohorts. Your agent stops guessing at field names and starts answering questions.
{
"range": "2026-04-11..2026-04-17",
"workspace": "demo-brand",
"totals": {
"revenue": 84210.00,
"orders": 612,
"aov": 137.60,
"returning": 41.3
},
"channels": {
"direct": 38210.50,
"google_ads": 18044.20,
"meta_ads": 16892.10,
"klaviyo_flows": 10012.30,
"other": 1051
},
"top_products": [
{ "sku": "SER-01", "rev": 12044, "qty": 86 },
{ "sku": "CRM-02", "rev": 9872, "qty": 74 }
]
} §13 Who it's for
Kreel assumes you can read a P&L and a MER chart. It removes the gathering, not the judgment.
§14 Built on our own book
"We built Kreel for our own agency first. We run every client's weekly review through it before it ever ships to anyone else."
§15 Where it fits
| Kreel | Polar Analytics | Ads-only MCPs | Build it yourself | |
|---|---|---|---|---|
| Platforms | Shopify · Klaviyo · Meta · Google | All four + | Ads only | You build it |
| Primary surface | MCP-first | Dashboard-first | MCP | Your call |
| Skills library | 8 beta skills | No | No | No |
| Monthly cost | Free demo · €99–499 | €500+ | Varies | Dev time |
| Setup to first value | Minutes | Hours–days | Minutes | Weeks |
§16 Pricing
Plans for when your beta access opens. Pricing is set; billing starts when you go live on real data.
Solo operator · 1 store
Fractional · 2–3 brands
Multi-client agency
Beta access includes a demo workspace. Larger agencies get custom workspace limits, SSO, Slack support, and priority SLAs.
§17 Security
Never your passwords. Only scoped OAuth tokens you can revoke at any time.
Primary compute and database in the European Union. Transfers covered by SCCs.
Kreel reads to analyze and report. It does not edit campaigns, flows, products, discounts, or customer data at launch.
§18 FAQ
An AI-ready ecommerce context layer. It connects Shopify, Meta Ads, Google Ads, and Klaviyo, normalizes the data, and serves it to the AI you already use through an MCP server, a CLI, a Claude Desktop extension, and a Claude.ai connector.
Kreel is in private beta. Request beta access and we onboard operators and agencies directly.
No. Kreel is read-only at launch. It does not edit campaigns, change Klaviyo flows, update Shopify products or discounts, or touch customer data. Connections use scoped OAuth you can revoke anytime.
No. You connect those platforms to Kreel once, then your agent calls Kreel for the combined ecommerce context instead of juggling one tool per platform.
Yes. Kreel connects Google Ads alongside Shopify, Meta Ads, and Klaviyo, so reporting can include campaign, keyword, conversion, and ecommerce context in the same workflow.
No. For most users, that means pasting a connector URL into Claude Desktop or Claude.ai — three clicks.
Polar is a full dashboard and attribution suite. Kreel is the data layer your agent reads — a fraction of the price, with a curated Skills library.
OAuth-only, EU-hosted, read-only. See the Security page for full details.
Yes — the product is built around agencies managing a book of clients. Each client is fully isolated.
On the roadmap. We publish progress in the Changelog.
Kreel is currently opening private beta access for ecommerce operators and agencies who want to automate reporting, creative analysis, and recurring performance reviews.