This article refers to an outdated version of the Tag Rocket Reports. We have since upgraded our system to provide more reliable, unified reporting. To learn more about it, and how to configure, go to our Tag Rocket Reports page.
We’ve developed several reports which work with the data created by the Tag Rocket app for BigCommerce. Before you can use the report, you will need to have installed Tag Rocket and Set up Google Analytics 4 in the app. Then we need to create a data source that points to your GA4 property.
Creating the Data Source
| Data Source | Changes |
|---|---|
| v2.2 | Added Save Data, Screen Width/Height and updated to deal with the latest GA4 parameters |
| v2.1 | Added Support for LCP |
| v2.0 | Reworked how the data source works so that we can write more varied reports. |
| v1.5 | Major restructure on how Core Web Vitals is gathered and reported on to bring it in line with Google’s standard practices. Reduced the number of dimensions and metrics to manage. Report improvements. |
| v1.4 | Changed ‘Largest Shift’ to ‘Debug Target’, which now identifies key elements for LCP, FID and CLS. |
| v1.3 | Fix where some fields would change to percent |
| v1.3 | Initial public version |
The reports are built using Google Data Studio. The first thing you need to do is create a special Data Source that can be used to connect your own store’s data with the report.
At the moment, the standard Data Source for GA4 is not usable. It randomly messes up the custom definitions. We have worked out the following steps to create a special Data Source that can be used in our reports. Hopefully, GA4/Data Studio fix this in the near future.
- Copy the latest Data Source Template version from the table above by opening the template and clicking on the copy icon and the copy button
- Select your GA4 account from the connection options, then click the ‘Reconnect’ button. The new data source is now based on your property. A popup will appear, indicating lots of issues. Ignore them and click ‘Apply’
- Rename it (top left) to include your store’s name. That way, you know which store and which version of the data source you are looking at. e.g. ‘Tag Rocket GA4 – My Store – vX.Y’
- Sometimes Data Studio duplicates some of the inbuilt fields with only one of the copies working. If you see any invalid formula warnings, then it is probably the case. Check through all the fields and add a ‘ 2’ after the make of duplicates. This will then let you try each duplicate in any failing formula.
- You now need to fix all the custom definition based fields, so the data source works. Check every field starting with an @ (indicates it uses custom definitions) and make sure all formulas match the formulas in the custom definitions fields table at the end of this guide. If the formula fails, then you may have to try the other duplicate for the referenced field.
Reports will have errors or be inaccurate if the functions on those fields are incorrect.

Your data source is now ready to use to power new reports.
Creating the Reports
| Report | Description |
|---|---|
| Website Errors (v2.0) | The Tag Rocket GA4 tag tracks page errors, including JavaScript, Console, Network, JSON-LD and missing page errors. Some of these may be causing a bad user experience. |
| Core Web Vitals (v2.6) | Provides details of your user’s page experience based on Google’s Core Web Vitals. Note that using the above data source for the report is less accurate than an implementation using BigQuery. |
| Title Tracking (v3.1) | This report helps you track changes in your title tags and the effect they had on visibility in Google Search. You will need to also make a Title Tracking – Search Console data source (URL->web) for this report. |
| Monetisation (v2.3) | This report shows user flow through the checkout process as well as helps you identify missing or duplicate transactions. |
- Click on a report link to see the report
- Click the menu (ellipsis icon), then “Make A Copy”
- Select the data source you have previously created
- Click ‘Copy Report’
- Rename the new report (top left) to include your store name. e.g. ‘GA4 Tag Rocket Report – My Store – vX.Y’
You should now have a working report based on your own GA4 property. If you have only just published your GA4 tag in Tag Rocket, you will have to wait a day or two before you start seeing data.
Data Source Updates
Your data source can be re-used in new updates of the reports. However, some report updates may require the addition of new fields. This table lists all the custom fields, their values, and what version of the data source they were last changed/added in. When adding the field, enter the name id and formula (you can’t change the id once you have saved it). Afterwards, you can change the type or aggregation if required (bold).
Pre v2.0 data sources are not usable for these reports. You would need to create a new data source.
If you do decide to create a data source from scratch, you will have to add all the following fields. In some cases, fields refer to other fields which have to be added before them.
The following # fields directly relate to core GA4 properties. They are required but do not need checking to see if their formula is correct after a copy.
| Last Change | Field Name | Field ID | Formula (fx) | Type | Default Aggregation |
|---|---|---|---|---|---|
| v2.2 | #Screen Width | fx_screen_width | CAST(REGEXP_EXTRACT(Screen resolution,'([0-9]*)x[0-9]*’) AS NUMBER) | Numeric.Number | |
| v2.2 | #Screen Height | fx_screen_height | CAST(REGEXP_EXTRACT(Screen resolution,'[0-9]*x([0-9]*)’) AS NUMBER) | Numeric.Number | |
| v2.0 | #Browser | fx_browser | Browser | Text | None |
| v2.0 | #Continent | fx_continent | 'Unknown' | Text | None |
| v2.0 | #Country | fx_country | Country | Country | None |
| v2.0 | #Date | fx_date | Date | Date | None |
| v2.0 | #Device | fx_device | Device | Text | None |
| v2.0 | #Device category | fx_device_category | Device category | Text | None |
| v2.0 | #Event count | fx_event_count | Event count | Numeric.Number | Auto |
| v2.0 | #Event name | fx_event_name | Event name | Text | None |
| v2.0 | #Event revenue | fx_event_revenue | Event revenue | Numeric.Number | Auto |
| v2.0 | #Event value | fx_event_value | Event value | Numeric.Number | Auto |
| v2.0 | #Operating system | fx_operating_system | Operating system | Text | None |
| v2.0 | #Operating system with version | fx_operating_system_with_version | Operating system with version | Text | None |
| v2.0 | #OS version | fx_os_version | OS version | Text | None |
| v2.0 | #Page path and query string | fx_page_path_query | Page path + query string | Text | None |
| v2.0 | #Page title | fx_page_title | Page title | Text | None |
| v2.0 | #Purchase revenue | fx_purchase_revenue | Purchase revenue | Numeric.Number | Auto |
| v2.0 | #Region | fx_region | Region | Region | None |
| v2.0 | #Session Engagement | fx_session_engagement | 'Not supported' | Text | None |
| v2.0 | #Session medium | fx_session_medium | Session medium | Text | None |
| v2.0 | #Session source | fx_session_source | Session source | Text | None |
| v2.0 | #Sessions | fx_sessions | Sessions | Numeric.Number | Auto |
| v2.0 | #Total users | fx_total_users | Total users | Numeric.Number | Auto |
| v2.0 | #Transactions | fx_transactions | Transactions | Numeric.Number | Auto |
| v2.0 | #Views | fx_views | Views | Numeric.Number | Auto |
The @ fields relate to GA custom definitions, and they do need checking to make sure they have the correct formula after a copy.
| Last Change | Field Name | Field ID | Formula (fx) | Type | Default Aggregation |
|---|---|---|---|---|---|
| v2.2 | @Save Data | fx_save_data | Save Data _ Tag Rocket | ||
| v2.1 | @Web Vitals value | fx_metric_value | Average Web Vitals value _ Tag Rocket / if(#Event name='LCP' | Numeric.Number | Average |
| v2.0 | @Customer group | fx_customer_group_name | customer_group_name | Text | None |
| v2.0 | @Customer ID | fx_customer_id | customer_id | Numeric.Number | None |
| v2.0 | @Date and time | fx_datetime | PARSE_DATETIME("%Y-%m-%dT%H:%M:%E*S",Date and time _ Tag Rocket) | Date & Time | None |
| v2.0 | @Debug target | fx_debug_target | Debug target _ Tag Rocket | Text | None |
| v2.0 | @Effective connection type | fx_effective_connection_type | Effective connection type _ Tag Rocket | Text | None |
| v2.0 | @Error column number | fx_error_colno | Error column number _ Tag Rocket | Text | None |
| v2.0 | @Error filename | fx_error_filename | Error filename _ Tag Rocket | URL.URL | None |
| v2.0 | @Error line number | fx_error_lineno | Error line number _ Tag Rocket | Text | None |
| v2.0 | @Error message | fx_error_message | Error message _ Tag Rocket | Text | None |
| v2.0 | @Error type | fx_error_type | Error type _ Tag Rocket | Text | None |
| v2.0 | @Meta description | fx_meta_description | Meta description _ Tag Rocket | Text | None |
| v2.0 | @Page type | fx_page_type | Page type _ Tag Rocket | ||
| v2.0 | @Missing Page | fx_missing_page | @Page type = '404' | Numeric.Boolean | None |
| v2.0 | @Order status | fx_order_status | Order status _ Tag Rocket | Text | None |
| v2.2 | @Page location | fx_page_location | CONCAT(‘https://’,Full page URL) | URL.URL | None |
| v2.0 | @Page referrer | fx_page_referrer | Page referrer _ Tag Rocket | URL.URL | None |
| v2.0 | @Transaction ID | fx_transaction_id | Transaction ID | Text | None |
| v2.0 | @User currency | fx_user_currency_code | user_currency_code | Text | None |
| v2.0 | @Web Vitals distribution | fx_metric_distribution | | Text | None |
| v2.0 | @Web Vitals status | fx_metric_status | Web Vitals status _ Tag Rocket | Text | None |