Choosing an integration method
Understand the different ways to bring data into UbiQuity, and choose the right approach based on your use case.
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
One-off or occasional uploads
Imports
Ongoing, automated data sync
Connectors
Real-time or custom integrations
API
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 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.
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
Last updated
Was this helpful?