I have seen similar issue due to browser cache. Try using any other browser. If it still doesn't work, as @metripat mentioned you should reach out to Adobe Customer Care.

That is where the Cross-Device Analytics comes into picture. This will ensure proper reporting and you get People metric instead of Unique Visitors.

 A few checks:- What is the currency code set with the AA call?- Are you passing any other event (mainly ecommerce) with these events?- Is product string populated? 

Pull a report with occurrences metric and Day as dimension. You will see that there is no data for one of the day in Feb.

Hi @Michael_Wills , The eVar persistence happens on the Adobe Servers where the hits are processed. Hence, you would not see it in the debugger. This is very briefly mentioned (not very clear as well) under the "How eVars work" section of the below article: https://experienceleague.adobe.com/docs/an...

Got it. Then as you confirmed, it's an internal issue which Engineering team will handle.

Hi @Kumar_Vaibhav , It's not a suggested approach to use setCustomerID as many of the Adobe integrations might not work with it.  Instead, you can pass the Visitor ID in an eVar and then create a Virtual Report Suite under which you can enable Cross-Device Analytics by selecting the checkbox "Stitch...

Right ... this is most probably due to the above mentioned comment: "What is the daily traffic estimates provided at the time of creating new report suite? If it is more than a million, Adobe Infrastructure team takes time to allocate resources and activate the report suite."

You should refer to the below documentation: https://experienceleague.adobe.com/docs/analytics-learn/tutorials/integrations/ad-cloud/introduction-to-the-analytics-for-advertising-cloud-dsp-integration.html?lang=en#:~:text=The%20Analytics%20for%20Advertising%20Cloud%20DSP%20integration%20is%20a%20nat...

On a first look, this seems like a timestamp configuration/implementation issue. I would check the report suite configuration and compare it with whether timestamp is being sent with the mobile hits. But, this doesn't seems to be the case if nothing changed (unless someone did it behind your back  ...