Leaning more towards a hashing issue at this point....   I created 2 new segments: site <> fmc-mdedge   page starts with mdedge   While the results do show some pages that qualify there are still plenty of pages that do not start with mdedge...    

Hey Paratheep   I updated the segment as follow:   This will not solve the issue. Having the "OR" in the container leave its open to undesired results:      

Hey @Alexis_Cazes_  Thanks for the info! I did a bit more digging as well so here is another screenshot with some findings.   Records on the top half are the "visit_num=0" records, bottom is valid records as expected.   Hit Source = 1 in both sets Exclude Hit = 0 in both sets visid_type = 5 in both...

A page view is just a (t()) call.... its up to you when to send them. It was easier years ago when we defined a page view being a unique HTTP request to our servers OR when more than 50% of the visible content changed by a user action.   These days with webApps and infinite scroll features we have m...

@Jennifer_Dungan and anyone else that might be following along here....   After exhaustive investigations between myself, my Data Management team and several calls with Adobe folks we have figured it out!  In short we were wrong  More specifically the logic we have been using for 14+ years against t...

Considering we collectively think there must be a processing rule at fault here, i added another processing rule which sets page name.  Now we have double the number of page views as expected via the front end and still only 1 "page event = 0" records in the data warehouse....  All the suggestions f...

This ticket has been opened, closed and reopened several times. Absolutely not resolved. Its basically ME looking at it and running tests so if i take more than 48hrs to respond to a ticket it gets closed.  

Still digging into the data on our end. We have not been able to identify the issue. Again same number of records BE vs FE but no "page event 0's" in the BE data.

We are indeed sending the default 5-10 sec heartbeat ping and we are using the time spent values that are being returned. There are a bunch of additional ad hoc calls (i.e. start/play etc) because we have not been able to rely on the heartbeat data. Ideally we would love to get rid of all the ad hoc...

Agreed BUT in the workspace only 96 page views are reported from 191 visitors and visits. Which indicates this issue is intermittent. I can identify the 96 records which are being counted as a page view and they are page event 50 which i know to be "Heartbeat Video: Media stream start" And the only ...