Skip to content

Commit d80708f

Browse files
spencerattickmarkzegarelli
andauthored
Describe latency with data appearing in Google Analytics (#4086)
* Update index.md * Update src/connections/destinations/catalog/actions-google-analytics-4/index.md Co-authored-by: markzegarelli <[email protected]>
1 parent c0143ba commit d80708f

File tree

1 file changed

+4
-0
lines changed
  • src/connections/destinations/catalog/actions-google-analytics-4

1 file changed

+4
-0
lines changed

src/connections/destinations/catalog/actions-google-analytics-4/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -147,3 +147,7 @@ Google recommends use of their Firebase SDKs to send mobile data to Google Analy
147147
### Reserved Names
148148

149149
Google reserves certain event names, parameters, and user properties. Google silently drops any events that include [these reserved names](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference?client_type=gtag#reserved_names){:target="_blank"}. If you notice that your data isn't appearing in Google, please check that you're not using a reserved name.
150+
151+
### Data taking a long time to appear in Google's reports
152+
153+
Google may take [24-48 hours](https://support.google.com/analytics/answer/9333790) to process data sent to Google Analytics. As a result, the Google Analytics user interface may not reflect the most current data. The Google Analytics [Realtime report](https://support.google.com/analytics/answer/9271392){:target="_blank"} displays activity on your site as it happens.

0 commit comments

Comments
 (0)