Personyze Wiki Personyze Wiki docs
Open Personyze
App & API Campaigns

Targeting & Personalization for Mobile Apps

Show native banners, popups, and inline messages inside your iOS or Android app, targeted with the same audience rules as your website.

Updated 7 hours ago 3 min read
A
by Admin

What This Does

Everything Personyze does on your website — targeted banners, popups, inline messages, A/B tests — can also run inside your native iOS or Android app.

The targeting is identical: the same audience rules, the same visitor profiles, the same data. What changes is delivery. There’s no browser to inject HTML into, so content reaches the app through the Personyze SDK and you render it natively (or in a WebView).

This is an SDK integration, not a point-and-click wizard. You build and target the campaign in the Personyze dashboard as usual, but getting it on screen requires a developer to wire up the SDK once. After that, marketers can create and target campaigns without further code.

How It Works

  1. The SDK is installed once in your app and initialized with your API key.
  2. The app reports where the user is — screen views and events — via SDK calls. This is what builds the visitor profile that targeting runs against.
  3. Personyze decides what to show using your audience rules, exactly as on web.
  4. Your app renders the result — either as HTML in a WebView, or as JSON you lay out with native components.

Setting Up the SDK

The Android and iOS SDKs, installation steps, and initialization code are documented in the Mobile App Integration Guide. In short:

  • Add the SDK to your project and grant internet permission.
  • Initialize PersonyzeTracker early in the app lifecycle with your API key (found under Settings → Integrations).
  • Call the navigation method as users move between screens, so Personyze knows the equivalent of a page view.

Once events are flowing, confirm them in the Live Visits dashboard before building campaigns.

Targeting

Audience rules work the same as on web — see Targeting Rules in Personyze. Two things behave differently in an app context:

  • “Page” becomes “screen”. The screen names you pass to the SDK are what URL-based rules match against, so pass meaningful, stable names.
  • Identity is stronger in apps. Users are typically logged in, so you can tie sessions to a CRM ID or email from the start rather than relying on anonymous cookies.

Rendering Options

  • HTML / WebView — fastest path. The campaign renders as designed in Personyze, displayed in a WebView. Good for banners and popups where you want marketers to control the design.
  • JSON — Personyze returns structured data and your app lays it out with native components. Slower to build, but it looks and performs like the rest of your app.

Related