Overview of recent changes to the ga add on (ga api v4) - Yasen Lilov | Merkle
•
0 likes•421 views
Overview of the new features and changes of the GA Add-on Plugin for Google sheets, after the migration of using the Core Reporting API (v3) to (v4).
Recommended
More Related Content
What's hot
What's hot (8)
Similar to Overview of recent changes to the ga add on (ga api v4) - Yasen Lilov | Merkle
Similar to Overview of recent changes to the ga add on (ga api v4) - Yasen Lilov | Merkle (20)
Recently uploaded
Recently uploaded (20)
Overview of recent changes to the ga add on (ga api v4) - Yasen Lilov | Merkle
- 1. Government Summit Overview of recent changes to the GA add-on
- 2. Agenda • Analytics Reporting API Overview • Google Analytics Add-on Upgrade • Features
- 3. © 2017 Merkle. All Rights Reserved. Confidential3 What is the GA Analytics Core API? • A set of functions and procedures that allow applications to directly access GA data • Alternative to querying data through the GA interface • Harder to use but far more customizable • Can be used as part of an automated process
- 4. © 2017 Merkle. All Rights Reserved. Confidential4 What is the GA Analytics Core API? • A set of functions and procedures that allow applications to directly access GA data • Alternative to querying data through the GA interface • Harder to use but far more customizable • Can be used as part of an automated process
- 5. © 2017 Merkle. All Rights Reserved. Confidential5 Google Analytics Add-on Upgrade The add-on migrated from using Core Reporting API (v3) to the Analytics Reporting API (v4) New Features • Multiple Segments • Calculated metrics expression • Unlimited* rows in a single report • Better sampling
- 6. © 2017 Merkle. All Rights Reserved. Confidential6 Using the GA Add-on – Create Repots
- 7. © 2017 Merkle. All Rights Reserved. Confidential7 New Feature – Multiple Segments Multiple Segments [Multiple segments in the same report] Segments can be specified as a list of comma or new-line separated: 1. Segment IDs 2. Segment Definitions
- 8. © 2017 Merkle. All Rights Reserved. Confidential8 New Feature – Calculated Metrics Metrics expression [Calculated metrics on the fly] You can now request not only built-in metrics but also combination of metrics expressed in mathematical operations. For example: the expression ga:goal1completions/ga:sessions will request the goal completions per number of sessions.
- 9. © 2017 Merkle. All Rights Reserved. Confidential9 New Feature – Multiple Segments Unlimited rows in a single report The old version of the add-on enforced the v3 API maximum of 10,000 rows per report. The v4 API maximum is 100,000 rows per report. Even better, the add-on now supports even higher limits or unlimited* report sizes (by not setting a value for the Limit parameter)
- 10. © 2017 Merkle. All Rights Reserved. Confidential10 New Feature – Multiple Segments Better sampling [Same sampling rate as GA] GA 360 clients can get higher sampling threshold - up to 100M sessions* Sampling Level: • "Default" (the same as leaving it blank) • "Small“ • "Large“ Use Resource Quotas: • False (same as leaving it black) • True
- 11. © 2017 Merkle. All Rights Reserved. Confidential11 Any Questions?
Editor's Notes
- The primary reason for the upgrade was to migrate the add-on from using the legacy Core Reporting API (v3) to the Analytics Reporting API (v4). NEW FEATURES: Multiple segments You can now get multiple segments in the same report. When more than one segment is specified, the left-most column of the report will show the segment name. Refer to the segments section of the documentation for usage instructions. Unlimited rows in a single report The old version of the add-on enforced the v3 API maximum of 10,000 rows per report. The v4 API maximum is 100,000 rows per report, but to make it easier to work with large reports, the add-on now supports even higher limits or unlimited report sizes by not setting a value for the Limit parameter. Note: for reports with more than 100,000 results, the add-on will make additional requests until the limit is reached or all results are returned. These additional requests will count toward your quota, so be careful when using this feature. These reports will also take longer to run, which in some cases can lead to timeout errors if you have lots of large reports. Lastly, Google Sheets imposes a limit on the number of cells that can be in a single spreadsheet, and this add-on cannot bypass that limit(400,000). Better sampling The Reporting API v4 has the same sampling rates as Google Analytics itself. In addition, Google Analytics 360 (Premium) customers can set the Use Resource Quotas parameter to get much higher sampling thresholds (up to 100 million sessions) where applicable. Calculated metrics expressions The Reporting API v4 supports metric expressions, which can be used to define calculated metrics on the fly, or programmatically using Sheet's functions. Refer to the metrics section of the documentation for usage instructions.
- Metrics expressions are different from the calculated metrics in the GA interface. The repeated metrics parameters can take any of the existing metrics but you can also create a custom calculated metric, by combining existing metrics into a new metrics expression. For that you can use different operators - /, *, +, etc.. Exampes -
- *Google Sheets imposes a limit on the number of cells that can be in a single spreadsheet, and this add-on cannot bypass that limit - 400,000 Note: for reports with more than 100,000 results, the add-on will make additional requests until the limit is reached or all results are returned. These additional requests will count toward the quota. *These reports will also take longer to run, which in some cases can lead to timeout errors if you have lots of large reports.
- The resource based quota system is designed to support a higher threshold of sampling while still protecting the Analytics Reporting infrastructure. Each property will be allocated a set amount of query resource tokens. The API client can add an optional field to the API request to get a higher threshold of sampling in exchange for the relative query resource tokens. A computationally more expensive request will require more tokens.