---
title: "Manual Tracking"
slug: "mapp-intelligence-android-sdk-v5-manual-tracking"
description: "Manual tracking options in Mapp Intelligence Android SDK v5 for apps that need explicit control over pages, events, media, and parameters."
status: "update"
updated: 2026-04-24T10:47:14Z
published: 2026-04-24T10:47:14Z
canonical: "docs.mapp.com/mapp-intelligence-android-sdk-v5-manual-tracking"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manual Tracking

Manual Tracking gives you explicit control over what is tracked and when tracking requests are sent. Use this area if automatic activity-based tracking is not enough for your implementation or if you need to model events, pages, products, or media interactions more precisely.

## Choose the right manual tracking approach

### Object Oriented Tracking

[Object Oriented Tracking](https://docs.mapp.com/docs/en/mapp-intelligence-android-sdk-v5-object-oriented-tracking) is the recommended approach for current implementations. You create strongly typed tracking objects such as page, action, product, order, campaign, user, or media events, and the SDK transforms them into the correct Mapp Intelligence request format.

### Query Parameter Tracking

[Query Parameter Tracking (Legacy)](https://docs.mapp.com/docs/en/mapp-intelligence-android-sdk-v5-query-parameter-tracking-legacy) is a legacy option that remains available for compatibility. Use it only if you maintain an existing implementation that still depends on parameter-based request construction.

## When to use Manual Tracking

- You need more control than automatic tracking provides.
- You want to track actions, media events, commerce data, or custom parameters explicitly.
- You need your implementation to reflect a specific tracking model rather than the app screen structure alone.

> [!NOTE]
> Note
> 
> For new implementations, start with Object Oriented Tracking unless you have a strong reason to keep a legacy query-parameter setup.