Troubleshooting

AI-generated Key Takeaways

outlined_flag

• Common implementation errors can cause events to not show up in Google Analytics.

• Ensure the api_secret is correct, valid, and copied accurately for the right stream.

• Do not use advertising_id; instead, use app_instance_id for Firebase or client_id for gtag.js.

• Use the correct firebase_app_id and app_instance_id when using the Google Analytics for Firebase SDK, and the correct measurement_id and client_id when using gtag.js.

• Server-side tagging events missing may be because events are being sent to a container instead of directly to the Measurement Protocol endpoint.

This guide outlines common troubleshooting steps to fix common implementation errors.

No events

If your events aren't showing up in Google Analytics, there are a few common issues you should look for.

First choose your client:

• Are you using the correct api_secret?

  Check that you're using the api_secret for the right stream. If you set up the measurement protocol for multiple streams, each stream will have its own secret.

• Is your api_secret still valid?

  In order to help combat spam, you're able to revoke api_secrets. Make sure that the api_secret you are using is still valid. It's possible that another user with access to your stream may have revoked access to it by mistake.

• Is your api_secret copied correctly?

  api_secret is case-sensitive. Double check that the api_secret in the Google Analytics UI is exactly the same as the one you're using in your code.

• Don't use advertising_id.

  advertising_id is not supported as a valid device identifier. Use app_instance_id if you're using Firebase and client_id if you're using gtag.js.

• Are you using the correct firebase_app_id?

  Make sure you're using the identifier for a Firebase app. This value is found in the Firebase console under: Project Settings > General > Your Apps > App ID.

  firebase_app_id is different from app_instance_id.

• Are you using the correct app_instance_id?

  Make sure you're using the identifier that's specific to an installation of a Firebase app. This value needs to be retrieved through the Google Analytics for Firebase SDK.

  • Android - getAppInstanceId()
  • Kotlin - getAppInstanceId()
  • Swift - appInstanceID()
  • Objective-C - appInstanceID
  • C++ - GetAnalyticsInstanceId()
  • Unity - GetAnalyticsInstanceIdAsync()

  app_instance_id is different from firebase_app_id.

Invalid IDs

Since the Measurement Procotol supports IDs from the Google Analytics for Firebase SDK and gtag.js, make sure you use the right ID. The IDs you should use changes depending on whether you are using the Google Analytics for Firebase SDK or gtag.js. The following outlines which IDs you should be using:

Google Analytics for Firebase SDK

If you're using the Google Analytics for Firebase SDK the IDs you should use are:

• firebase_app_id - Include this ID in the query parameters for the request. This ID uniquely identifies your Firebase App. All users of your app will have the same firebase_app_id. Found in the Firebase console under:
  Project Settings > General > Your Apps > App ID

• app_instance_id - Include this ID in the POST body for the request. This ID uniquely identifies a given installation of a Firebase App. This value will be different for every installation of your app. The methods to request this value for each Firebase platform are as follows:

  • Android - getAppInstanceId()
  • Kotlin - getAppInstanceId()
  • Swift - appInstanceID()
  • Objective-C - appInstanceID
  • C++ - GetAnalyticsInstanceId()
  • Unity - GetAnalyticsInstanceIdAsync()

You should not use the following:

• firebase_instance_id - This ID should not be included in your request. This ID is used for identifiying a given instance of the app, but is Firebase specific. It's used for tasks such as FCM messages.

gtag.js

If you're using gtag.js, the IDs you should use are:

• measurement_id - Include this ID in the query parameters for the request. This ID uniquely identifies a Data Stream. All users of your website will have the same measurement_id. Found in the Google Analytics UI under:
  Admin > Data Streams > choose your stream > Measurement ID
• client_id - Include this ID in the POST body for the request. This ID uniquely identifies a given user instance of a web client. This value will be different for every user of your app. See these examples for how to retrieve this value.

Server-side tagging events missing

A Server-side Tag Manager installation with a Measurement Protocol client lets you send events in the Measurement Protocol format to a container. The container then sends those events to Google Analytics using the same mechanism as all other SGTM events.

If you want all the features of the Measurement Protocol, send events directly to the Measurement Protocol instead of your container.