The reason I'd avoid using a bot rule is that the traffic isn't actually from a bot. Instead, it's from someone looking at an ad on Snapchat and the destination URL for that ad loading in the background. You may wind up advertising on Snapchat in the future without the pre-load function activated, a...

Is there any way to limit the segments/calculated metrics/etc. to the report suite selected in Analysis Workspace? I currently see everything, and with the same names used for some segments in different report suites it makes things a bit painful. I would like to avoid having to create a bunch of di...

I had to deal with an ad agency activating the Snapchat preload without informing anyone of the decision, and it was a giant pain. I wound up creating a virtual report suite and applied a segment excluding all Snapchat traffic because most of it was not "real" (i.e. the ad preloaded but the "visit" ...

The Experience Cloud ID is found in the data collection query string, and uses the parameter "mid". A list of the data collection query parameters can be found at https://docs.adobe.com/content/help/en/analytics/implementation/javascript-implementation/data-collection/query-parameters.html . You can...

The report is not using classifications of the variable in question, and the debugger shows that the value is being set correctly in the call. Because we're not seeing a similar issue in Ad Hoc or Analysis Workspace, this seems to be something that is specific to Report Builder.The issue started ove...

Has anyone else experienced a sudden increase in ::unspecified:: values in Report Builder? I recreated the Report Builder file in both Ad Hoc and Analysis Workspace and didn't have the same issue. I was running Report Builder version 5.6.29.0 when I first discovered the issue, but am still experienc...

Gigazelle​It's been 8 months since OP noted this bug, and it still hasn't been fixed. Is the development backlog causing the delay, or is it because not enough users have reported the issue?

I recommend reading up on the technical aspects of setting up cross-domain tracking before contacting Adobe support about secondary server calls. In order to monitor how a single "person" engages with different websites requires there to be a common value that the different websites share. For examp...

There have been a number of posts about the impact of third-party cookies in the forums. While most of the posts focus on Apple's ITP, Firefox is following a similar (albeit not the same) tack. Check out Intelligent Tracking Prevention (ITP) and Adobe Analytics and https://medium.com/adobetech/safar...

It's possible that this is related to Apple's Intelligent Tracking Prevention (ITP) initiative. ITP is supposed can impact how visitors using Apple products are tracked on your site, including cookie persistence, cross-domain tracking, and third-party cookie blocking. The impact varies according to ...