Try logging out, deleting all "adobe"-related cookies in your browser, then logging back in. If that doesn't work, check if you have any browser extensions that are running in your normal Chrome/Edge browser windows but not in Chrome/Edge private windows nor Firefox.

Your CMS is probably using "rich text" for its punctuation. Verify that AA has been configured to use UTF-8 encoding. If you're using AEP Tags as your tag manager, then in your AA extension's "General" section, check that the Character Set has been preset to "UTF-8". If that doesn't solve your probl...

Just to clarify, if the user does this: 12:00pm: runs a search for keyword "foo". 12:03pm: clicks a result from the "foo" search results to open page B. 12:07pm: returns to the "foo" search results page by pressing the browser's Back button. 12:08pm: clicks another result from the "foo" search resul...

If you don't see any value at your extension level, then check your rules that have AA's Set Variables actions, and check if those actions are setting the Page Name value there.

In simple terms, it's everyone who's been to any part of your website / mobile app.

Also, you can check the timestamp of the library build, by running _satellite.buildInfo.buildDate in your browser console. This helps you to see if you're loading an older build, in which case, clearing your browser cache or using a private window (as @Avinash_Gupta_ suggested) should help.

There's always a risk when updating any extension, including the vital Core extension. And yes, it sucks that AEP Tags doesn't allow you to rollback to a previous extension version if an error is found. You could choose to ignore the updated extension. But if you ignore the extension versions repeat...

@sdr1 , you're right. I don't know why I had suggested naming the data element as "event.message....". @SkyGazer , skip the whole data element creation. Just use "event.message.eventInfo" directly in your custom code, e.g. let eventInfo = event.message.eventInfo; let path = eventInfo.path;  

It's not as straightforward as putting the metrics (or dimensions) in a freeform table vs a fallout visualisation and expecting the numbers to match. I created a simple 2-step Visitor-based fallout from my data, then built a segment from the 2nd step's green area, i.e. proportion of visitors who had...

If you had updated your Classification Rules 2 days ago, then I would expect you to be able to see the results by now. Some reasons that you don't: If you're using regular expressions in your Rules, then the expressions might have been defined wrongly.There is whitespace in your key values.You didn'...