Event connectors allow you to stream incoming raw event data directly to partner platforms. This means the data sent is the same as what you'd receive in a historic event export. Event connectors provide flexibility to use raw data for reporting or activation without relying on audiences or journey orchestration.
Event connectors are ideal when you need to:
Pass raw event data to external platforms in real time
Use event data for reporting purposes
Activate data without building audiences or journeys
Instructions
Set up an event connector
Setting up an event connector is similar to creating any other connector.
On the Data Activation platform, select Connectors in the left-side navigation bar.
Select Event connector and click New event connector.
Select the destination partner you want to stream data to.
Create the connector by filling in the required information. If you need more details for the setup, refer to the documentation for the specific event connector.
Once saved, the new event connector activates and begins sending raw event data to the selected partner immediately. No further configuration or activation is needed. Log in to your partner dashboard to view the event data.
View statistics
Event connectors only support ADD calls. To view statistics, click the name of the connector in the list of configured event connectors.
View presets are 7, 30, or 90 days, but you can manually set dates to select a custom timeframe.
Deactivate an event connector
You can deactivate an event connector to stop sending data to the destination partner. Click the 3 dots (…) on the right and select Deactivate. This instantly stops data transmission to this destination.
To start sending data again, activate the connector using the same method and selecting Activate.
Delete an event connector
To delete an event connector, click the 3 dots (…) on the right and select Delete. This instantly stops data transmission and removes the connector.
Note
Once deleted, statics for the connector are permantently lost.
Handling failures
Event connectors use a retry mechanism to resend data if a failure occurs. For example, connection timeouts or error responses from the partner. If a failure happens, the connector retries 3 times before marking the transmission as Failed. If the connector can't send data after 3 attempts, it discards the data.
Failures appear in the connector statistics under two tabs:
Connector errors: Results from responses received from the external platform
Transformation errors: Occur when a datatype can't be transformed according to its settings. Read more information on transformations.
Error categories
Partner error codes: Partner platform error responses are grouped and listed. This provides a simple overview of error messages you've received from the external platform.
Invalid credentials: Something is wrong with the credentials — this could be an expired password or insufficient privileges.
Timeout: We stop the request if the destination doesn't respond within the timeout period (typically around 3 seconds).
ResourceAccessException: Couldn't connect to the target server.
Circuit breaker: The connector temporarily stops sending due to a large number of errors.
Other error: A general error that provides limited insights. If you're experiencing "other errors" and want to know more, we're happy to help.