For the complete documentation index, see llms.txt. This page is also available as Markdown.

Roivenue Measurement for Apps

Track page views and conversions in your iOS and Android apps with Roivenue Measurement. How app tracking works, what you need, and which guide to follow.

Roivenue Measurement also works in mobile apps. Your app sends Roivenue the same kind of data as your website: page views and conversions, with the marketing source that brought the user in. Roivenue then uses the app events in attribution.

There is no SDK to install. You add a small tracker class to your app that sends events to the Roivenue tracking API in JSON. The guides for iOS and Android contain sample code you can reuse.


How app tracking works

  • Page views. The app sends a page view event when a screen appears.

  • Conversions. The app sends a conversion event, for example a purchase with its details or a custom goal.

  • Context. Each event carries your Property ID, the event type, a timestamp, a URL, a device identifier, an optional hashed user identifier, and the screen size.

  • Marketing source. When a user opens the app through a deep link or universal link, the UTM parameters in the link are captured and sent with the events of that session. This is how Roivenue attributes app events to the right campaign.


What you need before you start

  • Property ID. A UUID that identifies your Roivenue property. Your Client Success Manager (CSM) gives it to you.

  • A developer for your iOS or Android app.

  • Deep links with UTM parameters in your campaigns, so the app can capture the marketing source.

  • A consent solution. As on the web, you are responsible for collecting user consent according to the applicable law.

Requirement
iOS
Android

Development tools

Xcode 15+

Android Studio Hedgehog (2024+)

Language

Swift 5.9+

Kotlin 1.9+

Other

Network access

Min SDK 24+, internet permission in AndroidManifest.xml


How to implement Roivenue Measurement in your app

  1. Capture UTM parameters. Read the UTM parameters from the deep link that opens the app, store them for the session, and reset them on a cold start.

  2. Create the tracker class. It collects device data and sends events to the Roivenue tracking API with your Property ID.

  3. Track page views. Send a page view event when a screen appears.

  4. Track conversions. Send a conversion event with the purchase details or the goal you want to measure.

  5. Check the data with your CSM. Let your CSM know when the first events are sent, so they can confirm the data arrives correctly.


Guides in this section

Guide
What it covers

Implementing tracking in an iOS app with Swift: UTM manager, app lifecycle, tracker class, page views, and conversions.

Implementing tracking in an Android app with Kotlin: capturing UTMs, handling deep links, tracker class, page views, and conversions.


FAQ

1. Is there a Roivenue SDK for apps?

No. You add a lightweight tracker class to your app that sends JSON events to the Roivenue tracking API. The iOS and Android guides include sample code.

3. Do I have to send a user ID?

No, it is optional. If users log in to your app, sending a hashed user ID helps Roivenue connect their activity across sessions. Send it hashed, not in plain text.

4. Where do I get my Property ID?

From your CSM.

5. How do I know the tracking works?

Tell your CSM when the app starts sending events. They check that the data arrives correctly before you rely on it.

Last updated

Was this helpful?