# Choosing an integration method

### Data & Integrations

UbiQuity provides multiple ways to capture and manage data. The right method depends on how often your data changes, how automated the process needs to be, and whether you require real-time interaction.

***

### Quick guide

| Use case                         | Best option |
| -------------------------------- | ----------- |
| One-off or occasional uploads    | Imports     |
| Ongoing, automated data sync     | Connectors  |
| Real-time or custom integrations | API         |

***

### [Imports](/documentation/data-and-integrations/imports.md)

Imports allow you to upload data into UbiQuity using files such as CSV.

This is the simplest way to get data into the platform and is typically used for one-off or occasional updates.

Common use cases include:

* Uploading campaign or marketing lists
* Migrating data into UbiQuity
* Making ad hoc updates to contact records

Imports are quick and flexible, but they are manual and not designed for ongoing synchronisation.

***

### [Connectors](/documentation/data-and-integrations/connectors.md)

Connectors allow UbiQuity to automatically exchange data with external systems on a scheduled basis.

They support both:

* Importing data into UbiQuity from external sources (import connectors)
* Exporting data from UbiQuity to external systems (export connectors)

This enables both pull and push data flows, depending on your use case.

At this stage, connectors operate using flat files and support the following storage locations:

* Azure Blob Storage
* Amazon S3
* SFTP

Connectors are designed for situations where data changes regularly and needs to stay up to date without manual effort.

Common use cases include:

* Regularly importing customer or transactional data
* Exporting audience or engagement data to external systems
* Keeping datasets in sync between UbiQuity and other platforms

Connectors reduce manual work and help ensure your data remains consistent over time.

***

### [API](/documentation/data-and-integrations/api.md)

The API allows external systems to send and retrieve data from UbiQuity programmatically.

It provides the most flexibility and is typically used for real-time or highly customised integrations.

Common use cases include:

* Capturing events or behaviours in real time
* Triggering workflows from external systems
* Building custom integrations with internal or third-party platforms

Using the API usually requires developer support, but enables more advanced use cases than imports or connectors.

***

### Choosing the right approach

If you're unsure which option to use, start by considering:

* How often does the data need to be updated?
* Does the process need to be automated?
* Do you need real-time interaction or is scheduled data sufficient?

In many cases:

* Use imports for simple, one-off needs
* Use connectors for ongoing data sync
* Use the API for real-time or advanced integrations


---

# Agent Instructions: 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:

```
GET https://docs.ubiquity.co.nz/documentation/data-and-integrations/choosing-an-integration-method.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.