Back

This article describes how to set up the Domo JSON Webhook connector in your Universal Data Hub account.

In this article:

Table of Contents Placeholder

Connector Actions

Action Name AudienceStream EventStream
Send Event Data
Send Visitor Data
Send Customized Data (Advanced)

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • Webhook URL
    • Paste the URL provided in the Details section of your Domo connector setup.
    • If you specify a URL endpoint here, it will be applied to all actions in the connector, but may be overridden in the action.
  • Webhook Secret

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Event Data

Parameters

Parameter Description
Webhook URL
  • Required only if not provided in the Configuration tab.
  • Overwrites the value defined in the Configuration tab if a value is provided.
Print Attribute Names
  • If attribute names get updated, the names in the payload will reflect the update.

Action - Send Visitor Data

Parameters

Parameter Description
Webhook URL
  • Required only if not provided in the Configuration tab.
  • Overwrites the value defined in the Configuration tab if a value is provided.
Include Current Visit Data
  • Check this box if current visit data is to be included.
Print Attribute Names
  • If attribute names get updated, the names in the payload will reflect the update

Action - Send Customized Data (Advanced)

Parameters

Parameter Description
Webhook URL
  • Required only if not provided in the Configuration tab.
  • Overwrites the value defined in the Configuration tab if a value is provided.
Custom Message Definition
  • Map values to names for simple one level JSON format, otherwise reference template name, select only the Custom Message Definition option, and ensure your template is valid JSON.
  • For template support, reference the template name to generate message data from a template.
Template Variables
  • Optional.
  • Provide template variables as data input for templates. (Learn more)
  • Name nested template variables with the dot notation.
  • Example: items.name
  • Nested template variables are typically built from data layer list attributes.
Templates
  • Optional.
  • Provide templates to be referenced in message data. (Learn more)
  • Templates are injected by name with double curly braces into supported fields.
  • Example: {{SomeTemplateName}}