> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-hub/working-with-leads/how-to-view-lead-activity-history.md).

# How to view activity history of a lead

Track a lead through its journey of interactions with your company

With Mobly, you can track a lead’s journey from the first scan at your booth to every interaction that follows. Events aren’t just about collecting one-time scans from people grabbing swag—they’re about building meaningful connections with prospects and customers. Mobly helps you capture ongoing conversations and engagement that matter.

Mobly tracks a lead's full activity history — every event they appeared at, every scan, every interaction — rather than just the initial scan. You'll see a timestamped record of each scan with where and when it happened, and who performed it.

This information is available in both the **Hub** and the **mobile app**.

## Hub

#### View Lead Activity

1. Navigate to an event in the **Events** tab and select the lead’s name, or go to the **Leads** tab and search for their name.

   Click the **Activities** tab to see a timeline of interactions with that lead. Activities include:

   * Scan details (when, where, and by whom)
   * Engagement (calls, texts, LinkedIn connections)
   * Campaign triggers

     ![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/6998cb610f8fc200dfd6c49f/file-Jwqfg5J1Bp.png)

#### Sorting & Filtering

You can also use this information to form reports in the **Leads** tab. You can sort or filter by **Number of Scans** and **Last Scanned By** in the Leads table

1. Navigate to the **Leads** tab.
2. Add the columns **Number of Scans** and **Last Scanned By**.
3. Sort of filter as needed. For example, maybe I'd like to identify high-intent buyers. I can sort by **Number of Scans** (descending) to see the leads with the most interactions and therefore most likely interested in buying our products.

   ![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/6998cc4f0f8fc200dfd6c4a9/file-qK9KCnT0Gh.png)

## Mobile App

#### View Lead Activity

1. Navigate to an event from the **Events** tab and select the lead’s name, or go to the **Leads** tab and search for their name.

   Click on the **More Info** icon in the top right corner to see a timeline of interactions with that lead. Activities include:

   * Scan details (when, where, and by whom)
   * Engagement (calls, texts, LinkedIn connections)
   * Campaign triggers

     ![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/685ed3ad75081a7298f3c980/file-pZzt7IYv0m.png)

### For Mobly Admins only:

The following fields are calculated based on the scanned activity events and can be mapped to any field in your CRM:

* Number of Scans
* Last Scanned By
* All Scanned Events
* First Scanned By
* Last Scanned Event

  ![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/6998cd200f8fc200dfd6c4b8/file-TWxUZG2cRc.png)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.getmobly.com/help-center/the-hub/working-with-leads/how-to-view-lead-activity-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.