some of options ..1. With Bot rules you can also filter by User Agent string (in addition for IPs) .. so, if you're able to identify a consistency in the UA string of the bots (that differs from normal) you can block this way.2. Sounds like you already have a segment in place to identify spikes, if ...

Hi @frankg15568879​We may be talking about two separate but related issues ...1. Issue caused by ITP where s_vi third party cookies being accepted, but deleted mid session, inflating the visitors and visits metrics.  Granted we've only implemented on a single domain, however the issue does appear to...

Frank,So ...1. Whilst Marketing Cloud ID Service uses first party cookies it also uses the demdex third party cookie to identify 'visitors' across multiple domains, that of course if the demdex cookie is accepted. ie. if cookie exists it'll use that to identify the visitor and then use this for the ...

Rickysee below ..Late Friday evening I moved over one of our sites to using Experience Cloud ID Service. For those that aren't aware this whilst dropping a first party cookie also drops a third party demdex cookie and thus allows for cross site de-duplication of visitors (if browser accepts a third ...

Update : Please note Adobe has recently changed it's advice and updated the original articleAdobe Analytics and ITPITP is inconsistent with Adobe's 3rd-party cookies. Occasionally, cookies are accepted but are frequently removed, even mid-visit.There's no timelines on a work around solution and ther...

Marion .. One of the calculated metrics below, this sums up the page views for articles that had 100+ PVs in the specified time frame.  There is a similar which does a distinct count of the rows too With regards being able to trend I'm not sure I know what you mean.  As you'll note from the calculat...

Also worth considering is creating exclude segment(s) ... if your IP's exhibit a specific behavior ie. correspond to a domain not applicable to other IPs (you do not want to filter). this would be historical.

Ricky,Visits are breaking mid session and thus inflating Visitors and Visits metric.  As this is happening mid session and the cookies being seen as new .. you should see the inflation if you trend visitors/vists over time and apply the filter apple devices, no referrer and visit no = 1eg.We were ru...

eg ...The highlighted metrics was produced relying on row count with calculated metric on a table for specified time frame. ie to produce this metric for different timeframes (for trended) would require separate tables ... and you can only trend data in a single table rather than across multiple tab...

That's what I've done to achieve dashboard above.. but this is limited and does not allow for what I mentioned in the previous post