> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.onesignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Message events

> Track per-user message interactions: delivered, opened, clicked, and more.

## What are message events?

A message event is recorded each time something happens between a message and a user: a push notification is delivered, an email is opened, an SMS is clicked, and so on. OneSignal records these events automatically across push, email, SMS, and in-app for every user in your app.

Message events give you a timestamped, per-user record of your messaging history. They are not the same as message reports — reports are campaign-level totals, while message events are per-user, per-message records.

## When to use message events

* **Support and investigation**: Look up a specific user to confirm whether and when a message was sent, delivered, or opened.
* **Journey debugging**: Trace a user's progress through a multi-step Journey by reviewing what they received and when.
* **Engagement context**: Understand a user's recent interaction history before contacting them or making a product decision about their experience.
* **Segmentation**: Target audiences based on message event behavior — for example, users who received but did not click a push in the last 30 days. See [Segmentation](./segmentation#message-event-filters) for full details.
* **Conversion attribution**: Message events are the basis for conversion attribution. When a user completes a conversion event, OneSignal checks their recent message history to determine which message, if any, influenced the action. See [Conversions](./conversion-metrics) for details.

## View message events for a user

To view message events for a specific user:

<Steps>
  <Step title="Open the user's profile">
    Go to **Audience > Users** in the OneSignal dashboard, then find and open the user's profile.
  </Step>

  <Step title="Select the Event log tab">
    The event log shows each message event associated with that user, in reverse chronological order.
  </Step>

  <Step title="Filter the log">
    Narrow results by:

    * **Time range** — a specific date range, up to your plan's full retention window.
    * **Channel** — push, email, SMS, or in-app events.
  </Step>
</Steps>

<Note>
  Events can take up to 5 minutes from when they occur to appear in a user's event log.
</Note>

## Segment users by message events

You can build audience segments based on message event behavior — for example, targeting users who clicked a push notification in the last 7 days, or who received an email but did not open it.

<Frame caption="Example of an email message event filter in segments">
  <img src="https://mintcdn.com/onesignal/YOTSrtBSoqdrJ37A/images/docs/4e72c093c64340ac91626550ecd94bd08a1a5d5c7553c0070e3e8c83d568764b-marketing_doc.png?fit=max&auto=format&n=YOTSrtBSoqdrJ37A&q=85&s=8924cc0c093fad5051b61d3b35f5a13c" alt="Email message event filter in the OneSignal segment builder" width="1047" height="648" data-path="images/docs/4e72c093c64340ac91626550ecd94bd08a1a5d5c7553c0070e3e8c83d568764b-marketing_doc.png" />
</Frame>

<Card title="Segmentation" icon="filter" href="./segmentation#message-event-filters">
  Build segments based on message event behavior across push, email, SMS, and in-app.
</Card>

## Retention

How far back you can view message events depends on your plan.

| Plan       | Retention     |
| ---------- | ------------- |
| Free       | Not available |
| Growth     | 30 days       |
| Pro        | 60 days       |
| Enterprise | 90 days       |

<Info>
  OneSignal began storing message events to support extended retention on April 14, 2026. Events before that date are not available to view on the user profile, regardless of plan.

  **Older events remain available for segmentation** — they just won't appear in the event log view.
</Info>

For more on how retention affects billing, see the [Billing FAQ](./billing-faq).

## Message events vs. Event Streams

Message events and Event Streams both involve the same underlying data, but they serve different purposes.

|                      | Message events                | Event Streams                           |
| -------------------- | ----------------------------- | --------------------------------------- |
| Where the data lives | OneSignal dashboard           | Your warehouse, CRM, or CDP             |
| Best for             | Per-user lookup, segmentation | Long-term analytics, external workflows |
| Retention            | 30 / 60 / 90 days by plan     | Whatever your destination keeps         |
| Latency              | Up to 5 minutes               | Near real-time                          |

Use **message events** when you need to look up or segment users within OneSignal. Use **Event Streams** when you need messaging data flowing into your own systems, especially when long-term storage of events is required.

<Card title="Event Streams" icon="bolt" href="./event-streams">
  Forward message events to an external destination in near real-time.
</Card>

## FAQ

### Why don't I see message events for a user on the Free plan?

Message event retention is not available on the Free plan. To view per-user event history in the dashboard, you'll need to upgrade to Growth, Pro, or Enterprise. Message events still feed segmentation regardless of plan.

### How long does it take for a message event to appear in the event log?

Up to 5 minutes from when the event occurs. If you need lower latency or external storage, use [Event Streams](./event-streams) instead.

### Can I see message events from before April 14, 2026?

Not on the user profile. OneSignal began storing message events for extended retention on that date, so earlier events do not appear in the event log. They remain available for segmentation.

### How do message events relate to conversion attribution?

When a user completes a conversion event, OneSignal looks back through their recent message events to determine which message influenced the action. Without message events, OneSignal cannot attribute conversions to specific messages. See [Conversions](./conversion-metrics) for the full attribution model.

### Can I export message events to my own data warehouse?

Yes — use [Event Streams](./event-streams) to forward message events to a destination like Snowflake, BigQuery, or a CDP in near real-time. Event Streams is the right tool when you need long-term storage or want to combine messaging data with your own analytics.

## Related pages

<Columns cols={2}>
  <Card title="Segmentation" icon="filter" href="./segmentation#message-event-filters">
    Build segments based on message event behavior across push, email, SMS, and in-app.
  </Card>

  <Card title="Event Streams" icon="bolt" href="./event-streams">
    Forward message events to an external destination in near real-time.
  </Card>

  <Card title="Conversions" icon="bullseye" href="./conversion-metrics">
    Attribute downstream user actions back to the messages that influenced them.
  </Card>

  <Card title="Billing FAQ" icon="circle-question" href="./billing-faq">
    How retention windows and event volume affect your plan.
  </Card>
</Columns>
