Creating the data source
Instructions
To add Google Analytics as a data source on Kondado platform, follow the steps below:
- On the Kondado platform, go to the add new sources page and select the GA4 data source
- Click AUTHORIZE
- Select the account you will use
- On the next screen, check ALL permissions that are required and click Continue
- You will be redirected to Kondado and all you have to do is give your data source a name and click on SAVE
Pipelines
Summary
- Channel Performance Monthly
- Custom report (core)
- Device & Region Performance
- Device Performance
- E-commerce Revenue Daily
- Events Tracking Daily
- Geographic Performance Daily
- Geographic Performance Monthly
- Landing Page Analysis
- Page Content Analysis
- Product Category Monthly
- Product Performance
- Traffic Acquisition Daily
Relationship chart
Click to expand
Custom report (core)
The GA Custom Report pipeline allows you to have full control over the format of your pipeline data:
First, the Property (GA4) to which the report will refer must be chosen. This choice is necessary because our report has the ability to allow you to select custom metrics and dimensions from your account, the same reason why it is not possible to get data from multiple accounts in the same pipeline.
Once the Property parameter is selected, you must select the metrics and dimensions. Dimensions can be understood as details of information. For example, date is one dimension and page is another. So, if you select these dimensions (date and page) you will get detailed information by page and date – "on this day, on this page we have X". Every report must have at least one dimension.
Metrics are the information that is given about the dimensions. So, going back to the previous example, on a given day, for a given page, you might want to get, for example, the number of users and the number of sessions – those are the metrics. Metrics are not mandatory for the report, it is possible to create pipelines with dimensions only.
Some dimensions can make your pipeline incremental or integral. If your pipeline is incremental, you will also need to choose the initial savepoint and an update window. The dimensions that make a pipeline incremental are date, dateHour, and dateHourMinute.
The savepoint defines the initial reading date. After a first read, the savepoint is updated to today's date. In this way, the data from the past (from the savepoint to today) will remain in your destination and in the next execution of your pipeline, only new and updated data will be fetched – avoiding re-reading.
The Update Window is a parameter that defines the updating of historical data. Depending on your metric's attribution model, data from a few days ago may change. For example, if a user sees a given page 1 week ago and just performs an action (goal/goal) today, the goal completion record can be assigned to a date one week ago – changing the past. The Update Window parameter solves this by always running a read a few days before the current savepoint.
The table that will be created in your database will be defined by the combination of metrics and dimensions you choose.
To learn which metrics and dimensions to use, use our dimensions and metrics reference.
Once all your parameters are configured, just click on NEXT to continue creating your pipeline.
Replication type: Full
Parameters:
- Property: Select which property to use
- Update window (days): How many days previous to the savepoint the data will be updated
- Read start date (Savepoint): Data replication initial date
- Metrics: Select which metrics to include on the pipeline. More on: kondado.com.br/wiki
- Dimensions: Select the report dimensions. More on: kondado.com.br/wiki
Replication type: Full
Parameters:
- Property: Select which property to use
- Update window (days): How many days previous to the savepoint the data will be updated
- Read start date (Savepoint): Data replication initial date
- Metrics: Select which metrics to include on the pipeline. More on: kondado.com.br/wiki
- Dimensions: Select the report dimensions. More on: kondado.com.br/wiki
Traffic Acquisition Daily
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 daily traffic acquisition report. Includes date, source/medium, and campaign dimensions with sessions, users, bounce rate, and engagement metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
text |
[en] The marketing campaign name for a session. Includes Google Ads Campaigns, Manual Campaigns, & other Campaigns. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The number of users who interacted with your site or launched your app for the first time (event triggered: first_open or first_visit). |
|
|
float |
[en] The percentage of sessions that were not engaged ((Sessions Minus Engaged sessions) divided by Sessions). This metric is returned as a fraction; for example, 0.2761 means 27.61% of sessions were bounces. |
|
|
int |
[en] The number of sessions that lasted longer than 10 seconds, or had a key event, or had 2 or more screen views. |
|
|
float |
[en] The average duration (in seconds) of users` sessions. |
Channel Performance Monthly
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 monthly channel performance report. Includes year/month, source/medium, campaign, and channel group dimensions with sessions, users, transactions, and revenue metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The combined values of year and month. Example values include 202212 or 202301. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
text |
[en] The marketing campaign name for a session. Includes Google Ads Campaigns, Manual Campaigns, & other Campaigns. |
|
|
text |
[en] The session's default channel group is based primarily on source and medium. An enumeration which includes `Direct`, `Organic Search`, `Paid Social`, `Organic Social`, `Email`, `Affiliates`, `Referral`, `Paid Search`, `Video`, and `Display`. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The number of users that logged purchase events for the time period selected. |
|
|
int |
[en] The count of transaction events with purchase revenue. Transaction events are in_app_purchase, ecommerce_purchase, purchase, app_store_subscription_renew, app_store_subscription_convert, and refund. |
|
|
float |
[en] The sum of revenue from purchases, subscriptions, and advertising (Purchase revenue plus Subscription revenue plus Ad revenue) minus refunded transaction revenue. |
|
|
int |
[en] The number of times users added items to their shopping carts. |
|
|
int |
[en] The number of times users completed a purchase. This metric counts `purchase` events; this metric does not count `in_app_purchase` and subscription events. |
Device & Region Performance
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 device and region performance report. Includes date, device, region, and channel dimensions with sessions, users, engagement, transactions, and revenue metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The type of device: Desktop, Tablet, or Mobile. |
|
|
text |
[en] The geographic region from which the user activity originated, derived from their IP address. |
|
|
text |
[en] The session's default channel group is based primarily on source and medium. An enumeration which includes `Direct`, `Organic Search`, `Paid Social`, `Organic Social`, `Email`, `Affiliates`, `Referral`, `Paid Search`, `Video`, and `Display`. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The number of users who interacted with your site or launched your app for the first time (event triggered: first_open or first_visit). |
|
|
int |
[en] The number of sessions that lasted longer than 10 seconds, or had a key event, or had 2 or more screen views. |
|
|
int |
[en] The count of transaction events with purchase revenue. Transaction events are in_app_purchase, ecommerce_purchase, purchase, app_store_subscription_renew, app_store_subscription_convert, and refund. |
|
|
float |
[en] The sum of revenue from purchases minus refunded transaction revenue made in your app or site. Purchase revenue sums the revenue for these events: `purchase`, `ecommerce_purchase`, `in_app_purchase`, `app_store_subscription_convert`, and `app_store_subscription_renew`. Purchase revenue is specified by the `value` parameter in tagging. |
Device Performance
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 device performance report. Includes date, device category, and source/medium dimensions with sessions, users, transactions, revenue, and bounce rate metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The type of device: Desktop, Tablet, or Mobile. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The count of transaction events with purchase revenue. Transaction events are in_app_purchase, ecommerce_purchase, purchase, app_store_subscription_renew, app_store_subscription_convert, and refund. |
|
|
float |
[en] The sum of revenue from purchases, subscriptions, and advertising (Purchase revenue plus Subscription revenue plus Ad revenue) minus refunded transaction revenue. |
|
|
float |
[en] The percentage of sessions that were not engaged ((Sessions Minus Engaged sessions) divided by Sessions). This metric is returned as a fraction; for example, 0.2761 means 27.61% of sessions were bounces. |
E-commerce Revenue Daily
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 daily e-commerce revenue report. Includes date, source/medium, and campaign dimensions with sessions, users, transactions, and revenue metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
text |
[en] The marketing campaign name for a session. Includes Google Ads Campaigns, Manual Campaigns, & other Campaigns. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The count of transaction events with purchase revenue. Transaction events are in_app_purchase, ecommerce_purchase, purchase, app_store_subscription_renew, app_store_subscription_convert, and refund. |
|
|
float |
[en] The sum of revenue from purchases, subscriptions, and advertising (Purchase revenue plus Subscription revenue plus Ad revenue) minus refunded transaction revenue. |
|
|
float |
[en] The sum of revenue from purchases minus refunded transaction revenue made in your app or site. Purchase revenue sums the revenue for these events: `purchase`, `ecommerce_purchase`, `in_app_purchase`, `app_store_subscription_convert`, and `app_store_subscription_renew`. Purchase revenue is specified by the `value` parameter in tagging. |
Events Tracking Daily
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 daily events tracking report. Includes date and event name dimensions with event count, value, users, and conversions metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The name of the event. |
|
|
int |
[en] The count of events. |
|
|
float |
[en] The sum of the event parameter named `value`. |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The count of conversion events. Events are marked as conversions at collection time; changes to an event's conversion marking apply going forward. |
Geographic Performance Daily
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 daily geographic performance report. Includes date, region, source/medium, and campaign dimensions with sessions, users, transactions, and revenue metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The geographic region from which the user activity originated, derived from their IP address. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
text |
[en] The marketing campaign name for a session. Includes Google Ads Campaigns, Manual Campaigns, & other Campaigns. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The count of transaction events with purchase revenue. Transaction events are in_app_purchase, ecommerce_purchase, purchase, app_store_subscription_renew, app_store_subscription_convert, and refund. |
|
|
float |
[en] The sum of revenue from purchases, subscriptions, and advertising (Purchase revenue plus Subscription revenue plus Ad revenue) minus refunded transaction revenue. |
Geographic Performance Monthly
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 monthly geographic performance report. Includes year/month, country, and region dimensions with users, new users, transactions, and revenue metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The combined values of year and month. Example values include 202212 or 202301. |
|
|
text |
[en] The country from which the user activity originated. |
|
|
text |
[en] The geographic region from which the user activity originated, derived from their IP address. |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The number of users who interacted with your site or launched your app for the first time (event triggered: first_open or first_visit). |
|
|
int |
[en] The count of transaction events with purchase revenue. Transaction events are in_app_purchase, ecommerce_purchase, purchase, app_store_subscription_renew, app_store_subscription_convert, and refund. |
|
|
float |
[en] The sum of revenue from purchases, subscriptions, and advertising (Purchase revenue plus Subscription revenue plus Ad revenue) minus refunded transaction revenue. |
Landing Page Analysis
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 landing page analysis report. Includes date, landing page, source/medium, and campaign dimensions with sessions, users, bounce rate, and engagement metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The page path + query string associated with the first pageview in a session. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
text |
[en] The marketing campaign name for a session. Includes Google Ads Campaigns, Manual Campaigns, & other Campaigns. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
float |
[en] The percentage of sessions that were not engaged ((Sessions Minus Engaged sessions) divided by Sessions). This metric is returned as a fraction; for example, 0.2761 means 27.61% of sessions were bounces. |
|
|
int |
[en] The number of sessions that lasted longer than 10 seconds, or had a key event, or had 2 or more screen views. |
|
|
float |
[en] The average duration (in seconds) of users` sessions. |
Page Content Analysis
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 page content analysis report. Includes date, page path, source/medium, and campaign dimensions with page views, users, and engaged sessions metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The portion of the URL between the hostname and query string for web pages visited; for example, the pagePath portion of `https://www.example.com/store/contact-us?query_string=true` is `/store/contact-us`. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
text |
[en] The marketing campaign name for a session. Includes Google Ads Campaigns, Manual Campaigns, & other Campaigns. |
|
|
int |
[en] The number of app screens or web pages your users viewed. Repeated views of a single page or screen are counted. (screen_view + page_view events). |
|
|
int |
[en] The number of distinct users who have logged at least one event, regardless of whether the site or app was in use when that event was logged. |
|
|
int |
[en] The number of sessions that lasted longer than 10 seconds, or had a key event, or had 2 or more screen views. |
Product Category Monthly
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 monthly product category report. Includes year/month, item category, name, and ID dimensions with revenue, purchases, views, and sessions metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The combined values of year and month. Example values include 202212 or 202301. |
|
|
text |
[en] The hierarchical category in which the item is classified. For example, in Apparel/Mens/Summer/Shirts/T-shirts, Apparel is the item category. |
|
|
text |
[en] The name of the item. |
|
|
text |
[en] The ID of the item. |
|
|
float |
[en] The total revenue from purchases minus refunded transaction revenue from items only. Item revenue is the product of its price and quantity. Item revenue excludes tax and shipping values; tax & shipping values are specified at the event and not item level. |
|
|
int |
[en] The number of units for a single item included in purchase events. This metric counts the quantity of items in purchase events. |
|
|
int |
[en] The number of units viewed for a single item. This metric counts the quantity of items in `view_item` events. |
|
|
int |
[en] The number of units added to cart for a single item. This metric counts the quantity of items in `add_to_cart` events. |
|
|
int |
[en] The number of sessions that began on your site or app (event triggered: session_start). |
Product Performance
Replication type: Full
Parameters:
- Update Window (days): How many days before the savepoint the data will be updated
- Read start date (Savepoint): Select the initial data extraction date
- Property: Select the GA4 property
- Period: Select the data extraction period
Pre-configured GA4 product performance report. Includes date, item name, and source/medium dimensions with revenue, purchases, views, and add-to-cart metrics.
| Campo | Tipo | |
|---|---|---|
|
date |
[en] The date of the event, formatted as YYYYMMDD. |
|
|
text |
[en] The name of the item. |
|
|
text |
[en] The combined values of the dimensions `sessionSource` and `sessionMedium`. |
|
|
float |
[en] The total revenue from purchases minus refunded transaction revenue from items only. Item revenue is the product of its price and quantity. Item revenue excludes tax and shipping values; tax & shipping values are specified at the event and not item level. |
|
|
int |
[en] The number of units for a single item included in purchase events. This metric counts the quantity of items in purchase events. |
|
|
int |
[en] The number of units viewed for a single item. This metric counts the quantity of items in `view_item` events. |
|
|
int |
[en] The number of units added to cart for a single item. This metric counts the quantity of items in `add_to_cart` events. |
Notes
Important Notes
- Our dimensions and metrics reference is prepared based on the GA4 documentation, and may have variations during its implementation in the pipelines
- While creating or editing pipelines, after selection, the list of possible options will be updated to reflect the combinations that can or cannot be performed based on the unsupported fields. Despite this functionality, there can still be false positives, where the documentation indicates that fields are supported when they are not. That way, you can also use this Google tool to check compatibility – however, even this tool can generate false positives, so the only way to know 100%% if the fields are compatible is to actually create the pipeline
- Metrics that count distinct values (for example, "distinct users") behave differently if you use a "day" dimension versus a "month" dimension. For example, let's say the same user visits your page for an entire month. In a pipeline that sees distinct users per day, you will get a value of 1 per row. Adding this value to get the number of unique users in that month would result in a value of 30 – which is wrong, as in that month it was the same unique user who accessed your page every day. In this case, the right thing would be to use the unique user's metric with the month dimension
- In order for data to be reported for events and custom parameters sent (for example event=purchase and parameter=purchase_value) it is necessary that there are custom dimensions and metrics created in the property
- Segments are not supported
- The quotas applied by the API limit the number of calls per hour and per day, which can make reading data slower in pipelines
- When creating pipelines, if the quota is consumed, custom fields will not be returned
- Due to API limitations, a maximum of 10 metrics and 9 dimensions can be selected per pipeline
- Due to API limitations, metrics that contain special characters cannot be selected
- Part of this documentation was automatically generated by AI and may contain errors. We recommend verifying critical information
- Part of this documentation was automatically generated by AI and may contain errors. We recommend verifying critical information