Here’s a table with short descriptions for each event type.
| Event Type | Backend Type | Description | Retains Event ID |
| Contact | ContactEvent | Scheduled evaluation of contact data (e.g., attributes, list membership). Runs on a schedule (daily, weekly, etc.) and evaluates contacts against criteria. | Yes |
| API Event | APIEvent | Triggered by external API calls. Uses an Event Definition Key for integration; events are fired when the API receives the matching key. | Yes |
| Date-Based | DateEvent | Triggers on contact date attributes (birthday, anniversary, etc.). Can run yearly, monthly, or once; no schedule, only attribute-based. | Yes |
| Mobile App Event | PushInAppEntryEvent | Triggered by mobile app events (app open, custom events). Uses Mobile Push SDK events to inject contacts into the journey. | Yes |
| Push Message Event | PushEngagementEvent | Triggered by push engagement (open, click, etc.). Starts the journey when a contact interacts with a push message. | Yes |
| In-App Message Event | PushInAppEngagementEvent | Triggered by in-app message engagement. Starts the journey when a contact interacts with an in-app message. | Yes |
| Data Extension / New Audience | ContactAudience,EmailAudience / DEAudience | Entry from Data Extension or Contact Builder audience. A new event definition is created on copy. | No |
| File Upload | FileUploadAudience | Entry from uploaded file. A new event definition is created on copy. | No |
| Automation Studio | AutomationAudience | Entry from Automation Studio. A new event definition is created on copy. | No |
| Mobile Push / MobileConnect / GroupConnect | MobilePushAudience, MobileConnectAudience,GroupConnectAudience | Entry from mobile or group audiences. A new event definition is created on copy. | No |
Note:
When Retain Event ID is YES, copied journeys will share the entry event with the original journey.
Changing an entry event in one journey that shares entry events will affect the other journeys that share that entry event.
Related Developer Documentation: https://developer.salesforce.com/docs/marketing/marketing-cloud/references/mc_rest_interaction/getEventDefinition.html
005315546

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.