A destination is a centralized location into which Stitch loads data replicated from your connected and active integrations. As you do with database integrations, you have the ability to control how Stitch accesses your destination, including where data is loaded.
The time to get value using Stitch and BigQuery was incredibly fast; we were set up and querying our data in under a day. The combination of Stitch and BigQuery answered our data needs before other vendors even answered our sales inquiries.
Co-Founder and COO, SaaSquatch
While all Stitch plans include support for a single destination, Stitch Enterprise can pipe data to multiple destinations for a variety of use cases:
Whatever your use case, if you need data replicated to multiple destinations, Stitch has you covered.
We recommend creating a Stitch-only user that Stitch can use when connecting your destination. The permissions required to load data into a destination depend on the type of destination you want to use. In general, the Stitch user needs to be able to perform the following tasks to load data:
In the Setup section of our destination documentation, you can find detailed information and instructions about granting the required permissions to our database user.
Stitch supports whatever way you want to structure access to your destination. As long as we have the required permissions to load data, how you grant access to your destination for the rest of your team is up to you.
From marketing to sales to finance to creative, there isn't anyone who doesn't use the data from Stitch.
Co-founder and CFO, Spotluck
If you don't already have a destination in mind and you're not sure how to make the best choice for your organization, don't worry. Our Choosing a Destination guide can help you make the right call. In it, we walk you through each destination's pricing structure, use cases, possible limitations, and more to ensure the destination you select is the one that best fits your needs.