This leads me to believe that those props and evars may not have been defined or on in prod. Can you check in Admin section report suites, are the props and evars defined? and enabled as on?

Ideally as a 3rd party site is the source: 1 You have the same header footer tag snippet you use for your report suite.2 If using tracking IDs on 3rd party website ensure URL CTA structure is in line with formats to your tracking ID infrastructure. This way it will be more of a seamless integration ...

ok this may sound totally counter intuitive. Can you code in launch to main Adobe extension script, make an edit, save then undo edit and save then republish. Sometimes it can be a weird thing like this to refresh a pushing cache error.

Understood I figured as most users use defacto browser in each it may relate in this case. I would suspect some firewall setting in Windows 11 is then the culprit.

So Adobe Analytics has 2 types of reports depending on your setup may cover these: New vs Returning visitors.Return frequency. (has a bunch of tiers under it) Both of these can then be correlated by Unique visitor to get as close a possible to the various user tiers you are after create a segment fo...

Check #1 did you use correct header footer code for DEV vs PROD. DO you happen to use this in your code base?var s_account ='YOURDOMAIN'This could make your data be directed to wrong RSID.  The network debugger is typically the way to go though there see what is being sent in beacon output.

Check with your marketing teams have they recently purchased any SEM/keyword or digital banner traffic? BOT like traffic could be when such traffic is bought from 3rd party suppliers...

Noticed alot of issues as well around scheduled reports... One thing we did notice was reports when sending to large distro groups...Found duplicating report then, splitting the groups into no more than 8 solved many of the problems not all though  GLTU.

So its likely a bug in how windows 11 is rendering pages.  try this see if it helps:https://customer.precisely.com/s/article/How-to-Check-Your-Compatibility-Mode-Settings-in-IE-11-360047849073?language=en_US

Typically Facebook pixels in their campaign tool will be associated to a PROD URL I suspect the STG is failing as you are trying to associate a prod URL to a stg URL. Ask whomever manages the  environment in Facebook if they can create a stg setup/pixels for your stg URLs. GLTU