Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Dub (Actions) Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Dub (Actions) in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.
  • This destination is in Beta

Dub(link takes you to an external page) is the all-in-one link attribution platform for businesses to understand how their marketing spend is converting to sales.

This destination is maintained by Dub. For any issues with the destination, contact the Dub Support team.


Getting started

getting-started page anchor
  1. From your Segment workspace's Destination catalog page(link takes you to an external page) search for "Dub (Actions)".
  2. Select Dub (Actions) and click Add Destination.
  3. Select an existing Source to connect to Dub (Actions).
  4. Open your Dub workspace(link takes you to an external page).
  5. Go to Settings > API Keys(link takes you to an external page) in your workspace and create a new API key.
  6. Return to your Segment workspace and enter the API Key in the Dub (Actions) destination settings page.

Property nameTypeRequiredDescription
API Keystring
required

The API Key is available via Dub Dashboard: https://app.dub.co/settings/tokens


Dub (Actions) has the following presets

Preset NameTriggerDefault Action
Dub Browser PluginEvent type = "track", Event type = "identify", Event type = "group", Event type = "page", Event type = "alias"Dub Browser Plugin

Build your own Mappings. Combine supported triggers with the following Dub-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Track a Lead

track-a-lead page anchor

Track a Lead for a Short Link.

Track a Lead is a Cloud action. The default Trigger is type = "track" and event = "Sign Up"

Property nameTypeRequiredDescription
Click IDSTRING
required

The ID of the click in Dub. You can read this value from "dub_id" cookie.


Event NameSTRING
required

The name of the Lead event to track.


External IDSTRING
required

The unique identifier for the customer in the your app. Used to track the customer's journey.


Event QuantityNUMBER

Optional

The quantity of the Lead event to track.


Customer NameSTRING

Optional

The name of the customer.


Customer EmailSTRING

Optional

The email of the customer.


Customer AvatarSTRING

Optional

The avatar of the customer.


MetadataOBJECT

Optional

Additional metadata to be stored with the Lead event.

Track a Sale for a Short Link

Track a Sale is a Cloud action. The default Trigger is type = "track" and event = "Order Completed"

Property nameTypeRequiredDescription
External IDSTRING
required

This is the unique identifier for the customer in the your app. This is used to track the customer's journey.


AmountNUMBER
required

The amount of the Sale.


Payment ProcessorSTRING
required

The payment processor via which the Sale was made.


Event NameSTRING

Optional

The name of the Sale event. It can be used to track different types of event for example "Purchase", "Upgrade", "Payment", etc.


Lead Event NameSTRING

Optional

The name of the Lead event that occurred before the Sale (case-sensitive). This is used to associate the Sale event with a particular Lead event (instead of the latest Lead event, which is the default behavior).


Invoice IDSTRING

Optional

The invoice ID of the Sale. Can be used as a idempotency key – only one Sale event can be recorded for a given invoice ID.


CurrencySTRING

Optional

The currency of the Sale. Accepts ISO 4217 currency codes.


MetadataOBJECT

Optional

Additional metadata to be stored with the Sale event.

Enriches all Segment payloads with dub_id cookie value

Dub Browser Plugin is a Web action. The default Trigger is type = "track" or type = "identify" or type = "page" or type = "group" or type = "alias"

This action does not have any fields.

For more information about developing with Dub, check out Dub's Integrations documentation(link takes you to an external page).


You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo(link takes you to an external page).

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

(information)

Real-time to batch destination sync frequency

Real-time audience syncs to Dub (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription
API Keystring
required

The API Key is available via Dub Dashboard: https://app.dub.co/settings/tokens