Use our iOS and Android Mobile SDKs to pull native app traffic data into your team's Real-Time Dashboards and see what’s resonating with your app users on a second-to-second basis — which articles, site sections and authors they’re engaging with, what they’re sharing, and more. With our SDKs integrated in your mobile apps, your Chartbeat customer success rep can enable new app traffic filters in the Real-Time Dashboard for your website, enabling your team to view audience data as a whole (app traffic with website traffic together) or drill down into device-specific app audience data with a one-click breakdown of traffic across iOS and Android apps.
Before your app developer team begins integrating our SDKs (instructions included in the following articles of this guide), check out the sections below to understand (A) importance of page metadata consistency across your Chartbeat tracked platforms, (B) how to test your integration in a sandbox dashboard on your Chartbeat with real-time data, and (C) how to track we-view-based pages of your app differently from native views.
If your app does not contain the same page metadata sent from your website to Chartbeat, for example canonical web URLs like
https://www.mysite.com/news/article-12345.html, your team should consider sending app audience data to a separate Site in your Chartbeat account to avoid creating discrepancies within the dashboard for your website traffic data. Consider creating a separate site in your Chartbeat account with a site ID like
mysite.app to view your app data separately from your website data.
We recommend first adding our code in a test app, and using a corresponding test dashboard in your Chartbeat account to view the data before pushing your app to production with your prod site ID. For example, if your production site ID is
mysite.com, your test site ID could be
test.mysite.app. In the following instruction articles for our Android and iOS SDK, remember when adding our code to your test app to use test site ID and update it to your production site ID only when your team is finished QA'ing the integration for data accuracy.
To ensure that these pageviews are also registered as app views in your Chartbeat data, use our mobileApp setting to track all web-view pageviews in your app:
_sf_async_config.mobileApp = true;
In a hybrid app where a user can navigate between native and web-view screens, be sure to stop our SDK tracker whenever a user moves from a native page to a web-view page, and resume the SDK tracker as the user navigates back to a native screen.
Instructions to integrate our Android SDK is up next, or skip to iOS SDK integration steps if your team does not have an Android app.