Overview
Introduction to Daasity integrations and data sources.
Overview: Daasity Integrations & Data Sourrces
Integrations are the lifeblood of the Daasity platform – the more (relevant ones) you connect, the fuller the picture of your business performance. With this overview, you should feel confident in adding new data sources and understanding how Daasity handles your data end-to-end, from extraction to insight. This overview will cover the types of integrations (API-based vs. file-based), and what to expect in terms of data flow and dashboards once connected.
What is a Daasity Integration?
An integration in Daasity is a connection to an external data source that pulls data into your centralized data warehouse. Daasity currently supports many common data sources used by DTC brands, including:
Retail/Wholesale Data: Syndicated data (Nielsen/SPINS) and retail portals (Target, ULTA, Whole Foods) are often CSV files.
E-commerce Platforms: Shopify, BigCommerce, Magento, Amazon Seller Central, Walmart Marketplace, etc.
Marketing & Advertising: Facebook Ads, Google Ads, TikTok Ads, Pinterest Ads, Snap (Snapchat) Ads, Google Analytics, Klaviyo (email), Attentive (SMS), etc.
Customer Service/CRM: Gorgias, Zendesk, etc.
Reviews & Loyalty: Yotpo, Okendo, LoyaltyLion, etc.
Custom Sources: virtually any data that can be provided via a CSV file, Google Sheet, or database connection (Snowflake, Bigquery, Redshift, etc.) can be integrated as well.
Integration Types
Daasity handles integrations broadly in three primary ways: API and database connections, and CSV file uploads.
API-Based Integrations:
These are sources where Daasity connects through an Application Programming Interface (API) provided by the platform. For instance, Shopify provides an API to fetch orders, products, customers; Facebook Ads has APIs for fetching ad spend, clicks, etc.
When you set up an API integration in Daasity, you usually authenticate (provide an API key, OAuth token, or login credentials) so Daasity can programmatically query that system’s data. Daasity’s backend will regularly call the API to get new data (like new orders since last sync, yesterday’s ad spend metrics, etc.). API integrations are convenient because once set up, the data flow is automatic. They often allow near real-time or at least daily updates.
Most of Daasity’s standard digital analytics connectors are API-driven. Although they are “set and forget”, it's important to monitor your in-appNotifications for warnings of any issues with the integration status.
CSV File-based Integrations:
These are used when a platform doesn’t have a readily available API, or when data comes from CSV files, which is common for Wholesale and Retail data sources.
Examples might include retailer portals where you download CSV reports, or custom internal data that you export from a database to a file.
Database Connections
Daasity connects directly to your cloud data warehouse (Snowflake, BigQuery, or Redshift) through secure database connectors.
Setting Up a New Integration (General Steps)
To add a new data source in Daasity, follow these broad steps (the specifics might differ slightly by source, but Daasity’s help center has source-specific instructions too):
Navigate to the Data Section (data icon) and click "New Integration" button in the top-right.
Select the Integration you want to setup: You’ll see icons or a dropdown of sources (Shopify, Google Ads, etc., plus generic ones for database and custom google sheet setups). Choose the one you want to add.
Authentication & Configuration:
For API sources: a form will appear asking for credentials. For example, Shopify requires your store URL and an API key/password (or nowadays, perhaps a private app token). Google or Facebook might redirect you to log in via OAuth to grant Daasity access. Fill in the required fields (Daasity’s UI will guide what’s needed). Some sources also ask for configuration like date range for initial import or specific subsets of data (not common, but e.g., if an API is extremely large, maybe you choose how much history to pull).
For CSV-file sources: reach out to the support team ([email protected]) to configure a new CSV-based data source.
After Integration - What’s Next ?
Data Harmonization: Your data will be normalized into Daasity’s Unified Schemas (like Unified Order Schema, Unified Marketing Schema) will contain combined data. For example, if you have multiple marketing channels, unified spend and performance metrics across them. This allows cross-channel analysis easily.
Historical Data Load: Upon saving the integration setup, Daasity will typically commence an initial load. Expect that first load to take some time if there’s a lot of history (for instance, pulling 5 years of Shopify orders could take a while). Some integrations might limit history by default (e.g., Facebook Ads might pull last 2 years by default). If you need more, check Daasity docs or ask support.
Verify Data & Dashboards: Once the integration says it’s connected and data loaded, verify that you see the data. You can go to an Explore that uses that data (for example, after connecting Klaviyo, go to a “Klaviyo Campaign” explore or dashboard). Often, Daasity’s templates include Integration Dashboards showing that source’s data – open those and ensure numbers make sense. For API sources, you can cross-check a known value (e.g., yesterday’s orders in Shopify vs Daasity’s orders for yesterday should match, or total ad spend last month in Facebook vs what Daasity shows).
Ongoing Sync (Workflows): Daasity will automatically schedule a daily workflow to fetch new data. Whether the source data updates daily, weekly or monthly may vary, but whenever it is available, it will be in your reports the next morning! Most sources update daily, some update weekly or monthly as the data is available. Shopify runs hourly.The exact schedule can vary; Daasity’s integration specs often mention how often data refreshes.
- Integration Errors (Notifications: If credentials expire (like a token refresh fails) or an API changes, an integration might break. Daasity typically notifies you (maybe via email or a notice in the app) if an extraction fails. For file integrations, if a file didn’t arrive on schedule or a format changed, it might error. You can monitor integration status in the app’s data section. If something is red or inactive, click in to troubleshoot (it might prompt for re-auth or show an error message). The Daasity support team is also there to help resolve issues.
Special cases: Some APIs have limits on how far back you can fetch or how heavy the calls are when doing the historical loads. Others might have a specific day of the week they will update each period- for these and all other fun and squirrely details, always check the particular Integration Setup Guides & Specifications,
Useful Links for Further Info
As mentioned, sometimes things go wrong with API-baed integrations, and credentials need to be re-entered, so remember to setup your notifications.
Integration Setup Guides & Specifications - details on how Daasity replicates data from each source (which tables, how often, any known issues like “Google Ads doesn’t include search query data” or such).
Last updated
Was this helpful?