@W-19143871 Marketing Consent Footer Email Capture component#3671
Closed
mitesh-patel-crm wants to merge 10 commits intodevelopfrom
Closed
@W-19143871 Marketing Consent Footer Email Capture component#3671mitesh-patel-crm wants to merge 10 commits intodevelopfrom
mitesh-patel-crm wants to merge 10 commits intodevelopfrom
Conversation
feat: react hooks for Shopper Consents v1.1.3. linking with commerce-sdk-isomorphic@4.0.0-nightly-20251031080733.
…ting subscription hooks (#3471) * footer component updated. button handler added. labels updated. * handler to query shopper-consents SCAPI using &tags=email_capture, and also to opt-in for all matching subscriptions using the input email address as the contactPointValue.
…-preferences # Conflicts: # packages/commerce-sdk-react/package-lock.json # packages/commerce-sdk-react/package.json # packages/commerce-sdk-react/src/hooks/types.ts # packages/template-retail-react-app/app/hooks/index.js
Collaborator
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
…n EnableConsentWithMarketingCloud flag is enabled
…y if feature is not enabled.
…y if feature is not enabled.
mitesh-patel-crm
force-pushed
the
feature/develop-shopper-consent-marketing-preferences
branch
from
e97788e to
f0a7015
Compare
mitesh-patel-crm
force-pushed
the
feature/develop-shopper-consent-marketing-preferences
branch
from
f0a7015 to
e97788e
Compare
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
REPLACING with PR #3674 to ensure all commits are signed.
This change is to add support for the Marketing Consent feature, which allows capture of shopper consent for marketing communications.
Description
The feature uses the Shopper Consents API to opt shoppers into consent subscriptions configured by an administrator in B2C Commerce.
Requires the
EnableConsentWithMarketingCloudShopper Configurations flag is set (meaning the feature is enabled in ECOM).SLAS Client requires the scope
sfcc.shopper-consentsto read consent options, andsfcc.shopper-consents.rwto submit consent (opt-in or opt-out).As an example, the SubscribeMarketingConsent footer component uses the useMarketingConsent hook for managing consent data and mutations via useEmailSubscription to help manage email subscriptions. This example footer component will not attempt any callouts if the feature is disabled (as indicated by the
EnableConsentWithMarketingCloudShopper Configurations flag).Types of Changes
Changes
How to Test-Drive This PR
Checklists
General
Accessibility Compliance
You must check off all items in one of the follow two lists:
or...
Localization