What should be done if mobile tracking beacons are not firing?

Mobile tracking beacons are network requests sent from a mobile application to Adobe Analytics servers. This functionality is managed entirely by the Adobe Mobile SDK integrated into the app. If beacons are not firing, the issue lies within the app's code. A developer must check that the SDK has been correctly initialized with the correct application ID, that the required libraries are included, and that tracking calls like trackState or trackAction are being executed at the appropriate times in the user's journey.

B. IP-Based Attribution Models are server-side settings within Adobe Analytics for data analysis and have no impact on whether the client-side mobile app sends a tracking request.
C. Real-Time Visitor Matching is a feature of the Adobe Experience Cloud Identity Service and is not related to the fundamental generation of tracking beacons from the SDK.
D. Cross-Device Analytics is a reporting and analysis feature that stitches data together post-collection; it does not influence the initial data collection from the mobile app.

1. Adobe Experience League. (n.d.). Lifecycle metrics. Adobe Experience Platform Mobile SDK Documentation. Retrieved from https://experienceleague.adobe.com/docs/mobile-services/android/lifecycle-metrics/lifecycle.html?lang=en (This document explains that the SDK must be correctly configured and initialized for lifecycle metrics, which are the most basic beacons, to be sent.)

2. Adobe Experience League. (n.d.). trackAction. Adobe Experience Platform Mobile SDK Documentation. Retrieved from https://experienceleague.adobe.com/docs/mobile-services/android/sdk-api-reference/track-action.html?lang=en (This page details a core tracking call. If this and similar calls are not implemented or are implemented incorrectly, beacons will not fire.)