Are there any jmx statistics exposes for the the number HTTP requests made,  as well as potentially broken out by status code response? Looking at /system/console/jmx - I didn't see anything out of the box that seemed to handle this.

When you have the forbidden error - check your browser console for all the cookies set for that domain.  Cookies are sent from the browser to the (web) server for things like state management. The sum size of all the cookie header sent by the browser is too large for the server (as configured) to ha...

I've suggested this too. Here's to hoping its implemented.reference: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-launch/search-add-rule-name-to-results/idi-p/403944

Is there a way to disable this Poller? We don't seem to be using anything livefyre related

I don't think Custom Event will work. The event is fired onto the window object. And the custom event rule seems to be element focuses. But I do see "Custom Code" in which case I could add my window.addEventListener("message". function(){if(checkPasses) trigger()})

Is there an event configuration where my rule would trigger on the equivalent of window.addEventListener("message" ...) ? Then even more vexxing is can I then create rule conditions filtering on the values in event.origin and event.data? Based on what I see - I think the answer is no. Use case is I ...

There are a 2 issues. (one right now, one I bet you'll discover later) 1) eVar38 is on the "s" variable. When editing custom code - The variable with the analytics attributes is "s". [But if you look in the browser during debugging, the minifier may change the variable to probably by "t".] This mean...

If you remain on the page to allow subsequent events trigger, you need to clearVars after each beacon send otherwise each event will have all the variables included from before (or at least the ones not overridden) So adding the clear variables rule after the beacon fire is the way to go. If you hav...

I see the Storage duration is set to session - So I suspect the initial page view was missing that parameter so that value carried as empty the rest of the session. https://experienceleague.adobe.com/docs/launch/using/ui/data-elements.html?lang=en

query is not an property on location. Based on the name, it seems like query means query-string is desired. In which case - that would be "location.search"