In Shopify Messaging, marketing automations send only to customers subscribed to marketing, so the welcome email is gated by consent at send time. The risk is a trigger that fires for the wrong people: newsletter signups mixed with account creation, imported contacts, or customers who unsubscribed after signing up. Fix the trigger, confirm the subscription state, exclude recent buyers, then test with a second address before switching it on.
What does "the wrong subscribers" actually mean here?
Two different problems get confused. The first is sending to someone who never consented — that is a consent problem. The second is sending a welcome to someone who consented months ago, already bought, or already received the same welcome — that is a relevance problem. Both make the automation look broken, but only the first carries real risk.
Shopify's own documentation is clear on the baseline: emails sent through marketing automations in Shopify Messaging go only to customers who are subscribed to marketing (Shopify Messaging marketing automations). That is the safety net. Your job is to make sure the trigger and the audience around it do not create the second problem, and that your store's subscription data is accurate enough for the first.
Why does a newsletter signup trigger catch the wrong people?
A welcome automation typically fires on a newsletter signup. But "signed up" can mean several things in a Shopify store:
- A customer ticked the marketing checkbox at checkout.
- A customer created an account and accepted marketing emails.
- Someone submitted a footer newsletter form.
- A contact was imported or added manually with marketing consent recorded.
If your trigger is broad — any subscription change, or any new customer — the welcome can land on people who joined for a different reason. A customer who ticked the box at checkout expecting order updates may not expect a welcome series. A contact imported from an old list may have consented under different wording.
The account-creation trap
Account creation and marketing consent are separate states. A customer can create an account without subscribing to marketing. If your automation is built on "customer created" rather than "subscribed to marketing", you are relying entirely on the send-time filter to catch it. That filter is real, but it means your automation silently does nothing for those people — which is fine — while giving you a false sense that the flow is working.
A decision table for choosing the trigger
| What you want to welcome | Trigger to look for | Main risk |
|---|---|---|
| Newsletter subscribers | Subscription to marketing | Imported or re-subscribed contacts |
| New account holders who opted in | Subscription to marketing, not account creation | Confusing account creation with consent |
| First-time buyers | Order placed, with a marketing-subscribed condition | Welcoming someone who is mid-purchase |
| Everyone who joins any list | Subscription to marketing, with exclusions | Duplicate welcomes after re-subscribe |
Use the narrowest trigger that matches the intent. If you cannot find a trigger precise enough in Shopify Messaging, Shopify's documentation notes that a custom automation or one including a third-party app can instead be built as a workflow in the Shopify Flow app (same source). That is the escape hatch, not the default.
How do you check consent before the email goes out?
You cannot inspect every contact by hand, so build a verification routine instead of trusting the trigger.
- Open the automation and read the audience condition. Confirm it references marketing subscription, not just customer status.
- Check whether the automation excludes customers who unsubscribed. If the platform filters at send time, note that the exclusion is automatic; if you have built a custom Flow workflow, add the condition yourself.
- Look at how re-subscribes are handled. Someone who unsubscribed and later subscribed again is a legitimate subscriber, but they may receive a second welcome. Decide whether that is acceptable.
- Check the timing. A welcome sent immediately after signup is normal. A welcome sent days later, after the customer has already bought, reads oddly.
Example (hypothetical)
Imagine a small UK homeware store with 400 newsletter subscribers. The welcome automation is set to fire on any marketing subscription. A customer unsubscribes in March, then re-subscribes in June through a pop-up. The automation fires again. The customer receives the same welcome they got in March. Nothing illegal happened — they consented — but the message feels careless. Adding a simple condition such as "has not received this automation before" or delaying the second send would have prevented it. The figures here are illustrative only.
What should the welcome email itself avoid?
Keep the first message narrow. A welcome email that also pushes a discount, a survey and three product categories is doing too much. The job of the first send is to confirm the subscription and set expectations for what arrives next.
Two practical rules:
- Do not repeat the abandoned checkout message. Shopify treats abandoned checkout automation emails separately from other marketing automation emails for counting purposes (same source), but from the customer's side both can arrive close together. If someone abandons a cart and then subscribes, they may get two emails in an hour. Sequence them deliberately.
- State the frequency. "You'll hear from us about once a month" is more useful than "welcome to the family".
How do you test without emailing real customers?
Testing is where most stores skip steps. A workable routine:
- Create a second email address you control, ideally on a different domain from your main one.
- Subscribe it through the same form a real customer would use.
- Confirm the subscription is recorded as marketing-subscribed in the customer record.
- Wait for the automation to fire and check the message renders correctly on a phone.
- Unsubscribe that address, then re-subscribe it, and watch whether the welcome fires twice.
- Repeat once with an address that creates an account but does not tick the marketing box. Confirm no welcome arrives.
Step six is the one that catches the account-creation trap. If a welcome arrives there, your trigger is too broad.
What are the most common mistakes?
- Treating account creation as consent. It is not.
- Importing a list and assuming the subscription state carried over correctly.
- Forgetting that a re-subscribe can trigger a second welcome.
- Letting the welcome and the abandoned checkout email collide.
- Testing with your own admin address, which may behave differently from a customer address.
- Assuming the send-time filter makes trigger choice irrelevant. It protects consent, not relevance.
Follow-up questions
Does Shopify Messaging send welcome emails to people who never opted in?
No. Marketing automation emails are sent only to customers subscribed to marketing, according to Shopify's documentation. If someone never opted in, the send-time filter should prevent delivery. The practical risk is not that filter failing, but that your trigger fires for people whose consent came from a different context than the message assumes.
Can I build a welcome automation with stricter rules than the default?
Yes. Shopify's documentation points to the Shopify Flow app for custom automations or ones that include a third-party app. That lets you add conditions the standard builder does not offer, such as excluding customers who already received the automation or who placed an order in the last few days. The trade-off is more setup and more to maintain.
