What is the native mobile spec?

• Smaller SDK: Move more destinations to the server-side, including the Facebook App Events destination.
• Less engineering time: Automatically collect key user events instead of coding them in yourself.
• Faster time to value: Set up your destinations with key metrics like Daily Active Users, sessions, and in-app purchases right away!
• Measure ROI of campaigns: Analyze campaign performance with spec'd events like "campaign hit", "install attributed" and "push notification opened" in your favorite analytics or BI tool.

The Facebook App Events cloud-mode destination uses the "Application Installed" event to power features like custom audience creation, dynamic ads, and conversion tracking, without needing to sit on the device. Other destinations, such as Google Adwords and Salesforce Marketing Cloud, and attribution providers offer similar functionality.

When an engineer installs the SDK, the SDK will automatically register on iOS and Android operation system handlers.

When the application is foregrounded on the phone, our SDK will be called and emit the Application Opened event. Similarly, when the user updates the app, on the next app open, the iOS and Android operation system will tell us and we'll emit a track event called Application Updated event. In-app purchases will trigger Order Completed, for example.

Automatic event collection is opted out by default. To collect these events, opt in as described in Segment's Quick Start guides (iOS, Android). You opt in by altering the configuration you pass into the SDK initialization methods, which tells the SDK to collect these events automatically.

Yes, they will be double counted, but that's only if you opt into this feature. You can either remove your own tracking code for these events or not opt into auto collection at all.

Yes. If you follow the Spec when you write your own custom events, you will be able to take advantage of certain features in downstream destinations on the server-side, like with our Facebook App Events destination.

We recommend migrating to these event names if you're tracking similar events so that you can take advantage of available features in our integrations which will depend on the spec as they become available.

No. Automatic events don't support custom properties.

No. Contact Segment support for alternative options.

You can, but the sooner you switch to the spec'd events, the further back you'll be able to look in your reporting with the same event name!

Segment's mobile marketing destinations can automatically capture campaign events around attribution, deep linking, and push notifications. These events go to destinations, including warehouses.

Android applications can't receive Push Notifications when the process is not running, and when apps are put into background they are eligible to have their Process killed when there is memory pressure. For more more on Android processes, view Android's Processes and app lifecycle documentation.

Segment tracks messages delivered to the application. So if the process has been killed for any reason, messages won't be delivered.

Firebase Cloud Messaging (FCM) has its own servers. When an FCM message is created and sent to a device, that message travels through FCM servers and is delivered to the local FCM client device that is part of Android OS. This FCM client is almost always running, even when the app is backgrounded. From there, the FCM message is intended to be delivered to a local application. If the app process is running, the message gets delivered. Otherwise, the user must tap a notification that starts the app and delivers the FCM message.

For more context on how this process works, view the Firebase FCM architecture documentation.