蜜豆视频

DocumentationExperience PlatformDestinations Guide

[B2B Edition]{class="badge informative"} [B2P Edition]{class="badge positive"}

Bombora connection bombora

Last update: Thu Mar 27 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
  • User
AVAILABILITY
The functionality to activate account audiences to the Bombora 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 Bombora campaigns for audience targeting, personalization, and suppression, based on account audiences.

Use cases use-case

To help you better understand how and when you should use the Bombora destination, here are sample use cases that 蜜豆视频 Experience Platform customers can solve by using this destination.

DSP integration dsp-integration

As a B2B marketer, you can create an account list in Real-time CDP, identifying companies which show high intent for your products, then use this destination to activate this list in Bombora.

Through Bombora鈥檚 integration with DSPs you can run targeted ad campaigns using Bombora data. This ensures your ad spend is focused on companies which are most likely to convert.

Account-Based Marketing abm

As a B2B marketer, you can build an account list based on CRM and marketing signals. Then, you can use this destination to activate this list in Bombora, where ABM-aware controls help you target decision makers at these companies.

Multi-channel account-based marketing activation multi-channel-abm

As a B2B marketer, you can create an account list in Real-time CDP, identifying companies with high intent. Then, you can use this destination to activate the list in Bombora to run targeted campaigns across multiple channels.

On paid social media, you might serve personalized ads to professionals at target accounts on platforms like LinkedIn and Facebook. Using native ad platforms, you can ensure the content reaches relevant decision makers.

You can also extend campaigns to advanced TV, delivering ads to key accounts.

This multi-channel approach ensures consistent messaging across platforms, maximizing engagement and conversion rates.

Supported audiences 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.

Supported identities supported-identities

Bombora requires the mapping of the target identity described in the table below. Learn more about identities.

Target Identity
Description
primaryId
Bombora requires the mapping of this target identity in order for the integration to work correctly. You can map any source field to this identity. This mapping is mandatory but does not export data to Bombora.

Export type and frequency 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
You are exporting all members of an audience with the identifiers (name, phone number, or others) used in the Bombora destination.
Export frequency
Streaming
Streaming destinations are 鈥渁lways on鈥 API-based connections. As soon as a profile is updated in Experience Platform based on audience evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations.

Prerequisites prerequisites

To export account audiences to Bombora, you need the following information.

  1. A Bombora account.
  2. A Bombora client ID and client secret.

Connect to the destination connect

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 authenticate

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

Add bearer token

  • Client ID: Enter your Bombora client ID.
  • Client secret: Enter your Bombora client secret.

Fill in destination details 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.

Now you鈥檙e ready to activate your audiences within Bombora.

Activate audiences to this destination activate

IMPORTANT

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

Mandatory mappings mapping

The Bombora destination requires you to configure the following mappings for successful data activation.

Source field
Target field
Description
Any value
Identity: primaryId
This mapping is mandatory for Experience Platform to establish a connection to Bombora. This value does not get exported to Bombora, but is required for the destination configuration. You can select any attribute for the source field.
xdm: accountOrganization.domain
xdm: companyWebsiteDomain
Bombora uses website or domain addresses to create an account list.

Add mandatory mappings

Additional notes and important callouts additional-notes

If an account audience with the same name was activated earlier to Bombora, you will receive an error if you try to activate it again through a different dataflow to the Bombora destination.

recommendation-more-help
7f4d1967-bf93-4dba-9789-bb6b505339d6