Choose a version:

Consent checkbox

Requires enabling of the sms_marketing capability of the Customer Privacy capability group to work.

The consent checkbox component collects customer approval for a given policy. Use consent checkbox to gather opt-in consent for SMS marketing.

Consent checkboxes support a policy attribute that connects to Shopify's consent framework. For standard multi-purpose checkboxes, use checkbox instead.

Only the sms-marketing policy is supported. Consent state is managed by Shopify and persisted automatically — custom storage isn't supported.

Support

Targets (24)

Supported targets

Anchor to PropertiesProperties

Configure the following properties on the consent checkbox component.

Anchor to accessibilityLabel accessibilityLabel string: A label used for users using assistive technologies like screen readers. When set, any children or label supplied will not be announced. This can also be used to display a control without a visual label, while still providing context to users using screen readers.
Anchor to checked checked boolean Default: false: Whether the control is currently checked.
Anchor to command command '--auto' | '--show' | '--hide' | '--toggle' Default: '--auto': Sets the action the commandFor target should take when this component is activated. Available options:

'--auto': Performs the default action appropriate for the target component.

'--show': Displays the target component if it's currently hidden.

'--hide': Conceals the target component from view.

'--toggle': Alternates the target component between visible and hidden states.

'--copy': Copies the target clipboard item.

The supported actions vary by target component type. Learn more about the command attribute.
Anchor to commandFor commandFor string: The ID of the component to control when this component is activated. Pair with the command property to specify what action to perform on the target component. Learn more about the commandFor attribute.

When both commandFor and href are set, commandFor takes precedence. The command runs and the link doesn't navigate.
Anchor to defaultChecked defaultChecked boolean Default: false: Whether the control is checked by default.
Anchor to disabled disabled boolean Default: false: Whether the control is disabled, preventing any user interaction.
Anchor to error error string: An error message displayed below the field to indicate validation problems. When set, the field is styled with error indicators and the message is announced to screen readers.
Anchor to id id string: A unique identifier for the element. Use this to reference the element in JavaScript, link labels to form controls, or target specific elements for styling or scripting.
Anchor to label label string: The text displayed as the control label, which identifies the purpose of the control to users. This label is associated with the control for accessibility.
Anchor to name name string: The name attribute for the control, used to identify its value when the form is submitted. Must be unique within the nearest containing form.
Anchor to policy policy 'sms-marketing': The policy for which buyer consent is being collected. Used by the consent checkbox and consent phone field components to identify the type of marketing permission requested.

sms-marketing: Represents the policy for SMS marketing consent.
Anchor to value value string: The value used in form data when the control is checked.

Anchor to EventsEvents

The consent checkbox component provides event callbacks for handling user interactions. Learn more about handling events.

Anchor to change change <typeof tagName>: A callback fired when the consent checkbox value changes.

Learn more about the change event.

CallbackEventListener

A typed event listener for custom element events. The listener receives a `CallbackEvent` with the correct `currentTarget` type for the associated custom element tag.

(EventListener & {
      (event: CallbackEvent<TTagName, TEvent>): void;
    }) | null

CallbackEvent

An event type that narrows the `currentTarget` to the specific HTML element associated with the custom element tag. This provides type-safe event handling in callback listeners.

TEvent & {
  currentTarget: HTMLElementTagNameMap[TTagName];
}

Anchor to ExamplesExamples

Anchor to Collect SMS marketing consentCollect SMS marketing consent

Add a pre-checked consent checkbox for SMS marketing. This example displays a consent checkbox with defaultChecked, a label, and the sms-marketing policy.

Collect SMS marketing consent

A marketing consent checkbox with a policy-compliant label for collecting buyer consent.

html

<s-consent-checkbox

defaultChecked

label="Text me with news and offers"

policy="sms-marketing"

></s-consent-checkbox>

Anchor to Display an unchecked consent promptDisplay an unchecked consent prompt

Present an opt-in consent prompt that starts unchecked. This example uses a consent checkbox without defaultChecked so the customer must actively opt in.

html

<s-consent-checkbox

label="I agree to receive text message promotions"

policy="sms-marketing"

></s-consent-checkbox>

Anchor to Best practicesBest practices

Be transparent: Write labels that clearly describe what the customer is consenting to, such as "Text me with news and offers."
Use supported policies: Always set the policy attribute to a supported value like sms-marketing so Shopify can track consent.
Respect opt-in preferences: Default to unchecked unless opt-out is the intended behavior for the policy.
Don't duplicate consent: Avoid rendering multiple consent checkboxes for the same policy on the same page.

Was this page helpful?