> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/technical-documentation/integrations/data-integrations.md).

# Data Integrations

Import external product data into Crobox as properties for use across experiences.

### Overview

Crobox supports managed integrations that import external product data as Crobox properties. Use these properties across Product Finders, Campaigns, and other Crobox experiences.

{% hint style="info" %}
Data integrations are managed features. Contact your Account Manager to discuss availability and setup requirements.
{% endhint %}

### How it works

When configured, Crobox connects to your external data source and imports agreed data points as product properties. The process works as follows:

1. Your team and Crobox define the data points to import.
2. Crobox configures the managed connection with your team.
3. Imported data is stored as product properties in Crobox.
4. You use the properties across Crobox experiences.

### Use cases

<details>

<summary><strong>Use review data in experiences</strong></summary>

Regularly import current review data as Crobox product properties. Use it to support product discovery and messaging within Product Finder results, Comparison Tools or Sagent review sections.&#x20;

</details>

<details>

<summary><strong>Enrich product attributes</strong></summary>

Import defined attributes from your external data source. Use them in Finder questions, recommendations, and Campaign targeting.

</details>

<details>

<summary><strong>Improve product relevance</strong></summary>

Add external data points to create more relevant product experiences.

</details>

### Available integrations

Crobox supports the following managed data enrichment integrations:

<table data-view="cards"><thead><tr><th>Integration</th><th data-card-target data-type="content-ref">Details</th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>Bazaarvoice</strong><br>Import review data and other agreed data points as Crobox product properties.</td><td><a href="/technical-documentation/integrations/data-integrations.md">Data Integrations</a></td><td><a href="https://1240120646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M6BXLJuZMkdXQg6osAC%2Fuploads%2FOFaR8jjwwYt9mzCMXIOx%2Fbazaarvoice-logo.png?alt=media&amp;token=cf761366-2cc5-4ab3-88aa-4e53ac1f8a80">bazaarvoice-logo.png</a></td></tr></tbody></table>

{% hint style="success" %}
Additional integrations may be available upon request. Contact your Account Manager to discuss your data source.
{% endhint %}

### Prerequisites

Before setting up a data enrichment integration, ensure you have:

* Access to the external data source and relevant data points.
* A Crobox contract that includes the integration.
* Technical resources available for data mapping and testing.
* Defined use cases for the imported product properties.

### Getting started

Data enrichment integrations require collaboration between your team and Crobox. The process includes defining the required data points, mapping them to Crobox product properties, and testing the connection.

To begin, contact your Crobox Account Manager. They will confirm availability and coordinate setup with your team.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.crobox.com/technical-documentation/integrations/data-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.