> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/search-profiles.md).

# Search Profiles

## Profile information

You can access the profile view using:

* Custom ID
* Installation ID
* Email address

The profile view page will present all data associated with a profile, including:

* Attributes: Display various profile characteristics and preferences.
* History: Show a history of profile actions, sent messages and interactions.
* Subscriptions: List any subscriptions or opt-ins associated with the profile.

This centralized view provides a complete picture of the user's data, enabling efficient profile management and analysis.

![Screenshot](https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2Fgit-blob-019d3ed9bdd73cdac8715fd41e3587def88c489f%2Fprofile-view-general-2.png?alt=media)

## History

### Profile actions

All events tracked by a profile apps or websites via Batch SDKs methods are displayed on the Profile view, as well as events sent via API.

Event display in the Profile view is limited to 3 months & 180 events. However, earlier activity remains available for targeting.

Events performed during anonymous sessions (before login) and later attributed to an identified profile are indicated with a specific icon. See Data Lifecycle page to better understand what happens when login happens.

Batch stores two timestamps for a custom event: the time it was sent and the time it was received. When they differ by at least one minute, a specific icon is displayed next to the event's time. Hovering the time then shows an additional **Received at** block, with the other timestamp in your browser's time zone.

### Message events

Message events are events related to messages sent by Batch.

The following events are tracked:

* Sent: for Email, Push v2, SMS
* Sent opt-in: for Push v2
* Delivered: for Email , SMS, Mobile Landing and In-App
* Open: for Email, Push v2.
* Machine open: for Email
* Click: for Email
* Bounces: for Email
* Suppressed: for Email, when an email adress is in the suppression list
* Dismissed: for Mobile Landing and In-App

{% hint style="warning" %}
This page applies to the data lifecycle of Profiles that powers email, SMS, and Push v2 channels.
{% endhint %}


---

# 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://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/search-profiles.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.