> For the complete documentation index, see [llms.txt](https://documentation.crossengage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.crossengage.io/data-and-engagement-platform/data-model/events/outbound-events.md).

# Outbound Events

Outbound events relate to outbound communications to your customers, such as emails and push notifications. These events store information about the messages, as well as customer interactions with these messages, such as opening an email.

Note that CrossEngage automatically collects events for messages sent out via CrossEngage Integrations. However, if you are using other outbound communication services, you should upload these events to the CrossEngage system.

### Events

* Message Sent
* Message Delivered
* Message Viewed
* Message Clicked
* Message Unsubscribed
* Message soft\_bounced
* Message hard\_bounced
* Message marked\_as\_spam

{% hint style="warning" %}
Different Third Party Providers might only support a subset of these events. For example, the Episerver (Optimizely) Integration provides Message Sent event, but does not provide Message Delivered Events.
{% endhint %}

### Properties

<table><thead><tr><th width="145">Properties</th><th width="272">Description</th><th width="123" data-type="checkbox">Mandatory</th><th>Example</th><th data-hidden></th></tr></thead><tbody><tr><td>User_id</td><td>Unique identifier for each customer</td><td>true</td><td>ABC12345</td><td></td></tr><tr><td>timestamp</td><td>The date and time of the event</td><td>true</td><td>2022-01-01</td><td></td></tr><tr><td>channel</td><td>Channel used to send the message</td><td>false</td><td>Email</td><td></td></tr><tr><td>type</td><td>categorization of the message</td><td>false</td><td>Newsletter</td><td></td></tr><tr><td>url</td><td>URL</td><td>false</td><td></td><td></td></tr><tr><td>campaign_id</td><td>Campaign Identified</td><td>false</td><td>123456</td><td></td></tr><tr><td>message_id</td><td>Message identifier</td><td>false</td><td>304405</td><td></td></tr></tbody></table>

### Examples

You can upload these events using the CrossEngage API, or via the Event Feed. Please go to [Data Management ](/data-and-engagement-platform/data-management.md)to learn more.

Here is an example of the JSON used to upload two events via the API.

```javascript
{
   "id": "ABC12345",
   "events": [{
           "event": "Message Sent",
           "timestamp": "2022-01-11T00:00:00Z"
          "properties": {
               "channel": "Email",
               "type": "Newsletter"
           }},
       {
           "event": "Message Delivered",
           "timestamp": "2022-01-11T00:00:00Z"
          "properties": {
               "channel": "Email",
               "type": "Newsletter"
           }}]}

```

Here is the same example, presented as a JSON file that can be uploaded via Data Feeds:

```javascript
[
   {
       "id": "ABC12345",
       "event": "Message Sent",
       "timestamp": "2022-01-11T00:00:00Z",
       "channel": "Email",
       "type": "Newsletter"
   },
   {
       "id": "ABC12345",
       "event": "Message Delivered",
       "timestamp": "2022-01-11T00:00:00Z",
       "channel": "Email",
       "type": "Newsletter"
   }
]
```


---

# 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://documentation.crossengage.io/data-and-engagement-platform/data-model/events/outbound-events.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.