Databox's update separates connections from data sources, enabling you to easily reauthenticate and share connections, streamlining data source management.
In August 2024, Databox will change how users connect data sources and how these connections are displayed in its products.
What exactly is going to change?
The current "data source connection" will be divided into two distinct entities: a connection and a data source.
-
Connection: This will include authentication information and authorization tokens granted to Databox by you. It functions as a contract, allowing Databox to access a specific integration on the user's behalf.
-
Data Source: This represents the actual resource being accessed within the integration, such as a property in Google Analytics, an ad account in Facebook Ads, or a hub ID in HubSpot.
How it was before
Previously, for each property, ad account, hub ID, etc., users had to authenticate and grant Databox permission to access these resources individually. This process had to be repeated multiple times for data sources tied to the same credentials, both for initial connections and reconnections.
In essence, the data source connection previously combined authentication information and data source details into a single entity, leading to redundant and time-consuming processes.
How it will be moving forward
When connecting an integration for the first time, a connection entity will be saved in the account, separate from the data source (e.g., property, ad account, hub ID) that was selected. This allows users to reuse the existing connection when adding another data source from the same integration, eliminating the need to reauthenticate during the connection process.
Data sources added this way will share the same connection. Therefore, if the connection breaks due to an issue on the provider's side (e.g., a password change), all data sources can be reconnected simply by reauthenticating the shared connection. This avoids the need to repeat the reauthentication process for each individual data source.
Why is Databox making this change?
Google has recently updated its Drive API scopes and usage policies, requiring updates to the Google Sheets and Excel (via Google Drive) integrations to remain compliant.
These changes provided an opportunity to enhance the overall data source management system, not only meeting Google's requirements but also streamlining the connection process. This improvement empowers users with greater control over how connections are established and reduces the time needed to reconnect multiple and related sources.
What else comes with this update?
Connection Sharing
To further facilitate the process, connections can now be shared among users and accounts. The user who establishes the connection can decide whether to share it with other users in the same account or with client accounts within the partner account.
Example 1:
- John is an admin in Databox and owns a GA4 account with 3 properties (A, B, and C). He connects GA4 and adds property A as a data source.
- John shares the connection with David, an editor in the Databox account.
- Although David does not have direct access to the GA4 account or its properties, he can now add properties B and C to the Databox account using the shared connection without additional input from John.
Example 2:
- Charlie is an account manager for two clients (ACME and XYZ). His agency has a Databox account with separate client accounts for each.
- Charlie has access to both the agency's and his clients' Facebook Ads accounts.
- He connects the agency's Facebook Ads account to the agency Databox account and shares that connection with the client accounts.
- Charlie can then log into client account ACME in Databox and use the shared connection to add their Facebook Ads account as a data source. The same applies to XYZ's account.
- If Charlie leaves the agency and loses access to the Facebook Ads account, the connections will stop working. A Databox account admin with access to these data sources can reauthenticate the connection to restore functionality.
Action Needed: Google Sheets & Excel (via Google Drive)
The current Google Sheets and Excel (via Google Drive) data source connections cannot be migrated into the new system as is. Users will need to reconnect all their matching data sources by September 1st. Failing to do so will result in data sync interruption.
If users have multiple data sources accessible through the same credentials, they can select the same connection while reconnecting each data source.
Example:
- Steve has three Google Sheets (Income, Expenses, Totals) connected via steve@acme.com.
- He reconnects the Income file first, updating the connection.
- When reconnecting Expenses and Totals, Steve can select the same connection used for the Income file, ensuring all three data sources share the same connection.
Migrations
Starting on release day, all data sources will be migrated to the new model in batches. The migration will create connections for the existing data source connections, merging data sources into unique connections whenever possible.
The migration order will be:
- Google Sheets and Excel (via Google Drive) integrations
- All non-shareable integrations
- Remaining integrations
As a result, it may take a few days for all connections to become available in a given Databox account.
Terminology Changes
Databox will update its terminology:
- Connection: Refers to the authentication information used to connect to an integration.
- Data Source: Refers to the resource being accessed from the integration.
The term "data source connection" will no longer be used in products, public communications, or documentation.
Will this change impact pricing?
No, there will be no impact on pricing. Users will continue to be charged based on the number of data sources in their account, not based on connections or connected integrations.