Distinguish consent by channel
A customer who receives email may not have agreed to SMS. The planned view must keep those states separate.
Integrations Omnisend
OmnisendPlanned
Omnisend context for ecommerce support.
Plan an Omnisend connector for useful subscriber context across email and SMS, with channel-specific consent kept intact.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Email marketing
What we’re planning to connect.
- 01Omnisend
- 02Planned connection
- 03Message support
Investigate campaign questions
Selected segment context can help staff understand which store communication the customer expected.
Keep order facts at the store
Use the commerce system for authoritative order status; marketing segments are not proof of a purchase.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Confirmed contact
Email and SMS consent separately
Selected segment context
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Identify the store and define the email and SMS fields support is allowed to inspect.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Test a contact opted in to one channel and opted out of the other without changing either preference.
Before you connect
Omnisend integration questions
Can I connect Omnisend to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Test a contact opted in to one channel and opted out of the other without changing either preference.