# 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](/files/b9j0wStY2bW9adDaGszY)

## 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](/getting-started/features/customer-engagement-platform/profiles/data-lifecycle.md#what-happens-when-setting-a-custom-id-on-an-anonymous-profile) to better understand what happens when login happens.

### 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: 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:

```
GET https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/search-profiles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.