MWPW-199932 [MEP] Update Consent Policy

[vgoodric]

Larger goals

• Implement the new guidance provided in https://wiki.corp.adobe.com/spaces/marketingtech/pages/3872515603/MEP+Manifests+and+User+Consent
• Mark manifests that are not specifying the consent type in the MEP button so that users are warned the manifest needs to be updated soon
• Provide all reasons why you are not eligible for the manifest to perform normally
• Create the ability to choose, save and retrieve an experience for offer tests.

Update details

• Introduced consentType to replace mktgAction in various functions and components.
• Added logic to handle consent requirements, including consentNotSpecified and consentEnabled flags.
• Updated manifest error handling to include consent-related errors.
• Modified tests to reflect changes in consent handling and ensure proper functionality.
• Enhanced analytics tracking based on consent requirements.

Resolves: MWPW-199932

Before/After

• Before: https://main--milo--adobecom.aem.page/?martech=off
• After: https://mepconsent--milo--adobecom.aem.page/?martech=off

QA Instructions:
No country spoof: https://main--da-cc--adobecom.aem.page/drafts/mepdev/fragments/2026/q3/mepconsent/?mepnext=on&milolibs=mepconsent
With country spoof: https://main--da-cc--adobecom.aem.page/drafts/mepdev/fragments/2026/q3/mepconsent/?mepnext=on&milolibs=mepconsent&country=za

The page has 7 pods and 7 manifests (one to target each pod). Each pod states the manifest settings and under what conditions the pod's title should be updated. Each time, check for:

• Each pod is updated or not updated per the description versus your cookie settings and country
• Look in the MEP button to see if the manifests you are ineligible for are marked as such
• Manifests that are ineligible for multiple reasons list all relevant reasons when you hover over the warning
• The manifest missing the consent setting is always marked in red
• Your chosen experience persisting in pod 2 even when you remove consent

Steps

• Make sure all incognito browsers are closed.
• Open a new incognito window.
• Check both links (I recommend having them both open in separate tabs).
• Update your cookies to remove advertising consent and check both links again
• Update your cookies to remove performance consent and check both links again

Checking the new experience saving and randomizing function

• Add performance consent back and clear cookies
• Check that your chosen experience is saved in local storage
• Remove performance consent and reload several times. Your experience should persist
• Clear cookies again and clear local storage
• Note in the network tab that Target is not called
• Note which experience you are given and that it is now saved in local storage.
• Reload to confirm your experience persists
• Clear local storage and reload until you get a different experience
• Note which experience you are given and that it is now saved in local storage.
• Reload to confirm your experience persists

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

• Re-sync branch

Commits

• 6e44d27 ✅ (latest)
• 27a0be3 ✅
• f5d0cc5 ✅
• 712f8b2 ✅
• 1f81d84 ✅
• 62afbb7 ✅
• 6568b39 ✅
• 413e509 ✅
• a64ff38 ✅
• 1c59f30 ✅
• 5fb685d ✅

[jpratt2]

@vgoodric
Here is the code review from Claude:
milo-mepconsent-review.docx
summary: