Hi @Jennifer_Dungan, Interesting point in regards to the "bookmarks" on mobile phones - something I'll want to look into! 100% not a sliver bullet, it has to be paired with other behavioural metrics. In our organisation's context, we do not expect a normal user to access the site via headless chrome...

Hi @skatofiabah ,A normal user agent will look something like this 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36'. You can also find out what is your personal user agent by opening dev tools and navigating to the console tab an...

Hi @Meghan_Powers,We're also seeing lots of ending ".999" browser versions, my assumption after using the user agent as a breakdown, it seems like some sort of bucketing method. Its just a guess though! Cheers,Vernon

Thank you @fhusain! It seems the error must be with how I've nested the containers. After modification, it works now. 

Hi @skatofiabah,For more information on user agent, here's a documentation of the string format.We capture user agent as a seperate eVar via the JS variable navigator.userAgent. I would personally highly recommend having this captured (especially with the rise of crawlers to power Gen AI tools). An ...

Hi all, Has anyone successfully updated the segment definition via the AA API 2.0? I can update the name, description and owner but not the definition.I get an 400 response when trying the below JSON with "definition" added and a 200 response when removing "definition" and just having "container" : ...

Hi @skatofiabah, Agreed that the query string parameter would not be indicative of a bot. Personally, what we use is a mixture of User Agent, IP address, Countries, Click behavioural data, Timestamp and page views events to help identify the larger bots. I would also check the IAB filter to ensure t...

Hi @abhijithr, There is a 10mb limit via the email delivery method, you may have to use an alternative delivery method like Amazon S3 bucket or Azure, etc. I personally use S3 bucket and it's pretty easy to get it set up.  Cheers

Just got the root cause from Adobe Support:"The report suites collections API is being replaced by a newer data suites API. The initial rollout exposed the missing fields behind an expansion. The service was rolled back to the original report suites API to resolve the issue." All seems to be working...

Confirming it is currently working for me too!