Bombora Intent

Last update: March 26, 2025

CREATED FOR:

  • Developer

Bombora is a comprehensive audience solution that specializes in B2B intent data. Bombora Intent is an Adobe Experience Platform source that you can use to connect your Bombora account to Experience Platform and integrate your account intent data.

With the Bombora Intent source, you can integrate Bombora’s company surge intent data to identify accounts actively researching your products or services. Use Bombora to prioritize in-market accounts to create precise segments and execute hyper-targeted ABM campaigns, ensuring your marketing efforts focus on those account most likely to convert. Additionally, you can leverage intent-driven strategies to optimize ad spend, boost engagement, and maximize ROI.

Read this document for prerequisite information on the Bombora source.

Use cases

Read the following for use case examples that you can apply to the Bombora source.

Demand-Side Platform (DSP) integration

As a B2B marketer, you can create an account list in Real-Time CDP, identify companies that show high intent for your products, then activate this list in Bombora, which integrates directly with DSPs, allowing you to run targeted programmatic ad campaigns using Bombora’s data. This ensures that your ad spend is focused on companies most likely to convert.

Account-Based Marketing (ABM) Capabilities

As a B2B marketer, you can build an account list based on first and third-party intent signals. You can then activate this list in Bombora, where ABM capabilities allow you to target employees at these accounts specifically, ensuring your ads reach decision-makers rather than a broad audience.

Multi-Channel ABM Activation

As a B2B marketer, you can create an account list in Real-Time CDP, identifying companies with high intent and activate it in Bombora to run targeted campaigns across multiple channels. On paid social media, you can serve personalized ads to professionals at target accounts on platforms like Linkedin and Facebook.

Using native ad platforms, you can ensure your content reaches decision-makers in relevant contexts. 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.

Prerequisites

Read the following sections for prerequisite steps before connecting Bombora to Experience Platform.

IP address allowlist

A list of IP addresses must be added to an allowlist prior to working with source connectors. Failing to add your region-specific IP addresses to your allowlist may lead to errors or non-performance when using sources. See the IP address allowlist page for more information.

Configure permissions on Experience Platform

You must have both View Sources and Manage Sources permissions enabled for your account in order to connect your Bombora account to Experience Platform. Contact your product administrator to obtain the necessary permissions. For more information, read the access control UI guide.

Naming constraints for files and directories

The restrictions listed below must be taken into consideration when naming your cloud storage file or directory:

  • Directory and file component names cannot exceed 255 characters.
  • Directory and file names cannot end with a forward slash (/). If provided, it will be automatically removed.
  • The following reserved URL characters must be properly escaped: ! ' ( ) ; @ & = + $ , % # [ ]
  • The following characters are not allowed: " \ / : | < > * ?.
  • Illegal URL path characters are not allowed. Code points like \uE000, while valid in NTFS filenames, are not valid Unicode characters. In addition, some ASCII or Unicode characters, like control characters (0x00 to 0x1F, \u0081, etc.), are also not allowed. For rules governing Unicode strings in HTTP/1.1 see RFC 2616, Section 2.2: Basic Rules and RFC 3987.
  • The following file names are not allowed: LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, PRN, AUX, NUL, CON, CLOCK$, dot character (.), and two dot characters (…).