nsx-marketing-consent
#
IntroductionMarketing consent is the capture of a customer's contact preferences for marketing purposes.
This experience pattern should be used in any journey where customer marketing preferences are captured.
This component is only used to capture and submit customer preferences, not view or change existing preferences.
#
Content guidanceIt is possible to change the heading and the first paragraph to suit specific context. However, we recommend using the default content as these have been signed off by the legal team.
If there is an official update to the default content, please inform the Nucleus team so that the the component can be updated.
#
Best practiceThis component is legally required when capturing contact preferences that will be used for marketing purposes.
๐ Do's | ๐ Don'ts |
---|---|
Always keep the same options | Reorder the options |
Use at the end of a journey that captures contact information used for marketing purposes | Use when collecting contact information that will be used solely for a service offering e.g. Booking an engineer |
Always use inside of an ns-form component | Have any of the options pre-checked |
Use only once per journey |
#
Usage#
Component placementThe nsx-marketing-consent component can only be used in the ns-form component.
#
SpecificationSlots | Type |
---|---|
heading | h tag |
paragraph | p tag |
#
Feedback- Do you have insights or concerns to share? You can raise an issue via Github bugs.
- See all the issues already raised via Github issues.
๐ฉ ๐ ๐ฆ If you have any questions, contact us on Microsoft Teams in the Nucleus Design System channels.