[BRANDCON-8316] Instrument analytics for BC in-chat navigation behavior by loganzartman · Pull Request #6579 · adobecom/milo

loganzartman · 2026-08-26T23:03:13Z

adds analytics for when users navigate back from an outgoing same-tab link.

adds navigation:backNavigation analytics event type matching spec in https://jira.corp.adobe.com/browse/BRANDCON-8316
- emitted on: bfcache (pageshow), and non-cached back/forward (via performance entries check)
augments BC client onEvent to record link information in browser history entry

depends on web client PR: https://github.com/adobe-brand-concierge/acom-brand-concierge-web-agent/pull/247
but merge/deploy order is not important

Resolves: BRANDCON-8316

Test URLs:

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

sample payloads

CTA click:

{
  "eventType": "navigation:backNavigation",
  "data": {
    "clickType": "product_card_cta",
    "sessionId": "e973c3ad-1a5a-4b01-bd9f-765d5b58d4e1",
    "sourcePage": "http://localhost:6456/drafts/nala/blocks/brand-concierge/brand-concierge",
    "destinationPage": "https://business.adobe.com/products/brand-visibility.html",
    "loginStatus": "logged-in",
    "navigatedBack": true
  }
}

Inline hyperlink:

{
  "eventType": "navigation:backNavigation",
  "data": {
    "clickType": "inline_hyperlink",
    "sessionId": "e973c3ad-1a5a-4b01-bd9f-765d5b58d4e1",
    "sourcePage": "http://localhost:6456/drafts/nala/blocks/brand-concierge/brand-concierge",
    "destinationPage": "https://business.adobe.com/products/brand-visibility.html",
    "loginStatus": "logged-in",
    "navigatedBack": true
  }
}

aem-code-sync · 2026-08-26T23:03:15Z

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

fa49671 ✅ (latest)
7f51c17 ✅
cdc4258 ✅
09d6bb4 ✅
bf1d349 ✅
82a88e7 ✅
54bfdbb ✅
264aed8 ✅
a02211d ✅
1644a16 ✅
06b5be0 ✅
b42c6a5 ✅
ae36b5b ✅

loganzartman · 2026-08-26T23:27:57Z

      onEvent: (event) => {
+        if (event.eventType === 'card:clicked') recordBcNavClick('product_card_cta', event.data?.element?.productPageURL);
+        else if (event.eventType === 'cta:clicked') recordBcNavClick('cta', event.data?.element?.productPageURL);
+        else if (event.eventType === 'link:clicked') recordBcNavClick(event.data?.element?.linkType ?? 'inline_hyperlink', event.data?.element?.href);


new event type; pending acom-brand-concierge-web-client PR

Covers getChatSessionId cookie parsing and the bcAnalytics navigation:backNavigation payload (event name + required fields). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

JasonHowellSlavin

LGTM. I might review the comments, we tend to try and be as comment free in our code in Milo.

The only thing staying approval on my end is that everything done here should also be done in /libs/c2/blocks/brand-concierge

JasonHowellSlavin · 2026-08-27T16:11:49Z

+        if (event.eventType === 'card:clicked') recordBcNavClick('product_card_cta', event.data?.element?.productPageURL);
+        else if (event.eventType === 'cta:clicked') recordBcNavClick('cta', event.data?.element?.productPageURL);
+        else if (event.eventType === 'link:clicked') recordBcNavClick(event.data?.element?.linkType ?? 'inline_hyperlink', event.data?.element?.href);


Seems like a decent spot to use a switch case.

colloyd · 2026-08-31T16:21:45Z


  setCssGnavHeight();

+  const emitAnalyticsIfBackNav = () => {


@loganzartman Can this be moved to bc-analytics.js? We recently did a massive refactor to cut down on extraneous stuff in the base block code and this being an analytics specific function, it seems a good fit to move there.

Also, there is a brand-concierge-global block that will likely need this same treatment. It imports from the base brand-concierge block, so moving to bc-analytics will be helpful for that block also:

https://github.com/adobecom/milo/blob/stage/libs/blocks/brand-concierge-global/brand-concierge-global.js

yeah, that's a good idea. I've pulled everything into bc-analytics with a single initAnalytics hook for the block. does that seem good?

Seems ok, there are other analytics elements to this that are invoked when the web client is bootstrapped and as long as the rest of it still works, then this looks great.

Again, though, we should add this to the brand-concierge-global block (the one that is used for gnav as seen on bacom stage here so it gets this goodness as well:

sorry, I misread your first comment. I've added the init call to brand-concierge-global as well. I didn't realize these were both the brand concierge block.

Thread the widget's cta:clicked `source` enum through history state into the navigation:backNavigation payload, so back-nav events are attributable to the CTA surface. Use an options object for recordNavClick. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

colloyd

Looks good!

colloyd · 2026-08-31T22:07:23Z

@loganzartman So we are trying to do some testing on the milo code contributions here, but the name format of the source branch is making it impossible to test, specifically the "/" and caps in the branch name. If we rename so we can test it, it will close the PR.

For context, we might ordinarily test something like this using one of two methods:

An AEM url, using this pattern: https://[branch-name]--milo--adobecom.aem.page/[path to test page]
Or on a stage page, like so: https://business.stage.adobe.com?milolibs=[branch-name]

Neither of these methods will work with the current branch name format.

As an alternative to renaming and hence closing your pr, you can push this same set of changes to a new branch, such as a simple: brandcon-8316

That way we could test your proposed changes using that other branch name without closing this PR.

loganzartman · 2026-08-31T22:16:33Z

ok, pushed to brandcon-8316: #6608
@colloyd

JackySun9 · 2026-09-01T00:07:47Z

@loganzartman do we need to wait for https://github.com/adobe-brand-concierge/acom-brand-concierge-web-agent/pull/247 get merging before do any validation? and if you can give some user cases to check, what will be better

disha-akarte · 2026-09-01T00:17:48Z

@loganzartman do we need to wait for https://github.com/adobe-brand-concierge/acom-brand-concierge-web-agent/pull/247 get merging before do any validation? and if you can give some user cases to check, what will be better

@JackySun9 I've asked Analysts to validate this, will let you know once we have a go ahead

github-actions · 2026-09-01T04:21:10Z

Reminder to set the Ready for Stage label - to queue this to get merged to stage & production.

github-actions · 2026-09-02T03:43:59Z

This pull request is not passing all required checks. Please see this discussion for information on how to get all checks passing. Inconsistent checks can be manually retried. If a test absolutely can not pass for a good reason, please add a comment with an explanation to the PR.

initial changes

ae36b5b

loganzartman force-pushed the akarte/BRANDCON-8316 branch from 1896144 to 41457e9 Compare August 26, 2026 23:04

aem-code-sync Bot deployed to akarte/BRANDCON-8316 August 26, 2026 23:04 View deployment

flesh out analytics payload; cleanup

b42c6a5

loganzartman force-pushed the akarte/BRANDCON-8316 branch from 41457e9 to b42c6a5 Compare August 26, 2026 23:05

loganzartman commented Aug 26, 2026

View reviewed changes

BRANDCON-8316: add tests for BC back-navigation analytics

06b5be0

Covers getChatSessionId cookie parsing and the bcAnalytics navigation:backNavigation payload (event name + required fields). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

loganzartman marked this pull request as ready for review August 27, 2026 00:01

disha-akarte requested a review from JasonHowellSlavin August 27, 2026 15:59

JasonHowellSlavin reviewed Aug 27, 2026

View reviewed changes

disha-akarte approved these changes Aug 27, 2026

View reviewed changes

colloyd reviewed Aug 31, 2026

View reviewed changes

loganzartman and others added 3 commits August 31, 2026 11:08

PR feedback; restructure

1644a16

fix payload

a02211d

loganzartman commented Aug 31, 2026

View reviewed changes

Comment thread libs/blocks/brand-concierge/bc-analytics.js Outdated

Apply suggestion from @loganzartman

54bfdbb

aem-code-sync Bot deployed to akarte/BRANDCON-8316 August 31, 2026 19:06 View deployment

loganzartman requested review from JasonHowellSlavin and colloyd August 31, 2026 19:07

init backnav analytics in bc-global

82a88e7

colloyd approved these changes Aug 31, 2026

View reviewed changes

colloyd requested a review from JackySun9 August 31, 2026 20:19

aem-code-sync Bot deployed to brandcon-8316 August 31, 2026 22:15 View deployment

loganzartman mentioned this pull request Aug 31, 2026

Brandcon 8316 #6608

Draft

loganzartman added 2 commits September 1, 2026 16:18

c2 impl

bf1d349

c2 basic tests

09d6bb4

aem-code-sync Bot deployed to brandcon-8316 September 1, 2026 23:19 View deployment

Merge branch 'stage' into akarte/BRANDCON-8316

cdc4258

aem-code-sync Bot deployed to akarte/BRANDCON-8316 September 3, 2026 20:15 View deployment

use new destination value

7f51c17

aem-code-sync Bot deployed to brandcon-8316 September 3, 2026 23:01 View deployment

c2 destination

fa49671

aem-code-sync Bot deployed to brandcon-8316 September 3, 2026 23:14 View deployment

Uh oh!

Conversation

loganzartman commented Aug 26, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

sample payloads

Uh oh!

aem-code-sync Bot commented Aug 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

loganzartman Aug 26, 2026

Choose a reason for hiding this comment

Uh oh!

JasonHowellSlavin left a comment

Choose a reason for hiding this comment

Uh oh!

JasonHowellSlavin Aug 27, 2026

Choose a reason for hiding this comment

Uh oh!

loganzartman Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

colloyd Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

loganzartman Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

colloyd Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

loganzartman Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

colloyd left a comment

Choose a reason for hiding this comment

Uh oh!

colloyd commented Aug 31, 2026

Uh oh!

loganzartman commented Aug 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

JackySun9 commented Sep 1, 2026

Uh oh!

disha-akarte commented Sep 1, 2026

Uh oh!

github-actions Bot commented Sep 1, 2026

Uh oh!

github-actions Bot commented Sep 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

loganzartman commented Aug 26, 2026 •

edited by github-actions Bot

Loading

aem-code-sync Bot commented Aug 26, 2026 •

edited

Loading

loganzartman commented Aug 31, 2026 •

edited

Loading