If there are issues with the data you’ve collected through the Google tag, Measurement Protocol, or data import sources, diagnostic alerts can appear across the areas you perform the data import, either the Data streams and Data import pages in Google Analytics. Learn more about purchase events.
On this page
Diagnostics in Data streams
- In Admin, under "Data collection and modification", click Data streams.
Note: The previous link opens to the last Analytics property you accessed. You must be signed in to a Google Account to open the property. You can change the property using the property selector. You must be an Editor or above to take specific action to resolve the issues shown in the diagnostic alerts.
- In the “Data streams” overview page, a badge will appear to reflect the diagnostic status of the data stream. Select the data stream you want to check.
- Go to the Diagnostics tab to view the diagnostics alert for your data stream.
- Click the call-to-action link of the diagnostic alert you want to resolve.
Diagnostics in Data import
- In Admin, under "Data collection and modification", click Data import.
Note: The previous link opens to the last Analytics property you accessed. You must be signed in to a Google Account to open the property. You can change the property using the property selector. You must be an Editor or above to take specific action to resolve the issues shown in the diagnostic alerts.
- In the “Data import” overview page, a badge will appear to reflect the diagnostic status of a data source. Click the arrow icon of the data source you want to check.
- View the diagnostics alert of your selected data source in the “Connection quality” section.
- Click the call-to-action link of the diagnostic alert you want to resolve.
Diagnostic statuses
The following diagnostic statuses appear in the “Data streams” and “Data import” pages in Google Analytics to highlight detected issues, their severity, and how to fix them. When you fix an issue, the status updates to show the improved data quality.
No issues detected
This diagnostic status means that no issues have been detected with the data collected for your data stream, or with the data import source. However, be sure to continue to check the diagnostic status as it might change when new issues are detected.
Excellent
An Excellent status means that no issues have been detected with the data collected for your data stream, or with the data import source. You won’t experience any issues for this data quality status.
Needs attention
Needs attention means there's an issue with some of the data collected, either from your data stream or data import source, that is affecting measurement and requires your attention. This issue should be fixed, but it isn't critical.
Urgent
An Urgent status indicates a critical issue with some of the data collected, either from your data stream or data import source, that requires immediate attention to maintain accurate measurement. To resolve an urgent issue, ensure that your setup is correctly configured.
Diagnostic alerts
We may show you one or more of the following diagnostic alerts to help you identify issues with your connection setup:
Data import
| Diagnostic | Description |
|---|---|
| Some web purchase events from the latest run aren't importing | This diagnostic indicates that the data import source you're using had some errors during the latest run and web purchase events aren’t imported. Resolve the latest run errors to ensure data is imported correctly. |
| Source for <data-source> not found | This diagnostic means that the specified data source can't be found. To fix this issue, make sure the data source exists and the credentials are valid. You should also ensure that the permission to read the data is granted. Learn how to Import events. |
| Invalid <data-source> credentials | This diagnostic indicates that the credentials you entered are invalid or do not have permission to read the data. To connect to the specified data source, ensure that the credentials are valid and grant permission to read the data. |
| Invalid <data-source> format | This diagnostic means that the specified data source does not match the required specific data format. In order for the data to be processed, reformat your data according to the requirements. |
| Transaction ID overlap rate was less than 10% for the past 2 days |
This diagnostic means that transaction IDs may be missing from some Google tag or data import events, or they’re not formatted correctly in either tag or additional data sources. Transaction IDs are used to match tag and data sources to report accurate conversions. Ensure transaction IDs are shared and consistent across your tag and data source. Additionally, make sure that transaction IDs are unique to each web purchase and are sent for every tag event. Learn how to Set up a purchase event and improve its measurement. |
Google tag
| Diagnostic | Description |
|---|---|
| Purchase events collected by your Google tag are missing transaction ID | This diagnostic indicates that your Google tag is sending data, but the transaction ID is missing or invalid. To fix this, ensure that you’re sending transaction IDs with your purchase events. |
| Google tag isn't sending purchase event data | This diagnostic means your Google tag hasn't sent any purchase event data for the past 48 hours. Use Tag Assistant to ensure your Google tag is correctly installed on your website and that it fires when users complete a purchase. |
Measurement Protocol
| Diagnostic | Description |
|---|---|
| Measurement Protocol has stopped sending web purchase event data | This diagnostic indicates that Measurement Protocol hasn't sent any web purchase event data for the past 48 hours. Learn how to Send Measurement Protocol events to Google Analytics. |
| Web purchase events collected by Measurement Protocol are missing transaction ID | This diagnostic means that Measurement Protocol is sending data, but the transaction ID is missing or invalid. Ensure that you’re sending transaction IDs with your purchase events. |
| Web purchase events collected by Measurement Protocol are missing user identifiers | This diagnostic indicates that some purchase events sent through Measurement Protocol are being dropped because they are missing user identifiers. Web purchase events must include at least one identifier. Learn more About improving measurement for purchase events. |
| Transaction ID overlap rate was less than 10% for the past 2 days | This diagnostic means that transaction IDs may be missing from some Google tag, or Measurement Protocol events, or they’re not formatted correctly in either tag or additional data sources. Ensure transaction IDs are shared and consistent across your tag and data source. Additionally, make sure that transaction IDs are unique to each web purchase and are sent for every tag event. |
Data stream
| Diagnostic | Description |
|---|---|
| Non-unique transaction IDs found | This diagnostic means that there are transaction IDs being reused across different user identifiers. Each transaction ID must be unique. Ensure your import source and Google tags are using unique transaction ID formatting for accurate reporting. |