Marketing Automation
Iterable
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Iterable, Inc. · iterable.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Iterable at a glance
- Vendor
- Iterable, Inc.
- Headquarters
- Incorporated in United States source, captured 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates Iterable 2/5, the mean of 6 judges. Iterable is an AI customer engagement platform, and the bench's scores put its strength in channels and journeys rather than sales-side lead handling. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Iterable is an AI customer engagement platform, and the bench's scores put its strength in channels and journeys rather than sales-side lead handling. Channel coverage runs 6–7: email, SMS, push, in-app and web push are documented as driven from one unified user profile, with behavioural personalisation through Catalog recommendations and data feeds. Journey orchestration sits at 5–6 — a visual builder with real-time behavioural triggers and per-stage A/B testing, capped by no public information on frequency capping or competing journeys for the same contact. Lead management runs 0–2: two judges declined to rate it, and the pages give no public information on lead scoring, routing or handover to sales. Sovereignty runs 1–2: the privacy notice states data may be stored in any of the vendor's data centres around the world and transmitted to its San Francisco headquarters under the Data Privacy Framework and SCCs, and we found no public information on EU residency or hosting. The widest ranges, consent and profiling and CRM and data at 2–4, still cluster closely. No price figures appear on the captured pages.
Speaks for it
- Five channels — email, SMS, push, in-app and web push — are documented as driven from one unified user profile, with channel coverage at 6–7
- A visual journey builder with real-time behavioural triggers, automatic pivots when users stall, and per-stage A/B testing, scored 5–6
- SMS compliance tooling is documented: automated single-word opt-in confirmation, opt-outs immediately processed and tracked, and configurable quiet hours
- A published subprocessor list, a DPO contact, and special-category data processed only under applicable legislation or explicit consent
- Catalog recommendations and real-time segmentation personalise messages without engineering or data-science support
Held against it
- Lead management scored 0–2, with no public information on lead scoring, qualification, routing or handover to sales
- No public information on frequency capping, suppression across journeys, or priority when one contact qualifies for several
- The privacy notice states data may be stored in any of the vendor's data centres around the world and transmitted to its San Francisco headquarters; sovereignty scored 1–2
- CRM and data scored 2–4, with no public information on a named CRM connector, field mapping, duplicate handling or API limits
- Consent and profiling scored 2–4, with no public information on consent timestamps per contact, per-channel consent states, retention per data category, or contesting automated decisions
Best for
- You run consumer lifecycle programmes — onboarding, win-back and loyalty journeys — across email, SMS and push from one profile
- Your team wants a no-code visual builder, with journeys documented as built, tested and updated without SQL or custom code
- Your SMS programme needs compliance tooling out of the box, from single-word opt-in confirmation to tracked opt-outs and quiet hours
- You want an assisted migration in which the vendor's team brings your data, schemas and user and event streams across
Avoid if
- You need documented lead scoring and routing into a sales pipeline — scored 0–2, with two judges declining to rate
- You must keep behavioural profiles of EU residents in the EU — the notice states data may be stored in any of the vendor's data centres around the world and transmitted to its San Francisco headquarters
- You need programme-level contact governance — the captured pages give no public information on frequency capping or competing journeys for the same contact
- Your implementation hinges on a documented CRM join — the integration ecosystem is described without naming any CRM, with no public information on field mapping or duplicate handling
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 3 of 5 |
| Lead scoring, routing & lifecycle | 1 of 5 |
| Channels & personalisation | 3 of 5 |
| Consent, tracking & profiling | 1.5 of 5 |
| CRM integration & data model | 1 of 5 |
| European sovereignty | 1 of 5 |
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Demand Gen Lead
A visual journey builder spanning email, SMS, push and in-app from a single studio is documented, with real-time behaviour triggers, journeys that pivot automatically when a user stalls, per-stage journey A/B testing, and per-individual optimisation of timing, content and channel. I found no public information on frequency capping, cross-journey suppression, priority when one contact qualifies for several journeys, or per-step reporting, so this is branching done well but not programme-grade orchestration. 3 6 8
The Sales Ops Manager
A visual journey builder covering email, SMS, push and in-app from a single studio, triggered by real-time behaviour with journeys that pivot when a user stalls, plus A/B testing at each workflow stage — that is real orchestration. What I could not find is the arbitration layer: nothing on waits, goals or exit conditions, frequency capping, or what happens when the same contact qualifies for two journeys at once, which is exactly where my pipeline reports start lying to me. 1 3 6 8
The Data Protection Officer
A visual journey builder spanning email, SMS, push and in-app is documented, with real-time behavioural entry, automatic pivots when a user stalls, and A/B testing of each workflow stage. However, we found no public information on frequency capping, suppression across journeys, or priority handling when one contact qualifies for several — the decision layer a DPO looks for when journeys decide what a named person receives. Journeys adapt 'in milliseconds', but what governs competing journeys for the same individual is undocumented. 3 5 6 8
The Lifecycle Marketer
The captured product pages show a visual journey builder with real-time behavioural entry — onboarding paths that pivot automatically when a user stalls, win-back triggered by disengagement signals, journeys triggered from SMS clicks and keyword replies — plus per-stage journey A/B testing and an agent that builds, tests and updates workflows without code. What I found no public information on is programme-level governance: frequency capping, suppression across journeys, or what happens when a contact qualifies for several journeys at once, so I cannot place it in the upper band. 3 5 6 8
The Solution Architect
The journeys pages document a visual builder running email, SMS, push and in-app from a single studio, entry from real-time behavioural signals and SMS clicks, automatic pivots when a user stalls, and A/B testing of each workflow stage. I found no public information on frequency capping, suppression across journeys, or what happens when one contact qualifies for several journeys at once — the conflict case that bites first in production. 3 6 8 5
The Skeptic
The captured product pages document a visual journey builder spanning email, SMS, push and in-app, with journeys triggered by real-time feature engagement, SMS clicks and keyword replies, automatic pivots when a user stalls, and A/B testing at each workflow stage. Nothing in the pages speaks to waits, goals or exit conditions, frequency capping, or what happens when a contact qualifies for several journeys at once, so the visual-builder level is where the evidence stops. 3 5 6 8
Lead scoring, routing & lifecycle
n/r
n/r
Show reasoningHide reasoning
How this is scored
Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
0 — No scoring, lifecycle or lead handling at all; the product is a sending tool for lists.
3 — A rule-based lead score from attributes or engagement, or lifecycle stages set by tags or fields.
5 — Configurable lead scoring on attributes and behaviour, lifecycle or pipeline stages, and qualified leads assigned or notified to sales.
8 — Multiple scoring models per product or region, negative scoring and score decay, account-level scoring alongside contact-level, routing rules to owners or teams with follow-up SLAs, and score history visible per contact.
10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.
The Demand Gen Lead not rated — no public information
We found no public information on lead scoring, qualification, routing or handover to sales on the captured pages; the nearest language is lifecycle journeys aimed at retention and long-term value, not at scoring a lead or routing it to a rep. I cannot score a sales-facing capability the public record does not show, and this is the criterion my own quarter lives or dies on. 3 4
The Sales Ops Manager
The pages document lifecycle marketing — onboarding, win-back and loyalty journeys keyed to engagement signals — but I found no public information on lead scoring, qualification stages, or rules routing a warm lead to a rep. Nothing here tells me how or whether a qualified contact ever reaches my CRM with a reason attached to it. 3
The Data Protection Officer
What the captured pages document is lifecycle marketing — onboarding, win-back and loyalty journeys triggered by engagement and disengagement signals. We found no public information on lead scoring, qualification, routing or handover to sales, and therefore nothing on score history or on explaining to an individual why the system decided what it decided about them. 3
The Lifecycle Marketer
Lifecycle shows up as journey patterns — onboarding, win-back and loyalty journeys that adapt over time — but I found no public information on lead scoring, qualification, routing rules or handover to sales in the captured pages. From a lifecycle standpoint the retention half is real; the lead and sales half is simply not evidenced. 3
The Solution Architect not rated — no public information
We found no public information on lead scoring, qualification or handover to sales: the captured pages, including the lifecycle engagement page, describe onboarding, win-back and loyalty journeys but no scoring models, routing rules or pipeline stages, and nothing a sales team could trace back to a lead. 4 3
The Skeptic
What the pages document is lifecycle journey marketing — onboarding paths triggered by real-time engagement and win-back journeys triggered by early disengagement — not lead management. No lead scoring, qualification, routing rules or handover to sales appears in anything captured, so a buyer cannot see how a qualified lead reaches a salesperson or how a score would be explained. 3
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
0 — Not a sending platform; the product cannot deliver messages on any channel.
3 — Email with merge-field personalisation, plus sign-up forms or landing pages.
5 — Email plus at least one further channel (SMS, push, or ad-audience sync) driven from the same contact profile, and dynamic content blocks based on contact data.
8 — Email, SMS and push from one profile with shared unsubscribe handling, on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.
10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.
The Demand Gen Lead
Email, SMS, push, in-app and web push are documented as delivered from one unified profile, with personalisation on behaviour and attributes through data feeds, handlebars, snippets and catalog-driven recommendations, plus immediately processed and tracked SMS opt-outs. We found no public information on ad-audience sync, cross-channel frequency capping or on-site content personalisation, which holds this below the top band. 2 5 6
The Sales Ops Manager
Five channels — email, SMS, push, in-app and web push — documented as running off one unified user profile, with behavioural personalization through Catalog and data feeds and AI optimization of timing, content and channel per individual. The gaps a buyer feels: no public information on ad-audience sync or cross-channel frequency capping, and the immediately processed and tracked opt-outs are documented for SMS specifically. 1 2 3 5 6 8
The Data Protection Officer
Five channels — email, SMS, push, in-app and web push — are documented as running from one unified user profile, with personalisation driven by actions and attributes via handlebars, data feeds and Catalog recommendations. We found no public information on ad-audience sync, cross-channel frequency capping, or unsubscribe handling shared across channels; the documented opt-in and opt-out processing is SMS-specific, and quiet hours are configured for SMS only. That places this above a basic multichannel setup but short of one governed suppression state across every channel. 2 3 5 6 8
The Lifecycle Marketer
Email, SMS and MMS, push, in-app and web push are all documented as driven from one real-time user profile, with personalisation from data feeds, Catalog recommendations and behavioural segmentation rather than merge fields alone, and vendor claims of per-individual channel and timing optimisation. I found no public information on ad-audience sync to the major networks, cross-channel frequency capping, or shared unsubscribe handling beyond immediately-processed SMS opt-outs, which keeps this in the middle band. 2 5 6 8
The Solution Architect
Email, SMS, push, in-app and web push are all documented as driven from one unified user profile, with personalisation on behaviour through Catalog, data feeds and real-time segmentation rather than stored fields alone. I found no public information on ad-audience sync or cross-channel frequency capping, and the cross-channel opt-in feature is marked coming soon, so unsubscribe handling is evidenced per channel rather than shared across channels. 2 6 5 8 1
The Skeptic
Email, SMS, push, in-app and web push are documented as delivered from one unified real-time profile, with behaviour-driven personalisation through data feeds, Catalog recommendations, snippets and AI decisioning that optimises timing, content and channel per individual. Ad-audience sync, on-site content personalisation, cross-channel frequency capping and shared unsubscribe handling across channels appear nowhere in the captured pages — quiet hours and immediately processed opt-outs are documented for SMS only. 2 3 5 6 8
Consent, tracking & profiling
Show reasoningHide reasoning
How this is scored
The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
0 — The vendor states a practice that defeats consent, such as importing purchased lists or tracking named contacts with no opt-in mechanism at all.
3 — Double opt-in available and unsubscribe handled per contact.
5 — Double opt-in with the consent timestamp and source stored per contact, consent or subscription status per channel, and a documented way to answer access and erasure requests.
8 — Consent reproducible as evidence with the wording versioned, tracking switchable per contact or a cookieless or first-party tracking mode, profiling suppressible per person, retention for inactive records stated and executed per data category, and erasure covering derived scores.
10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 DSGVO assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
The platform builds behavioural profiles of named people — a unified profile of interaction, behaviour and preference data plus over twenty trackable metrics — and documents confirmed SMS opt-in with opt-outs immediately processed and tracked. We found no public information on consent timestamps and source stored per contact, per-channel subscription status, retention for inactive records, or erasure covering derived scores, and at this volume of profiling that gap decides the level. 2 5 8
The Sales Ops Manager
Opt-outs are processed and tracked immediately for SMS with real compliance tooling, and the privacy notice commits to GDPR handling with a published subprocessor list. But this product profiles named individuals in real time and applies AI decisioning to every message, and I found no public information on double opt-in, consent timestamps stored per contact, retention for inactive records, or how a person contests a decision the model made about them. 1 2 5 8
The Data Protection Officer
SMS opt-in requests with automated single-word confirmation and immediate, tracked opt-out processing are documented, alongside a privacy notice acknowledging GDPR and UK GDPR scope, a DPO contact, SCCs and a published subprocessor list. We found no public information on consent timestamps or sources stored per contact, per-channel consent status, retention executed per data category, or erasure covering derived scores. For a platform performing real-time AI decisioning over unified behavioural profiles of named individuals, we found no public information that would let a DPO assess or contest those automated decisions under Art. 22. 1 2 5 8
The Lifecycle Marketer
For SMS the pages document automated single-word opt-in confirmation, dynamically included compliant opt-out language and opt-outs immediately processed and tracked, and the privacy notice commits to GDPR, explicit-consent-only special categories, SCCs and a DPO inbox. For what matters most to profiling of named people — consent timestamps and sources stored per contact, tracking switches, retention per data category, and contestable automated decisions — I found no public information, which is thin for a platform whose pitch is behavioural profiles in real time. 2 5 8
The Solution Architect
The SMS pages show opt-in requests with automated single-word confirmation and reply, compliant opt-out language, and opt-outs immediately processed and tracked, while the privacy notice covers GDPR scope and restricts special-category data to explicit consent. I found no public information on consent timestamp and source stored per contact, per-channel consent states, retention periods, or the ability to suppress profiling per person. 5 2 7
The Skeptic
For SMS, opt-in requests with automated single-word confirmation and reply, compliant opt-out language and immediately processed, tracked opt-outs are documented, and the privacy notice names a privacy contact, a DPO address and GDPR representatives in Dublin and Hampshire. But for a platform that centralises behavioural, preference and interaction data per named person in real time, the pages are silent on consent timestamps and source per contact, per-channel consent states, retention and any way to suppress profiling — and the AI that decides timing and channel per individual is not documented as automated decision-making a DPO could assess. 2 5 8
CRM integration & data model
Show reasoningHide reasoning
How this is scored
The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
0 — No way to get contact data in or out beyond typing it in.
3 — CSV import and export, and a sync or connector to a named CRM.
5 — Two-way sync with at least one major CRM (or a built-in CRM) with field mapping, duplicate handling, and a documented API.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry and an error log, and API rate limits documented.
10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.
The Demand Gen Lead
Documented: real-time capture into a unified profile from the martech ecosystem, a plug-and-play integration ecosystem, and assisted migration of data, schemas and user and event streams. No captured page names a CRM connector, a sync direction, field mapping, duplicate handling or an API with rate limits — the join that decides the implementation is claimed, not documented. 6 8
The Sales Ops Manager
A unified user profile centralizing demographic, interaction, behaviour and preference data is documented, along with assisted migration that brings in data, schemas and user and event streams, and an integration ecosystem described without naming any CRM. I found no public information on field mapping, duplicate handling, configurable conflict resolution, sync error logs or API rate limits — the join to my CRM of record is entirely undocumented on these pages, and that is the part that decides my implementation. 1 8
The Data Protection Officer
The captured pages document a unified user profile capturing demographic, interaction, behaviour and preference data in real time, assisted migration of data, schemas and event streams, and an unnamed 'ecosystem of integrations'. We found no public information on a connector to a named CRM, field mapping, duplicate handling, conflict resolution per field, or documented API rate limits — the join that decides how two systems agree on who a person is, and what happens when they disagree, is not evidenced. 8
The Lifecycle Marketer
The documented story is a unified user profile capturing demographic, interaction, behaviour and preference data in real time, fed from the wider martech ecosystem, with expert-led migration of data, schemas and existing user and event streams. I found no public information on a named CRM connector, field mapping, duplicate handling, conflict resolution or documented API limits — the join that decides the implementation is left open. 8
The Solution Architect
The centralized-data pages describe a unified user profile capturing demographic, interaction, behaviour and preference data in real time, an assisted migration that brings data, schemas and user and event streams across, and a plug-and-play integration ecosystem. No named CRM sync, field mapping, duplicate or conflict handling, custom objects or documented API rate limits appear in the captured pages, and the migration is led by the vendor's own team — the opposite of a data model the customer extends without vendor services. 8
The Skeptic
The data page offers an unnamed plug-and-play ecosystem of integrations and a vendor-led migration that brings data, schemas and event streams into a flexible data environment. No named CRM connector, two-way sync, field mapping, duplicate handling or API documentation appears in the captured pages, so the join that decides an implementation — how the platform and the CRM agree on who a person is — is not documented. 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily. Dimensions the sources do not establish are unknown, not non-EU.
0 — Proven non-EU: a non-EU vendor and contracting entity with hosting and tracking stated outside the EU.
3 — One European element proven — an EU contracting entity or EU data residency stated — with the rest of the chain undocumented.
5 — An EU contracting entity and EU hosting both stated, and a data processing agreement offered.
8 — EU hosting on named infrastructure, EU contracting entity, a subprocessor list published with locations, and any non-EU processing (tracking, AI scoring, support access) named with its legal basis.
10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.
The Demand Gen Lead
The contracting vendor is Iterable, Inc. of San Francisco; the privacy notice states personal data may be stored in any of its data centres around the world and is transmitted to the US, with the Data Privacy Framework and SCCs as the safeguards. Irish and Portuguese service entities and a published subprocessor list exist, but the captured notice does not establish which entity contracts or that any processing stays in the EU — for behavioural profiles of named EU residents, that is not a chain I can sign off on. 1 2
The Sales Ops Manager
European entities exist — Iterable, Ireland and a Lisbon entity — but the captured pages do not establish which one contracts with the customer, and they state that personal data may be stored in secure data centres around the world and transmitted to the San Francisco headquarters under the Data Privacy Framework. I found no EU data residency commitment and no processing agreement on the vendor's own pages, and for a platform profiling named EU residents that is a chain my DPO will want documented before signature. 1 2
The Data Protection Officer
European entities are named — Iterable, Ireland and a Lisbon entity responsible for services and the EU site — but the captured notice does not say which entity a European customer contracts with. Storage is stated as 'secure data centres around the world' with personal data stored 'in any one of them', transfers to the San Francisco headquarters are named, and the transfer safeguards offered are the Data Privacy Framework and Standard Contractual Clauses — precisely the Schrems II analysis a buyer holding behavioural profiles must survive. We found no public information on EU hosting options, and no data processing agreement confirmed on the vendor's own captured pages. 2
The Lifecycle Marketer
The privacy notice states personal data may be transmitted outside the UK and EEA to the San Francisco headquarters, that data may be stored in any of its data centres around the world, and relies on the Data Privacy Framework and SCCs; UK, Irish and Portuguese entities are listed and a subprocessor list is published, but the captured excerpt does not establish which entity is the contracting counterpart. With no EU residency or hosting commitment evidenced, this is not a chain I can treat as European for profiles of EU residents — and I weigh that heavily. 2
The Solution Architect
The privacy notice names a San Francisco headquarters that receives personal data and says data may be stored in any of its data centres around the world, with reliance on the Data Privacy Framework and Standard Contractual Clauses for transfers. Irish, UK and Portuguese entities appear, but the captured pages do not establish which entity is the contracting counterpart or where behavioural profiles are actually hosted, so non-EU processing is on the table rather than ruled out. 2 1
The Skeptic
The vendor is Iterable, Inc. of San Francisco; the notice names three controllers across England, the US and Ireland without saying which one contracts, states that servers sit in secure data centres around the world with personal data possibly stored in any of them, and says data is transmitted outside the UK and EEA to the San Francisco headquarters under the EU-U.S. Data Privacy Framework. EU entities in Dublin and Lisbon and a Dublin GDPR representative exist, but no EU hosting, residency commitment or published processing agreement is established — for profiles of named EU residents this chain leans on a Schrems II argument rather than on sovereignty. 1 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or a single tier with its contact limit.
5 — Prices per tier public with the billing period and contact limits stated, and which tier includes automation visible.
8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.
The Demand Gen Lead
The captured pages speak of a "simplified pricing structure, usage reports, transparent invoicing" and a paid SMS Strategy Package, but give no figures — no tier prices, contact limits, billing periods, or the tier where automation begins. A real annual invoice is not computable from the public pages; every number is a sales conversation. 5
The Sales Ops Manager
No price figures appear on the captured pages — the only pricing facts are a claim of a "simplified pricing structure, usage reports, transparent invoicing" and a paid SMS Strategy Package whose cost is not stated. A buyer cannot begin to estimate an annual invoice from this, and I could not even tell which tier automation starts in. 5
The Data Protection Officer
The only pricing statements on the captured pages are qualitative — 'simplified pricing structure, usage reports, and transparent invoicing' — plus a paid SMS Strategy Package whose price is not stated. We found no public price figures, tier contact limits, overage terms or onboarding costs on the captured pages, so a buyer cannot compute an annual invoice from what we read. 5
The Lifecycle Marketer
No price figure of any kind appears on the captured pages — no tiers, contact limits, send volumes or starting price — and the only pricing facts are a claim of a 'simplified pricing structure' and 'transparent invoicing' plus a 'Paid SMS Strategy Package' whose cost is not stated. A buyer cannot begin to compute an annual invoice from what I read. 1 5
The Solution Architect
The SMS pages advertise a simplified pricing structure, usage reports and transparent invoicing, plus a paid SMS Strategy Package, but publish no tier prices, contact limits, billing period or the tier where automation begins. We found no public figures on the captured pages from which a buyer could compute an annual invoice. 5
The Skeptic
No price figure, tier, contact limit or overage rate appears in any page captured, and the only pricing language is a claim of a simplified pricing structure and transparent invoicing plus a paid SMS Strategy Package with personalized plans. A personalized plan is a sales conversation; the tier where automation begins and any mandatory services fee cannot be read from anything captured. 1 5
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in US ⚠ unverified | 0/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Iterable
Is Iterable European?
Not determined: the vendor’s pages as captured do not say where Iterable is based. Its vendor, Iterable, Inc., is incorporated in United States, per the vendor’s page captured 3 Nov 2026.
Where does Iterable store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Iterable have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Iterable?
As of 3 Nov 2026, the panel rates Braze (3/5), HubSpot Marketing Hub (3/5) and ActiveCampaign (Automation) (3/5) highest among the other 18 Marketing Automation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Evalanche (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Iterable alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The privacy notice lists three controllers across three countries (Iterable, Ltd. in England and Wales, Iterable, Inc. in the US, and an Ireland-located entity whose name is cut off), and the excerpt does not say which entity is the contracting counterpart.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 6 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page iterable.com Checked 3 Nov 2026 Details →
- 2 Legal notice — found from the homepage iterable.com Checked 3 Nov 2026 Details →
- 3 Journeys & orchestration — found from sitemap iterable.com Checked 3 Nov 2026 Details →
- 4 Lead scoring, routing & lifecycle — found from sitemap iterable.com Checked 3 Nov 2026 Details →
- 5 Channels & personalisation — found from sitemap iterable.com Checked 3 Nov 2026 Details →
- 6 Channels & personalisation — found from sitemap iterable.com Checked 3 Nov 2026 Details →
- 7 Consent, tracking & profiling — found from sitemap iterable.com Checked 3 Nov 2026 Details →
- 8 CRM integration & data model — found from sitemap iterable.com Checked 3 Nov 2026 Details →