> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/integration/implementation-steps/react-native/sdk-react-native/activity-tracking.md).

# Activity Tracking

How to implement activity tracking within your application to enable segmentation based on content views

## Overview

The PushSDK provides methods that allow you to track the type of content a subscriber is viewing within your application. This information can then be used in the Pushly platform to create cohorts of subscribers that have visited specific URLs  or screens with tags based on the number of visits and visit recency.

For example: "Subscribers who have visited a page/screen tagged with "Astrology" at least 4 times in the last 30 days".

## Methods

### UserProfile.trackActivity

To track a URL or screen visited along with its keyword/tag metadata:

{% tabs %}
{% tab title="React" %}

```tsx
PushSDK.UserProfile.trackActivity("myapp://dashboard", ["my-tag"]);
```

{% endtab %}
{% endtabs %}

Or if there are no tags to be provided omit the `tags` parameter:

{% tabs %}
{% tab title="React" %}

```tsx
PushSDK.UserProfile.trackActivity("myapp://sports/article-1");
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.pushly.com/integration/implementation-steps/react-native/sdk-react-native/activity-tracking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.