No, you still have to build each environment... The Dev environment won't get the "upstream" resources until it is built and deployed.   So let's say you have 5 Environments.... Production, Staging, Dev 1, Dev 2 and Dev 3. (Prod and Staging you can only have one each, but you can have many Dev envir...

I haven't reached out to support... I figured since my code was kind of a modification to get buttons to work I wasn't going to get very far.... I felt I might have better luck talking to the product team directly, but I think they have been busy.. they didn't answer my post in the champions slack.....

No worries, I don't need the specific site.. just curious about the type of content.   So I see that GSK.com has a mix of article type content, but also products... not sure if your site has a mix.. I would think that trying to see the bounce rate per page type / section would be helpful. Along with...

Keep in mind that the 3 mins average time would be calculated from the non-bounces.... Adobe is not a heartbeat system... it's engaged time is a calculation between time stamps.... if a user bounces (which by Adobe's definition means a single server call in a visit), then there is no second timestam...

Ah you're right, I did miss the last question... that one I am not sure about... I don't have an active APIs running at this time.. Adobe also has multiple API endpoints...    Most of the examples I see seem to use: https://analytics.adobe.io/api/{GLOBAL_COMPANY_ID}/   Followed by the endpoint, then...

Adobe changed something recently... even the custom code to pick up buttons with Activity Map is no longer working for me... which makes me sad, cause my solution has worked for over a decade, and now I am missing all those buttons being tracked.....

API 2.0 is "fast" because it limits what you can pull back at once... that's why when you are doing breakdowns, you have to make multiple requests... one for each breakdown.   API 1.4 allowed for "all in one" calls because of the queuing system.   However, if you are basically looking for "Dimension...

The "Page" dimension is not calculated... this is every value that was sent to the Page dimension... "Entry Page" however is calculated... Adobe tries to determine the first value that was set during a visit. When that is mixed with a segment (whether a full segment, or a quick segment, or stacking ...

Good luck! I am sure the folks over there will be much more help.

Hahah yeah, this would be awesome... but it might make them more careful in the future....