B2B Edition B2P Edition

Demandbase connection

Last update: 2024-11-07
  • Created for:
  • Admin
    User
AVAILABILITY

The functionality to activate account audiences to the Demandbase destination is available for companies purchasing the Business-to-Business and Business-to-Person editions of Real-Time Customer Data Platform.

Activate profiles for your Demandbase campaigns for audience targeting, personalization, and suppression, based on account audiences .

Use case

Use this destination to activate your account audiences for Account-Based Marketing (ABM) use cases. Advertise to relevant personas and roles in your target accounts via DemandBase’s B2B Demand Side Platform (DSP). Target accounts can also be enriched with Demandbase third-party data, for other downstream use-cases in marketing and sales.

For instance, leverage Demandbase’s ad-tech DSP to target specific personas or roles within key accounts for top-of-funnel lead generation, or create and grow buying groups. Use the Demandbase destination to explore other use cases to target your accounts effectively.

With this integration, you can also personalize the website experience using real-time account information lookup to optimize engagement.

Supported audiences

This section describes which type of audiences you can export to this destination.

Audience origin Supported Description
Segmentation Service Audiences generated through the Experience Platform Segmentation Service.
Custom uploads X Audiences imported into Experience Platform from CSV files.

Export type and frequency

Refer to the table below for information about the destination export type and frequency.

Item Type Notes
Export Type Audience export All audience members will be exported with key identifiers like name, phone number, and more.
Frequency Streaming “Always-on” API-based connections. Updates are sent downstream immediately after profile changes.

Prerequisites

To export account audiences to Demandbase, you need the following:

  1. A Demandbase account.
  2. A Demandbase API token. You can generate an API token with your user in Demandbase. To generate a token, navigate to My Profile > API Token after logging into your Demandbase account.

Connect to the destination

IMPORTANT

To connect to the destination, you need the View Destinations and Manage Destinations access control permission. Read the access control overview or contact your product administrator to obtain the required permissions.

To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.

Authenticate to destination

To authenticate to the destination, fill in the required fields and select Connect to destination.

Add bearer token

  • Bearer token: Fill in the bearer token to authenticate to the destination. View prerequisites for information on how to obtain the token.

Fill in destination details

To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.

Add information about the destination connection

  • Name: A name by which you will recognize this destination in the future.
  • Description: A description that will help you identify this destination in the future.
  • Entity type: Select Account as the entity type.

Now you’re ready to activate your audiences within Demandbase.

Activate audiences to this destination

IMPORTANT

Read Activate account audiences for instructions on activating account audiences to this destination.

Additional notes and important callouts

  • If an account audience with the same name was activated earlier to Demandbase, you cannot activate it again through a different dataflow to the Demandbase destination.
  • If you have exported audiences to Demandbase and the exports are successful in Experience Platform, yet not all of the data reaches Demandbase, you might have encountered API throttling on the Demandbase side. Reach out to them for clarification.

On this page