Loops vs Mailchimp
Loops wins · 25–7 (23 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to LoopsLoops has a live, probe-confirmed llms.txt (loops-probe-1) with dedicated agent-oriented docs at /agents and /agents/api, plus an OpenAPI spec (loops-probe-3) and MCP server for agent connectivity (loops-docs-6, loops-probe-4). Missing for 10: independent hands-on confirmation that an agent successfully consumes llms.txt end-to-end rather than just server availability.
- [probe] “PROBE llms.txt: HTTP 200 at https://loops.so/llms.txt # Loops > Loops is an email platform for software companies. Send transactional and m…”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
A direct probe confirms Mailchimp serves an llms.txt file at the expected URL returning HTTP 200 with structured content summarizing the site, which is exactly what this story asks for. However, there's no evidence of broader agent-oriented documentation beyond this single file, nor independent corroboration of its usefulness or completeness. Missing for 10: evidence of dedicated agent/AI-native docs beyond llms.txt, third-party confirmation of quality/usefulness of the file, and any first-party announcement of this feature.
- [probe] “PROBE llms.txt: HTTP 200 at https://mailchimp.com/llms.txt # Mailchimp - Complete Web Content Analysis > Comprehensive analysis and documen…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to LoopsLoops exposes a REST API with Bearer-token auth, an OpenAPI spec, and a CLI for terminal-based contact/event/email management, which supports scripted/CI usage. However, evidence doesn't explicitly confirm a headless automation workflow (e.g., CI pipeline examples, non-interactive auth for automation, or documented CI recipes) beyond API/CLI existence. Missing for 10: explicit CI/CD examples or automation-pipeline documentation, evidence of non-interactive/service-account auth flow, and independent confirmation of headless use in production automation.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Manage contacts, send events, and test transactional email from your terminal”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimp exposes REST APIs (Marketing API, Transactional/Mandrill API and SMTP) that could in principle be called headlessly from scripts or CI pipelines to create contacts, send campaigns, or send transactional messages (mailchimp-docs-1,2,4,5,6). However there is no first-party guidance on CI/automation workflows, official SDKs, or CLI tooling, and community reports describe accounts being auto-banned or automation silently shut off (e.g., devtools-triggered blocks and Mandrill sending disabled without notice) which undercuts reliable unattended/headless use (mailchimp-comm-4,5,9,11). missing for 10: documented CI/headless automation examples, official CLI/SDK support, evidence of stable unattended operation without account/service suspension.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Send a new SMS message through Mandrill”
- [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
- [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
- [community] “MailChimp blacklists your IP if you open the browser's dev tools; as a developer who often has devtools open, I get banned from Mailchimp fo…”
- [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to LoopsLoops documents an official MCP server ('Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.') with a dedicated docs page, backed by a first-party API and CLI/skills for agent integration. Missing for 10: independent/hands-on verification of the MCP server working end-to-end and more detail on setup/auth for MCP specifically.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
Mailchimpnone0/10No evidence of an official MCP server for Mailchimp; only Marketing/Transactional REST APIs and an llms.txt file are documented, none of which constitute an MCP server. missing for 10: any mention of MCP protocol support, an official MCP server endpoint, or agent-connection tooling.
ai-native userUse an official CLI
weight 2 · round to LoopsLoops documents an official CLI ('Manage contacts, send events, and test transactional email from your terminal' and 'Install the CLI and skills with one command so your coding agent can use Loops for you'), explicitly positioned for AI-native/agentic workflows. Missing for 10: independent hands-on verification of the CLI's functionality and no detailed command reference in the evidence pack.
- [claimed-docs] “Manage contacts, send events, and test transactional email from your terminal”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
Mailchimpnone0/10Evidence pack only shows Mailchimp's REST APIs (Marketing, Transactional, Commerce) and an llms.txt file; there is no mention of an official CLI tool for AI-native workflows. missing for 10: existence of any official CLI, documentation of CLI installation/usage, evidence of AI-native tooling built on a CLI.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Mailchimp Open Commerce (formerly Reaction Commerce) is an open source, API-first, modular commerce stack made for technical, growth-minded …”
ai-native userDrive the product through a documented public API
weight 3 · round to LoopsLoops provides a documented public REST API with authentication (Bearer token), endpoints for events, contacts, campaigns, and email sending, plus an OpenAPI spec (confirmed live at /openapi.json) and SDKs/CLI for programmatic access. This clearly enables an AI-native user to drive the product entirely via API. Missing for 10: independent third-party developer corroboration of API robustness/versioning in practice beyond founder claims.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Add Loops to your application in minutes with our SDKs.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
Mailchimp exposes well-documented REST APIs (Marketing API, Transactional/Mandrill API, Commerce API) with concrete endpoint-level documentation (contacts, campaigns, SMS, routes) suitable for programmatic/AI-driven control. Missing for 10: independent third-party corroboration of API robustness/rate limits for automated agent use, and no evidence of official SDKs or AI-specific tooling beyond raw REST docs.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Send a new SMS message through Mandrill”
- [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnLoopsnone0/10Evidence shows a single Bearer-token API key auth model with no mention of scoped, restricted-permission, or per-agent credentials — only a full-access API key pattern is documented across docs, MCP, and CLI. No evidence of least-privilege or scoped token issuance.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpnone0/10No evidence of scoped or least-privilege API key/credential issuance for AI agents; Mailchimp docs only describe standard API endpoints for campaigns, contacts, and transactional email with no mention of granular permission scopes or agent-specific credential management.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a new SMS message through Mandrill”
ai-native userBuild against official SDKs
weight 2 · round to LoopsLoops documents official SDKs plus a REST API with Bearer auth, an OpenAPI spec, and a CLI/skills installer for coding agents, indicating strong AI-native SDK support beyond just docs. missing for 10: independent hands-on developer confirmation of SDK reliability/coverage across languages, and no explicit list of supported languages beyond generic 'SDKs' mention.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “Add Loops to your application in minutes with our SDKs.”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpnone0/10Evidence shows Mailchimp's Marketing and Transactional REST APIs and endpoint documentation, but nowhere does it mention official client SDKs/libraries for building against these APIs. Missing for 10: any mention of official SDKs in specific languages, SDK repos, or versioned client libraries.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a new SMS message through Mandrill”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnLoopsnone0/10Evidence shows Loops lets users send events INTO Loops (POST /events/send) and use APIs/MCP/CLI to manage contacts and campaigns, but there is no mention of Loops emitting outbound webhooks that a user's system could subscribe to for platform events (e.g., opens, bounces, unsubscribes). Missing for 10: any documentation of a webhook subscription/callback mechanism, webhook payload schema, or webhook management endpoint.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpnone0/10No evidence pack item mentions webhooks or event subscription mechanisms for Mailchimp; only API endpoints for campaigns, contacts, and transactional sending are documented. Absence of evidence for this applicable API capability yields 'none'. missing for 10: webhook documentation, event subscription setup, webhook payload/event types.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to MailchimpLoopsnone0/10Loops documents analytics/segmentation (loops-docs-16), campaign drafting via API, and an email 'Guardian' check (loops-docs-19), but none of this evidence describes AI-generated insights or suggestions derived from a customer's data (e.g., predictive recommendations, anomaly detection, or AI-surfaced trends). The agent/API/MCP features are about enabling external agents to act on Loops, not the product itself surfacing AI insights.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [claimed-docs] “Run Guardian checks on an email message”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
Mailchimp's marketing pages list 'Predictive Segmentation', 'Generative AI features', and 'Actionable insights into audience growth and conversion funnels', suggesting some AI-driven analytics/suggestions exist inside the product, but these are thin pricing-page bullet points with no detailed documentation of how insights are generated or surfaced. Missing for 10: first-party docs explaining the AI insight/suggestion features in depth, independent/hands-on evidence confirming these work as described, and concrete examples of generated insights.
- [claimed-docs] “Multivariate and A/B Testing”
- [claimed-docs] “Predictive Segmentation”
- [claimed-docs] “Generative AI features”
- [claimed-docs] “Actionable insights into audience growth and conversion funnels”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to LoopsLoops supports event-triggered workflows (POST /events/send triggers workflows) and lifecycle automations (onboarding, activation, upgrade, winback emails) that are 'set up once' and run autonomously over time, which is the core of background automation for an email/lifecycle platform. Missing for 10: detailed documentation of workflow logic (branching, delays, conditions), and independent/hands-on corroboration that these automations reliably run unattended long-term.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
Evidence shows only that RSS campaigns send on a schedule and that the Marketing/Transactional APIs allow event-driven, API-triggered messages, which implies some autonomous background behavior, but there is no direct documentation of Mailchimp's automation/journey-builder feature or AI-native automation setup. Missing for 10: explicit documentation of the Customer Journey/automation builder, evidence of AI-driven or agent-configurable automation setup, and independent confirmation that automations run reliably unattended.
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to MailchimpLoopsnone0/10Loops' 'agents' materials describe APIs/MCP/CLI/skills that let external coding agents (Claude, Cursor, etc.) act on Loops on the user's behalf — this is Loops being consumed by an agent, not a built-in AI assistant living inside the Loops product that a user delegates tasks to. No evidence of an in-app assistant (e.g., an AI chat/copilot embedded in the Loops dashboard) exists in the pack.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
The pricing page lists 'Generative AI features' as an included capability, suggesting some AI assistance exists, but there is no documentation describing a built-in assistant that can be delegated tasks (e.g., autonomously drafting/sending campaigns, managing audiences) rather than just generating content snippets. missing for 10: concrete docs on an AI assistant's task scope, autonomy/delegation workflow, and independent/hands-on confirmation it functions as an agent rather than a content-suggestion tool.
- [claimed-docs] “Generative AI features”
ai-native userOperate the product with natural-language commands
weight 2 · round to LoopsLoops provides an MCP server and CLI/skills that let an AI agent operate Loops via natural-language-driven tool calls (create contacts, send events, draft campaigns, run Guardian checks) rather than requiring manual API scripting, which supports agentic/natural-language operation. However, the evidence is all vendor docs describing agent-facing surfaces (MCP, CLI, API) rather than a chat/NL command interface for end-users themselves, and there's no independent/hands-on confirmation of how well natural-language control actually works. Missing for 10: independent verification of natural-language command execution, evidence of an end-user-facing NL/chat interface (not just agent APIs/MCP), and confirmation of reliability/quality of agent-driven actions in practice.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Install the CLI and skills with one command so your coding agent can use Loops for you.”
- [claimed-docs] “Run Guardian checks on an email message”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
Mailchimpnone0/10Evidence shows only traditional REST/API endpoints and generic 'Generative AI features' mention, with no natural-language command interface, chat/agent UI, or NL-to-action capability documented. No evidence of an AI assistant that lets users operate Mailchimp via conversational commands.
- [claimed-docs] “Generative AI features”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to LoopsLoops documents API endpoints (contacts, events, Guardian checks) and exposes a valid openapi.json spec, suggesting a structured API reference exists, but there's no evidence of an interactive 'try it now' console or runnable code examples within the docs themselves. Missing for 10: explicit interactive/try-it API console, runnable code snippets in docs, independent confirmation of the reference UI's interactivity.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Run Guardian checks on an email message”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpnone0/10Evidence only shows standard API reference pages listing endpoints (create contact, send campaign, etc.) with no mention of an interactive console, runnable code samples, or try-it-now sandbox features expected for an AI-native exploratory API reference.
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Send a new SMS message through Mandrill”
- [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
- [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to LoopsA probe confirms a valid OpenAPI spec is served at https://loops.so/openapi.json (contains an 'openapi' key, HTTP 200), and this is complemented by full API reference docs. Missing for 10: independent third-party confirmation that the spec is complete/versioned or widely used by external tooling.
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
Mailchimpnone0/10The evidence pack shows Mailchimp's developer docs describe API endpoints (Marketing, Transactional) but never mentions an OpenAPI/Swagger spec or any downloadable machine-readable schema; the only spec-like artifact found is an llms.txt content summary, not an API spec. Missing for 10: explicit OpenAPI/Swagger file, published schema download link, or documentation referencing machine-readable spec format.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [probe] “PROBE llms.txt: HTTP 200 at https://mailchimp.com/llms.txt # Mailchimp - Complete Web Content Analysis > Comprehensive analysis and documen…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnLoopsnone0/10No evidence of a sandbox/test environment, test API keys, or staging mode separate from production data; docs cover API auth, SDKs, MCP, and migration guides but nothing about sandboxing. Missing for 10: dedicated sandbox/test-mode environment, test API keys or data isolation guarantees, documentation of a non-production testing workflow.
Mailchimpnone0/10No evidence of a sandbox/test environment or test API keys for Mailchimp's API; docs only describe production endpoints (campaigns, contacts, transactional sends) with no mention of a sandbox mode. Missing for 10: any documentation of a sandbox/test environment, test API keys, or dry-run mode that avoids touching production data.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to LoopsA founder comment mentions the API has versioning ('performant API with versioning for transactional email') and an OpenAPI spec is exposed, but there is no documented deprecation policy, version lifecycle, or migration guidance anywhere in the evidence. Missing for 10: documented deprecation/sunset policy, versioning scheme details, migration guides between API versions.
- [community] “Founder describes Loops' approach: simplified pricing (no tables, one metric), performant API with versioning for transactional email, text-…”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpnone0/10Evidence confirms Mailchimp has Marketing, Transactional, and Commerce APIs with documented endpoints, but nothing in the pack describes API versioning scheme or a deprecation policy for AI-native reliability; community evidence even shows abrupt, unannounced account/API access shutdowns, undermining trust in predictable API lifecycle.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
- [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
Analytics attribution — stories about analytics attribution in this arenaAnalytics attribution
Stories about analytics attribution in this arena
Api metrics
developerPull campaign and flow performance metrics through the API into my own warehouse or dashboards
weight 2 · round drawnLoopsnone0/10Evidence covers API endpoints for creating contacts, sending events, drafting campaign content, and MCP integration, but nothing documents an endpoint for retrieving campaign or flow performance metrics (opens, clicks, conversions, revenue) via API for warehousing or BI use. The analytics mentioned (e.g., 'see which emails lead to upgrades') appear to be dashboard-only features, not exposed via API.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpnone0/10The evidence pack shows Mailchimp has a general Marketing API (contacts, campaign send, transactional email) but contains no documentation of report/analytics endpoints for pulling campaign or automation (flow) performance metrics into an external warehouse or dashboard. Missing for 10: explicit reports/analytics API endpoints, examples of exporting campaign/flow metrics, and any dashboard/warehouse integration evidence.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Actionable insights into audience growth and conversion funnels”
Attribution
founderAttribute signups or revenue to specific emails and flows, not just opens and clicks
weight 2 · round to LoopsLoops explicitly markets seeing 'which emails lead to upgrades, lower churn, and add revenue' with dynamic segments, suggesting some revenue/conversion attribution beyond opens/clicks, but this is a single marketing-page claim with no detail on methodology, dashboards, or per-flow attribution granularity, and no independent or hands-on corroboration exists in the evidence pack. Missing for 10: detailed docs on how revenue/signup attribution is computed, screenshots or hands-on reports of attribution reporting, and third-party validation.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
Mailchimpnone0/10The evidence pack only shows generic marketing/API docs and vague analytics claims (e.g., 'actionable insights into audience growth and conversion funnels', 'predictive segmentation') with no documentation of revenue/signup attribution tied to specific emails or automation flows. No reporting feature, e-commerce revenue-per-campaign dashboard, or flow-level conversion tracking is evidenced.
- [claimed-docs] “Actionable insights into audience growth and conversion funnels”
- [claimed-docs] “Predictive Segmentation”
Reporting core
marketerRead opens, clicks, unsubscribes, and conversions per campaign and per automation step, over time
weight 3 · round to MailchimpLoopsnone0/10Evidence covers Loops' API, SDKs, CLI, MCP, and migration tooling, plus a generic mention of segmentation revenue impact, but there is no documentation of an analytics dashboard or API reporting opens, clicks, unsubscribes, and conversions per campaign or per automation step over time. Missing for 10: any analytics/reporting endpoint or dashboard docs showing per-campaign/per-step metrics, time-series breakdowns, or conversion attribution.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
The evidence only vaguely gestures at analytics ('actionable insights into audience growth and conversion funnels') without any documentation of per-campaign or per-automation-step reporting on opens, clicks, unsubscribes, or conversions over time. Missing for 10: campaign report API/dashboard details, automation-step-level analytics, time-series breakdowns, and independent corroboration that these metrics are accessible and reliable.
- [claimed-docs] “Actionable insights into audience growth and conversion funnels”
Audience segmentation — stories about audience segmentation in this arenaAudience segmentation
Stories about audience segmentation in this arena
Agent segments
ai-native userAn agent can translate a plain-language audience description into a real segment via the platform's programmatic surface
weight 2 · round drawnLoopsnone0/10While Loops exposes API endpoints for contacts, events, and campaign content (loops-docs-3, loops-docs-4, loops-docs-6), and mentions segments only as a dashboard feature that stays dynamic (loops-docs-16), there is no documented endpoint or MCP tool for creating or defining an audience segment programmatically from a natural-language description. No evidence shows an agent can translate plain-language criteria into a real segment via the API or MCP surface.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
Mailchimpnone0/10The evidence pack shows generic Marketing API capabilities (create contacts, send campaigns) and mentions 'Predictive Segmentation' as a paid feature, but there is no documentation of an API endpoint or agent-facing surface that translates a plain-language audience description into a concrete segment. Missing for 10: any segment-creation API reference, any NL-to-criteria translation mechanism, and any example of an agent invoking this programmatically.
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Predictive Segmentation”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
Api contacts
developerCreate, update, and suppress contacts with custom properties through the API at production scale
weight 3 · round to LoopsEvidence confirms a REST API with bearer-token auth and a POST /contacts/create endpoint plus an OpenAPI spec, and dynamic segment properties are mentioned, implying custom contact properties exist. However, there is no explicit documentation of contact update or suppression endpoints, nor any mention of rate limits, bulk operations, or production-scale guarantees. Missing for 10: explicit contacts/update and suppression API endpoints, documented custom-property schema support, and evidence of production-scale throughput/rate limits.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Docs confirm a Marketing API contact-creation endpoint ('Create a new omni-channel contact for an audience') and general API access to custom app data, but the pack lacks any explicit documentation of update or suppression (unsubscribe/cleaned) endpoints, custom merge-field schemas, or batch/production-scale operations. Community reports of accounts being banned, contacts wiped, and automated API/browser access blocked (e.g., dev-tools-triggered bans) raise real doubts about reliability of sustained programmatic contact management at scale. Missing for 10: documented update/suppress endpoints, custom property/merge-field API docs, evidence of bulk/batch operations, and independent confirmation of stable production-scale API usage.
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
- [community] “MailChimp removed half my users from a mailing list claiming lots of unverified sign-ups and spam complaints, even though the sign-ups were …”
- [community] “MailChimp blacklists your IP if you open the browser's dev tools; as a developer who often has devtools open, I get banned from Mailchimp fo…”
- [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”
Api segments
developerCreate and update segments, tags, or lists programmatically and read back exactly who is in them
weight 3 · round to LoopsLoops' API supports creating/updating contacts and triggering events (loops-docs-4, loops-docs-3), and segments are described as dynamic (loops-docs-16), but no evidence shows an endpoint to read back which contacts belong to a segment, tag, or list. Missing for 10: documented GET/list endpoints for contacts by segment/tag/list, and confirmation that programmatic tag/list membership queries are supported.
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpnone0/10The evidence pack only shows generic mentions of Mailchimp's Marketing API and a single endpoint for creating a contact (mailchimp-docs-4), with no documentation of segment, tag, or list CRUD operations or reading back exact membership. Missing for 10: explicit API endpoints for creating/updating segments or tags, listing/reading segment membership, and any developer or hands-on confirmation that programmatic read-back works as described.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
Segment core
marketerBuild audience segments from profile attributes, tags, and behavioral events, and they stay live as data changes
weight 3 · round to LoopsLoops explicitly claims segments are built from profile properties and stay dynamic as data changes (loops-docs-16), and the API supports contacts with properties and events that trigger workflows (loops-docs-3, loops-docs-4), suggesting behavioral/event-based segmentation is possible. However, there's no explicit documentation of tag-based segmentation or a dedicated segment-builder UI walkthrough, and no independent/hands-on confirmation of live segment updates. Missing for 10: explicit tag-attribute mention, segment-builder UI documentation, and independent corroboration of segments staying live.
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
Evidence shows Mailchimp offers 'Predictive Segmentation' and audience growth insights, and the Marketing API supports contact creation and custom data ingestion, which implies segmentation capability, but no direct documentation describes building segments from tags or behavioral events or confirms segments update live as data changes. missing for 10: explicit docs on tag-based segmentation, event-based triggers, and dynamic/live segment updating.
- [claimed-docs] “Predictive Segmentation”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Actionable insights into audience growth and conversion funnels”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to MailchimpLoopsnone0/10Evidence shows only single-item API operations (create one contact, send one event, send one transactional email) and no documented bulk/batch endpoints, CSV import, or bulk update/segment operations for AI agents to invoke at scale.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
Mailchimpdisputedcontradicted4/10Mailchimp's Marketing API allows creating/sending campaigns and contacts (mailchimp-docs-1, mailchimp-docs-4, mailchimp-docs-5), implying some bulk-capable API surface, but there is no documented batch/bulk-specific endpoint in the evidence, and multiple hands-on reports show that performing bulk operations like migrating or importing large contact lists triggered account bans or data loss (mailchimp-comm-3, mailchimp-comm-6), directly contradicting reliable bulk-operation support. missing for 10: explicit batch API documentation, evidence of successful large-scale bulk imports/exports, and independent confirmation that bulk workflows don't trigger account suspension.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [community] “They banned me after migrating an email list over because they said I couldn't confirm how I got the emails, even though they were legitimat…”
- [community] “MailChimp removed half my users from a mailing list claiming lots of unverified sign-ups and spam complaints, even though the sign-ups were …”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to LoopsLoops' event API explicitly triggers workflows ('Send an event to trigger workflows') and marketing copy references onboarding/activation/winback flows set up once and running automatically, matching the rule-on-event automation pattern. However, the evidence pack lacks detail on how rules/conditions are authored (branching logic, if/then rules, workflow builder specifics) beyond the event-trigger primitive. Missing for 10: documentation of conditional rule logic/branching in workflows, independent hands-on confirmation of workflow automation depth.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
Mailchimp’s Transactional API supports event-driven messaging (mailchimp-docs-2) and the Marketing API can trigger campaign sends via API calls, suggesting some rule/event-based automation capability, but no evidence describes a dedicated 'automation rules' or 'journey builder' engine that lets users define custom trigger-action logic. missing for 10: explicit documentation of a rule-builder/automation-journey feature, examples of user-defined trigger conditions, and independent confirmation that such automations work reliably.
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to LoopsLoops supports event-triggered workflows (POST /events/send) and lifecycle emails (onboarding, winback, etc.) that run automatically once set up, which touches on workflow automation, but there is no evidence of an API or agent-facing capability to schedule recurring jobs/crons directly — workflow triggers are event-based and configured largely via the dashboard. missing for 10: explicit recurring/cron scheduling API, agent-driven workflow creation beyond event triggers, independent confirmation of automation depth.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
The only recurring-schedule evidence is RSS campaigns that send 'according to its schedule' (mailchimp-docs-5); all other campaigns send immediately, and there is no documentation of an API or workflow engine (e.g., Customer Journeys automation) for AI-native users to configure arbitrary recurring jobs. Missing for 10: explicit automation/workflow API docs, recurring-trigger configuration beyond RSS, and any independent confirmation of automation reliability.
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnLoopsnone0/10Loops evidence covers email campaign creation, API/MCP integration, and content authoring, but there is no mention of versioning, reviewing changes, or rolling back automations/workflows — the closest is draft campaigns reviewed before sending, which is not version history or rollback.
Mailchimpnone0/10No evidence of automation versioning, review workflows, or rollback capability in Mailchimp's docs or API; only campaign creation/sending and unrelated API features are documented. missing for 10: version history for automations, diff/review UI, rollback/restore functionality, audit trail of automation changes.
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Multivariate and A/B Testing”
- [claimed-docs] “Predictive Segmentation”
Campaign sending — stories about campaign sending in this arenaCampaign sending
Stories about campaign sending in this arena
Agent campaigns
ai-native userAn agent can draft a campaign against a segment and leave it scheduled or queued for a human to approve before send
weight 3 · round to LoopsLoops explicitly supports agents creating draft campaigns via API that are then reviewed/sent from the dashboard (loops-docs-5, loops-docs-9), and has API/MCP access for contacts, events, and content (loops-docs-3,4,6). However, there's no explicit evidence of segment targeting being part of the drafted campaign creation flow, nor of a 'scheduled/queued' state distinct from 'draft awaiting dashboard review' — the described flow is draft-then-manual-send rather than draft-then-schedule-with-approval-gate. missing for 10: explicit mention of segment-targeted campaign creation via API, a distinct 'scheduled pending approval' state vs plain draft, and independent/hands-on confirmation of this human-approval workflow.
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
Mailchimpnone0/10The evidence shows only that the Marketing API can create campaigns and send them (with immediate send noted explicitly in mailchimp-docs-5), but there is no evidence of a scheduling/queuing mechanism that lets an agent draft a campaign and leave it pending for human approval before it goes out. No API endpoint, workflow, or documentation describing draft/approval states is present in the evidence pack.
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
Api campaigns
developerCreate and schedule a campaign or broadcast entirely through a documented public API, without touching the dashboard
weight 3 · round to MailchimpLoops documents a Content API that lets developers create draft campaigns via API, but its own docs explicitly state that review and sending happen from the dashboard ('Create draft campaigns... Review and send from the dashboard'), directly contradicting the 'without touching the dashboard' requirement for sending/scheduling. Missing for 10: documented API endpoints for scheduling/sending a campaign, evidence of full campaign lifecycle (create+schedule+send) without dashboard interaction, and independent confirmation of this workflow.
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
Mailchimp's Marketing API docs confirm creating audience contacts and sending campaigns via API (mailchimp-docs-4, mailchimp-docs-5), showing the core send-via-API capability exists, but the cited evidence only describes immediate sending or RSS-based scheduling, not a general 'schedule campaign' endpoint or full campaign-creation-to-send workflow purely via API. Missing for 10: explicit documented schedule-campaign endpoint, full campaign creation API details, and independent/developer corroboration that the entire flow works without dashboard use.
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
Campaign core
marketerCompose an email campaign, pick its audience, and send or schedule it — the arena's table-stakes loop
weight 3 · round drawnDocs describe composing campaigns via editor or Content API, segmenting/targeting dynamic audiences, and sending from the dashboard, covering the core compose→audience→send loop (loops-docs-5, loops-docs-9, loops-docs-16, loops-docs-17, loops-docs-18). Missing for 10: explicit documentation of a 'schedule for later' feature and independent/hands-on confirmation of the end-to-end campaign flow (community evidence only covers pricing/editor tech, not campaign sending itself).
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [claimed-docs] “Set your colors, type, and spacing in one place. Every email you send picks them up automatically, so your brand stays consistent without an…”
- [claimed-docs] “How to craft an email using our editor”
Docs show core loop elements: creating audience contacts (docs-4), sending campaigns with scheduling support for RSS campaigns (docs-5), and email design/testing tools (docs-9, docs-14) — this is Mailchimp's flagship product function. Missing for 10: explicit first-party documentation of scheduled (non-RSS) send-later flow and independent hands-on confirmation of a full compose-audience-send cycle; some community reports (mailchimp-comm-12) note deliverability issues on lower tiers that add minor quality risk.
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Multivariate and A/B Testing”
- [claimed-docs] “Design better emails”
- [community] “I tried Mailchimp's free tier a few years ago; everything was great except the email servers had terrible reputation and most of what I sent…”
Experiments
marketerA/B test subject lines or content variants and have the winner picked from real engagement
weight 2 · round to MailchimpLoopsnone0/10No evidence in the pack mentions A/B testing of subject lines or content, nor any automated winner-selection based on engagement metrics; docs cover campaigns, transactional email, contacts, and API/MCP integration but not split-testing functionality.
Mailchimp's pricing page lists 'Multivariate and A/B Testing' as a feature, confirming the capability exists, but the evidence pack lacks any documentation detailing automatic winner selection based on real engagement metrics (open/click rates) or how variants are configured. missing for 10: first-party docs describing the A/B test setup, winning-criteria selection (opens/clicks/revenue), and automatic winner send-out; independent/hands-on confirmation the feature works as described.
- [claimed-docs] “Multivariate and A/B Testing”
Deliverability domains — stories about deliverability domains in this arenaDeliverability domains
Stories about deliverability domains in this arena
Deliverability signals
marketerSee bounce, complaint, and blocklist signals per send and get actionable guidance when deliverability degrades
weight 2 · round drawnLoopsnone0/10The evidence pack has no mention of bounce, complaint, or blocklist tracking per send, nor any deliverability health dashboard or actionable guidance when deliverability degrades; the closest item ('Guardian checks on an email message') is vague and not tied to bounce/complaint/blocklist metrics. Missing for 10: per-send bounce/complaint/blocklist reporting, deliverability health dashboard, automated alerts or actionable remediation guidance.
- [claimed-docs] “Run Guardian checks on an email message”
Mailchimpnone0/10The evidence pack contains no documentation of per-send bounce/complaint/blocklist reporting or actionable deliverability guidance—only generic API descriptions, pricing feature bullets, and community complaints about account bans and poor sender reputation, none of which describe the specific reporting/guidance capability the story asks for.
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
- [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
- [community] “I tried Mailchimp's free tier a few years ago; everything was great except the email servers had terrible reputation and most of what I sent…”
Domain auth
ops userAuthenticate my own sending domain — SPF, DKIM, DMARC alignment — with guided DNS setup and verification
weight 3 · round drawnLoopsnone0/10No evidence in the pack describes domain authentication setup (SPF/DKIM/DMARC), DNS record guidance, or verification tooling; one migration doc merely mentions 'verify your domain' as a step without detail. missing for 10: DNS setup guide, SPF/DKIM/DMARC record instructions, verification status UI or API, any deliverability-domain documentation.
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
Mailchimpnone0/10The evidence pack contains no documentation about domain authentication, SPF/DKIM/DMARC setup, or guided DNS verification flows — only unrelated API docs, pricing feature lists, and community complaints. Missing for 10: any docs or hands-on evidence of domain authentication UI, DNS record generation, or verification status checks.
Suppression
ops userUnsubscribes, bounces, and spam complaints are suppressed automatically and honored across every send type — CAN-SPAM/GDPR hygiene by default
weight 3 · round drawnLoopsnone0/10No evidence pack items describe automatic suppression of unsubscribes, bounces, or spam complaints, nor honoring suppression lists across transactional and marketing sends; the community thread even raises a concern about pricing encouraging unlimited sends without addressing suppression handling. Missing for 10: documentation of automatic unsubscribe/bounce/complaint suppression, cross-send-type enforcement, and CAN-SPAM/GDPR compliance details.
- [community] “Concern raised: 'your service seems priced in a way that encourages spam (send unlimited emails to an address)' regarding deliverability/ded…”
Mailchimpnone0/10No evidence in the pack documents Mailchimp's suppression list, bounce/complaint handling, or cross-send-type unsubscribe enforcement; docs cited are about API endpoints, pricing tiers, and unrelated features. Community evidence discusses account bans and deliverability reputation issues but does not confirm or deny automatic suppression hygiene, so absence of applicable evidence yields 'none'.
Integrations webhooks — stories about integrations webhooks in this arenaIntegrations webhooks
Stories about integrations webhooks in this arena
First party integrations
ops userConnect the platform to my existing stack — Stripe or Shopify, a CDP like Segment, my product database — with maintained first-party integrations
weight 2 · round drawnLoopsnone0/10Evidence only shows generic API/SDK/events/contacts endpoints and migration guides from competing ESPs (Brevo, Customer.io) — there is no mention of maintained first-party integrations with Stripe, Shopify, Segment, or a product database. Ops users would need to build custom API/webhook connections themselves rather than use a documented native integration.
Mailchimpnone0/10The evidence pack only shows generic Marketing/Transactional APIs and an open-source commerce stack, but contains no mention of maintained first-party integrations with Stripe, Shopify, Segment, or product databases. Missing for 10: explicit Stripe integration docs, Shopify integration docs, Segment/CDP integration docs, and any customer/database sync integration evidence.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Open Commerce (formerly Reaction Commerce) is an open source, API-first, modular commerce stack made for technical, growth-minded …”
Webhooks
developerSubscribe webhooks to delivery and engagement events — sends, opens, clicks, bounces, unsubscribes — with a documented, signed payload
weight 3 · round drawnLoopsnone0/10No evidence pack item mentions webhooks for delivery/engagement events (sends, opens, clicks, bounces, unsubscribes) or signed payloads; the docs focus on REST API, MCP, CLI, and events for triggering workflows, not outbound webhook subscriptions. Missing for 10: any webhook subscription endpoint, event types list, and payload signing/verification documentation.
Mailchimpnone0/10The evidence pack includes only general Marketing/Transactional API descriptions and community complaints, with no mention of webhook subscriptions, event types (opens, clicks, bounces, unsubscribes), or signed payload verification. Absence of evidence for this applicable integrations axis means it cannot be credited as delivered.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
Lifecycle automation — stories about lifecycle automation in this arenaLifecycle automation
Stories about lifecycle automation in this arena
Automation core
marketerBuild multi-step lifecycle automations — welcome series, onboarding, winback — with branches, delays, and exit rules
weight 3 · round to LoopsEvidence confirms Loops supports lifecycle email use cases like onboarding, activation, upgrade, and winback sequences (loops-docs-15) and event-triggered workflows via API (loops-docs-3), but there is no documentation of branching logic, time-based delays, or exit-rule conditions within a visual automation builder. missing for 10: explicit branch/condition support, delay/wait-step configuration, exit-rule mechanics, and independent confirmation of a multi-step workflow builder.
- [claimed-docs] “Reach users after they close the tab. Set up onboarding, activation, upgrade, and winback emails once, then improve them over time.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
Mailchimpnone0/10The evidence pack contains no documentation of Mailchimp's journey/automation builder, branching logic, delays, or exit rules — only generic API references (campaigns, transactional email, contacts) and pricing-page feature bullets (A/B testing, predictive segmentation, AI) that don't address multi-step lifecycle automations.
Event triggers
developerFire a custom event from my product and have it trigger an automation for exactly that person
weight 3 · round to LoopsLoops' API includes a documented POST /events/send endpoint explicitly for triggering workflows per contact, alongside contact identification via API key/email, matching the story of firing a custom event to trigger a targeted automation. This is corroborated by an OpenAPI spec and SDK/docs references, though there's no independent hands-on report specifically testing event-triggered automation reliability. missing for 10: independent/hands-on verification of event-to-automation triggering, more detail on per-contact targeting semantics.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Add Loops to your application in minutes with our SDKs.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [claimed-docs] “Manage contacts, send events, and test transactional email from your terminal”
Mailchimpnone0/10The evidence pack references Mailchimp's Marketing API pulling 'custom data' from apps and creating contacts, but nowhere documents a specific Events API or mechanism for firing a custom event that triggers a Customer Journey/automation for a single contact. Without an explicit events endpoint or automation-trigger documentation, there is no evidence this capability is delivered.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
Flow operations
ops userSee where any individual person sits inside an automation and pull or re-enter them without breaking the flow
weight 2 · round drawnLoopsnone0/10The evidence shows Loops can trigger workflows via events and manage contacts via API, but there is no documentation of viewing an individual contact's position within a live automation/workflow or safely pulling/re-entering them without disrupting the flow. Missing for 10: workflow visualization UI, per-contact automation status view, documented pull/re-enter mechanics.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
Mailchimpnone0/10No evidence describes Customer Journey Builder subscriber-level visibility, or the ability to locate a specific contact within an automation and pull/re-enter them without disrupting the flow; docs only cover general API/campaign features. Missing for 10: journey/automation visual map showing contact position, per-contact pull/remove/re-entry controls, documentation or hands-on confirmation that this doesn't break the automation state.
List portability — stories about list portability in this arenaList portability
Stories about list portability in this arena
Export
founderExport my entire audience — contacts, custom fields, tags, engagement history, and suppression list — in an open format, self-serve
weight 3 · round drawnLoopsnone0/10The evidence pack shows API endpoints for creating contacts and sending events, migration guides for moving data INTO Loops from other providers, and CLI/SDK/MCP tooling, but no documented export endpoint, bulk-export feature, or self-serve mechanism to pull contacts, tags, engagement history, or suppression lists OUT of Loops in an open format. Missing for 10: a documented export/download API or dashboard feature, evidence of tags/engagement/suppression data being included in any export, and confirmation of an open file format (CSV/JSON) for full audience export.
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
- [claimed-docs] “A guide to moving contacts, events, workflows, and transactional email from Customer.io to Loops, with before and after code and a cutover c…”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
Mailchimpnone0/10The evidence pack contains no documentation of a self-serve export feature covering contacts, custom fields, tags, engagement history, and suppression list in an open format — API docs cover creating contacts and sending campaigns, not exporting. Community reports actually describe cases where audience data could not be self-serve recovered after account issues (mailchimp-comm-1, mailchimp-comm-2), reinforcing the absence of a documented reliable export path. missing for 10: no first-party docs on CSV/data export, no mention of engagement history or suppression list export, no confirmation of open-format guarantee.
- [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
- [community] “I had a mailing list with them removed with all contacts lost and account banned without notification. Support falsely claimed data was wipe…”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
Import migration
marketerMigrate in from another email platform with guided list import that preserves tags, custom fields, and unsubscribe state
weight 2 · round to LoopsLoops publishes migration guides for moving contacts, lists, events, and transactional email from platforms like Brevo and Customer.io with 'before and after code and a cutover checklist,' indicating some list-portability support, but these are developer-facing API migration guides rather than a marketer-friendly guided import wizard. No evidence explicitly confirms preservation of tags, custom fields, or unsubscribe state during import. Missing for 10: explicit UI-based guided import flow for marketers, confirmation that tags/custom fields/unsubscribe status are preserved, and independent evidence of successful migrations.
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
- [claimed-docs] “A guide to moving contacts, events, workflows, and transactional email from Customer.io to Loops, with before and after code and a cutover c…”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
Mailchimp's marketing site references a 'Switch from another tool' migration feature, but the evidence pack contains no documentation or hands-on detail confirming that tags, custom fields, or unsubscribe state are actually preserved during import. missing for 10: detailed migration/import API or guide docs, evidence of tag/custom-field mapping, evidence of unsubscribe-state preservation, independent confirmation of successful migrations.
- [claimed-docs] “Switch from another tool”
Marketing data access — stories about marketing data access in this arenaMarketing data access
Stories about marketing data access in this arena
Agent access
ai-native userAn agent can pull my whole email program — audiences, live automations, recent campaign results — programmatically and report on what's working
weight 2 · round drawnLoops exposes API/MCP access to contacts (audiences), events (automation triggers), and campaign content creation, and dashboard analytics on which emails drive upgrades/churn exist, but there's no documented endpoint or MCP capability for pulling campaign performance/results data programmatically — the 'report on what's working' analytics piece is not evidenced as API-accessible. missing for 10: an API/MCP endpoint for campaign performance metrics, evidence of reading analytics/results data programmatically rather than just creating content or contacts.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “See which emails lead to upgrades, lower churn, and add revenue. Segments are dynamic and stay current as properties change.”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
Mailchimp's Marketing API (mailchimp-docs-1, mailchimp-docs-4, mailchimp-docs-5) confirms programmatic access to audiences/contacts and campaign sending, implying an API surface an agent could query, but the evidence pack contains no explicit endpoints for automations or campaign performance/reports data, nor any AI-agent/MCP integration proof. Missing for 10: documented reporting/analytics endpoints, automation-status endpoints, and evidence of an agent actually consuming this data end-to-end.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
Api access
developerRead per-person engagement history — what was sent, opened, clicked — through the API for any contact
weight 3 · round drawnLoopsnone0/10The evidence pack documents contact creation, event sending, campaign drafting, and transactional email APIs, but nowhere shows an endpoint or documentation for retrieving per-contact engagement history (sends, opens, clicks) via the API. This is a fair capability to expect from an email marketing platform, but no evidence confirms it exists.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Run Guardian checks on an email message”
Mailchimpnone0/10Evidence shows generic Marketing API endpoints for creating contacts and sending campaigns, but no documentation of an endpoint or object returning per-contact engagement history (sent/opened/clicked activity log) via the API. Mailchimp does have an 'activity' endpoint in reality, but no evidence pack item mentions it, so per the rules absence must be judged as none. missing for 10: any docs referencing a contact activity/engagement history endpoint, example response showing opens/clicks/sends per contact, independent confirmation of this API capability.
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
Scoped access
ops userMint scoped or read-only API credentials so an agent or contractor can read analytics without the power to send
weight 2 · round drawnLoopsnone0/10Evidence shows only a single Bearer-token API key auth model with no mention of scoped, read-only, or per-agent/contractor credentials; nothing indicates permission tiers or restricted-scope keys.
- [claimed-docs] “add an Authorization header and set the API key as a Bearer token”
Mailchimpnone0/10No evidence of API key scoping or read-only/permission-restricted credentials in Mailchimp's docs; the only API key model referenced is a single full-access account key with no mention of granular scopes for analytics-only or contractor access. Missing for 10: any documentation of scoped/read-only API keys, role-based API access, or OAuth scopes limiting an agent to analytics without send permission.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to LoopsLoops exposes a broad API (contacts, events, transactional email, content/campaign drafting, Guardian checks) plus an OpenAPI spec, CLI, and MCP server, letting AI-native users perform most workflows programmatically (loops-docs-3, loops-docs-4, loops-docs-5, loops-docs-19, loops-probe-3, loops-probe-4). However, campaign creation explicitly notes 'Review and send from the dashboard,' meaning the final send step is UI-only, and analytics/segmentation dashboards have no documented API equivalent. Missing for 10: API parity for sending/publishing campaigns, API access to analytics/segments, independent confirmation of full UI-API parity.
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “POST /contacts/create Add a contact to your audience”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Run Guardian checks on an email message”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
Mailchimp exposes a fairly complete Marketing API (contacts, campaigns, sending) and a separate Transactional API, showing broad coverage of core UI actions, but there is no first-party claim of full UI/API parity, and community evidence suggests some UI-only features (e.g., the drag-and-drop email builder's advanced editing) are not fully replicable via API/inspector access. missing for 10: explicit vendor statement of full API/UI parity, evidence that advanced design/template features available in the UI builder are fully scriptable via API, independent confirmation of parity across all account/admin settings.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [claimed-docs] “Send a Mailchimp campaign. For RSS Campaigns, the campaign will send according to its schedule. All other campaigns will send immediately.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to MailchimpLoopsnone0/10Evidence shows API endpoints for creating/writing contacts and events, migration guides for moving data INTO Loops from other providers, and an OpenAPI spec, but nothing documents a bulk export feature or open-format data portability for users wanting to leave Loops with their data.
Mailchimpdisputedcontradicted3/10Mailchimp's Marketing API allows programmatic access to contacts/campaigns (mailchimp-docs-4), which could support data export, but there's no documented bulk/open-format export-and-leave feature, and community reports describe accounts being banned or deleted with contact lists lost entirely, support falsely claiming data was wiped, and only providing a data dump under public pressure — directly contradicting a smooth 'export all my data and leave' experience. Missing for 10: an official bulk export/data-portability doc, an open standard export format, and confirmation that account closure preserves user access to their data.
- [claimed-docs] “Create a new omni-channel contact for an audience.”
- [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
- [community] “I had a mailing list with them removed with all contacts lost and account banned without notification. Support falsely claimed data was wipe…”
- [community] “MailChimp removed half my users from a mailing list claiming lots of unverified sign-ups and spam complaints, even though the sign-ups were …”
ai-native userRead the product's source under an open license
weight 2 · round drawnLoopsnone0/10Loops is a closed-source SaaS email platform; no evidence of an open-source license or public source code repository is provided anywhere in the evidence pack.
Mailchimpnone0/10Mailchimp is closed-source SaaS; while it references 'Mailchimp Open Commerce' as open source, this is a separate discontinued product, not Mailchimp's own source. No evidence of an open license for Mailchimp's core platform code.
- [claimed-docs] “Mailchimp Open Commerce (formerly Reaction Commerce) is an open source, API-first, modular commerce stack made for technical, growth-minded …”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnLoopsnone0/10No evidence in the pack mentions data residency, regional storage options, or compliance controls letting users choose where data is stored; Loops' documentation focuses on email API, agents, and pricing, not data residency.
Mailchimpnone0/10No evidence pack items mention data residency, region selection, or geographic storage controls for Mailchimp; the docs focus on API features and pricing tiers, not data location controls. Missing for 10: any documentation of region/residency selection, data center choice, or geographic storage controls.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnLoopsnone0/10No evidence in the pack addresses AI-training data usage, opt-outs, or privacy commitments regarding model training; Loops' materials focus on email/marketing API features, not data-privacy policy toward AI training. Missing for 10: any privacy policy statement, opt-out mechanism, or documentation about AI training data usage.
Mailchimpnone0/10No evidence in the pack addresses AI-training opt-out or data-use controls for Mailchimp; the evidence is limited to product feature descriptions and unrelated account-management/community complaints. Missing for 10: any documentation of an AI-training opt-out setting, privacy policy language on model training, or admin controls to exclude data from AI/ML use.
ai-native userControl data retention and deletion
weight 2 · round drawnLoopsnone0/10No evidence pack items address data retention policies, deletion controls, data export, or GDPR/CCPA-style deletion APIs for contacts/events. The docs focus on sending email, API/SDK usage, and migration, with nothing on how a user or agent controls retention or deletion of stored data. Missing for 10: documented data retention policy, contact/event deletion API or endpoint, data export/erasure workflow, and any privacy compliance certification.
Mailchimpnone0/10No documentation is provided showing Mailchimp gives AI-native users explicit APIs or settings to control data retention/deletion policies; the evidence pack only covers marketing/API features unrelated to retention controls. Community reports actually describe Mailchimp unilaterally deleting accounts and data without user consent or recourse, further indicating the user lacks control over retention/deletion.
- [community] “MailChimp deleted my account with no warning after a period of inactivity, giving no notice, and support offered no path to recover the mail…”
- [community] “I had a mailing list with them removed with all contacts lost and account banned without notification. Support falsely claimed data was wipe…”
- [community] “We wanted to pause our paid MailChimp account and return to free tier, but they said there was no way to do that — you either keep paying or…”
Template content — stories about template content in this arenaTemplate content
Stories about template content in this arena
Ai content
marketerHave the platform's built-in AI draft or refine subject lines and email copy from a brief, inside the composer
weight 2 · round drawnLoopsnone0/10Evidence shows API-driven draft campaign creation, agent/MCP integrations, and a text-based editor, but there is no mention of a built-in AI feature inside the composer that drafts or refines subject lines/email copy from a brief — the 'AI drafting' capability described is done by external coding agents via API/MCP, not a native in-app AI assistant.
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
- [claimed-docs] “How to craft an email using our editor”
Mailchimpnone0/10The evidence pack only mentions 'Generative AI features' as a pricing line item with no description of composer-integrated subject line/copy drafting from a brief, and no docs or hands-on confirmation of this specific workflow. missing for 10: documentation or demo of AI subject-line/copy generation inside the composer, any first-party feature description, independent/hands-on confirmation it works as described.
- [claimed-docs] “Generative AI features”
Editor
marketerDesign on-brand emails with a visual editor, reusable templates, and personalization tokens that render correctly across clients
weight 2 · round to LoopsLoops documents an email editor, brand-consistency settings (colors/type/spacing applied automatically), dynamic personalization variables, and reusable content built via templates/Content API (loops-docs-17, loops-docs-18, loops-docs-2, loops-docs-9, loops-docs-14). Community evidence confirms the editor is a customizable, text-based system built on extended MJML (loops-comm-7), which supports templating but is not a classic drag-and-drop visual builder, and no evidence addresses cross-client rendering testing or guarantees. missing for 10: explicit cross-email-client rendering validation, confirmation of a fully visual (non-code) editor experience, independent hands-on review of template reuse in practice.
- [claimed-docs] “Set your colors, type, and spacing in one place. Every email you send picks them up automatically, so your brand stays consistent without an…”
- [claimed-docs] “How to craft an email using our editor”
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
- [community] “Founder explains editor was rewritten using Lexical (switched from Slate.js) to power their text-based, customizable email editor, built on …”
Only a generic marketing-site blurb ('Design better emails') hints at a visual editor, with no documentation of reusable templates, personalization/merge tags, or cross-client rendering testing; one community report also describes the drag-and-drop/CKText editor failing to load, undermining reliability. missing for 10: docs on template library, merge-tag personalization, cross-client rendering QA, and independent corroboration of editor quality.
- [claimed-docs] “Design better emails”
- [community] “I used ChatGPT to get a refund from Mailchimp when their CKText editor failed to load on International Women's Day, preventing sending an em…”
- [community] “I had to use their drag-and-drop email builder because a non-dev would edit it; when a Code module became inaccessible via UI, I tried injec…”
Templates as code
developerManage email templates as code — HTML/MJML or API-managed templates with variable substitution — under version control
weight 2 · round to LoopsLoops offers a Content API to author campaigns in code (loops-docs-9), transactional emails with dynamic data variables (loops-docs-2), and an editor built on extended MJML (loops-comm-7), which together enable API-managed templates with variable substitution that a developer could store in their own repo. However, there's no first-party feature for native version-control integration, template diffing, or a documented HTML/MJML file-based workflow — the API/editor split still centers editing in the dashboard. Missing for 10: explicit git/version-control integration or CLI-based template push/pull workflow, and independent confirmation that Content API templates round-trip cleanly with raw MJML/HTML files.
- [claimed-docs] “Author campaigns in code with the Content API and keep editing visually in Loops.”
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [community] “Founder explains editor was rewritten using Lexical (switched from Slate.js) to power their text-based, customizable email editor, built on …”
- [claimed-docs] “Create draft campaigns, content and all, straight from the API. Review and send from the dashboard.”
- [claimed-docs] “I scanned your codebase and found every send, template, and webhook. Each one maps to a Loops equivalent, so I swapped the API calls and reb…”
Mailchimpnone0/10The evidence pack contains no documentation of Mailchimp's Templates API, HTML/MJML template management, merge-tag variable substitution, or any version-control workflow for templates; only general marketing API mentions are present. Missing for 10: Templates API docs, variable/merge-tag substitution details, MJML/HTML support, version-control integration examples.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Create a new omni-channel contact for an audience.”
Transactional sending — stories about transactional sending in this arenaTransactional sending
Stories about transactional sending in this arena
Transactional api
developerSend one-to-one transactional email — receipts, magic links, notifications — through the same platform's API alongside marketing sends
weight 3 · round to LoopsLoops explicitly documents sending transactional emails with dynamic data via API/SDK alongside marketing/lifecycle sends from the same platform, with an OpenAPI spec and events API to trigger workflows, and this is corroborated by community mention of a 'performant API with versioning for transactional email.' Missing for 10: no hands-on developer report of using the transactional send endpoint specifically (e.g. receipts/magic links) beyond docs framing, and no independent deliverability benchmark for transactional use.
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [claimed-docs] “POST /events/send Send an event to trigger workflows”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
- [probe] “PROBE llms.txt: HTTP 200 at https://loops.so/llms.txt # Loops > Loops is an email platform for software companies. Send transactional and m…”
- [probe] “PROBE openapi: HTTP 200 at https://loops.so/openapi.json — contains "openapi" key”
- [community] “Founder describes Loops' approach: simplified pricing (no tables, one metric), performant API with versioning for transactional email, text-…”
Mailchimp Transactional (formerly Mandrill) provides API/SMTP-based transactional sending (receipts, event-driven messages) per docs-2, docs-6, docs-7, docs-8, satisfying the core capability, but it is a separate product with its own distinct API endpoint rather than truly unified with the Marketing API, and community reports confirm it was never fully integrated post-acquisition (mailchimp-comm-8) and has suffered abrupt, unexplained shutdowns of transactional sending (mailchimp-comm-4, mailchimp-comm-5). missing for 10: evidence of a single unified API/dashboard combining marketing and transactional sends, and confirmation of reliable uptime for transactional messages without account suspension risk.
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Send a new SMS message through Mandrill”
- [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
- [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”
- [community] “Some years ago MailChimp decided to act as a cash cow, invest very little except a recent redesign. Mandrill still isn't integrated after th…”
- [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
- [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
Transactional hygiene
ops userTransactional email is kept separate from marketing — its own templates, suppression rules, and reputation — so a receipt still delivers to an unsubscribed contact
weight 2 · round drawnDocs confirm Loops offers distinct transactional email sending (its own API/backend calls) separate from marketing/lifecycle campaigns, and migration guides note transactional vs marketing distinctions, but there is no explicit documentation of separate suppression-list logic or dedicated sending reputation ensuring transactional mail still reaches unsubscribed contacts. Missing for 10: explicit suppression-rule separation, reputation isolation, and confirmation that unsubscribe status doesn't block transactional sends.
- [claimed-docs] “Send transactional emails with dynamic data variables, right from your backend.”
- [claimed-docs] “Add marketing, lifecycle, and transactional email to your SaaS from one product. Keep your current transactional provider while you migrate.”
- [claimed-docs] “Move transactional email, contacts, and lists from Brevo to Loops: swap the SDK, map each call, verify your domain, and cut over one email t…”
- [claimed-docs] “A guide to moving contacts, events, workflows, and transactional email from Customer.io to Loops, with before and after code and a cutover c…”
Mailchimp Transactional (Mandrill) is documented as a distinct product with its own API/SMTP, dedicated IPs, and routing separate from the Marketing API, which supports the general premise of separated transactional infrastructure. However, there is no direct evidence that transactional sends bypass marketing suppression/unsubscribe lists or that templates are kept fully separate, and community reports (e.g., Mandrill sends being silently shut off after a single complaint, poor integration between the two products) suggest the separation is imperfect and reputation is fragile rather than cleanly isolated. Missing for 10: explicit documentation of suppression-list independence for transactional sends, confirmation that unsubscribed marketing contacts still receive transactional receipts, and evidence of fully separate templates/reputation management.
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Send a new SMS message through Mandrill”
- [claimed-docs] “Requests an additional dedicated IP for your account. Accounts may have one outstanding request at any time, and provisioning requests are p…”
- [claimed-docs] “Add a new route to an inbound domain or SMS program. Provide either domain or phone (not both).”
- [community] “A similar thing happened to me while using their Mandrill system. After years of using it with no issues, all of a sudden no emails were get…”
- [community] “Someone sent a marketing email another customer complained about (just one complaint) and Mailchimp silently shut off our incoming email pro…”
- [community] “Some years ago MailChimp decided to act as a cash cow, invest very little except a recent redesign. Mandrill still isn't integrated after th…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableLoopsn/aLoops is an email/marketing SaaS platform, not an AI agent — the evidence shows Loops publishing its own MCP server so other agents can call ITS tools (loops-docs-6, loops-probe-4), which is the server role, not Loops acting as a client that plugs in external MCP servers to gain their tools. There is no agentic/assistant capability within Loops that could consume external MCP servers, so this axis is a category error for this product.
- [claimed-docs] “Connect your agent to Loops over MCP. Read and write contacts, events, and content from any client.”
- [probe] “official MCP server documented at https://loops.so/agents/mcp”
Mailchimpn/aMailchimp is a marketing/email SaaS platform, not an AI agent; the story asks about plugging MCP servers into a product so it can use their tools, which applies to agentic/AI-assistant products acting as MCP clients. No evidence shows Mailchimp positioning itself as an MCP client or agent host, so this axis is a category error for this product type.
ai-native userSelf-host the core product
weight 3 · not comparableLoopsn/aLoops is a hosted SaaS email platform; nothing in the evidence suggests a self-hostable core product, and this is inherently a cloud service (with SES/SES-like MTA infra) rather than software distributed for self-hosting — this axis is a category error for this product type.
Mailchimpnone0/10Mailchimp's core email marketing platform is a closed, cloud-only SaaS with no self-hosted deployment option; the only open-source item mentioned (Mailchimp Open Commerce) is a separate commerce stack, not the core marketing product. missing for 10: any self-host package/instructions for the core Marketing/Transactional product, on-prem licensing, or Docker/VM deployment option.
- [claimed-docs] “Mailchimp’s Marketing API powers timely, relevant marketing campaigns with custom data pulled directly from your app.”
- [claimed-docs] “Mailchimp Transactional (formerly Mandrill) sends targeted and event-driven messages via the API or SMTP, fast—with best-in-class deliverabi…”
- [claimed-docs] “Mailchimp Open Commerce (formerly Reaction Commerce) is an open source, API-first, modular commerce stack made for technical, growth-minded …”
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableLoopsnone0/10No evidence in the pack mentions telemetry, analytics opt-out, or usage tracking controls for Loops as a product/tool; the evidence focuses on email API/agent features and pricing/UX community feedback. missing for 10: any documentation of telemetry collection or an opt-out mechanism, privacy settings, or data-collection disclosure.