The storefront account component (sign-in UI) now adds a marketing subscription checkbox below the email field. Customers who check it and complete sign-in are automatically added to the email subscriber list.
The account component was only a UI for entering an email address and signing in. Capturing subscriptions required a separate path (checkout, a separate form, etc.).
A checkbox sits right below the email field, so you cancapture subscriptions within the existing sign-in flow. The setting uses the same option shared with checkout.
| Item | Before (previous) | After (now) |
|---|---|---|
| Checkbox in the sign-in UI | None | Shown directly below the email field |
| Timing of adding to the subscriber list | A separate flow such as checkout | When sign-in completes |
| Admin screen for opt-in settings | Settings > Checkout > Marketing opt-in | Shares the same location |
| Impact on customers who only want to sign in | — | Unchanged from before if the box is left unchecked |
| API / Webhook specifications | — | Not documented |
In the Shopify admin, open Checkout from Settings.
Here you decide whether the box is checked or unchecked by default.
Once you add the account component menu to your online store, it is reflected automatically.
The article explicitly states it is below the email field , and the placement is not a spec that themes can freely move—it is the component's default behavior.
There is no independent opt-in setting for sign-in; it referencesSettings > Checkout > Marketing opt-in directly. Changing it on the checkout side also carries over to the sign-in side.
Simply checking the box does not subscribe the customer; they are added to the subscriber listat the point the sign-in process is completed. Sessions abandoned partway through are not subscribed.
Whether the box is shown pre-checked or unchecked is determined by the Marketing opt-in setting under Settings > Checkout. It must align with regional consent requirements.
The article covers only the admin operational flow. How this is reflected in the Customer object's email_marketing_consent fields, or the differences in Webhook events, isnot describedin this article. If you build CDP / MA tool integrations, separate verification is required.