Email Marketing & Newsletter
Sarbacane
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Sarbacane Software SAS · www.sarbacane.com
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.
The panel's verdict
Sarbacane (rebranded to Positive User) is an email marketing and newsletter tool whose public documentation is strongest on campaign creation and integrations: campaign and automation scores cluster at 5-6 for a drag-and-drop editor, reusable blocks and template folders, and A/B testing across subject line, sender and content with automatic or manual winner selection, while integrations scores run 4-5 on named connectors for Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets. Its weakest scored ground is deliverability, 2-4, where judges credit a real help-centre collection on domain reputation and the dedicated-versus-shared IP choice but found no public information on SPF, DKIM or DMARC setup or bounce suppression. The genuine split is sovereignty, spanning 1-4: some judges credit the evidenced French contracting entity (Positive Groupe France) and the GDPR claim, while others withhold credit because data residency, ownership and subprocessors are unknown on the captured pages. Consent and proof spreads 2-4 too — documented unsubscribe and per-contact tracking consent, but no public information on double opt-in or stored consent records. The captured pricing page exists but states no prices.
Speaks for it
- A/B testing documented across subject line, sender and message content with automatic or manual winner selection.
- Named connectors for Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets, plus API and mobile SDK documentation.
- Contact import documented across.xlsx,.txt and.csv files, manual entry and copy-paste, with automatic column mapping and a default source column.
- Unsubscribe link rules documented as free and unconditional, with an unsubscription list that excludes unsubscribed recipients from mailings.
- A per-contact tracking-consent flag governs whether opens are measured by tracking pixel.
Held against it
- We found no public information on SPF, DKIM or DMARC setup, bounce suppression or complaint-loop handling.
- We found no public information on exporting subscribers, engagement history or unsubscribe state, or on documented deletion.
- We found no public information on where subscriber data is hosted or which subprocessors touch the send.
- We found no public information on double opt-in or on what a stored consent record contains.
- Journey automation rests on marketing copy — more than 50 ready-to-use scenarios — with no documented branching on behaviour or data.
Best for
- You run a shop on Shopify, Magento (Adobe Commerce) or PrestaShop and want documented connectors plus CRM list synchronisation.
- You build template-based newsletters and want documented A/B testing across subject line, sender and content.
- You need per-contact control over tracking consent and a documented, unconditional unsubscribe flow.
Avoid if
- Your lifecycle programmes need behavioural branching or significance-tested winners — the documented A/B test picks its winner on raw open or click rate.
- Your procurement requires documented data residency or a published subprocessor list, and the judges' sovereignty scores split 1-4 on exactly this.
- You need to model your invoice from public prices before a sales conversation — the captured pricing page states no prices.
- Your list-exit plan requires documented export or deletion, which we found no public information on.
The scores
Campaigns & automation
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — One-off broadcasts from a fixed template; no segmentation and no automation of any kind.
3 — A drag-and-drop editor and simple list segmentation, but automation is a single welcome mail and there is no testing.
5 — Reusable templates, attribute and behaviour segmentation, multi-step automations on common triggers, and subject-line A/B testing.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, and testing that reports significance rather than raw counts.
10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.
The CRM Manager
The drag-and-drop editor, reusable blocks, template folders and an automated campaign type are documented, and A/B testing goes beyond subject lines to sender and full content with automatic winner selection. But the winner is chosen on raw open or click rate with a victory cup — no significance reporting — and the journey claims (more than fifty ready-to-use scenarios, intelligent multi-channel triggers) are marketing copy with no documented branching on behaviour or data. Good broadcast-and-test tooling; the lifecycle branching I measure programmes on is unproven. 1 2 3
The Deliverability Engineer
A drag-and-drop editor, template management with reusable blocks and folders, segmentation, automated multi-channel journey scenarios with a library of more than fifty ready-made ones, and A/B testing documented down to winner criteria, test elements and sample-size guidance. We found no public information on branching on behaviour and data, dynamic content per segment, send-time optimisation or testing that reports significance. 1 2 3
The Data Protection Officer
A drag-and-drop editor, reusable template blocks and folders, segmentation claims and multi-step automated journey scenarios are all documented, and the A/B test is unusually well covered — subject, sender and full content, automatic or manual winner on open or click rate. We found no public information on behavioural branching, dynamic content per segment, send-time optimisation or significance reporting; the winner is picked on raw counts. 1 2 3
The Shop Owner
A drag-and-drop editor, reusable template blocks with folders, segmentation, and automated customer-journey scenarios with a library of more than 50 ready-to-use ones would let me build a welcome and post-purchase rhythm, and A/B testing of subject, sender and full content is documented down to automatic winner selection by open or click rate. I found no public information on branching on behaviour or data, dynamic content per segment, or tests that report significance, and nothing naming abandoned-cart or post-purchase flows specifically despite the shop connectors. 1 2 3
The Integrator
Reusable templates with folders and saved blocks, a drag-and-drop editor and contact segmentation are all documented, and the A/B testing is properly so — sender, subject or full-content variants, automatic or manual winner selection, a recommended hundred contacts per group. Automation appears as multi-channel customer journey scenarios with a library of more than fifty ready-to-use ones, but we found no public information on branching on behaviour or data, dynamic content per segment, or send-time optimisation. 1 2 3
The Skeptic
Reusable templates with folders and blocks, a drag-and-drop editor, and a genuinely documented A/B test across subject, sender and content with automatic or manual winner selection are all evidenced. The automation story rests on marketing copy about journey scenarios and a library of ready-made scenarios plus an "Automated Campaign" type; we found no public information on branching, dynamic content per segment, send-time optimisation or significance reporting. 1 2 3
Deliverability infrastructure
Show reasoningHide reasoning
How this is scored
Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
0 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.
3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.
5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.
8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.
10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.
The CRM Manager
There is real documentation here — a deliverability collection with best practices, domain reputation, why mail lands in spam, and a documented choice between shared and dedicated sending IPs, which is more than a marketing number. We found no public information on SPF, DKIM or DMARC setup, on bounce suppression, or on complaint-loop handling, which is the layer I need documented before trusting the pipe. 4 5
The Deliverability Engineer
A help-centre collection covers best practices for content and headers, domain reputation, why mail ends up in spam, and the choice between a dedicated and a shared IP — real hygiene guidance. But we found no public information on SPF, DKIM or DMARC setup, on bounce suppression, or on complaint-loop handling; the claim that Sarbacane improves deliverability is a marketing sentence, not documented infrastructure. 4 5
The Data Protection Officer
A help-centre collection on deliverability and domain names exists, with domain reputation as a named factor, spam-placement guidance and both dedicated and shared IP options documented. We found no public information on SPF, DKIM or DMARC setup documentation, bounce suppression policy, complaint-loop handling or IP warm-up, so the collection's depth cannot be verified. 4 5
The Shop Owner
There is a genuine deliverability collection in the help centre covering best practices, domain reputation, why mail lands in spam, and the choice between a dedicated and a shared IP, which is more than a marketing number. I found no public information on SPF, DKIM or DMARC setup, nor on bounce suppression or complaint-loop handling, which is what actually keeps my order confirmations out of the spam folder. 4 5
The Integrator
A dedicated help collection covers domain names with settings and usage sections, domain reputation, why mail lands in spam, and the documented choice between a dedicated and a shared IP — which is more than a marketing number. We found no public information on SPF, DKIM or DMARC setup, on bounce suppression or complaint-loop handling, which is the authentication and bounce evidence this criterion turns on. 4 5
The Skeptic
A real help-centre collection covers domain names, domain reputation, why mail lands in spam, and the choice between dedicated and shared IP — more than a marketing number. But we found no public information on SPF, DKIM or DMARC setup, on any stated bounce policy, or on complaint-loop handling, which is the floor of a credible deliverability story. 4 5
Consent, proof & tracking limits
Show reasoningHide reasoning
How this is scored
How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
0 — Single opt-in with no consent record; tracking is always on and cannot be disabled.
3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.
5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.
8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, tracking off-by-default available, and retention rules for inactive subscribers.
10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.
The CRM Manager
Unsubscribe is documented properly — clear and unconditional exit, a form-type link insertable in the editor, and an unsubscription list that collects and excludes leavers — and tracking consent is a per-contact flag governing the open-measurement pixel, which is more granular than most. We found no public information on double opt-in, on what the consent record stores beyond tracking consent, or on versioning of the wording consented to, and that is the proof burden I would be carrying alone. 6 7 9
The Deliverability Engineer
Unsubscribe handling is genuinely documented — link rules requiring unsubscription to be free and unconditional, an unsubscribe form insertable from the editor, and an exclusion list that keeps unsubscribed recipients out of all mailings — and the measurement pixel is governed by a per-contact tracking-consent flag. We found no public information on double opt-in, on a stored consent record with source, IP or the wording consented to, or on retention of inactive subscribers. 6 7 9
The Data Protection Officer
Opens are gated on an explicit per-contact tracking consent tied to the tracking pixel, the editor inserts an unsubscribe form with documented rules that are free and unconditional, and an unsubscription list excludes leavers from mailings. We found no public information on double opt-in, on what the stored consent record contains beyond a default source column at import, or on any limit to click tracking — consent that would survive a complaint is not evidenced. 6 7 9
The Shop Owner
Unsubscribe handling is properly documented — the link must be free, unconditional and clearly worded, and an unsubscription list collects and excludes those recipients — and a per-contact tracking-consent flag governs whether opens are measured by pixel. I found no public information on double opt-in, on what a stored consent record contains beyond a default source column on import, or on preference-centre granularity. 6 7 8 9
The Integrator
Unsubscribe link rules are documented as free and unconditional with editor-inserted links and a transactional exemption, an unsubscription list excludes leavers from mailings, and a per-contact tracking-consent flag governs the open pixel — a real switch, not a promise. We found no public information on double opt-in, on what a stored consent record contains, or on retention and erasure handling, so proof beyond unsubscribe mechanics stays unevidenced. 1 6 7 9
The Skeptic
Unsubscribe handling is documented in real detail — free and unconditional, insertable from the editor, with an unsubscription list that excludes leavers from mailings — and a tracking-consent field ties open-measurement to consent per contact. We found no public information on double opt-in, on what a consent record stores beyond the fact of tracking consent, or on turning tracking off per campaign. 6 7 9
List ownership, import & exit
Show reasoningHide reasoning
How this is scored
Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.
0 — Export is addresses only; engagement history, segments and automations cannot leave.
3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.
5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.
8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.
10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.
The CRM Manager
Import is genuinely good — xlsx, txt and csv plus paste, with automatic column mapping, custom columns, a source column recording how each contact arrived, and lists auto-populated from business applications. But we found no public information on export, on whether engagement history or unsubscribe state can leave, or on documented deletion; entry is well built while exit is the part I cannot verify. 8 9 10
The Deliverability Engineer
Import is documented thoroughly — xlsx, txt or csv files, copy-paste and manual entry, automatic column mapping, custom columns, replace-or-append — and a synchronised list can be auto-populated from business applications, with CRM list synchronisation on top. The exit side is the gap: we found no public information on export, on whether engagement history can leave the account, or on documented deletion of a subscriber across all records. 8 9 10
The Data Protection Officer
Import is thoroughly documented —.xlsx/.txt/.csv, copy-paste, automatic column mapping, custom column creation and a default source column for provenance. We found no public information on export of subscriber fields, engagement history or unsubscribe state, nor on documented deletion of a subscriber across records. 8 9
The Shop Owner
Import is well documented —.xlsx,.txt or.csv with automatic column mapping, custom columns, replace-or-supplement, and a default source column — and lists can synchronize automatically from business applications. I found no public information on exporting subscribers with their engagement history, on deletion across records, or on what leaving the tool looks like, and that silence matters when the list is the asset. 8 9 10
The Integrator
Import is documented in real depth —.xlsx,.txt or.csv with automatic column mapping, new column creation, a default source column and replace-or-supplement choices — plus synchronized lists auto-populated from business applications and CRM list synchronisation. We found no public information on export of subscribers, engagement history or unsubscribe state, nor on deletion or any export throttling, so the way out remains an assumption rather than a documented feature. 8 9 10
The Skeptic
Import is the best-documented part of the product: file, manual and paste routes, automatic column mapping, new-column creation, a default source column recording how each contact arrived, and replace-or-append. We found no public information on export — including engagement history or unsubscribe state — or on executing deletion, so the exit half of list ownership is unevidenced. 8 9 10
Integrations & API
Show reasoningHide reasoning
How this is scored
The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.
0 — No API and no named integrations; the list is maintained by CSV upload.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks for the core subscriber events.
8 — Maintained bidirectional integrations with named systems including at least one major shop platform, event webhooks with retries, documented rate limits, and a sandbox.
10 — The tool is a component rather than a destination: transactional and marketing sending on one API, events flowing both directions, versioned API with a deprecation policy, and integrations the vendor maintains rather than lists.
The CRM Manager
Seven-plus named connectors including Shopify, Magento, Prestashop, Salesforce, WordPress, Google Sheets and noCRM, plus API and mobile SDK documentation and CRM list synchronisation, give a reasonable surface for shop and CRM data. We found no public information on webhooks, documented rate limits, a sandbox, or whether the connectors are bidirectional, so I cannot confirm the event flows in and out that my automation programmes would depend on. 1 9 10
The Deliverability Engineer
Named connectors for Shopify, Magento, PrestaShop, Salesforce, noCRM, WordPress and Google Sheets — more than a handful, and the shop connectors automate e-commerce actions rather than only reading — plus a documented API with HTTPS and TLS 1.2 and mobile SDK documentation. We found no public information on webhooks, documented rate limits or a sandbox. 1 10
The Data Protection Officer
Named connectors cover Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets with CRM list synchronisation, and a documented API secured with HTTPS and TLS 1.2 plus mobile SDK documentation. We found no public information on webhooks, rate limits or a sandbox environment. 1 10
The Shop Owner
Shopify, Magento (Adobe Commerce) and Prestashop connectors plus Salesforce, noCRM, WordPress and Google Sheets cover exactly the shop and CRM surface I need, with API and mobile SDK documentation published and connectors meant to automate e-commerce actions. I found no public information on webhooks, documented rate limits, or a sandbox, so I cannot see how cart and order events flow back to trigger anything. 1 9 10
The Integrator
The connector list is exactly what I wire against — Shopify, Magento (Adobe Commerce), Prestashop, Salesforce, noCRM, WordPress and Google Sheets — with public API and mobile SDK documentation and API calls over HTTPS with TLS 1.2. We found no public information on webhooks or retries, on rate limits, on a sandbox, or on API versioning and a deprecation policy, and those decide whether I can build here without a partner form. 1 10
The Skeptic
Named connectors for Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets, plus API documentation and mobile SDK documentation, form a real connection surface with two major shop platforms. We found no public information on webhooks, documented rate limits or a sandbox, which is what separates a connector catalogue from an API somebody can build against confidently. 1 10
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.
0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.
3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.
The CRM Manager
The contracting entity is French (Positive Groupe France) with a France-based team and an explicit GDPR-compliance claim, which is the right posture on paper. But we found no public information on where subscriber data and behavioural tracking are hosted, on the contracting situation after the rebrand to Positive User, or on any published subprocessor list — and this category decides procurement for me, so an unverified chain earns no benefit of the doubt. 1
The Deliverability Engineer
The vendor is a French SAS, the copyright is held by Positive Groupe France, the team of three-hundred-plus is based in France, and GDPR compliance is claimed on the site. Yet data residency, hosting location, ownership and every subprocessor in the send chain are unstated on the captured pages, so the path subscriber data and behavioural tracking actually take cannot be verified from public information. 1
The Data Protection Officer
The vendor presents as French — a SAS entity, a Positive Groupe France copyright line, staff and coaches based in France, and stated GDPR compliance. We found no public information on where subscriber data or the behavioural tracking data is hosted, and no subprocessor list, so the question of where open-and-click history lives has no documented answer here. 1
The Shop Owner
The vendor's own pages state a French contracting entity, Positive Groupe France, a France-based team and GDPR compliance, which is a start. I found no public information on where subscriber data and behavioural tracking are hosted or which subprocessors touch the send, and for a criterion I weigh heavily that absence caps the score. 1
The Integrator
The contracting entity is evidenced as French — Sarbacane Software SAS under Positive Groupe France, with a stated France-based team of three hundred plus and a GDPR claim. We found no public information on where subscriber data and behavioural tracking are hosted, on the data-centre provider, or on any subprocessor, and a chain I cannot verify is not one I can call sovereign. 1
The Skeptic
The captured marketing asserts "conformité totale au RGPD" and a France-based team, and the copyright names Positive Groupe France — but hosting location, contracting-entity jurisdiction, ownership and the subprocessor list are all unevidenced by the captured pages. We found no public information on where subscriber data or the sending infrastructure sit, or which subprocessors touch the send; a French team and a GDPR badge are not data residency. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A headline price per contact tier exists, but send limits, overage rates or the tier where automation begins are not stated.
5 — Contact-tier prices public with the billing period stated and send limits given, but at least one commonly needed capability sits in an unpriced tier or add-on.
8 — Every tier priced publicly with contact and volume limits, overage rates, feature boundaries and VAT treatment stated; only genuinely custom volume lacks a number.
10 — Complete price computability: a calculator producing the annual invoice for a given list size and send frequency, including overage, additional domains and dedicated IPs.
The CRM Manager
The captured pricing page states no prices at all, so I cannot compute an invoice for any list size — send limits, overage, where automation begins and VAT treatment are all publicly unpriced. That makes every tier a sales conversation before I can even model the cost of a migration. 1
The Deliverability Engineer
A pricing page exists, but it states no prices at all, so a sender cannot compute even a first approximation of the invoice for their list size and send volume. The dedicated coach on the same site points to a sales conversation rather than public figures. 1
The Data Protection Officer
A pricing page exists, but no prices, tiers, send limits or overage rates are stated on it, so a sender cannot compute any part of an invoice from public pages. We found no public information on where automation or additional capabilities sit in the tier structure. 1
The Shop Owner
A pricing page exists, but the captured page states no prices at all, so I cannot compute the invoice for my list size and send volume to weigh against what the newsletter contributes. As far as the public pages show, every number is a conversation. 1
The Integrator
The captured pricing page states no prices at all, so no tier, billing period, send limit or overage rate is public. As a buyer I cannot compute any part of the invoice from these pages; every number is a sales conversation. 1
The Skeptic
The captured pricing page carries no prices at all — no contact tiers, send limits, overage rates or VAT treatment — and the sales motion advertises a dedicated coach. A buyer cannot compute any invoice for any list size from the public pages captured. 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 | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 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.
- 5 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
- 2 integrations 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 hosting 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 legal 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
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.sarbacane.com Checked 22 Sep 2026 Details →
- 2 Campaigns & automation — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 3 Campaigns & automation — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 4 Deliverability infrastructure — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 5 Deliverability infrastructure — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 6 Consent, proof & tracking limits — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 8 List ownership, import & exit — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 9 List ownership, import & exit — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →
- 10 Integrations & API — found from sitemap help.sarbacane.com Checked 30 Sep 2026 Details →