- Destinations overview
- Destination types and categories
- Destinations (Activation) guardrails
- How destinations work
- API tutorials
- Activate data to file-based destinations by using the Flow Service API
- Connect to streaming destinations and activate data using the Flow Service API
- Connect to file-based email marketing destinations and activate data using the Flow Service API
- Activate audiences to batch destinations via the ad-hoc activation API
- Edit destination
- Update destination dataflows
- Delete destination accounts
- Delete destination dataflows
- Export datasets
- Sort and filter API responses for destinations
- UI guides
- Destinations workspace
- Create a new destination connection
- Activate data to destinations
- Activation overview
- Activate audiences to streaming audience export destinations
- Activate audiences to streaming profile export destinations
- Activate audiences to batch profile export destinations
- Activate audiences to edge personalization destinations
- Look up profile attributes on the edge in real-time
- Activate audiences to curated destinations based on LiveRamp identifiers
- Activate prospect audiences to destinations
- Activate account audiences to destinations
- Export files on-demand to batch destinations using the Experience Platform UI
- Export datasets using the Experience Platform UI
- (Beta) Use the last qualification time XDM attribute in the new beta cloud storage destinations
- Export arrays, maps, and objects
- Perform transformations on data exported to cloud storage destinations
- View destination details
- Update destination accounts
- Delete destination accounts
- Edit activation dataflows
- Delete destinations
- Monitor dataflows
- Configure file formatting options for file-based destinations
- Subscribe to in-context destination alerts
- Destinations catalog
- Destinations catalog overview
- Adobe destinations
- Advertising destinations
- (Beta) Acxiom Audience Distribution
- Advertising destinations overview
- Adobe Advertising Cloud connection
- Adobe Advertising Cloud extension
- Amazon Ads connection
- Awin Advertiser Conversion Tag extension
- Awin Advertiser Mastertag extension
- Bing Ads Universal Event Tracking (UET) extension
- Bombora connection
- Branch extension
- Criteo connection
- Demandbase connection
- Demandbase People connection
- DoubleClick Floodlight (Beta) extension
- Facebook Pixel extension
- Flashtalking OneTag extension
- Google Ads connection
- Google Ads extension
- Google Ad Manager connection
- (Beta) Google Ad Manager 360 connection
- Google Customer Match connection
- (Beta) Google Customer Match + DV360 connection
- Google Display & Video 360 connection
- Google gtag extension
- LinkedIn Insight Tag extension
- LiveRamp - Onboarding connection
- LiveRamp - Distribution connection
- Magnite Batch
- Magnite Streaming Real-time connection
- Microsoft Bing connection
- Pinterest Conversion Tracking extension
- Pinterest Customer List connection
- PubMatic Connect connection
- Snapchat Ads connection
- The Trade Desk connection
- The Trade Desk CRM connection
- Twitter Universal Website Tag extension
- Yahoo/Verizon DataX connection
- Analytics destinations
- Analytics destinations overview
- Adform Website Tracking extension
- Adobe Analytics extension
- Adobe Media Analytics for Audio and Video extension
- Clicktale extension
- Contentsquare extension
- Decibel extension
- Demandbase extension
- DialogTech extension
- Gainsight PX connection
- Google Global Site Tag extension
- Google Universal Analytics extension
- JW Player Analytics (Beta) extension
- Nielsen BSDK extension
- Nielsen IMA Handler extension
- Nielsen VideoJS Player Handler extension
- Parse.ly Analytics extension
- Quantum Metric extension
- SessionCam extension
- TMMData extension
- Yext Conversion Tracking extension
- Cloud storage destinations
- Customer Relationship Management (CRM) destinations
- Data Management Platform destinations
- Data & Identity Partner
- eCommerce destinations
- Email destinations
- Email marketing destinations
- Email marketing destinations overview
- Adobe Campaign connection
- Adobe Campaign Managed Cloud Services connection
- Mailchimp Interest Categories
- Mailchimp Tags
- (API) Oracle Eloqua connection
- (Files) Oracle Eloqua connection
- Oracle Responsys connection
- (API) Salesforce Marketing Cloud connection
- (Files) Salesforce Marketing Cloud connection
- Salesforce Marketing Cloud Account Engagement
- SendGrid connection
- Tag extensions
- Marketing automation
- Mobile engagement destinations
- Personalization destinations
- Personalization destinations overview
- (Limited availability) Audience Analysis
- Adobe Commerce connection
- Adobe Target connection
- Adobe Target extension
- Adobe Target v2 extension
- Beemray extension
- Custom personalization connection
- D&B Visitor Intelligence extension
- Experience Cloud ID Service extension
- Gainsight extension
- KickFire extension
- Marketo Web Personalization extension
- Pega CDH Realtime Audience connection
- (V2) Pega CDH Realtime Audience connection
- Pega Profile connection
- Social destinations
- Streaming destinations
- Survey destinations
- Voice of the customer destinations
- Destination SDK
- Overview
- Integration prerequisites
- Getting started with Destination SDK
- Glossary
- Functionality
- Configuration options
- Destination server components
- Destination configuration components
- Configure audience data type
- Customer authentication configuration
- OAuth2 authorization
- Customer data fields
- UI attributes
- Partner schema configuration
- Identity namespace configuration
- Supported mapping configurations
- Destination delivery
- Audience metadata configuration
- Aggregation policy
- Batch configuration
- Historical profile qualifications
- Rate limiting and retry policy for streaming destinations
- Audience metadata management
- Guides
- Use Destination SDK to configure a streaming destination
- Use Destination SDK to configure a file-based destination
- Submit for review a destination authored in Destination SDK
- Configure file-based destinations
- Configure file formatting options
- Configure an Amazon S3 destination with predefined file formatting options and custom file name configuration
- Configure an Amazon S3 destination with custom file name and formatting options
- Configure an Azure Blob Storage destination with custom file formatting options and custom file name configuration
- Configure an Azure Data Lake Storage destination with custom file formatting options and custom file name configuration
- Configure an Data Landing Zone (DLZ) destination with custom file formatting options and custom file name configuration
- Configure an SFTP destination with predefined file formatting options and custom file name configuration
- Configure a file-based destination to export prospect audiences
- Destination authoring API reference
- Audience metadata API reference
- Credential configuration API reference
- Destination testing API reference
- Destination publishing API reference
- Document your destination
- Frequently asked questions
- Experience Platform release notes
Bombora connection
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
To help you better understand how and when you should use the Bombora destination, here are sample use cases that Adobe Experience Platform customers can solve by using this destination.
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’s 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
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
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
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
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
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 “always 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
To export account audiences to Bombora, you need the following information.
- A Bombora account.
- A Bombora client ID and client secret.
Connect to the destination
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.
- Client ID: Enter your Bombora client ID.
- Client secret: Enter your Bombora client secret.
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.
- 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’re ready to activate your audiences within Bombora.
Activate audiences to this destination
- To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
- To export identities, you need the View Identity Graph access control permission.
Read Activate account audiences for instructions on activating account audiences to this destination.
Mandatory mappings
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. |
Additional notes and important callouts
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.
