Developer
User guidesDeveloper websiteHelp centerLog in
  • Welcome!
  • Organisations structure
    • Datamart
    • Users and roles
  • User points
    • User identifiers
      • Networks IDs
        • Device-based Network IDs
          • Custom Device ID integration
          • ID5
          • First ID
        • User-based Network IDs
          • Custom User ID integration
          • UTIQ martechpass
      • Accounts
      • Emails
      • Device identifiers
    • User activities and events
    • Compartments
    • User profiles
    • User segments
    • Hyper point & Quarantine
  • Data model
    • Defining your schema
    • Computed fields
      • Concepts
      • Setup
      • Development
      • Examples
  • Data ingestion
    • Real time user tracking
      • Website tracking
      • Mobile apps tracking
      • Ads exposure tracking
      • AMP tracking
      • Conversions tracking
      • Email views and clicks
      • Tracking API
      • Event rules
      • Activity analyzers
    • Bulk processing
      • Imports
        • User activities import
        • User profiles import
        • User choices import
        • Segments import
      • Deletions
        • User identifiers deletion
        • Device points deletion
        • User points deletion
      • User identifiers association
      • Integration batch
    • Activities analytics
    • Data warehouse
      • Preliminary setup
        • BigQuery
      • Create data warehouse
  • Querying your data
    • OTQL queries
    • OTQL examples
    • GraphQL queries
    • UserPoint API
    • User activities
    • Activities analytics queries
      • API Quickstart
      • Dimensions and metrics
      • Use cases
    • Funnel API
  • Alerting
    • Alert configurations
  • Data visualisation
    • Quickstart
    • Dashboards
    • Sections and cards
    • Charts
    • Datasets and data sources
      • Using a data file data source
    • Transformations
    • Filters
    • Cookbook
    • Reference
  • Advanced usages
    • Audience segmentation
      • Audience features
      • Segment builders
      • Audience segment metrics
      • Audience segment feed
        • Building new feeds
        • Monitoring a feed
        • Curated Audiences (SDA)
      • Edge segments
      • Cohort-based Lookalike
    • Contextual targeting
      • Setup
      • Activation
        • Google Ad Manager
        • Xandr (through prebid.js)
      • API documentation
    • Exporting your data
      • Query Exports
      • Datamart replication
    • Data privacy compliance
      • User choices
      • Cleaning rules
      • Exercise of user rights
      • Cookies
    • Campaigns
    • Automations
      • Email routers
      • Email renderers
      • Opt-in provider
      • Custom action plugins
      • Usage limits for automations
    • Plugins
      • Concepts
      • Creation & Deployment
      • Coding your plugin
      • Manage existing plugins
      • Layouts
      • Presets
      • Monitoring
      • Throttling
      • Batching (for external feeds)
    • Platform monitoring
      • Resources usage
        • Dimensions and metrics
      • Collection volumes
        • Dimensions and metrics
      • Events ingestion monitoring
        • Dimensions and metrics
    • Data Clean Room
      • Bunker
      • Clean room
  • Resources
    • Tutorial: Data Ingestion
      • Your first events
        • Add the mediarithmics tag
          • Getting the tag
          • Adding the tag
        • Send events using the tag
          • Adding event properties
          • Finding the UserEvent type in your schema
          • Matching your schema
          • Standard events
      • Your first bulk imports
        • API basics
          • Authentication
          • Your first API call
        • Send documents using the API
          • Requirements
          • Sending documents
    • Using our API
      • Authentication
    • Tools & libraries
      • mics CLI
      • JS Tag
      • Plugin SDK
    • Data cubes
      • Creating a report
      • Reference
Powered by GitBook
On this page
  • Setup summary
  • Mobile app integration options
  • Mobile app specificities
  • Predefined event names
  • User activities for mobile apps

Was this helpful?

Export as PDF
  1. Data ingestion
  2. Real time user tracking

Mobile apps tracking

PreviousWebsite trackingNextAds exposure tracking

Last updated 1 year ago

Was this helpful?

Setup summary

In order to track activities on your mobile app, you'll need to keep in mind the following :

  • All mobile user activities need to be sent to mediarithmics using the

  • The should be used to authenticate any requests between your app and mediarithmics. Don't hesitate to contact your Account manager to have more information about this.

  • The activity and events in the payload need to comply with mobile app specificities described in the

  • The user agent identifier ($user_agent_id) needs to be particularly formatted using guidelines

Mobile app integration options

The first option is to integrate a small piece of code (approx. 100 lines) into the mobile application to execute calls to the mediarithmics tracking API. Sample code for iOS and Android is available in the section (see illustration below).

The second option is to re-use an existing analytics tool. It is then possible to transfer events from the analytics solution's server to the mediarithmics API.

Mobile app specificities

Predefined event names

  • app open event ($app_open) corresponds to the opening of the app and app resume event (when the app becomes active again)

  • app install event ($app_install)

  • app update event ($app_update)

The install and update events are automatically calculated on server side and you don't have to send them :

  • The install event ($app_install) is triggered the first time an app open event is received for a user, regardless if the user is new or existing.

  • The update event ($app_update) is triggered when the SDK version, app version or OS version changes from one open to the next.

User activities for mobile apps

In the context of Mobile App Tracking, some fields of the User Activity objects have a limited set of possible values. Details below:

Field
Type
Description

$type

String enum

The activity type should only be APP_VISIT

$session_status

String enum

The sessions status should be: IN_SESSION: This value should be used if you’re making one API call per tracked event (recommended way). The platform will automatically aggregate all the events of a session sent through many API calls when this value is used. CLOSED_SESSION: should be used only if you do a single API call per session at its end. In this case, you should provide ALL the events of the session in the $events array in the call. Each API call with this value will generate a new User Activity in the Platform.

$user_agent_id

String (Optional)

$app_id

String

The mobile app id (previously created through Navigator / API)

In the context of Mobile App Tracking, predefined event names are available out-of-the-box to simplify and automate event processing ():

The of the user device containing a unified representation of an advertising id. Ex: mob:ios:raw:6d92078a-8246-4ba4-ae5b-76104861e7dc for a raw IDFA on iOS platform.

user agent identifier
Tracking API
Signature authentication
mobile application identifiers
next section
Authentication
full list of predefined event names