> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/commerce-data-models/chords-methodology-as-compared-to-other-platforms/google-analytics-4.md).

# Google Analytics 4

## Google Analytics 4

## Overview

Google Analytics offers an excellent version of attribution, but it doesn’t let you combine attribution with other insights that non-tracked data can deliver. For example, e-commerce merchants might want to compare attribution channels for specific products or for certain user segments.

## Variations between Chord data models and the Google Analytics 4 platform

### Timezones

Chord provides various timezones for timestamp fields so you can customize them to your timezone. Chord's default timezone is UTC and provides the following additional timezone options: Pacific, Mountain, Central, and Eastern.

In Google Analytics 4 (GA4), the timezone can be configured in settings, so you can check the timezone of your account to then use the same timezone within Chord.

### Bounce rate calculations

Chord's definition of a bounce is **any single-page session**. On the GA4 platform, a bounce is defined as\*\* any session that was not engaged\*\*\*,\* which means that the bounce rate is now also susceptible to what is also configured as a [key event](https://support.google.com/analytics/answer/9355848?sjid=11469173535203784940-NA) in GA4.

**For example:** If there are single-page sessions with a particular event (such as `order_completed`) and if the same event was also configured as a "key event" via GA4, it will not be counted as a bounce in GA4.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/model-your-data/commerce-data-models/chords-methodology-as-compared-to-other-platforms/google-analytics-4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.