Basically no if we talk about Adobe solutions only. Adobe mobile SDK, old and new, requires you to code for tracking explicitly. Even for websites, you need to explicitly send beacons using Launch or calling s.t() or s.tl() for tracking.

Another reference, developer.adobe.com/client-sdks/documentation/getting-started/track-events/#send-events-to-edge-network, create the ExperienceEvent and send it out. A sample Swift code for a simple page view tracking let xdmData: [String: Any] = [ "eventType": "web.webpagedeta...

AEM tags live only in AEM for content classification. If you want that to be tracked in Adobe Analytics, you need to publish tags to the final web page first. However, I have no experience in AEM development and do not know if this is possible or not. Please check with your AEM developer and rise th...

You may try to look at the "user_agent" for those lines with 0 on "browser" and see if there is a valid "user_agent" for Adobe to determine the browser.

I have a similar question which is if using WebSDK to merge ID for multiple events and have Adobe Analytics as the service in Datastream, will multiple events actually merge as one or still multiple records/hits in the data feed? My gut feeling is that the merge id only works for CJA but not AA wher...

You have two  AA hits just on the page load, so it is not a bounce. You need to check what is the second hit and if it should be there. One common trick is to calculate another version of the bounce rate using "Single Page Visit" / "Visit".

You can also further click on the "hit" in the upstream to check what data exactly was received by Adobe Analytics and stored in Data Feed format. Since the availability of AEP Assurance, it is the prefered way to QA tracking for me than the old browser plugin.  

Did you try to use Edge Transaction in the debugger to monitor how tracking going through the client/edge/upstream    

The "Custom Event" trigger involves quite a log of coding which I only tested but don't bother to find any actual use of it, just because of tracking. However, the Data Element Change, Element Exists, and Enter Viewport triggers are good and reliable. I had been using quite a lot of data element cha...

There is also an "Enter Viewport" from the Core extension you can use where you provide the CSS selector of the specific piece of content and the rule should be triggered when the first time the element entered viewport and seen.