Skip to main content

iOS and Android Campaign Measurement for App installs

Android: Google Play Campaign Measurement

Google Play Campaign Measurement is a feature of Google Mobile App Analytics that enables the attribution of native Android app installs to advertising campaigns and other marketing efforts in your Google Analytics app reports. Verifying that your Google Play Campaign Measurement implementatin is working properly before the application is submitted to Google Play ensures that campaign measurement data is as accurate as possible at the time of launch.

This guide will illustrate one means of testing a Google Play Campaign Measurement implementation.


iOS: Cookie Tracking / Browser Identification

For iOS no such standard way exists. The main workarounds involve the setting of a cookie in the ad and then opening a WebView with the ad again after install - alternate identify the device by the informations the browser publishes (IP, accept-encoding, ...).
There are some rumors Apple would reject apps for cookie tracking...

Apple provides an Identifier for Vendor (same among same apps installed on device) and an Identifier for Advertisement, but both are available In-App only.

The main methods:
  • Device Fingerprinting
  • UDID (Deprecated)
  • OpenUDID/Copy-and-Pasteboard
  • MAC Address (Deprecated)
  • ODIN
  • Cookie Tracking
  • TRUSTed Mobile Ads
  • Apple Advertising Identifier and Identifier for Vendor
  • Android Referrer (see above)

Apple ID APIs

  • UDID
    • Deprecated
  • Application ID
    • Scope: App
    • Lifetime: Uninstall app
    • Backed up: Yes
    • Restores across devices: Yes
  • Vendor ID
    • Scope: Developer
    • Lifetime: Uninstall developer's apps
    • Backed up: Yes
    • Restores across devices: No
  • Advertising ID
    • Scope: Device
    • Lifetime: Erase all Content and Settings
    • Backed up: Yes
    • Restores across devices: No

Pros & Cons of the Top Mobile App Tracking Methods with a nice overview of the main methods

Comments

Popular posts from this blog

Pattern: Riblets vs. VIPER

Engineering the architecture behind Uber's new rider app

Not being held back by our extensive codebase and previous design choices gave us the freedom where we otherwise would have made compromises. The outcome is the sleek new app you see today, which implements a new mobile architecture across both iOS and Android. Read on to learn why we felt the need to create this new architecture pattern, called Riblets, and how it helps us reach our goals.

The platforms share:

Core architectureClass namesInheritance relationships between business logic unitsHow business logic is dividedPlugin points (names, existence, structure, etc.)Reactive programming chainsUnified platform components
Each Riblet is made up of one Router, Interactor, and Builder with its Component (hence the name), and optional Presenters and Views. The Router and Interactor handle the business logic, while the Presenter and View handle the view logic.

Uber

Stetho - A Chrome debug bridge for Android applications

Stetho is a sophisticated debug bridge for Android applications. When enabled, developers have access to the Chrome Developer Tools feature natively part of the Chrome desktop browser. Developers can also choose to enable the optional dumpapp tool which offers a powerful command-line interface to application internals.

Facebook Github

WireMock

WireMock is a flexible library for stubbing and mocking web services. Unlike general purpose mocking tools it works by creating an actual HTTP server that your code under test can connect to as it would a real web service.

It supports HTTP response stubbing, request verification, proxy/intercept, record/playback of stubs and fault injection, and can be used from within a unit test or deployed into a test environment.

Although it’s written in Java, there’s also a JSON API so you can use it with pretty much any language out there.

WireMock.org