Track event in Iterable.
Application
Iterable
Inputs (what you have)
Name | Description | Data Type | Required? | Example |
Connected Account | The connected account to use for the request | Connected Account | Yes | |
Name | The name of the event to track | Text (Short) | Yes | |
Campaign ID | Campaign tied to conversion | Text (Short) | No | |
Created at | Time event happened | Datetime | No | |
Key 1 | The end event specified key of the event defined data | Text (Short) | No | |
Value 1 | The end event specified value of the event defined data | Text (Long) | No | |
Key 2 | The end event specified key of the event defined data | Text (Short) | No | |
Value 2 | The end event specified value of the event defined data | Text (Long) | No | |
Key 3 | The end event specified key of the event defined data | Text (Short) | No | |
Value 3 | The end event specified value of the event defined data | Text (Long) | No | |
Either email or userId must be passed in to identify the user. If both are passed in, email takes precedence | Text (Short) | No | ||
ID | Optional event ID. If an event exists with that ID, the event will be updated. If none is specified, a new ID will automatically be generated and returned | Text (Short) | No | |
Template ID | Text (Short) | No | ||
User ID | The user ID that was passed into the update user call | Text (Short) | No |
Outputs (what you get)
Name | Description | Data Type | Required? | Example |
JSON Output | JSON output returned by the API | Text (Long) | No |
Outcomes
Name | Description |
Success | This status is selected if the job has successfully completed. |
Unsuccessful | This status is selected if the job has completed unsuccessfully. |
Requirements
N/A