Marketing Automation
Acoustic Campaign
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Acoustic · www.acoustic.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.
Acoustic Campaign at a glance
- Vendor
- Acoustic
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Acoustic Campaign 1.5/5, the mean of 6 judges. Acoustic Campaign (vendor Acoustic; flagship platform Acoustic Connect) scores highest on channel coverage, 6-7, and journey orchestration, 4-5: email, SMS, WhatsApp and mobile compose in one shared drag-and-drop editor off a single real-time 360° profile, and an email opt-out reroutes the next message through WhatsApp. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Acoustic Campaign (vendor Acoustic; flagship platform Acoustic Connect) scores highest on channel coverage, 6-7, and journey orchestration, 4-5: email, SMS, WhatsApp and mobile compose in one shared drag-and-drop editor off a single real-time 360° profile, and an email opt-out reroutes the next message through WhatsApp. It scores weakest on lead management, 1-2 — the positioning is explicitly B2C, aimed at retail and ecommerce, financial services, travel and hospitality, media and entertainment, and judges found no public information on lead scoring, qualification stages or handover to sales — and on sovereignty, 0-1, where no hosting location, contracting entity or subprocessor list is on record while the vendor's cookie policy names Google and DoubleClick among third-party partners. Consent and profiling sits at 3-4: journeys honour real-time consent, but the only tracking documentation is the vendor's cookie policy — pixels, cross-device linking, remarketing. The widest spread, CRM and data at 2-4, pits documented identity resolution against an undocumented CRM join. Persona-weighted verdicts run 2.6 to 4.2; no prices appear on any page the bench reviewed.
Speaks for it
- Email, SMS, WhatsApp and mobile run from one real-time 360° profile and a shared drag-and-drop editor — channel coverage scores 6-7
- An email opt-out automatically routes the next message through WhatsApp, so consent state is shared across channels rather than per-channel
- The drag-and-drop journey canvas supports triggers and branching logic, with segments narrowed, expanded or moved between lifecycle paths mid-campaign
- Anonymous activity is captured early and applied once identity is known, feeding a real-time unified profile with identity resolution
- Real-time segments keyed on churn-risk, fatigue and in-market signals update automatically as behaviour changes
Held against it
- Lead management scores 1-2 — positioning is Built for B2C and judges found no public information on lead scoring, qualification stages, routing to owners or sales handover
- Judges found no public information on any named CRM connector, field mapping, bidirectional sync or documented API, and audience structure is sold as a professional-services engagement
- No sovereignty attributes are on record — judges found no public information on hosting location, contracting entity or subprocessors
- No public information on cross-journey suppression, frequency capping or priority when several journeys want the same contact
- The cookie policy documents email tracking pixels, cross-device linking and Google remarketing, and judges found no public information on a per-contact switch for that tracking
Best for
- You run B2C retention and lifecycle programmes in the industries named on the pages — retail and ecommerce, financial services, travel and hospitality — and need behaviour-triggered multi-step journeys you can adjust mid-campaign
- You want one consent-aware channel stack where email, SMS, WhatsApp and mobile share a single real-time profile, one editor and one consent state
- Your personalisation must run on live behaviour — SKU-level browsing, churn-risk and in-market segments — rather than stored fields alone
Avoid if
- You need lead scoring, qualification stages and routing to sales owners — lead management scores 1-2 and the pages are positioned Built for B2C
- Your implementation depends on a documented CRM integration — a named connector, field mapping and sync rules — rather than a professional-services build
- Your procurement cannot proceed without a hosting location, contracting entity or subprocessor list on record
- You need cross-journey collision handling — suppression, frequency capping, priority — evidenced before committing to a live programme
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 2.5 of 5 |
| Lead scoring, routing & lifecycle | 1 of 5 |
| Channels & personalisation | 3 of 5 |
| Consent, tracking & profiling | 2 of 5 |
| CRM integration & data model | 1.5 of 5 |
| European sovereignty | 0 of 5 |
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
The drag-and-drop journey canvas with behavioural triggers and branching that reacts to real-time actions is the level of branching I need, and multi-step upsell campaigns that re-route on behaviour plus mid-flight segment changes show it working on live programmes. I found no public information on waits and goals, on seeing where a contact currently sits in a journey, or on capping, suppression and priority when several journeys want the same person — which is what survives contact with a real programme. 3 4 5 8
The Sales Ops Manager
The drag-and-drop journey canvas with triggers, branching logic and multi-step behavioral campaigns is documented, and segments can be narrowed or moved between lifecycle paths mid-campaign, but we found no public information on waits, per-contact journey state, or suppression, frequency capping and priority when a contact qualifies for several journeys. Consent-based channel prioritization chooses a delivery channel, not a winning journey, so the collision question stays unanswered. 3 4 5 8
The Data Protection Officer
A drag-and-drop journey canvas with branching that reacts to every action, behavioural triggers and multi-step campaigns that re-target mid-flight is a genuine step above linear sequences. We found no public information on waits, entry and exit conditions, where a contact currently sits in a journey, or what happens when two journeys want the same person, so the collision-handling core of this criterion stays unevidenced. 3 5 8
The Lifecycle Marketer
A drag-and-drop journey canvas with behavioural triggers, branching logic and multi-step campaigns is confirmed, and audiences can even be moved between lifecycle paths mid-campaign. But I found no public information on waits and goals, entry and exit conditions, per-contact journey state, frequency capping across journeys, versioning of a live journey or holdout groups — the collision handling and measurement layer that decides whether a programme survives contact with reality. 3 4 5 8
The Solution Architect
The drag-and-drop journey canvas with triggers and branching logic, behavioral triggers, and the ability to narrow or expand audiences mid-campaign are real and documented. What I could not find is anything on waits, entry and exit conditions, per-contact journey state, or the part that decides survival: what happens when a contact qualifies for several journeys — no frequency capping, suppression across journeys, priority, or live-journey versioning is shown. 3 4 5 8
The Skeptic
A drag-and-drop journey canvas with triggers, branching logic and behavior-triggered multi-step campaigns is documented, and the ability to narrow a segment mid-campaign or move people between lifecycle paths shows live management. But we found no public information on waits, goals, entry and exit conditions, or visibility into where a contact currently sits — and nothing on cross-journey suppression, priority between competing journeys, or versioning of a live journey. 3 4 5 8
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
This is a platform that profiles named people in real time, yet I found no public information on lead scoring, decay, negative scoring, qualification stages, or routing to a sales owner with any follow-up commitment. The lifecycle language that does exist — loyalty and advocacy, churn-risk segments, consumers moved between lifecycle paths — is marketing-funnel work, not a score a rep can act on. 3 8
The Sales Ops Manager
This is a B2C platform whose pages treat contacts as audience segments; we found no public information on lead scoring, score decay, lifecycle stages or routing to sales owners. The churn-risk and in-market indicators are audience logic, not a qualification model a rep can explain or act on. 3 8
The Data Protection Officer
Lifecycle-flavoured segmentation is documented — churn-risk and fatigue indicators, segments that adapt to the consumer lifecycle — but we found no public information on a scoring model, decay, routing to owners or score history per contact. Nothing documents how those behavioural indicators are computed for an individual, which is exactly what I would need to assess them as automated decision-making. 3 8
The Lifecycle Marketer
Contacts are not treated alike — real-time segments carry churn-risk and fatigue indicators, and consumers can be moved between lifecycle paths — but this is consumer retention, not lead management. I found no public information on lead scoring, qualification stages, routing to owners or sales handover, and nothing on whether a score's signals are explainable per record. 3 8
The Solution Architect
The behavioral segments — churn-risk attributes, fatigue index — are campaign targeting, not lead management, and the positioning is explicitly B2C with no sales handover in sight. We found no public information on scoring models, decay, lifecycle stages with handover, routing to owners, or score history per contact, so there is no way for a customer to explain a decision the system made about a person. 8 1 3
The Skeptic
This is built and marketed for B2C — retail, financial services, travel, gaming — and the only lifecycle language is consumer lifecycle paths and churn-risk segments. We found no public information on lead scoring, score decay, qualification stages, routing to owners, or handover to sales, so a buyer cannot assess this dimension at all. 1 3 8
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, SMS, WhatsApp and mobile hang off one real-time profile whose consent state updates the moment a signal occurs, with consent-based channel prioritization routing around opt-outs — that is one profile and one consent state across channels — and personalisation runs on behaviour like play history, spend patterns and SKU-level intent rather than stored fields alone. I found no public information on on-site personalisation, ad-audience sync to the major networks, or cross-channel frequency capping beyond a fatigue-index segment. 3 4 8 9
The Sales Ops Manager
Email, SMS, WhatsApp and mobile are composed in one editor and driven from one real-time profile, with journeys rerouting across channels on consent and personalisation drawing on live behavior and catalog data rather than stored fields alone. We found no public information on on-site personalisation, ad-audience sync to the major networks, or cross-channel frequency capping. 3 4 5 8 9
The Data Protection Officer
Email, SMS, WhatsApp and mobile are documented as composed in one shared editor and driven from one real-time profile whose consent state updates as signals occur, with routing that follows per-channel consent. Personalisation draws on behaviour — play history, real-time intent signals — rather than stored fields alone. We found no public information on on-site personalisation, ad-audience sync as a product capability, or cross-channel frequency capping beyond a fatigue indicator used in segments. 3 4 5 8 9
The Lifecycle Marketer
Email, SMS, WhatsApp and mobile share one drag-and-drop editor, one real-time 360° profile and consent-based channel routing, and personalisation draws on the behavioural record — SKU-level browsing, fatigue index, real-time intent segments — rather than only stored fields. I found no public information on on-site personalisation, ad-audience sync to the major networks, web forms, or cross-channel frequency capping. 1 4 5 8 9
The Solution Architect
Email, SMS, WhatsApp and mobile run from one real-time profile with a shared editor, and the consent-based channel routing — opt out of email, the journey sends WhatsApp — tells me consent state is shared rather than per-channel siloed. Personalisation on behavior, visit frequency and spend patterns is evidenced, not just stored fields; we found no public information on on-site personalisation, ad-audience sync to the major networks, or cross-channel frequency capping. 4 9 5 8
The Skeptic
Email, SMS, WhatsApp and mobile are driven from one unified profile with a shared editor, and consent-based routing means an email opt-out automatically moves the next message to WhatsApp — a genuinely shared suppression state rather than per-channel lists. Personalisation runs on behaviour (play history, real-time intent, in-market signals), but we found no public information on on-site personalisation, ad-audience sync to the major networks, or cross-channel frequency capping; the fatigue index appears only as a segment attribute. 3 4 8 9
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
Consent-based routing and a profile that updates consent in real time are real, and anonymous activity is folded into known profiles on identification — which makes the missing controls matter more. I found no public information on double opt-in defaults, a stored consent record with its source, per-contact tracking switches, retention, or access and erasure handling; the captured cookie policy describes tracking pixels, cross-device linking and third-party advertising and analytics partners, and no per-person controls over that tracking appear in what was captured. 4 6 8
The Sales Ops Manager
Per-channel consent states are real enough that a journey reroutes an email opt-out through WhatsApp, and the profile updates consent as signals arrive, but the cookie policy documents tracking pixels, third-party cross-device linking, interest-based advertising and Google remarketing features. We found no public information on double opt-in, stored consent records with source, retention, erasure handling, or suppressing a person from profiling — heavy given anonymous activity is captured early and stitched to named profiles. 3 4 6 8
The Data Protection Officer
Consent is more than decoration: journeys route messages according to consent and channel preferences, the profile updates consent the moment a signal occurs, and first-party behavioural data is emphasised. Against that, the cookie policy describes tracking pixels counting how often an email is read, cross-device linking with third-party partners and interest-based advertising, and we found no public information on any per-contact switch for that tracking. We further found no public information on double opt-in, a stored consent record with its source and wording version, retention rules, or the handling of access and erasure requests including derived scores — the accountability spine of this criterion is simply not evidenced. 3 4 6 8
The Lifecycle Marketer
Consent sits on the real-time profile and drives channel routing when someone opts out, and onboarding help covers consent strategies. But I found no public information on double opt-in defaults, a stored consent record with source, switching tracking per contact, retention per data category, or access and erasure handling — and the documented tracking, email pixels counting re-reads and cross-device linking with third-party advertising partners in the cookie policy, is described without any per-contact limit. 3 4 6 8
The Solution Architect
Conscent updates land in the profile in real time and channel routing honours it, which is the right shape — but the vendor's own cookie policy describes email tracking pixels, cross-device linking with unnamed third-party partners, and interest-based advertising, which tells me the tracking posture is traditional third-party cookies. We found no public information on double opt-in defaults, stored consent records with source, retention, per-person profiling suppression, or handling of access and erasure requests including derived signals like the fatigue index. 6 8 4 9
The Skeptic
Consent states live on the real-time profile and drive per-channel routing, which is more than a checkbox. But we found no public information on double opt-in defaults, consent records with source and wording versions, retention rules, or switching tracking off per contact — and the only tracking documentation captured is the vendor's own cookie policy, which describes tracking pixels, cross-device linking by third-party partners and Google remarketing. 3 4 6 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 — 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
Identity resolution across anonymous and known states, a unified real-time 360-degree profile and live behavioural segments are the hard half of a data model and they are evidenced. But I found no public information on a named CRM connector, sync direction, field mapping, conflict rules, custom objects or a documented API — the join between platform and CRM, the thing that decides the implementation, is not described in the captured pages. 5 8
The Sales Ops Manager
Identity resolution and a real-time 360-degree profile are documented, including anonymous activity applied once identity is known, which is automated resolution rather than hand-dedup. But on the join itself we found no public information on any CRM connector, field mapping, configurable conflict rules or a sync error log somebody can act on, and the audience-structure work is marketed as a professional-services engagement rather than a self-serve data model. 5 8
The Data Protection Officer
Identity resolution across anonymous and known activity, applied the moment identity is established, plus a real-time unified profile, are documented and matter for who a person is. We found no public information on sync with any named CRM, field mapping, conflict rules, custom objects or a documented API, so the join with the customer's system of record cannot be assessed from the captures at all. 5 8
The Lifecycle Marketer
Identity resolution across anonymous and known states plus a real-time 360° profile unifying engagement, product and first-party behavioural data are evidenced, which is the genuinely hard part of the data model. But I found no public information on any CRM connector — no named CRM, field mapping, bidirectional sync, conflict rules or documented API — so the join that decides the implementation is entirely undocumented. 5 8 9
The Solution Architect
Identity resolution with anonymous activity captured early and applied once identity is known is exactly the documented path from anonymous visitor to known contact I look for, and the real-time 360° profile unifying engagement, product and first-party data is evidenced. But the CRM half of the join is invisible: we found no public information on any CRM connector, bidirectional sync, field mapping, conflict resolution, custom objects, or a documented API with rate limits — and the audience data structure itself is sold as a professional-services engagement, which points to a model you buy rather than extend yourself. 5 8
The Skeptic
Identity resolution and a real-time unified profile are documented — anonymous activity captured early and applied once identity is known — which is the data-model half of the join. On the CRM half, we found no public information on any named CRM integration, field mapping, bidirectional sync, conflict rules, sync error logs or API rate limits; the join to a CRM is what decides implementations, and the captured pages are silent on it. 5 8 9
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
No hosting location, contracting entity or subprocessor list appears in what was captured, and a platform building real-time behavioural profiles of named consumers needs exactly that paper trail. The only data-flow evidence is third-party advertising and analytics partners such as Google and DoubleClick, and no EU basis for any processing is stated. 6 8
The Sales Ops Manager
No sovereignty attributes are on record: hosting location, contracting entity and subprocessors are all unstated while the product captures anonymous activity and builds real-time behavioral profiles of named people. The only chain evidence visible is a cookie policy naming third-party advertising companies and Google features, which is not a published subprocessor list for the product. 6 8
The Data Protection Officer
Nothing is on record for hosting location, contracting entity, named infrastructure or a subprocessor list, and the cookie policy refers to third-party partners who receive behavioural data without naming them. For behavioural profiles of named EU residents that absence sits at the very bottom of what I can justify; the single point above zero reflects only that the captures do not establish the vendor's own jurisdiction either way. 6
The Lifecycle Marketer
I found no public information on where profiles, events and derived scores are processed, on the contracting entity, or on a subprocessor list, while the product's entire premise is real-time behavioural profiles of named people. The cookie policy names third-party advertising partners and cross-device linking with no stated transfer basis; for a buyer weighing this heavily, unstated hosting and unnamed subprocessors land this at the bottom. 1 6 8
The Solution Architect
No hosting location, contracting entity, or subprocessor list appears on any captured page, and the cookie policy names unnamed third-party partners in cross-device linking and interest-based advertising. For a platform building behavioral profiles of named people, that silence on where profiles, events and derived scores are processed is decisive as this buyer weighs it. 1 6
The Skeptic
For a platform whose product is real-time behavioural profiles of named people, we found no public information on hosting location, contracting entity or a subprocessor list — nothing is on record at all. The vendor's own cookie policy names third-party partners including Google and DoubleClick in its tracking chain, so at least part of the chain is non-EU without any stated safeguard. 6 8
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 captured product pages show no price, tier, billing period, send limit or onboarding fee of any kind. Professional services, managed services and a multi-journey fast-track are described and never priced, so a buyer cannot begin to compute an annual invoice from public pages. 4 5 8
The Sales Ops Manager
We found no public prices at all — no tiers, no contact or send limits, no overage rates, no VAT treatment — and the onboarding, deliverability and managed-services offerings are described without any fees. A buyer cannot begin to compute an annual invoice from these pages. 4 5 8
The Data Protection Officer
The vendor's own homepage and product pages in the captures carry no prices whatsoever. We found no public information on tiers, contact or send limits, overage rates, onboarding fees, minimum terms or VAT treatment — a buyer has nothing with which to compute an invoice. 1 5
The Lifecycle Marketer
No public prices appear anywhere in the captured material — no contact tiers, no send limits, no billing period, no overage and no indication of the tier where journeys or identity resolution begin. Professional services, a multi-journey fast-track and managed services are all offered with no fees stated, so a buyer cannot even sketch an annual invoice from public pages. 5 8
The Solution Architect
We found no public information on prices, contact tiers, send limits, overage rates, or term minimums on any captured page. The professional services, managed services and onboarding offerings are described in detail with no figures attached, so a buyer cannot compute even the shape of an annual invoice from public pages alone. 1 8 5
The Skeptic
Not a single price, tier, contact band, send limit or billing period appears on any captured page, so a real annual invoice is not computable from public information. Meanwhile the pages do sell a services arm — onboarding, managed services, multi-journey fast-track, deliverability audits and IP warm-up — with no figures attached to any of it, which is exactly where a mandatory implementation cost hides. 4 5 8
Questions about Acoustic Campaign
Is Acoustic Campaign European?
Not determined: the vendor’s pages as captured do not say where Acoustic Campaign is based.
Where does Acoustic Campaign store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Acoustic Campaign have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Acoustic Campaign?
As of 21 Oct 2026, the panel rates ActiveCampaign (Automation) (3/5), Evalanche (3/5) and HubSpot Marketing Hub (3/5) highest among the other 16 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: Acoustic Campaign alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- We found no public information on pricing on the pages we read (acoustic.com, acoustic.com/product-tour-library/campaigns, acoustic.com/use-case-library/increase-player-spend-with-multi-step-campaigns, acoustic.com/product/sms-whatsapp-marketing, acoustic.com/product/email-marketing, acoustic.com/cookie-policy and 3 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 20 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
- 11 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
- 3 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
- 1 compliance 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
- 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
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.acoustic.com Checked 13 Oct 2026 Details →
- 2 Journeys & orchestration — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →
- 3 Journeys & orchestration — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →
- 4 Channels & personalisation — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →
- 5 Channels & personalisation — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →
- 6 Consent, tracking & profiling — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →
- 7 Consent, tracking & profiling — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →
- 8 CRM integration & data model — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →
- 9 CRM integration & data model — found from sitemap www.acoustic.com Checked 13 Oct 2026 Details →