[MWPW-189877] Site Redesign Analytics

[AdobeLinhart]

Updates:

1. Router Marquee

• Add data-block-daa-lh to block div so the parent block doesn't get an lh value
• Adds daa-lhs for slides so each slide is treated like a block
• Updates the daa-lls for navigation button clicks to keep the headline from the marque they are associated with
• Adds an intersection observer that fires when the user first sees each slide, including if the slide was requested by the user or shown automatically. Seeing a slide from hovering or swiping on mobile is considered a user request. Auto-advance or scrolling up to an unseen slide is considered automatic.

3. Elastic carousel

• added daa-ll value because the title is not correctly detected when the headline is inside the link
• also added an analytic the first time a user hovers over the carousel
• deconstructed left.children for improved readability

4. Explore cards

• Added custom data-tracking-label so only header is used for link text

5. Modal

• imported sendAnalytics and fireAnalyticsEvent to reuse identical code

7. personalization.js

• imported sendAnalytics, fireAnalyticsEvent and getMepConsentConfig to reuse identical code

8. martech/attributes.js

• Adds a check for blocks to bypass adding daa-lh if it has a data-block-daa-lh attribute.

9. martech/helpers.js

• Move getMepConsentConfig, fireAnalyticsEvent and sendAnalytics into this file for shared use

Confirmed default functionality is sufficient:

1. Cards
2. Carousel
3. News
4. rich-content

Being handled by other teams:

1. Footer
2. Brand Concierge
3. GNAV

This adds analytic tracking to marquee slide controls, differentiating between user and auto impressions. Each tracking should only fire once per slide.
QA Instructions for router-marquee

• Open test link.
• Verify that the router marquee block does not have a daa-lh attribute.
• Verify that rm-card and rm-slide tracking attributes have been updated.
• Follow instructions for Option 2 to monitor network calls.
• Test each of the actions described in features and/or use the analytic list below.
• Confirm that event only fires the first time each slide is seen, regardless if it's from auto or a user action.

Expected Analytics:

rm-card

• daa-ll: rm-nav${index}|${title of associated slide}
• Hover: user-${rm-card-label}-${index}

rm-slide

• daa-lh: b${index}|rm-slide|${mepMartech}
• Auto: auto-${rm-card-label}-${index}
• Intersection: auto-${rm-card-label}-${index}

Events should look like the following and start with "user" for user actions or "auto" for automated.

Example:

Resolves: MWPW-190372

Password: site-redesign-2026

Test URLs:

• Before: https://load-c2-styles--upp--adobecom.aem.page/homepage/drafts/ramuntea/redesign-demo?milolibs=site-redesign-foundation
• After: https://load-c2-styles--upp--adobecom.aem.page/homepage/drafts/ramuntea/redesign-demo?milolibs=MWPW-190372
• Psi: https://MWPW-190372--milo--adobecom.aem.page/?martech=off