Marketing Automation
Encharge
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Ench Corp. (Encharge) · encharge.io
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
No written verdict for this product
The panel scored Encharge, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
The scores
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, and — the part that decides whether it survives contact with reality — what happens when journeys collide.
0 — Autoresponders on a single trigger; no branching, no waits, no conditions.
3 — Linear sequences with simple conditions, one entry trigger per journey, and no visibility into where a contact currently sits.
5 — A visual builder with branching on attributes and behaviour, waits and goals, entry and exit conditions, and per-contact journey state visible.
8 — Event-driven entry from external systems, frequency capping and suppression across journeys, priority when a contact qualifies for several, versioning 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 a journey a colleague can read months later without a diagram.
The Demand Gen Lead
Drag-and-drop flows with 100+ triggers and actions, behaviour-based segments on pageviews and product events, and real-time per-person activity views give me branching on behaviour plus visibility into where a contact actually sits — and trial-expiration automation off Stripe and Chargebee shows entry from external events. What I found no public information on is the part that decides whether journeys survive contact with reality: frequency capping, suppression across journeys, or versioning of a live journey. 1
The Sales Ops Manager
A drag-and-drop flow builder with 100+ triggers and actions, A/B testing on flows and emails, and per-user activity history gets partway to real orchestration. But the captured pages show nothing on branching, waits, entry and exit conditions, or what happens when journeys collide — for a product whose pitch is flows, that silence is the finding. 1
The Data Protection Officer
A drag-and-drop builder for flows and automations, more than a hundred triggers and actions, behaviour-based segmentation and A/B testing of flows are all evidenced, which sits between the linear-sequence and visual-builder levels. What I care about most — being able to see where an individual currently sits — is partially supported by real-time user profiles with full activity history. I found no public information on waits, goals, entry and exit conditions, frequency capping, or what happens when journeys collide. 1
The Lifecycle Marketer
A drag-and-drop flow builder with 100+ triggers and actions, A/B testing on flows, and behaviour-based segmentation is a real step past linear sequences, and real-time profiles show every action a user has taken. We found no public information on waits and goals, entry and exit conditions, or where a contact currently sits in a journey. Nothing is evidenced on frequency capping, suppression, priority, or holdout measurement when several journeys want the same person. 1
The Solution Architect
A drag-and-drop builder for flows and complex automations, 100+ triggers and actions, and A/B testing on both emails and flows is genuine orchestration territory. But the page stops at the builder: we found no public information on waits, goals, entry and exit conditions, or where a contact currently sits in a flow — and nothing on what happens when two flows claim the same person, which is the part that decides whether this survives contact with reality. 1
The Skeptic
A drag-and-drop builder for flows with one hundred-plus triggers and actions is evidenced, and real-time profiles show every action a person has taken, which is more than an autoresponder. But we found no public information on branching conditions, waits, entry and exit rules, or what happens when a contact qualifies for several journeys — the parts that decide whether automation survives contact with reality. 1
Lead scoring, routing & lifecycle
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 or lifecycle model; every contact is treated alike.
3 — A single additive score with fixed rules, no decay, no lifecycle stages and no routing.
5 — Configurable scoring on attributes and behaviour with decay, lifecycle stages, and routing to owners or teams with notification.
8 — Multiple scoring models per product or region, negative scoring, account-level scoring alongside contact-level, SLA on follow-up, 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
The closest thing in the captured pages is copy about nurturing leads into sales opportunities. We found no public information on lead scoring, lifecycle stages, decay, or routing to owners — I would be handing reps leads on trust with nothing to explain why the system decided what it decided. 1
The Sales Ops Manager
"Nurture leads into sales opportunities" is the whole of it, and that is marketing copy, not a model. I found no public information on scoring, decay, lifecycle stages, routing or handover, so there is nothing here that tells a rep why one lead ranks above another or who owns it next. 1
The Data Protection Officer
Lead nurturing and behaviour-based segmentation are on the page, but I found no public information on lead scoring, lifecycle stages, decay, routing to owners, or score history. For a platform built on profiling named users, there is nothing documented on scoring that I could even begin to assess as automated decision-making. 1
The Lifecycle Marketer
Lead nurturing and automated trial-expiration emails hint at lifecycle touches, but we found no public information on lead scoring, decay, lifecycle stages, or routing and handover to sales. A buyer cannot see from these pages how a person is qualified or why they received a given treatment. 1
The Solution Architect
Beyond 'nurture leads into sales opportunities' marketing copy, we found no public information on lead scoring, lifecycle stages, score decay, or routing to owners or teams. Behavior-based segmentation could feed a scoring model, but no model is evidenced on the captured page. 1
The Skeptic
We found no public information on scoring, decay, lifecycle stages, routing, or score history; the closest evidence is a lead-nurturing tagline and behavior-based segmentation, which is targeting, not scoring. 1
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can actually send and personalise: email, SMS, push, on-site content, ads audiences — judged on what shares one profile and one suppression list.
0 — Email only.
3 — Email plus one further channel, managed separately with its own list and no shared suppression.
5 — Email, SMS or push and web forms driven from one contact profile, with dynamic content blocks and shared unsubscribe handling.
8 — The above plus 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 is the only sending channel evidenced, and it is serious email — SendGrid delivery, daily monitoring against 86 blacklists, A/B testing on emails and flows. Facebook Ads appears in an integrations list with no stated function, and we found no public information on SMS, push, on-site personalisation, or ad-audience sync, let alone shared suppression across channels. 1
The Sales Ops Manager
Email is the only evidenced outbound channel — deliverability, blacklists and reputation are all the pages discuss. Facebook Ads and Intercom appear as one-click integrations, but the pages never say they act as send channels or share one profile and suppression list, and I found no public information on SMS, push or on-site personalisation. 1
The Data Protection Officer
Email is the only sending channel the captured page evidences; tracking of pageviews and in-product behaviour feeds segmentation rather than delivering messages. Facebook Ads and Intercom appear as one-click integrations with no statement of what they synchronise, and I found no public information on SMS, push, on-site content, ad-audience export, or shared suppression across channels. 1
The Lifecycle Marketer
Email is clearly the core of the platform — A/B emails, managed deliverability, monitoring against 86 blacklists. A Facebook Ads integration appears among the one-click integrations, but we found no public information on SMS, push, on-site content, or ad-audience sync, and equally no public information on one suppression list shared across channels. 1
The Solution Architect
Email is clearly the core — deliverability run through SendGrid with daily checks against 86 blacklists — and Facebook Ads appears among the 48+ one-click integrations, though the page does not describe what that integration does. Behavior-based segmentation on pageviews implies web tracking, but we found no public information on SMS, push, web forms, on-site personalisation, ad-audience sync, or shared suppression across channels. 1
The Skeptic
Email is the only sending channel the captured page evidences, from SendGrid delivery to blacklist monitoring and A/B emails. Behavioral tracking of pageviews and product use is profiling, not a channel, and the Facebook Ads entry is a name in an integration list rather than evidence of ad-audience sync; we found no public information on SMS, push, on-site content, or additional channels sharing one profile and suppression list. 1
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 — Tracking always on and undocumented, single opt-in, no consent record, no retention rule, no way to exclude a person from profiling.
3 — Double opt-in available with a timestamp, cookie tracking that cannot be disabled per contact, and retention described as the customer's problem.
5 — Double opt-in as documented default with a stored consent record including source, per-channel consent states, tracking switchable per contact, and stated retention for inactive records.
8 — Consent reproducible as evidence with the wording versioned, profiling suppressible per person, retention executed per data category, documented handling of access and erasure requests including derived scores, and a cookieless or first-party tracking mode.
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 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
Profiling named people is the product's engine — pageviews, product behaviour, feature use, real-time profiles with full activity history — yet the only consent evidence is that a GDPR page exists. We found no public information on stored consent records with source, per-channel states, retention for inactive records, or any way to switch off tracking for an individual. 1
The Sales Ops Manager
The product's core is real-time behavioural profiles of named users — pageviews, feature use, email opens — yet the only consent evidence is that a GDPR page exists, with no content captured from it. I found no public information on double opt-in defaults, stored consent records, per-contact tracking switches or retention, which is thin for this much profiling. 1
The Data Protection Officer
The product's core proposition is behavioural profiling of identified people — real-time user profiles with pageviews, product behaviour, feature use, email activity and third-party data — and the only consent-related evidence is that a GDPR page exists, with its contents unpublished. I found no public information on double opt-in, stored consent records with source, per-channel consent states, a per-contact tracking switch, retention rules, or handling of access and erasure requests including derived scores. Nothing here would let me reproduce consent for a single person, switch off tracking for someone who never agreed to it, or assess automated decisions under Article 22. 1
The Lifecycle Marketer
Real-time behavioural profiles of named users — pageviews, product behaviour, feature use, email activity — are the product's stated heart, yet the only consent evidence is that a GDPR page exists. We found no public information on consent records with source and timestamp, per-channel consent states, per-person tracking switches, retention rules, or handling of access and erasure requests. Given how deep the profiling goes, that weighs heavily in how I score it. 1
The Solution Architect
The product's premise is behavioural profiles of named people — real-time user profiles, pageviews, product behaviour, feature use — yet the only consent evidence is a GDPR page whose contents the capture does not show. We found no public information on stored consent records with source, per-channel consent states, per-contact tracking switches, retention for inactive records, or suppression from profiling. 1
The Skeptic
The core product is behavioral profiles of named people — pageviews, feature use, email activity, third-party attributes — assembled in real time, while the GDPR page exists by title only. We found no public information on consent records with source, per-contact tracking switches, retention rules, or the handling of access and erasure requests for derived data. 1
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 — CSV import and export; no CRM integration and no identity resolution.
3 — One-way sync into a named CRM on a schedule, with duplicates resolved by hand and no conflict rules.
5 — Bidirectional sync with at least one major CRM, field mapping, deduplication rules, and a sync error log somebody can act on.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry, and a documented API with rate limits.
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
The join exists in raw form: one-click integrations with HubSpot and Salesforce among 48+ native tools, Segment in the list, and public API and developer docs. We found no public information on sync direction, field mapping, deduplication rules, conflict resolution, or a sync error log somebody on my team could act on when the two systems disagree about who a person is. 1
The Sales Ops Manager
HubSpot and Salesforce ship as native one-click integrations alongside API and developer docs, which clears the bar of a real CRM connection. But every question that decides my week — sync direction, field mapping, deduplication rules, field-level ownership when both systems write, and whether any sync error log exists — has no public information behind it, so I have to assume duplicates land on my desk. 1
The Data Protection Officer
One-click native integrations with HubSpot, Salesforce and Segment, plus published API and developer documentation, evidence genuine CRM connectivity above simple import. I found no public information on sync direction, field mapping, deduplication rules, conflict handling, or a sync error log somebody can act on, so how the two systems stay in agreement about who a person is cannot be judged from public pages. 1
The Lifecycle Marketer
One-click integrations with HubSpot and Salesforce, a Segment pipe, and public API and developer documentation put this comfortably above CSV hand-offs. We found no public information on sync direction, field mapping, deduplication rules, conflict resolution, or identity resolution between anonymous and known states. 1
The Solution Architect
HubSpot and Salesforce appear among the native one-click integrations and public API documentation exists, which clears the CSV-only floor. We found no public information on sync direction, field mapping, conflict resolution, deduplication rules, custom objects, or documented rate limits — the joins that decide whether a two-system implementation holds together — and nothing on the path from anonymous visitor to known contact. 1
The Skeptic
Native one-click integrations with HubSpot and Salesforce, plus documented API and developer docs, put this above a CSV handoff. We found no public information on sync direction, field mapping, deduplication rules, conflict handling, or a sync error log somebody can act on — the join that decides the implementation. 1
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.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed, behavioural data leaving the EU with no stated basis.
3 — EU data residency for storage while tracking, sending or support access remain non-EU, or the contracting entity sits outside the EU.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — tracking scripts, AI scoring, analytics — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, and any non-EU processing 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 entity is a Florida LLC and the delivery chain is stated as SendGrid and AWS with no hosting region given, while the product's whole value is behavioural profiles of named people. A GDPR page exists; we found no public information on EU data residency, a published subprocessor list, or any stated basis for transfers — given what this platform profiles, that weighs heavily. 1
The Sales Ops Manager
The contracting entity is PXCH Holding I, LLC of Miami, and the platform runs on AWS with SendGrid delivery, with no EU residency claim, subprocessor list or transfer basis anywhere on the captured pages. Given the product is behavioural profiling of named people, I found no public information on where profiles and events are processed or under what safeguards. 1
The Data Protection Officer
The contracting entity is PXCH Holding I, LLC of Miami, Florida, and email delivery runs on SendGrid with AWS, with no hosting region stated, no subprocessor list published, and no stated basis for transfers. Behavioural profiles of named EU residents would sit with a US contracting entity and US delivery infrastructure with no published safeguard, and there are no sovereignty attributes on record; the naming of AWS and SendGrid is the only step above an entirely opaque chain. 1
The Lifecycle Marketer
The contracting entity is PXCH Holding I, LLC of Miami, Florida, and the infrastructure is stated as SendGrid plus AWS with no processing region given. For behavioural profiles of named EU residents, we found no public information on EU hosting, a published subprocessor list, or the legal basis for any transfer. 1
The Solution Architect
The contracting entity is PXCH Holding I, LLC of Miami, Florida, hosting is on AWS with no region given, and email delivery runs through SendGrid. For behavioural profiles of named EU residents the captured page offers no EU residency claim, no subprocessor list, and no stated legal basis for transfer. 1
The Skeptic
The contracting entity is PXCH Holding I, LLC in Miami, with infrastructure named as AWS and SendGrid and no processing region stated for either. We found no public information on EU hosting, a subprocessor list, or a legal basis for European profiles leaving the EU — and for a platform whose product is profiling named users, that weighs heavily. 1
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, and onboarding fees are never mentioned.
3 — A contact-tier headline exists, but the tier where journeys, scoring or CRM sync begin is unstated, as is any mandatory implementation fee.
5 — Contact-tier prices public with billing period and send limits stated, but at least one commonly needed capability sits in an unpriced enterprise tier.
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 only price signal is a free-start claim, and the migration and done-for-you onboarding premium plans are named without any figures. We found no public information on contact-tier prices, send limits, overage rates, or minimum term — nobody can compute a real annual invoice from public pages. 1
The Sales Ops Manager
The only pricing signal on the pages is "Get Started — It's Free"; no contact tiers, billing periods or send limits are shown. Onboarding and migration exist as named premium plans with no figures attached, so a buyer cannot compute anything close to a real invoice from what is published. 1
The Data Protection Officer
A "Get Started — It's Free" claim and two named premium plans — Done-for-you Onboarding and Migration — are the entire public pricing picture, with no figures stated for any of them. I found no public information on contact-tier prices, billing periods, send limits, which tier automation or CRM sync begins in, or the cost of the premium plans, so a buyer cannot begin to compute an annual invoice. 1
The Lifecycle Marketer
The only public pricing signal is a "Get Started — It's Free" claim; no contact tiers, send limits, billing period, or overage rates are published. Onboarding and migration appear as unpriced "Premium Plans". A buyer cannot compute even an approximate annual invoice from public pages alone. 1
The Solution Architect
The only pricing signal is 'Get Started — It's Free', with onboarding and migration offered as Premium Plans whose prices are not given. No tier prices, contact or send limits, overage rates, or VAT treatment appear on the captured page, so a buyer cannot compute an annual invoice from public information. 1
The Skeptic
The only pricing signal is "Get Started — It's Free"; there is no contact-tier ladder, no send limits, no billing period, no VAT treatment, and no overage rates, so no invoice can be computed from public pages. Meanwhile onboarding and migration are sold as unpriced Premium Plans, and the buyer cannot tell whether the hands-on setup is optional or a hidden cost of starting. 1
European sovereignty — proven facts
0 of 4 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Sep 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 residency, Subprocessors, Legal entity. Not confirmed on the vendor’s own pages as captured.
- 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.
- 18 compliance 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
- 12 legal 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
- 8 pricing 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
- 7 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
- 6 subprocessors 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
- 2 data 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
- 2 hosting 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 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page encharge.io Checked 29 Sep 2026 Details →
- 2 Terms of service — found from the homepage encharge.io Checked 30 Sep 2026 Details →
- 3 Security / trust page — found from the homepage gdpr.encharge.io Checked 30 Sep 2026 Details →
- 4 Journeys & orchestration — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 5 Journeys & orchestration — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 6 Lead scoring, routing & lifecycle — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 7 Lead scoring, routing & lifecycle — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 8 Channels & personalisation — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 9 Channels & personalisation — found from sitemap help.encharge.io Checked 1 Oct 2026 Details →
- 10 Consent, tracking & profiling — found from sitemap encharge.io Checked 1 Oct 2026 Details →
- 11 Consent, tracking & profiling — found from sitemap help.encharge.io Checked 1 Oct 2026 Details →
- 12 CRM integration & data model — found from sitemap help.encharge.io Checked 1 Oct 2026 Details →
- 13 CRM integration & data model — found from sitemap docs.encharge.io Checked 1 Oct 2026 Details →