Email Marketing & Newsletter
Get a Newsletter
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Get a Newsletter AB · www.getanewsletter.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.
Get a Newsletter at a glance
- Vendor
- Get a Newsletter AB
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates Get a Newsletter 2/5, the mean of 6 judges. Get a Newsletter is a Swedish email-marketing tool, and the bench scores it highest on sovereignty and integrations (4 throughout). how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Get a Newsletter is a Swedish email-marketing tool, and the bench scores it highest on sovereignty and integrations (4 throughout). Sovereignty rests on documented facts: a Swedish company storing personal data on its own servers in Sweden, sending through the vendor's gansend.com domain; judges noted support runs on Intercom and we found no public information on a subprocessor list. Integrations cover Quickbutik, Starweb, Wikinggruppen, Nortic, WordPress and Google Analytics plus a token-based API. Deliverability and campaign and automation rest on DKIM and SPF documented down to CNAME records, attribute segmentation and a signup-triggered autoresponder. Weakest is consent and proof, where judges genuinely split: the data protection officer scored 0, finding the criterion unanswered — no public information on double opt-in, consent records, unsubscribe handling or tracking limits — while others credited the documented signup forms. List data control is held down by the stated retention of email addresses after list deletion. Pricing transparency: beyond the free account (no card required), no public prices.
Speaks for it
- Swedish company storing personal data on its own servers in Sweden, with sending routed through the vendor's gansend.com domain
- DKIM and SPF setup documented down to the CNAME records, with a vendor-managed return-path subdomain that collects bounces and an in-account DKIM status check
- Segmentation on text and number contact attributes with combinable conditions, and an autoresponder that runs a timed mail series on signup with edit, pause and delete
- Six named integrations including the Nordic shop platforms Quickbutik, Starweb and Wikinggruppen, plus Nortic, WordPress, Google Analytics and a documented token-based API
- File import with duplicate handling and contact updating, an export path before list deletion, and signup forms placeable on websites, popups and landing pages
Held against it
- We found no public information on double opt-in, stored consent records, unsubscribe handling, or any way to limit open and click tracking — consent and proof scores range from 0 to 2
- The deletion article states "Email addresses connected to the list will not be deleted", and we found no public information on exporting engagement history
- Support runs on Intercom and we found no public information on a published subprocessor list or on where the sending infrastructure operates
- The documented automation is a linear timed series on signup; we found no public information on branching journeys, A/B testing or purchase-triggered flows
- The Nordic shop integrations are documented as one-way contact imports, and we found no public information on webhooks, rate limits or a sandbox
Best for
- You need a European contracting party, with personal data stored on the vendor's own servers in Sweden
- You run a shop on Quickbutik, Starweb or Wikinggruppen and want contacts imported into your list, backed by a token-based API for syncing
- You send straightforward newsletters and a signup-triggered welcome series, and want DKIM and SPF setup documented at the DNS-record level
- You want to explore newsletters, landing pages and surveys on a free account with no card required
Avoid if
- You need every record deleted on exit — the captured deletion article states that email addresses connected to the list will not be deleted
- You need branching, behaviour-triggered journeys — the documented automation is a linear timed mail series started on signup
- Your compliance review requires the support chain inside the EU — the helpdesk is documented to run on Intercom
- You need two-way flow from your shop platform — the Quickbutik, Starweb and Wikinggruppen integrations are documented as importing contacts only
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 2 of 5 |
| Deliverability infrastructure | 2 of 5 |
| Consent, proof & tracking limits | 1 of 5 |
| List ownership, import & exit | 2 of 5 |
| Integrations & API | 2 of 5 |
| European sovereignty | 2.5 of 5 |
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
Attribute segmentation is real — text and number conditions that can be combined — and an autoresponder runs a timed series from signup that you can edit, pause or delete. But the documented automation is a linear drip; I found no public information on branching journeys, behavioural segmentation, send-time optimisation or A/B testing of any kind, and a lifecycle programme cannot be run on what is evidenced here. 1 2 3
The Deliverability Engineer
Segmentation on contact attributes is real and documented — text and number conditions that can be combined — and the autoresponder runs a timed mail series off signup rather than a single welcome mail. I found no public information on subject-line testing, behavioural segmentation, or any branching journey, which keeps this short of the mid level. 1 2 3
The Data Protection Officer
Automation is the autoresponder — a welcome mail or mail series triggered on signup, scheduled in days and hours, with edit, pause and delete as the only lifecycle controls — alongside attribute-based segmentation that can combine several text and number conditions. We found no public information on a journey builder, behavioural branching, A/B testing, dynamic content or send-time optimisation. 1 2 3
The Shop Owner
Attribute segmentation is real — combinable text and number conditions — and a signup-triggered mail series with timed steps I can edit, pause or delete covers the welcome journey. Beyond that we found no public information on behavioural segmentation, A/B testing, or flows triggered by purchases or abandoned carts. The marketing page claims every click, opening and purchase is measurable, which is the revenue hook I'd want, but nothing shows how it drives a journey. 1 2 3
The Integrator
The captured pages show an autoresponder — a timed mail series started on signup, which can be edited, paused or deleted — alongside segmentation on text and number attributes with combinable conditions. I found no public information on A/B testing, branching journeys or dynamic content, and the documented automation is a linear timed sequence rather than a flow I could drive from events in other systems. 1 2 3
The Skeptic
Segmentation is real — combinable text and number conditions on contact attributes — and the autoresponder runs a timed mail series on signup with edit, pause and delete. We found no public information on A/B testing, templates, an editor, or automation triggered by anything other than signup. 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
Authentication setup is documented down to the CNAME records, the vendor collects bounces and manages SPF once a sending subdomain is in place, and there is a DKIM status check in the account. I found no public information on DMARC guidance, a bounce-suppression policy, dedicated-IP options or inbox-placement testing, and the documented sending domain points at shared infrastructure. 4 5
The Deliverability Engineer
This is the part I can actually read: DKIM setup is documented down to the CNAME values, and the subdomain option aligns return-path with the from address while the vendor collects the bounces and manages SPF — infrastructure on the page, not an inbox-percentage claim. Beyond that I found no public information on DMARC guidance, a stated hard-bounce suppression or complaint-loop policy, or dedicated-IP and warm-up options; the documented setup routes sending through the vendor's gansend.com infrastructure. 4 5
The Data Protection Officer
DKIM and SPF are documented with a custom subdomain whose return-path matches the sender, a vendor-managed SPF record, an in-account DKIM status check, and the vendor collects the bounces. We found no public information on DMARC guidance, automatic hard-bounce suppression, complaint-loop handling or dedicated-IP options, so this sits just above basic setup. 4 5
The Shop Owner
DKIM and SPF setup is documented down to the CNAME records, with a vendor-managed sending subdomain where return-path and from match, bounces are collected on their side, and a status check sits in the account. We found no public information on DMARC guidance, hard-bounce suppression policy, or complaint handling, so beyond the welcome handshake I cannot judge whether the mail lands. 4 5
The Integrator
DKIM and SPF setup is documented with CNAME records on a custom sending domain, a vendor-managed return-path subdomain that collects bounces, and a DKIM status check inside the account. I found no public information on DMARC guidance, a hard-bounce suppression policy, complaint-loop handling or dedicated-IP options, so this sits just above basic authentication. 4 5
The Skeptic
DKIM and SPF setup is documented with CNAME records on the vendor's own sending domain, a subdomain mode where return-path and from match and the vendor collects bounces and manages SPF, and an in-account DKIM status check. We found no public information on DMARC guidance, dedicated IPs, complaint-loop handling, or placement testing. 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
Signup forms across websites, popups and landing pages are evidenced, and the vendor says it keeps up to date with GDPR — but that is posture, not proof. I found no public information on double opt-in, a stored consent record, unsubscribe handling, or any way to switch off tracking, while the pages advertise that every click, open and purchase can be measured. 1 6
The Deliverability Engineer
Signup and subscription forms are documented, but I found no public information on double opt-in, on what consent record is stored, on unsubscribe handling, or on whether the click and open tracking the product clearly measures can be switched off. With none of that in public documentation, this sits just above the floor. 1 6 9
The Data Protection Officer
The pages show signup forms collecting subscribers and advertise that every click, opening and purchase can be measured, with Google Analytics tracking traffic on top. We found no public information on double opt-in, a stored consent record, unsubscribe handling or any way to limit or switch off tracking — which from my seat is the whole criterion unanswered. 1 6
The Shop Owner
The captured pages show signup forms, popups and landing pages to grow the list plus a general GDPR statement, but we found no public information on double opt-in, stored consent records, unsubscribe handling, or whether open and click tracking can be limited or switched off. For a shop mailing paying customers I cannot see what I could prove about how a subscriber arrived, and Google Analytics traffic tracking is offered with no limits documented. 1 6 9
The Integrator
The pages show signup forms in several placements and a stated GDPR posture, but I found no public information on double opt-in, a stored consent record, unsubscribe handling, or any way to limit or switch off open and click tracking. Google Analytics is offered to track traffic from newsletters with no documented tracking limits. 1 6 9
The Skeptic
Signup forms are documented, but we found no public information on double opt-in, consent records, unsubscribe handling, or any way to limit open and click tracking. Clicks, opens and purchases being measurable is advertised; we found no public information on tracking controls or pixel-free sending. 1 6 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
File import deduplicates and can update existing contacts, and an export through the subscription filter is documented before deleting a list. But the vendor states that email addresses connected to a deleted list will not be deleted, and I found no public information on exporting engagement history or on deletion that executes across all records — that retention note is the detail a buyer planning an exit should weigh. 7 8
The Deliverability Engineer
Import is documented with duplicate handling and update-on-import, an export of subscriptions can be taken before deleting a list, and the API is advertised for automatic synchronisation with external systems. But the captured page states plainly that "Email addresses connected to the list will not be deleted," and I found no public information on exporting engagement history or campaign assets. 7 8 9
The Data Protection Officer
File import with duplicate handling and updating of existing contacts is documented, an export path exists before list deletion, and an API is offered for synchronisation. The deletion page itself states that email addresses connected to the list will not be deleted, and we found no public information on exporting engagement history or unsubscribe state. 7 8 9
The Shop Owner
Import from file or paste with duplicate handling and attribute updates, an export path through the subscriptions filter before deleting a list, and an API for automatic syncing give me a genuine way in and out. However, we found no public information on exporting engagement history or campaign content, and the captured deletion article states that email addresses connected to the list will not be deleted, so a clean full exit is not evidenced. 7 8 9
The Integrator
File import with duplicate handling and updating of existing contacts, a documented export path, and an API for automatic synchronisation give a workable baseline for keeping the list mine. The deletion page states that email addresses connected to a deleted list will not be deleted, and I found no public information on exporting engagement history or unsubscribe state. 7 8 9
The Skeptic
File import with duplicate handling and contact updating, an export path from the subscriptions view, and an API for automatic synchronisation are documented. The list-deletion page states "Email addresses connected to the list will not be deleted", and we found no public information on exporting engagement history or a documented deletion across all records. 7 8 9
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
Six named integrations including three Nordic shop platforms, WordPress and Google Analytics, plus a token-based API with documentation positioned for keeping data synchronised automatically. The shop connections are described as import-direction only, and I found no public information on webhooks, rate limits or a sandbox. 9 10
The Deliverability Engineer
A handful of named integrations exist — mostly contact imports from Swedish shop platforms, plus WordPress signup collection and Google Analytics — and there is a documented API with tokens meant to synchronise data in both directions. I found no public information on webhooks, rate limits, or a sandbox, which is what the next level up would require. 9 10
The Data Protection Officer
Six named native integrations — WordPress, Google Analytics, Nortic, Quickbutik, Starweb and Wikinggruppen, the last three importing contacts from shop platforms — plus a documented API with named tokens for automatic synchronisation. We found no public information on webhooks, event delivery with retries, rate limits or a sandbox. 9 10
The Shop Owner
There are native contact imports from the Nordic shop platforms Quickbutik, Starweb and Wikinggruppen, plus Nortic and WordPress signup collection, and a documented API with tokens that replaces manual import and export syncing — the bones of a shop connection. The shop integrations run in the contact-import direction only as documented, and we found no public information on webhooks, rate limits, or a sandbox, so cart events, product data and revenue attribution per campaign are not evidenced. 1 9 10
The Integrator
There is API documentation with tokens for automatic data synchronisation, and named integrations with Nortic, Quickbutik, Starweb, Wikinggruppen, WordPress and Google Analytics — every connector described as importing contacts or tracking traffic, nothing flowing back out. I found no public information on webhooks, rate limits, a sandbox or a deprecation policy, which is exactly what I would need before building against this. 9 10
The Skeptic
Named integrations exist for Nordic shop platforms plus WordPress and Google Analytics, and there is a documented API with tokens for keeping data synced to and from external systems. We found no public information on webhooks, rate limits, or a sandbox, and most named integrations are described as importing contacts in one direction. 9 10
European sovereignty
panel opinion
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
Storage on the vendor's own servers in Sweden, a Swedish contracting company and an explicit GDPR posture make the data-residency story genuinely European. But we found no public information on a published subprocessor list beyond the incidental mention that support runs on Intercom, nor on certification or where the sending infrastructure itself operates. 1 3 5
The Deliverability Engineer
Own servers in Sweden, a Swedish company, and a stated GDPR posture give EU hosting as standard with an EU contracting entity — the storage half of the chain is solid. But the support desk runs on Intercom, a non-EU provider, without an explained safeguard, and I found no published subprocessor list saying who else touches a send. 1 3 5
The Data Protection Officer
The vendor states it is a Swedish company storing personal data on its own servers in Sweden with GDPR awareness, which is where I want subscriber behaviour to live. Support and the helpdesk run on Intercom with no stated safeguard, and we found no public information on a published subprocessor list or certification, so the chain is not evidenced end to end. 1 3 5
The Shop Owner
A Swedish company holding personal data on its own servers in Sweden, with GDPR compliance stated as kept up to date, gives me European hosting as standard and a European contracting party — which I weigh heavily. But the helpdesk runs on Intercom, Google Analytics is offered for traffic tracking, and we found no published subprocessor list, no named data-centre provider, and no legal basis stated for those non-Swedish links in the chain. 1 3 5 9
The Integrator
A Swedish company storing personal data on its own servers in Sweden, with sending on a vendor domain, is a genuinely good start for this buyer. The support chain runs on Intercom and analytics is offered via Google Analytics, and I found no published subprocessor list or named legal basis for those transfers, which holds this at mid-scale rather than sovereign end to end. 1 3 5 9
The Skeptic
A Swedish company storing personal data on its own servers in Sweden and sending under its own domain is a genuine EU core rather than an option. But no subprocessor list is published, support runs on a named third-party helpdesk with no stated location, and we found no public information on where the sending infrastructure itself is hosted. 1 3 4 5
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
A free account and trial are documented with unusually clean terms — no card required, cancel any time. That is where price information ends: I found no public information on paid tiers, contact or send limits, or overage, so a real invoice cannot be computed from these pages. 1 9
The Deliverability Engineer
The only public price signal is a free starting point with no card required and the ability to cancel anytime. I found no public information on paid tier prices, contact or send limits, overage, or VAT treatment — a sender cannot compute an invoice from what is published. 1 9
The Data Protection Officer
Only the free tier is priced in public — start for free, no card required, cancel anytime, with newsletters, landing pages and surveys in the free account. We found no public information on paid contact tiers, send limits, overage rates or VAT treatment, so a real invoice cannot be computed from the captured pages. 1
The Shop Owner
Beyond a free account to explore newsletters, landing pages and surveys, and a trial with no card required that I can cancel anytime, we found no public prices at all — nothing on tiers, per-contact pricing, send limits, overage or VAT treatment. I cannot compute the monthly invoice for my list size and send volume from anything captured, so the paid decision becomes a sales conversation. 1 9
The Integrator
The pages state a free start with no card required and cancellation at any time, but beyond that I found no public information on paid tier prices, contact or send limits, overage rates or VAT treatment. A buyer cannot compute the invoice for a real list size and send volume from what is captured here. 1 9
Questions about Get a Newsletter
Is Get a Newsletter European?
Not determined: the vendor’s pages as captured do not say where Get a Newsletter is based.
Where does Get a Newsletter store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does Get a Newsletter have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Get a Newsletter?
As of 21 Oct 2026, the panel rates Brevo (3/5), CleverReach (3/5) and Mailchimp (3/5) highest among the other 27 Email Marketing & Newsletter 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 Brevo (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Get a Newsletter alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 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.
- 10 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data 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 pricing 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.getanewsletter.com Checked 20 Oct 2026 Details →
- 2 Campaigns & automation — found from sitemap support.getanewsletter.com Checked 20 Oct 2026 Details →
- 3 Campaigns & automation — found from sitemap support.getanewsletter.com Checked 20 Oct 2026 Details →
- 4 Deliverability infrastructure — found from sitemap support.getanewsletter.com Checked 20 Oct 2026 Details →
- 5 Deliverability infrastructure — found from sitemap support.getanewsletter.com Checked 20 Oct 2026 Details →
- 6 Consent, proof & tracking limits — found from sitemap getanewsletter.com Checked 20 Oct 2026 Details →
- 7 List ownership, import & exit — found from sitemap support.getanewsletter.com Checked 20 Oct 2026 Details →
- 8 List ownership, import & exit — found from sitemap support.getanewsletter.com Checked 20 Oct 2026 Details →
- 9 Integrations & API — found from sitemap getanewsletter.com Checked 20 Oct 2026 Details →
- 10 Integrations & API — found from sitemap support.getanewsletter.com Checked 20 Oct 2026 Details →