Data Bridge is where you move customer data in and out of UMAP360 — import a spreadsheet of customer traits, or export your profiles as a CSV file. You build each flow as a pipeline, run it when you need it, and watch its results from one screen.
What you can do today
Right now Data Bridge supports two things:
- CSV import — upload a spreadsheet of customer traits and map its columns to profile fields.
- CSV export — download your profiles as a CSV file.
You'll see other sources (like Shopify, WooCommerce, and Razorpay) and other destinations (like Google Sheets, BigQuery, HubSpot, and ad-platform audiences) listed in the pipeline builder, but they're marked Coming soon and can't be selected yet.
A few terms
A pipeline is one configured flow from a source to a destination. A source is where data comes from (a CSV upload), a destination is where it goes (a downloadable CSV), and a run is a single execution of that pipeline.
Create a pipeline
- Open Data Bridge from the sidebar.
- Click New Pipeline to open the 3-step wizard.
- Work through the steps:
| Step | What you do |
|---|---|
| 1. Source | Choose where the data comes from. Only CSV Upload is selectable today. |
| 2. Configure | Give the pipeline a clear name (e.g. "Customer Traits Import"). For a CSV source, drop in your file and map each column to a profile field — email, phone, user ID, or a trait. |
| 3. Destination | Choose where the data goes. Only CSV Export is selectable today. |
- Click Create Pipeline.
Check your column mapping
Any CSV column you don't map is ignored. Double-check the mapping before you create the pipeline so nothing important gets dropped.
Run a pipeline
Pipelines don't run on a background schedule — they run when you trigger them. There are two cases:
- Import — your CSV file is processed at the moment you create the pipeline.
- Export — click the Run / Export (▶) action on a pipeline row to generate a fresh CSV of your profiles.
The schedule shown on a CSV pipeline reads as manual for this reason.
Monitor your pipelines
The Data Bridge dashboard lists every pipeline, with a row of summary cards across the top:
| Card | What it shows |
|---|---|
| Records — Latest Run | Records processed in each pipeline's most recent run, added up across all pipelines |
| Active Pipelines | Pipelines that are currently enabled (paused ones aren't counted) |
| Import Sources | Pipelines pulling customer data into UMAP360 |
| Export Pipelines | Pipelines pushing profiles out to external tools |
Pipeline status at a glance
Each pipeline row shows a status pill:
| Status | Meaning |
|---|---|
| Running | The pipeline is executing right now |
| Success | The last run finished without errors |
| Error | The last run hit a problem (the message appears under the pipeline name) |
| Stale | A run has been stuck for over 10 minutes, so you can spot a stalled run |
| Inactive | The pipeline is paused or disabled |
| Never run | The pipeline was created but hasn't run yet |
See the details of a run
Click the Run history (clock) icon on a pipeline row to open its run-history drawer. Each run shows its start time, status, records processed, duration, the error message for failed runs, and what triggered it.
When a run fails
- Read the error message for the failed run — it shows up under the pipeline name and on each row in the run-history drawer.
- Common causes include:
- Schema mismatches — your source data changed shape, so revisit the column mapping.
- Data validation failures — the source data doesn't meet what the destination expects.
- Connection or rate-limit issues — the destination is unreachable or throttling.
- Fix the issue, then click the Run / Export (▶) action on the pipeline row to try again.
A few good habits
- Use descriptive names so your whole team understands each pipeline at a glance.
- Test with a small file first before importing or exporting a large dataset.
- Set up alerts so you're notified when a pipeline fails — see Alerts.
Next steps
- New to bringing data in? Start with the Connecting Your Data overview.
- Want to see the customers your imports build up? Visit the Customers overview.
- Having trouble with a connection? See Connector health and troubleshooting.
Last updated 2026-06-11