Data Source (By Request)
A data source is a unique origin from which data originates, such as advertising platforms like Amazon Ads, Apple Search Ads, TikTok Ads, and Salesforce. These four platforms represent different data sources.
How are they counted? They are calculated as the data sources collected through "By Request" and "By Request Premium" pipelines from Ad service to Google BigQuery. Even if a client has five different AdAccounts within Amazon Ads, it still counts as one data source.
Let's explore an example below:
| Pipelines | Data Sources (By Request) count |
|---|---|
Amazon Ads:
|
1 |
Apple Search Ads:
|
1 |
TikTok Ads:
|
1 |
| Total of Consumed Units: | 3 Data Source (By Request) |
Â
Pipeline (By Request)
The 'By Request' or 'By Request Premium' Pipeline automatically collects and processes all the data you need for building reports and gaining insights quickly. It runs periodic jobs, importing and updating historical data into your Data Destination.
What are the 'By Request' and 'By Request Premium' Pipelines?
- The 'By Request' Pipeline is set up by an OWOX manager at the client's request and is available for 'Professional' and 'Enterprise' subscriptions.
- The 'By Request Premium' Pipeline is set up by an OWOX manager at the client's request and is exclusively available for 'Enterprise' subscriptions.
Show a list of available 'By Request' and 'By Request Premium' pipelines
How are they counted?
A number of active data pipelines.
The data pipeline is created by combining a Data Source (By Request) and a Data Destination, each with its own unique Pipeline ID. Some data sources require multiple data pipelines. For example, Google Ads and TikTok Marketing necessitate a separate data pipeline for each Ad Account. Therefore, 1 Ad Account equals 1 active pipeline. A pipeline is considered active and counts as a consumed unit if at least 1 byte of data was transferred through it during the subscription period.
Let's explore an example below:
| Data Source (By Request) | Data Destination | Pipeline ID | Transferred data during the subscription period | Counted as an active pipeline |
|---|---|---|---|---|
| Amazon Ads AdAccount A | GBQ Dataset X | id111 | >1byte | ✅ |
| Amazon Ads AdAccount B | GBQ Dataset Y | id222 | >1byte | ✅ |
| Amazon Ads AdAccount A | GBQ Dataset W | id333 | >1byte | ✅ |
| TikTok AdAccount C | GBQ Dataset X | id444 | >1byte | ✅ |
| Pinterest AdAccount D | GBQ Dataset X | id555 | 0 byte | – |
| Total: | 4 Pipelines (By Request) | |||
Â
Pipeline Historical Month (By Request)
The definition is a one-time import of historical data for a calendar month in the 'By Request' or 'By Request Premium' Pipeline, available for customers on demand.
How are they counted?
Pipeline Historical Month (By Request) represents the count of months with historical data imported to the destination within the unique Pipeline ID beyond the initial start date of this Pipeline. It is considered a consumed unit if at least 1 byte of data was transferred during a period.
The count of Pipeline Historical Month (By Request) is rounded up to the ceiling number if the period of historical import is less than a whole month.
0 Comments