Connections: where the addresses go

Your own tools already own your sender domain, your templates, your unsubscribe link and your deliverability reputation. Handing them an address is almost always better than us mailing on your behalf, so every address the app collects - try-on leads, review requests, back-in-stock signups - is passed to a destination you control.

The one exception is a back-in-stock alert, which the app can send itself. That is not a change of mind about the above: most people who ask to be told are not signed in, so there is no customer record for your automation to trigger on, and without our own send the feature would only work for merchants who had wired something up first. It stays a fallback, it stays optional, and it is described on the Back in Stock delivery page.

The destinations

• Shopify Segments - the address becomes a customer in your admin, tagged so a segment can find it.
• Klaviyo - added to a list of yours with your own private API key.
• Omnisend - added as a contact with a tag you choose.
• Webhook - the event is POSTed to any URL you control. See the webhook page.

Consent

Nothing here sets marketing consent on a shopper's behalf. A contact arrives as a member of the audience, not as someone signed up for campaigns - Omnisend contacts land as non-subscribed, Klaviyo profiles carry no subscription. Where a shopper can opt in to marketing, it is a separate, unticked box, and only ticking it feeds these destinations.