Tracking

Tracking covers the SDK's primary purpose: sending page views, user actions, commerce events, media playback, form interactions, and notification interactions to Mapp Intelligence. Pick the implementation path that fits your app, then drill into the topic pages for the parameter and event details.

Implementation paths

• Object Oriented Tracking — recommended. Build typed event objects (MIPageViewEvent, MIActionEvent, MIMediaEvent, MIFormSubmitEvent) and attach typed parameter classes.

• Query Parameter Tracking (Legacy) — use the dictionary‑based trackCustomPage / trackCustomEvent calls when you forward parameters from a runtime or scripting layer.

Sub‑sections

• Default Parameters — what the SDK attaches automatically to every request.

• Manual Tracking — page, event, commerce, session, user, campaign, media, and form tracking via the typed APIs.

• Special Tracking Scenarios — user authentication, deep links, and WebViews.

• Push & In-App Notifications — track Mapp Engage push and in‑app message interactions.

Privacy and lifecycle controls — opt‑out, anonymous tracking, user matching, crash tracking, runtime track-ID changes, SDK reset — live under Runtime & Privacy.