Launch

Ortto connector: lists and unsubscribes, kept in step both ways

Planes and Ortto now share your email lists and unsubscribes. Push Planes lists to Ortto as tags, pull Ortto audiences into Planes, and let opt-outs flow in both directions — safely.

Highlights

  • Push Planes lists to Ortto. Anyone on a mapped Planes list is tagged in Ortto as planes:<list name>; people added get the tag and people removed lose it. Smart lists work too. Build an Ortto audience on the tag once and it follows the Planes list from then on.
  • Pull Ortto audiences into Planes. An Ortto audience becomes a Planes list marked Synced from Ortto. People are matched by email, customers preferred over contacts; anyone new can be added as a contact (optional).
  • Unsubscribes flow both ways. Unsubscribe in Ortto → opted out of marketing email in Planes. Opt out in Planes → unsubscribed in Ortto when the person is on a pushed list.
  • Re-subscribes are handled safely. A re-subscribe in Ortto only reverses an opt-out that Ortto itself caused. Opt-outs made by your team, by an unsubscribe link, or by a STOP reply are never undone by Ortto.
  • Sync every 15 minutes, Planes-side changes reach Ortto in about 30 seconds, and Sync now runs everything or a single list with live status.

What changed

Marketing opt-outs

  • Unticking marketing opt-out is now per record. Turning opt-out off on one customer or contact clears only that record. If the same email or phone is still opted out on another record (an unsubscribe link, a STOP reply), Planes keeps treating the address as opted out. Turning opt-out on still applies to every record with that address.
  • Every opt-out change is audited — who, when, and how (by hand, by import, or by a connected tool). A record created already opted out simply stores the flag.

Lists

  • Lists can be managed by an integration. A list owned by an integration shows a Synced from badge; its member controls are disabled and the bulk Add to list picker no longer offers it.
  • Faster audiences. Resolving the people on a list takes a fixed handful of queries instead of several per person — list recipient views and CSV exports on large lists are quicker.

All releases