Skip to content
Law & compliance

Marketing Opt-Outs: Sync Objections Across All Systems

Sync marketing opt-outs across shop, newsletter tool, CRM and ERP: the unsubscribe as an event, a central suppression list, a precedence rule and a send test.

23 min read WerbewiderspruchCRM-AnbindungNewsletterAPI

In short and in plain language

A customer wants no more ads. They click on unsubscribe. Often only one program learns about it.

The shop, the customer program and the stock program do not know. Then the ads come back.

A better way is one list for all. It holds each opt-out. Each opt-out goes to all programs at once. No sync may delete it.

The list also keeps the way: mail, letter or phone. Before a big ad run, a test address shows if it all works.

We build the link between the programs.

In the weeks before Black Week and Christmas, mailing lists get merged: the customer list from the shop, the recipients from the newsletter tool, the contacts from the CRM, the contact persons from the ERP. This is exactly the step in which an opt-out tends to get lost. Someone clicked “unsubscribe” in the newsletter, the CRM still lists the contact as open to marketing, and the nightly sync writes the old flag back into the system the objection came from. The customer receives ads again, although they said no. This article shows how an objection recorded in one place takes effect in every connected system: as an event rather than a field in the nightly run, with a central suppression list as the leading record, a clear precedence rule, separate channels for email, post and phone, rules for contact persons at business customers, proof for each system and a test before every large send-out. The legal anchors are Section 7 of the German Act against Unfair Competition (UWG) for marketing email to existing customers and the GDPR for withdrawal of consent and objection.

Key takeaways

  • Two cases, two rules: marketing email to existing customers without consent requires, among other things, that the customer has not objected (Section 7(3) UWG). A newsletter based on consent ends with withdrawal under Art. 7(3) GDPR.
  • The opt-out reaches every system as an event, not as a field in the nightly run. Google recommends processing unsubscribe requests within 48 hours (Google), and the supervisory authorities require implementation without undue delay (DSK).
  • A central suppression list with hashed address, channel, scope, timestamp and origin is the leading record. The latest objection wins, and only new explicit consent lifts a block, not a sync.
  • Channels stay separate: clicking “unsubscribe” blocks marketing email, not automatically letters or calls. Consumer consent to telemarketing must be kept on record for five years (Section 7a(2) UWG), and calls without it cost up to EUR 300,000 (Section 20(2) UWG).
  • For business customers, the block attaches to the contact person and the address. Supervisory authorities consider a suppression entry after deletion permissible under conditions (DSK); a prerequisite is marketing based on legitimate interests.
  • Before every large send-out, a blocked test address runs through all systems and the mailing list is matched against the suppression list. The log records receipt and confirmation per system, and the customer gets an answer within one month at the latest (Art. 12(3) GDPR).

Why an opt-out gets lost in the neighboring system

In most companies there is no single place where marketing originates. The shop sends emails to existing customers, the newsletter tool keeps its subscriber list, the CRM plans campaigns and field sales calls, the ERP produces print data for the catalog and the price list. Each system has its own field for marketing permission, often with its own name and its own meaning. An objection first lands where the customer declared it and reaches the other systems only if an interface carries it there. Where that interface is missing or treats the flag like an ordinary master data field, the familiar leaks appear:

  • The nightly sync transfers the marketing flag in both directions and overwrites the fresh opt-out with the older state from the CRM.
  • For the Christmas campaign, a list exported in spring is imported again, including the addresses that have opted out since.
  • The CRM builds a target group from its own data and knows nothing about the opt-out in the newsletter tool.
  • The customer replies to a marketing email with “Please stop sending me ads.” The reply sits in the sales inbox, and no system learns about it.
  • The ERP holds the same person with a second address or in capital letters, and the sync does not recognize them as the same.
  • A contact person objects on the phone, and the remark ends up as a free-text note on the contact instead of a block.

How costly an unclear data situation can become is visible in the area where an authority imposes fines itself: telemarketing. In 2025, Germany’s Federal Network Agency received 39,842 (Bundesnetzagentur) written complaints about unlawful telemarketing, six percent more than the year before (Bundesnetzagentur). For the first time, it penalized breaches of the duty to document and retain consent to marketing, and it noted that the unclear data situation within the companies concerned led to numerous unlawful marketing calls (Bundesnetzagentur). Email and post follow the same mechanism: whoever does not know who has objected keeps advertising anyway.

Before an interface is built, it has to be clear which no it carries. Under the German Act against Unfair Competition, marketing by email generally requires the prior express consent of the recipient (Section 7(2) No. 2 UWG). For existing customers there is an exception that depends on four conditions, all of which must be met together (Section 7(3) UWG):

  1. The business received the email address from the customer in connection with the sale of goods or services.
  2. It uses the address for direct marketing of its own similar goods or services.
  3. The customer has not objected to this use.
  4. When the address is collected and each time it is used, the customer is clearly and unambiguously informed that they can object to the use at any time without incurring costs other than the transmission costs at basic rates (Section 7(3) UWG).

For data management, condition 3 is the delicate one. It applies not only to the system in which the objection was received, but to every system that uses the address for marketing. Condition 4 requires the notice each time the address is used, which means in every marketing email, whichever system sends it. An unsubscribe link in the shop email that only changes the list in the newsletter tool provides the notice, but lets marketing from the shop and the CRM continue. There, condition 3 is then missing.

A newsletter that someone explicitly signed up for is a different case. Its basis is consent, and the data subject has the right to withdraw their consent at any time (Art. 7(3) GDPR). Withdrawing consent must be as easy as giving it (Art. 7(3) GDPR). Someone who subscribed with a single click does not have to unsubscribe through a contact form with mandatory fields. What exactly an opt-out covers, this one newsletter or all marketing email, is to be clarified with the person in case of doubt (DSK). The cautious approach is therefore to treat a click on “unsubscribe” as an objection to marketing email as a whole, unless the person has explicitly made a narrower choice.

Alongside this stands the right to object under the GDPR. Where personal data are processed for direct marketing purposes, the data subject has the right to object at any time (Art. 21(2) GDPR). The consequence is phrased briefly and without any balancing test: where the data subject objects to processing for direct marketing purposes, the personal data shall no longer be processed for such purposes (Art. 21(3) GDPR). This affects every system that processes data for marketing and every channel the declaration covers. The right must be explicitly brought to the person’s attention at the latest at the time of the first communication, separately from any other information (Art. 21(4) GDPR), and in the context of information society services the objection may also be exercised by automated means (Art. 21(5) GDPR).

SituationLegal basisWhat the no doesRelated duty
Newsletter after sign-upConsent, withdrawal under Art. 7(3) GDPRno more sending of this newsletter to the addresswithdrawal as easy as sign-up
Marketing email to existing customersException under Section 7(3) UWGcondition “has not objected” fails, no more marketing email without consentnotice at collection and in every marketing email
Marketing in general, for example by letterObjection under Art. 21(2) and (3) GDPRno more processing for marketing within the declared scopenotice at the latest at the first communication (Art. 21(4) GDPR)
Marketing call to consumersprior express consent (Section 7(2) No. 1 UWG)withdrawal ends the callsdocument and retain the consent (Section 7a UWG)

Opting out is not canceling

An objection ends the marketing, not the customer relationship. Order confirmations, invoices and shipping notices keep going out, because they are not marketing. An advertising add-on inside them is, though: Germany’s Federal Court of Justice held that automatically generated confirmation emails containing advertising unlawfully interfere with the general right of personality if the recipient had previously expressly objected to receiving advertising (BGH, judgment of 15 December 2015, VI ZR 134/15). The block therefore also belongs on the text templates of order and service emails.

The opt-out as an event, not as a field in the nightly run

Many integrations treat marketing permission like any other master data field: a flag on the contact that is synced once a night together with the other fields. That is good enough for a phone number, but not for an objection. First, it arrives too late. The supervisory authorities require the advertising objection to be implemented in the company without undue delay (DSK). If it comes through a link in a marketing email or through the customer portal, it must, in their view, be observed immediately for advertising sent purely electronically (DSK). Second, it gets lost in a field sync as soon as two systems write the same field and the older state wins. Third, it lacks its origin: a field says “no”, but not since when, through which route and for which channel.

A large mailbox provider such as Google also counts in hours, not weeks. Google recommends that senders process unsubscribe requests within 48 hours (Google). Senders who send more than 5,000 (Google) messages a day to Gmail accounts must make sure that marketing messages support one-click unsubscribe (Google). Technically, RFC 8058 describes the route through the email headers. For the integration, the only thing that matters is that this click ends in an event that reaches every system, not merely a checkbox in one list.

The robust pattern is therefore a dedicated event. Wherever an objection comes in, in the newsletter tool, in the shop’s customer account, in the CRM after a call or in the customer service inbox, that place creates an event “advertising objection recorded” and sends it to a central interface. The interface writes the entry into the suppression list and distributes it through a queue to all connected systems. Each system confirms the takeover with a receipt. How events are delivered reliably is covered in the articles on webhooks and polling and on event-driven architecture with message queues. An event contains only what the recipients need for the block:

advertising-objection-event.json
{
  "event": "advertising_objection.recorded",
  "event_id": "8f3c2a1e-6b0d-4e57-9a51-2d7c4f1b9e30",
  "occurred_at": "2026-11-11T09:14:03+01:00",
  "subject": {
    "email_sha256": "c0f2e9a4...",
    "customer_id": "K-104582"
  },
  "scope": {
    "channel": "email",
    "reach": "all_marketing_email"
  },
  "source": {
    "system": "newsletter",
    "method": "one_click_unsubscribe",
    "notice_version": "2026-09"
  }
}

The recipients work idempotently: if the same event arrives twice, there is no second entry and no error. The pattern for this is described in the article on idempotency and retry strategies. The nightly sync does not disappear, it gets a new role. It is the safety net that finds lost events by comparing the blocks in each system with the suppression list. It may add blocks, but not remove them. If it finds a gap, that is a finding for the log and a pointer to a place where an event was lost.

The central suppression list as the leading record

For an event to mean the same thing everywhere, there has to be one place that holds the authoritative answer on advertising objections. That place is the central suppression list. It leads on exactly one question: may this address receive marketing through this channel? All other fields such as name, postal address or customer group stay where they are kept today. Shop, newsletter tool, CRM and ERP query the suppression list before every marketing send-out or keep a copy that stays current through the events. Which system leads on which field should be defined explicitly, as described in the article on CRM integration.

The suppression list does not hold the address in plain text, but as a hash value. There is a practical reason for this: the list is distributed to many systems, and a hash allows matching without storing the address openly everywhere. It is not anonymization. Anyone who knows the address can recompute the hash, which is exactly what it is for. The entries remain personal data because they relate to an identifiable natural person (Art. 4(1) GDPR), and the suppression list is a processing operation with its own purpose that belongs in the record of processing activities.

Before hashing, every system prepares the address according to the same rule, otherwise the same address produces two different values: trim spaces at the edges, convert to lowercase consistently, encode special characters in the domain part the same way. This rule belongs in a shared library or in the central interface, not in four separate implementations. Special characters and differing field lengths otherwise make the same address arrive in two systems in two different forms. Each entry in the suppression list carries six details:

Identifier

Hash of the prepared address, for phone the prepared number. Plus the customer number, so that a changed address stays blocked as well.

Channel

Email, letter or phone. An entry applies to one channel or explicitly to all, depending on what the person declared.

Scope

A single newsletter, all marketing email or any marketing. The scope follows the declaration, not the convenience of the system.

Timestamp

When the objection was received, including the time zone. The precedence rule uses it to decide which state applies.

Origin

Unsubscribe link, customer account, reply email, call or letter, each with a reference to the case, such as a ticket or event ID.

Notice version

Which notice text on the right to object applied at that time. This supports the proof that the notice was given at each use.

Precedence: the latest objection wins

Most errors do not occur with the first objection, but afterwards: at the next sync, the next import, the next sign-up through a prize draw. That is why the suppression list needs a precedence rule that is implemented the same way in every interface. It fits into five sentences:

  1. An objection wins against every older state, whichever system it comes from.
  2. No sync and no import resets a block. A field “marketing allowed” from a source system is ignored if the suppression list knows a more recent objection.
  3. Only new, explicit consent with a later timestamp lifts a block, and only for the channel and scope for which it was given. For the newsletter, this usually means a new sign-up with confirmation.
  4. A new purchase is not consent. Someone who orders again after an objection stays blocked until they declare otherwise themselves.
  5. If the timestamps are equal, the block wins.

Technically, the block is therefore a field that may only move in one direction. In a bidirectional sync, exactly this kind of field needs a clear owner, otherwise the systems keep overwriting each other. The patterns for this are in the article on data conflicts in bidirectional sync. For advertising objections, the suppression list is the owner, and the source systems only supply events. A source system that wants to set a marketing flag to “yes” does not send a field value, but an event “consent given” with timestamp and proof, and the suppression list decides according to the rule.

Keep channels separate: email, letter, phone

Not every no means the same thing. Someone who clicks “unsubscribe” below a newsletter wants no more marketing email; whether they also want to stop the printed catalog, the click does not say. Someone who writes “I object to any use of my data for advertising”, on the other hand, means all channels, and for direct marketing the consequence is then unambiguous (Art. 21(3) GDPR). The suppression list reflects this by giving every entry a channel and a scope. Google also advises senders to let recipients unsubscribe from individual lists or from all lists at once (Google). Whoever offers this choice must also store it: an entry “only the tools topic” is not the same as “all marketing email”.

The phone is the strictest channel. Marketing calls require the prior express consent of consumers and at least the presumed consent of other market participants (Section 7(2) No. 1 UWG). Consumer consent to telemarketing must be documented and retained for five years from the time it is given and after each use (Section 7a(2) UWG). For marketing calls to consumers without consent, the law provides for fines of up to EUR 300,000, and for breaches of the documentation duty up to EUR 50,000 (Section 20(2) UWG). A withdrawal on the phone therefore does not belong in the contact note as free text, but in the suppression list as an event, with the timestamp and the person who took it.

For letters, the time of production counts. If a campaign is already running, it may in individual cases be unreasonable to pull a single addressed letter from the batch. After an objection, however, no new print jobs may be started with the address (DSK). For the interface, this means the suppression list is queried before the print file is generated, not only at dispatch. An objection can also be communicated in any form (DSK), by reply card, call, letter or reply email. Each of these routes needs an entry point into the same event.

ChannelLegal anchorWhen the block must take effectTypical entry points
EmailSection 7(2) No. 2 and 7(3) UWG, Art. 7(3) and Art. 21 GDPRbefore the next send-out, immediately for unsubscribe link or customer portal (DSK)unsubscribe link, customer account, reply email
LetterArt. 21(2) and (3) GDPRbefore the next print job (DSK)reply card, letter, call
PhoneSection 7(2) No. 1 and Section 7a UWGbefore the next call; keep proof of consumer consent for five years (Section 7a(2) UWG)conversation, email to sales

Contact persons at business customers

In B2B, the situation is not simpler, just different. Marketing email to businesses also generally requires the prior express consent of the recipient (Section 7(2) No. 2 UWG), and the existing-customer exception refers to the customer in general terms (Section 7(3) UWG). On top of that, behind a buyer’s address there is a natural person whose data are personal data (Art. 4(1) GDPR). If she objects, this applies to her data, even if the company continues to be supplied as a customer. This leads to a few rules for the suppression list:

  • The block attaches to the person and their address, not to the company account. Other contacts at the same company remain unaffected as long as the company does not declare otherwise.
  • If the company itself, for example its management, declares that it no longer wants marketing, the company account gets its own entry with the scope “all contacts”.
  • Role addresses such as purchasing@ or info@ are blocked like personal addresses. The reader changes, the declaration does not.
  • If a contact person moves to another company and gets in touch with a new address, that is a new address without an objection, but also without consent. The customer number of the old company does not transfer any permission.
  • Field sales and inside sales record objections from conversations in the CRM as an event, not as a note.

For an entry to get the right scope, contact person, company account and customer number must be clearly linked in shop, CRM and ERP. In the ERP, business customers are often set up with several delivery addresses and contacts, in the shop with sub-accounts, in the CRM with roles. How customer accounts come together across these worlds is handled by the ERP and inventory integration. Without this link, the suppression list can block the address, but cannot recognize that a company declaration applies to all contacts.

Keep the suppression entry even after deletion

A common conflict: the customer objects to marketing and at the same time demands that their data be deleted. After an objection to direct marketing, the data subject can demand erasure (Art. 17(1)(c) GDPR). If the address is deleted completely, however, every trace is gone at the next import of an old list, and the marketing starts all over again. The supervisory authorities describe the advertising suppression file for this: if the person only wants to prevent further advertising approaches, adding their contact details to an advertising suppression file can be the right means (DSK). What the person wants to achieve with their declaration is to be clarified with them in case of doubt (DSK).

The guidance attaches conditions to this. Such suppression files can be permissible, but the prerequisite is processing for marketing purposes based on legitimate interests; if the marketing is based on consent, consent must be present in every single case anyway (DSK). The person must be informed about the meaning and purpose of being added to the suppression file (DSK), and anyone who explicitly also demands deletion from the suppression file should be told that they may receive advertising again (DSK). The suppression list is therefore a means the authorities consider permissible under conditions, not a duty expressly named in the law.

In practice, only the suppression entry with hash, channel, scope and timestamp remains after deletion. Name, postal address and order history disappear from shop, CRM and ERP according to the deletion concept across system boundaries, unless a retention duty prevents it. Every import route checks new addresses against the suppression list before they are created as open to marketing. This keeps the objection effective without the rest of the customer data staying longer than necessary.

Suppression list: permissible under conditions

Neither Section 7 UWG nor Art. 21 GDPR expressly mentions a suppression list. In the view of the supervisory authorities, advertising suppression files can be permissible; a prerequisite is marketing based on legitimate interests, and the person must be informed about the purpose (DSK). This assessment belongs in the record of processing activities and in the coordination with the data protection officer. The notes in this article do not replace legal advice.

Proof and a log for each system

Anyone who advertises must be able to show in a dispute that they followed the rules. The controller is responsible for compliance with the principles and must be able to demonstrate it (Art. 5(2) GDPR). Where processing is based on consent, the controller must be able to demonstrate that the person has consented (Art. 7(1) GDPR). The same applies to the objection in the opposite direction: it must be possible to show when it arrived and from when each system observed it.

The log therefore records for each event: receipt, entry in the suppression list, delivery to each connected system and that system’s receipt. If a receipt is missing after a defined time, an alert goes to the responsible team. Customer data do not belong in the log in plain text; hash and event ID are enough, as described in the article on customer data in integration logs.

The customer gets an answer as well. Information on the action taken on a request must be provided without undue delay and in any event within one month; the period can only be extended for complex or numerous requests (Art. 12(3) GDPR). The supervisory authorities recommend an individual reply that confirms the objection is being observed and names, as precisely as possible, a short period during which advertising may still arrive (DSK). With an event interface, this period can be read from the receipts instead of being estimated.

Infringements of the data subject’s rights under Articles 12 to 22 GDPR, which include the right to object, can be fined up to EUR 20 million or, for companies, up to 4 percent of worldwide annual turnover, whichever is higher (Art. 83(5) GDPR). The more important reason for a clean log is a different one, though: it shows where an opt-out got stuck before the customer notices.

Test before every large send-out

Black Week and Christmas are the weeks in which most lists are merged and the largest send-outs go out. That is exactly when the route of the block has to hold up. The supervisory authorities require informally received objections to be processed without undue delay and up-to-date data to be used for marketing measures at all times (DSK). A test before the send-out checks this not on paper, but in the data flow. How the interfaces themselves prepare for the order peak is covered in the article on Black Week.

One test address per channel in all systems, set up like a normal contact with marketing permission. The addresses belong to the company, not to a customer.

After the test, the test addresses are released again, but only through new explicit consent, as the precedence rule requires. This way the same test also checks that no sync silently lifts the block. A separate test environment with realistic data makes this easier; how to set one up is described in the article on test environments for ERP interfaces.

Rollout in five steps

None of this usually requires replacing a system. The work lies in the interfaces in between: they are extended by an event, a lookup and a rule. The order follows the dependencies: each step builds on the previous one, and after the second step there is already a shared overview of the objections recorded in the systems.

From unsubscribe link to a block in every system

  1. 1

    Map the opt-out routes

    List every place where an objection can come in and every system that generates marketing. For each place, record which field is set today.

  2. 2

    Build the suppression list

    Define the data model with identifier, channel, scope, timestamp and origin, take over the existing opt-outs from all systems and reconcile them against each other.

  3. 3

    Connect the event interface

    Every entry point reports objections as events, every marketing system takes them over and confirms. For entry points without an interface, customer service gets an input form.

  4. 4

    Enforce the precedence rule

    Build into every sync and every import the rule that a block can only be lifted by more recent explicit consent.

  5. 5

    Test and document

    Run the test with test addresses before every large send-out and record the assessment of the suppression list in the record of processing activities.

We take on the part that lies between the systems: the API development for the event and the suppression list, the connection through a middleware layer and the precedence rule in the existing syncs. What else belongs to an integration is shown in the overview of our services. You make the legal assessment with your data protection officer or legal counsel, and we implement it technically.

One no, one source

An advertising objection is not a field that tags along at some point, but an event with timestamp, channel and origin. The suppression list records it, every system takes it over and confirms, and no sync resets it. Then a no stays a no, even after the next import.
This article is based on data from: German Act against Unfair Competition (UWG), Section 7(2) and (3), Section 7a(2) and Section 20(2); General Data Protection Regulation (Regulation (EU) 2016/679), Art. 4(1), Art. 5(2), Art. 7(1) and (3), Art. 12(3), Art. 17(1), Art. 21(2) to (5) and Art. 83(5); German Data Protection Conference (DSK), guidance of the supervisory authorities on processing personal data for direct marketing purposes, February 2022; Bundesnetzagentur (Federal Network Agency), press release of 26 January 2026 on unlawful telemarketing; Federal Court of Justice (BGH), judgment of 15 December 2015, VI ZR 134/15; Google, Gmail Help: email sender guidelines and the related FAQ; RFC 8058. The notes on competition and data protection law do not replace legal advice.

Related Articles

APIs, middleware & architecture

Webhooks vs. Polling: Event-Driven Shop Integration

Webhooks or polling for shop-to-ERP integration? A comparison of latency, delivery guarantees, HMAC security and resilience with practical recommendations.

13 min read
Shop integration & processes

ERP Migration: From Legacy Interfaces to Modern APIs

ERP migration from legacy interfaces to modern API connections: strangler fig pattern, risk analysis and gradual replacement of old integrations.

14 min read
IT & API security

B2B Shop Single Sign-on: Log In with the Company Account

Single sign-on for B2B shops with OpenID Connect: map logins to company accounts and customer groups, derive roles from groups, block leavers, plan a fallback.

20 min read