Untaggle HelpSign in →

Unsubscribe sync

Opt out once, honored everywhere. When a contact unsubscribes on one of your connected platforms, Untaggle applies that opt-out on the others — automatically, in both directions, with every occurrence in your Events Log. On the HighLevel side, that means a click on the unsubscribe link in an email: DND set any other way does not sync (see below).

It's already on

You don't set unsubscribe sync up by hand. The moment a new platform finishes connecting, Untaggle wires it against every eligible platform you've already connected — in both directions. There's nothing to remember when you add a platform later; the wiring extends itself.

Platforms that participate: HighLevel, Kit, Flodesk, Klaviyo and Postmark. Teachable has no unsubscribe concept, so it neither sends nor receives opt-outs. Postmark only sends them: it is a delivery service with no contacts to opt out, so opt-outs from your other platforms are not written back to it.

What actually happens

  • Someone unsubscribes in Kit, Flodesk or Klaviyo → Untaggle sets that contact's email DND in HighLevel, and unsubscribes them on your other email platforms if you have any.
  • Someone clicks the unsubscribe link in an email sent from HighLevel → Untaggle unsubscribes them in Kit, Flodesk and/or Klaviyo. It is the only HighLevel DND change that syncs on its own.
  • Someone unsubscribes from an email HighLevel sent through Postmark — the one-click button in Gmail or the link in Postmark's footer (in our testing, October 2026, the only one-click unsubscribe those emails carried) → Untaggle sets their email DND in HighLevel and unsubscribes them on your email platforms. A spam complaint counts too, and so does a hard bounce: Postmark stops delivering to that address (until someone reactivates it in Postmark), so HighLevel should stop trying. Taking an address off Postmark's suppression list does not clear anything — opt-outs only ever flow one way, and Postmark only sends them.
  • In HighLevel, only email DND is set — SMS and calls are never touched.
  • Klaviyo does not send webhooks to apps like Untaggle, so its unsubscribes are picked up every few minutes rather than instantly.
  • Buying never unsubscribes anyone: unsubscribe actions can't be attached to purchase rules, by design.

What doesn't sync from HighLevel

Email DND can be turned on in HighLevel in other ways too, and none of them sync to your email platforms:

  • DND set by a form or a workflow step
  • DND set because an email bounced
  • DND turned on by hand

None of these is the person clicking unsubscribe. A bounce is a delivery problem, and a workflow can set DND for any reason, so Untaggle doesn't treat them as opt-outs. The one exception runs the other way: a hard bounce reported by Postmark (above) does set DND in HighLevel, because Postmark has stopped delivering to that address.

Have a dedicated unsubscribe or email-preferences form in HighLevel? Give it its own form rule: Actions → Forms, pick the form, then add an action with your Kit account and Unsubscribe (Flodesk and Klaviyo work the same way). Everyone who submits that form is unsubscribed, so use it only on a form whose whole purpose is opting out. A wildcard form rule never unsubscribes anyone.

Two platforms — the common case

One selling platform plus one email platform (say, HighLevel and Kit) gives you a simple two-way sync: a Kit unsubscribe sets email DND in HighLevel, and a click on the HighLevel unsubscribe link unsubscribes the contact in Kit. This is wired the moment the second platform connects.

Three or more platforms

Running several platforms — multiple HighLevel locations, Kit and Flodesk, an agency-scale stack? Every eligible pair gets its own two-way wiring as each platform connects, so the full web builds itself: connect a third platform and it's wired against both existing ones automatically. An opt-out anywhere propagates to every connected platform, and each pair can be controlled independently.

Two connections on the same platform (for example two HighLevel locations) are never wired to each other automatically — locations usually serve different audiences, and cross-location opt-outs are a deliberate choice, not a default.

Reviewing and fine-tuning it

Open any connection on the Connections screen and go to its Unsubscribe tab:

  • The Unsubscribes card at the top shows whether this platform's unsubscribe events are being processed at all — Active or Paused, with a Pause/Resume button.
  • Send Unsubscribes → Sync to other connections lists each of your other platforms with an on/off control per destination — that's the per-pair switch.
  • The receiving side of each pair shows its status read-only on the destination connection's own Unsubscribe tab, with a link back to the source to change it.

Turning it on never rewrites the past

Enabling or resuming unsubscribe sync only applies to opt-outs that happen from that moment forward. Untaggle will never retroactively unsubscribe a contact based on something that happened before the switch was flipped — not even if an old event is replayed later. Opt-outs are one-way doors, so this guard is enforced in the database, not just the interface.

Questions about your specific setup? support@untaggle.com — or check the connection guides: HighLevel, Kit, Flodesk, Klaviyo, Teachable.