Bombora Data Source

Bombora is a B2B intent data and account intelligence provider whose APIs expose account lists, digital audiences, intent data, signal definitions, and B2B demographic reference data. Follow the instructions below to create a new data flow that ingests data from a Bombora source in Nexla.

Bombora

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

2. Select the Bombora connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Bombora instance, and click Next; or, create a new Bombora credential for use in this flow.

3. In Nexla, Bombora data sources can be created using pre-built endpoint templates, which expedite source setup for common Bombora endpoints. Each template is designed specifically for the corresponding Bombora endpoint, making source configuration easy and efficient.
   • To configure this source using a template, follow the instructions in Configure Using a Template.

   Bombora sources can also be configured manually, allowing you to ingest data from Bombora endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Bombora endpoints. Each template is designed specifically for the corresponding Bombora endpoint, making data source setup easy and efficient.

Endpoint Settings

• Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

  List Account Lists

  This endpoint returns all account lists configured in your Bombora account. Account lists group the target accounts that intent measurement and audience activation are scoped to. Use this endpoint to sync your account-list catalog into a warehouse or to obtain account-list IDs for use with the account-list-scoped endpoints below.

  • No configuration is required for this endpoint beyond selecting it. The endpoint calls GET /account-list/v1/account-list and treats each element of the top-level accountLists array as a record.

  For the full Account List API contract, see the Bombora Account List API documentation.

  Get Account List

  This endpoint retrieves the full details of a single account list by ID. Use it to enrich an existing dataset of account-list IDs with the latest list metadata.

  • Enter the account list ID in the Account List ID field. This field is required. Account list IDs can be obtained from the List Account Lists endpoint or from upstream Nexla data flows.

  Search Accounts

  This endpoint searches for accounts within a specific account list and returns the matching accounts in a single response. Use it for ad-hoc lookups against an account list — for example, to confirm whether a specific company is included in a target list.

  • Enter the account list ID in the Account List ID field. This field is required and identifies the list to search within. Account list IDs can be obtained from the List Account Lists endpoint.
  • Enter the search criteria in the Search Query field. This field is optional — leave it blank to return all accounts in the list, or enter the value to filter by (for example, a domain or company name).

  This endpoint uses POST /account-list/v1/account-list/<id>/accounts/search with the query value passed in the JSON request body. For very large lists, prefer the Get Search Results endpoint, which paginates through results using a page token.

  Get Search Results

  This endpoint retrieves the accounts within a specific account list using token-based pagination. Use it to sync the full membership of a large account list into a warehouse or downstream system.

  • Enter the account list ID in the Account List ID field. This field is required and identifies the list to retrieve accounts from.
  • Enter the maximum number of results per page in the Limit field. This field is optional and defaults to 100. Larger pages reduce the number of HTTP calls; smaller pages reduce per-call payload size.

  Nexla automatically follows the pageToken values returned by Bombora until all results have been retrieved, so the Limit value controls page size — not the total number of records that will be ingested.

  Get Digital Audience

  This endpoint retrieves the full details of a single digital audience by data exchange, external ID, and partner ID. Digital audiences are activation segments that Bombora distributes to a partner data exchange such as a DSP or DMP. Use this endpoint to read back the configuration of an existing audience.

  • Enter the data exchange identifier in the Data Exchange field. This field is required and identifies the destination platform for the audience (for example, the partner exchange where the audience is delivered).
  • Enter the external identifier of the audience in the External ID field. This field is required and uniquely identifies the audience within the data exchange.
  • Enter the partner identifier in the Partner ID field. This field is required and identifies the partner account that the audience belongs to.

  For the full Digital Audience Builder API contract, see the Bombora Digital Audience API documentation.

  Search Intent Data

  This endpoint searches the Bombora intent dataset using a JSON filter object and returns the matching records. Use it for targeted intent queries — for example, to retrieve Company Surge® scores for a specific topic cluster, account list, or time window.

  • Enter the filter criteria in the Search Filters field as a JSON object. This field is optional and defaults to {}, which returns the full dataset available to your credential. Refer to the Bombora Intent API documentation for the supported filter fields.

  The filter object is sent in the JSON request body wrapped in a filters property — for example, {"filters": {"topic": "Data Integration"}}. Use this endpoint when the entire result set fits in a single response; for paginated retrieval, use List Intent Data.

  List Intent Data

  This endpoint returns Bombora intent data records using token-based pagination. Use it to ingest the full intent dataset that your credential is entitled to — for example, into a warehouse for downstream scoring or attribution modeling.

  • Enter the maximum number of records per page in the Limit field. This field is optional and defaults to 100. Nexla automatically follows the pageToken values returned by Bombora until all results have been retrieved.

  Intent datasets can be very large. For periodic full refreshes, schedule the source during low-traffic periods; for incremental ingestion, prefer Search Intent Data with a date filter that matches your refresh cadence.

  List Signal Definitions

  This endpoint returns all signal definitions configured in your Bombora account. A signal definition specifies the topics and thresholds that drive intent measurement for a given use case. Use this endpoint to sync your signal-definition catalog into a warehouse or to obtain signal-definition IDs for use with the signal-definition-scoped endpoints below.

  • No configuration is required for this endpoint beyond selecting it. The endpoint calls GET /intent/v1/signal-definitions and treats each element of the top-level data array as a record.

  Get Signal Definition

  This endpoint retrieves the full details of a single signal definition by ID. Use it to enrich an existing dataset of signal-definition IDs with the latest configuration — for example, the topic list and threshold settings associated with the signal.

  • Enter the signal definition ID in the Signal Definition ID field. This field is required. Signal definition IDs can be obtained from the List Signal Definitions endpoint or from upstream Nexla data flows.

  List B2B Personas

  This endpoint returns the B2B personas available for demographic segmentation in Bombora. Personas describe the buyer roles that Bombora classifies content consumption against. Use this endpoint to sync the persona reference dataset into a warehouse, or to look up valid persona identifiers when configuring downstream segmentation.

  • No configuration is required for this endpoint beyond selecting it. The endpoint calls GET /reference/v1/demographic/b2b-personas and treats each element of the top-level personas array as a record.

  This endpoint is also used by Nexla to validate Bombora credentials during the credential save step.

  List Functional Areas

  This endpoint returns the functional areas available for demographic classification in Bombora. Functional areas describe the job-family taxonomy (for example, Engineering, Marketing) that Bombora classifies content consumption against. Use this endpoint to sync the functional-area reference dataset into a warehouse.

  • No configuration is required for this endpoint beyond selecting it. The endpoint calls GET /reference/v1/demographic/functional-area and treats each element of the top-level functionalAreas array as a record.

  List Webhook Destinations

  This endpoint returns all webhook destinations configured in your Bombora account. Webhook destinations are HTTP endpoints that Bombora calls when subscribed events occur. Use this endpoint to inventory the webhook destinations in your account or to obtain destination IDs for use with the Get Webhook Destination endpoint.

  • No configuration is required for this endpoint beyond selecting it. The endpoint calls GET /webhooks/v1/destinations and treats each element of the top-level destinations array as a record.

  Get Webhook Destination

  This endpoint retrieves the full configuration of a single webhook destination by ID. Use it to enrich an existing dataset of webhook-destination IDs with the latest URL, event subscriptions, and authentication settings.

  • Enter the webhook destination ID in the Destination ID field. This field is required. Destination IDs can be obtained from the List Webhook Destinations endpoint or from upstream Nexla data flows.

Endpoint Testing

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

• To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

• If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually

Bombora data sources can be manually configured to ingest data from any valid Bombora API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Bombora sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request bodies or query parameters.

API Method

1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

2. Select the API method that will be used for calls to the Bombora API from the Method pulldown menu. The most common methods are:

   • GET: For retrieving data from the API (used by most Bombora read endpoints)
   • POST: For searches that pass filter criteria in a JSON request body (used by Bombora intent and account-list search endpoints)

API Endpoint URL

3. Enter the URL of the Bombora API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Bombora API endpoints follow the format https://api.bombora.com/<api>/v1/<resource> — for example, https://api.bombora.com/intent/v1/data or https://api.bombora.com/account-list/v1/account-list.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL.

Date/Time Macros (API URL)

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements. This is useful for Bombora endpoints that accept date filters, such as a weekly intent refresh that targets only the most recent reporting period.

Macros are particularly useful for APIs that require date ranges, pagination parameters, or other dynamic values that change between data ingestion runs.

1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

   • {now} – The current datetime
   • {now-1} – The datetime one time unit before the current datetime
   • {now+1} – The datetime one time unit after the current datetime
   • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data. For Bombora, this is useful for driving record-level endpoints — for example, iterating over a list of account-list IDs to fetch the membership of each list.

Lookup-based macros are useful when you need to create API endpoints that reference specific IDs, values, or parameters from other data sources in your Nexla environment.

1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data

Optional

If only a subset of the data that will be returned by the API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful because Bombora list responses typically wrap the records in a named array (for example, accountLists, personas, or data) alongside pagination metadata.

For example, when a request call is used to fetch a list of items, the API will typically return an array of records, along with metadata, in the response. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

• To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

  • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.data.items[*] to access an array of items within a data object).

  • For responses in XML format, enter the XPath that points to the object/array containing relevant data. XPath uses slash notation (e.g., /response/data/item to access item elements within a data element).

  Path to Data Example:

  Bombora list endpoints return a top-level array named for the resource. For the intent endpoint /intent/v1/data, which returns a top-level array named data, the path to the response would be entered as $.data[*].

Autogenerate Path Suggestions

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

• To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

• Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

  

Metadata

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array.

For example, Bombora list responses may include a pageToken value alongside the records array. If you have specified the path to the relevant records but want to retain the page token in each record, you can specify a path to this metadata to include it with each record in the generated Nexset(s).

Metadata paths are particularly useful for preserving API response context like request IDs, timestamps, or summary statistics that apply to all records in the response.

• To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

  • For responses in JSON format, enter the JSON path to the object or array that contains the metadata, and for responses in XML format, enter the XPath.

Request Headers

Optional

• If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom requirements.

  You do not need to include any headers already present in the credentials. The Bombora Authorization bearer-token header is handled automatically by Nexla based on your credential configuration.

Endpoint Testing

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

• To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

• If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source

1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Bombora data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.