> This page is part of the [Customer.io documentation](https://docs.customer.io). For the complete index, see [llms.txt](https://docs.customer.io/llms.txt).
> Last updated: September 14, 2026
> To take actions in Customer.io from an agent, use the [Customer.io CLI](https://docs.customer.io/ai/cli/get-started.md) or the [MCP server](https://docs.customer.io/ai/mcp/get-started.md).

# Profile activity: review changes to your data

This article is about your workspace-wide profile activity. You can also find profile activity for each of your customers within their [profile page](/messaging/people/manage/overview/#recent-activity).

To track changes made by your *teammates*, go to your [Audit Logs](/accounts/audit-logs/).

## Overview

On the *Profile activity* page, you can track the activities performed by people, anonymous people, and [objects](/journeys/objects-data/objects/). This can help you ensure you’re receiving certain events, troubleshoot people across a similar activity, and more.

Profile activity has two types of dates: **Timestamp** and **Processed At**.

 ![](https://docs.customer.io/images/activity-log-item-annotated.png)

*   **Timestamp** represents the date and time listed on an event. If you don’t set a timestamp, we use the date-time when we receive the event.
*   **Processed at** is the date and time when we process an event. Anonymous events are not processed, and therefore do not have a “processed at” time.

*Timestamp* may be significantly earlier than *Processed At* for several reasons:

*   **Anonymous event merge**: Customer.io processes anonymous events after they’re merged into people, which happens when the anonymous user is identified. So it’s possible the event timestamp occurred well before the anonymous event merge.
*   **Manually set *Timestamp***: You might manually set timestamps when you [backdate events](/integrations/data-in/importing-old-data/#advanced-backfilling-events) or want to log the exact date-time that an event occurred because it’s not immediately sent to Customer.io.
*   Customer.io [experienced a **processing delay** ↗](https://status.customerio.com).

## Filter activities

To find specific activities:

1.  Decide whether you want to filter by *Identified* or *Anonymous* users.
2.  Filter by *Activity Type*. Some examples include *Failed Event*, *Person Deleted*, *Bounced Email*, or *Skipped Update*.
3.  Decide a date range.

Note

*Profile activity* shows identified activity from the last 30 days and anonymous activity from the last 24 hours.

Click to view the payload of the activity. Or click the person or object to go to their profile for more info.

 ![Profile activity timestamps](https://docs.customer.io/images/activity-log-item.png)

## Find activity older than 30 days

The *Identified* tab only shows the past 30 days, but your data is stored well beyond that timeframe. We evaluate data for segment conditions, automation triggers, and liquid personalization no matter how old it is—you just can’t view activities older than 30 days on this page.

To find a specific person’s older activity, [export their data](/messaging/people/manage/single-user-export/). The export isn’t limited to 30 days: it includes all of a person’s events, attributes, and deliveries.

## Troubleshoot automations that didn’t trigger

When an event-triggered automation doesn’t fire the way you expect, check the event’s *Timestamp*. An event won’t trigger an automation if its *Timestamp* is:

*   Before you activated the automation
*   Before a customer person existed
*   More than 72 hours before *Processed At* and the automation’s first action isn’t a longer delay—see [Backfilled historical data](/integrations/data-in/importing-old-data/#event-triggered-automations) for more info.

Your event timestamp may fall outside of this criteria if a CSV import doesn’t have a timestamp column, a webhook carries an upstream system’s original event time, or a batch send from one of your data sources is delayed. The event still lands on the person and appears in Profile activity, but its *Timestamp* falls outside the window an automation needs, so nothing triggers.

©2026 Peaberry Software, Inc. [Status](https://status.customerio.com/) [Terms of Service](https://customer.io/legal/terms-of-service/) [Privacy Policy](https://customer.io/legal/privacy-policy/)

[](https://www.linkedin.com/company/customer-io)[](https://twitter.com/customerio)[](https://www.youtube.com/channel/UCkCaWdezRoa8ZyR9pEVaipA)[](https://www.instagram.com/customer.io/)