The DIY connector gives you full control to set up a server-to-server connection between the Data Activation platform and any suitable external platform or endpoint.
The DIY event connector sends any raw event received by the Data Activation platform to an external endpoint as soon as the configured event arrives. This can be an engagement, fact, or any other available event type.
Why use this connector
Use the DIY event connector when you need to:
Send event data to a custom endpoint not covered by standard connectors
Have complete control over the request method, headers, and payload
Dynamically construct endpoints and payloads using event data
Before you begin
To configure a DIY event connector, you’ll need:
The correct endpoint URL
Authentication credentials (API key, username/password, or a bearer token)
Payload format requirements from your target platform
All relevant dynamic values included in event ingestion
Configuration options
Method
Select the appropriate request method based on your endpoint requirements. Your partner should provide the correct method:
GET
POST
PUT
DELETE
Endpoint URL
Configure the endpoint URL here. The URL can be static or contain dynamic properties.
To include dynamic parameters, use property placeholders with the ${xxx} notation. The placeholder can reference:
A static property defined in the connector (see Properties section)
A dynamic value from the event configured through attached transformations (see Transformations section)
Example URL:
https://webhook.site/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx?prop1=${prop1}&prop2=${productIdTrimmed}
Authorization
We support 3 authorization options:
API key
Basic authentication (username and password)
Bearer token
Headers
Different endpoints require different headers. Headers consist of a key and a value. Your partner should provide the appropriate headers.
Properties
Properties allow you to use placeholders in the URL and payload while maintaining a generic syntax. Configuring values in the properties tab makes it easy to change variables while limiting the risk of mistakes.
If any values contain sensitive information, check the Secure checkbox to ensure sensitive information isn't unintentionally disclosed when other users edit the configuration.
Payload
The payload is a free input field where you can use placeholders. Payloads are typically JSON objects.
Example payload:
{"action":"add","staticPropertyValue":"${staticProperty}","valueFromEvent":"${eventProperty}"}In this example, staticProperty and eventProperty should be either configured in an attached transformation or as a property in the properties tab.
Filters
Applying one or more filters restricts which events you send. For example, you can send only conversions or a specific engagement.
To apply a filter to your DIY event connector, first create a filter by navigating to Data → Filters → Add filter.
Read more about filters in Data Activation.
Transformations
If the events you want to send don't contain the exact data format you need, apply transformations. Read more about transformations.
When configuring a transformation:
Source property: The value contained by the configured event
Destination property: The placeholder you can use in your URL and payload
Example: If you configure a transformation with productIdTrimmed as the destination property, you can use the placeholder ${productIdTrimmed} in your DIY event connector URL to include the productId event property value as a parameter.