Skip to main content
Data Sources FAQs
Openbridge Support avatar
Written by Openbridge Support
Updated over a year ago

Does Openbridge store copies of my source data?

No, Openbridge is a data pipeline. We do not persist in your data. Your data in our system is transient, which means the time it takes for us to collect data from a source and deliver it to a target destination.

If a situation occurs that prevents data from loading to your data destination (a copy error, a transformation error, type conversion error, etc.), the events that have not yet replicated to your data destination is temporarily stored in our system as a backup until destination errors are rectified.

What is the difference between plans?

We offer several integrations as "standard" connectors. All plans include these types of connectors. Another tier of integration is "Premium" connectors. Premium connectors often are more complex, advanced, and require additional development resources. "Premium" connectors are only available within Professional, and Business plans.

Enterprise or third-party integrations are only available to those users with Enterprise plans. Pricing for third-party integrations varies according to each vendor's procedures and policies.

What is the difference between standard or premium destinations?

We offer several data lakes or warehouse solutions as "Standard" destinations. All plans include these types of destinations. Another tier of destination is "Premium." Premium destinations are only available within specific plans.

  • Standard β€” Amazon Redshift, Google BigQuery, Snowflake, Amazon Athena, Amazon Redshift Spectrum

  • Premium β€” Databricks, Delta Lake

Is Openbridge resilient to changes in my source data?

We know data schemas change, so our platform embraces this change. We've created a "set and forget" your data, which we call "zero administration." When setting up an integration, we handle the schema and definition mapping to your target data destination automatically. As source data changes, all corresponding schema changes are registered and updated automatically in your target destination. See more on this approach here.

How do I load my source data?

Once you activate a connector, your data is automatically collected, processed, and routed once you've created and configured a data source and your target data destination. This process can take up to 24-48 hours after set up depending on the data source.

What if I don't see a source that I need in your list of connectors?

Talk to your product specialist or submit a support ticket indicating the source you need, and your request is routed to the correct person. The more requests we get for a data source, the higher we prioritize building the new connectors.

How does Openbridge handle changes in the source?

Our pipelines are configured to handle new fields or tables added to your source gracefully, so you don't need to make changes on your end. We continuously monitor and stay ahead of changes or deprecations, so you don't need to think about it.

What is the average data sync time for each source?

Most sources complete data sync in less than a day. However, the amount of data in the source and API rate limits may cause this to vary.

Why do I need to set up a call to discuss Enterprise and third-party data integrations?

Our goal is to make every data source available for ordering online. However, we do not currently support online ordering for 3rd party integrations. There are a couple of extra steps involved in setting those up to ensure that your integration and the data you are looking for are available.

How many integrations can I have?

You can add as many as you need. If you manage a large number of accounts and want to consolidate the data from each, reach out to us for some tips and best practices on how best to set up that type of configuration.

How long does it take to get set up and running?

In many cases, it is minutes. For 3rd party integrations, it takes 24-48 hours to get up and run. However, that timing can vary depending on a few variables. For example, there may be individual permissions, contracts, or setup required by a vendor that is outside our control.

What do I do if an integration I want is not supported?

If the integration you want isn't supported, you can check whether that data source supports access via batch SFTP export.

We are continuously expanding its support for integrations and targets. If you have an integration, you'd like to have us support which isn't currently, please contact us! An integration may already be in development, and there may be opportunities to join a beta group.

What if my data structure changes over time?

We know that data changes β€” schemas grow, shrink, and change. We've got your back! See our data catalog process that automatically adapts to changes.

Did this answer your question?