Microsoft Azure Event Hubs is a cloud service for receiving and processing high volume of events. This article describes how to configure the service in your Customer Data Hub profile.
|Action Name||Trigger on Audience||Trigger on Streams|
|Send Event Data to Event Hub||✗||✓|
|Send Visitor Data to Event Hub||✓||✗|
|Send Customized Data to Event Hub||✓||✓|
Go to the Connector Marketplace and add a new Microsoft Azure Service Bus connector. Read the Connector Overview article for general instructions on how to add a connector.
To configure your vendor, follow these steps:
In the Configure tab, provide a title for the connector instance.
Sign in to the Azure Portal and create an Event Hubs Namespace, Shared Access Policy Name and Key. Then create an Event Hub. For more information, see: Create an Event Hubs namespace and an event hub using the Azure portal.
Use the Event Hub namespace, Shared Access Policy and Shared Access Key to configure the connector.
Click Test Connection to verify API connectivity with the provided credentials.
Shared Access Policies can claim three type of permissions:
Manage. Provided policy must claim at least
Click Next or go to the Actions tab. It's where you'll set up actions to trigger.
This section describes how to set up parameters and options for each action.
All actions support Message User and Broker properties. They provide useful and convenient information about a message using key-value pairs. But, they are set as HTTP headers and do not reside within the message body. For more information, see: Message User & Broker Properties.
|Content Type||Sets HTTP header
|Correlation ID||Unique identifier of the correlation|
|Session ID||Can be used to partition and route messages to particular consumers|
|Message ID||Overrides default auto-generated Message ID|
|Reply To||Can be used to specify where to send a response for message consumers|
|Time to Live in Seconds||Expire message after X number of seconds (overrides Event Hub level)|
|To||Send to address|
|Scheduled Enqueued Time||Scheduled date and time at which the message is enqueued|
|Reply to Session ID||Similar to Reply To but targets a session for a response|
|Partition Key||Unique identifier of the partitioned event hub|
If necessary, templates can also be referenced and injected in user and broker properties.