@Tienzen there could be multiple reasons for this behavior . May I know which reporting source are you working with ? If you are using A4T (Analytics as a reporting source) then this behavior could be because of unstitched hits . You may have a look at this document for more details around "unstitched hits/partial data" : https://experienceleague.adobe.com/docs/target/using/integrate/a4t/troubleshoot-a4t/minimizing-infla....
You may also look at the firing order of the experience cloud libraries on the page . The order should be Visitor ID > Target > Analytics .
If you are using Target as a reporting source , then please ensure you are not using any audience refinements that may lead to tis behavior.
For more detailed investigation you may create a ticket with the client care team using Admin console.
Hope this helps.