Comprueba que estás usando el api_secret para el flujo correcto. Si configuras Measurement Protocol para varios flujos, cada uno tendrá su propio secreto.
Para ayudar a combatir el spam, puedes revocar los api_secret. Comprueba que el api_secret que estás usando sigue siendo válido. Es posible que otro usuario con acceso al flujo haya revocado el acceso por error.
api_secret distingue entre mayúsculas y minúsculas. Comprueba que el api_secret en la interfaz de Google Analytics es exactamente el mismo que usas en el código.
No uses advertising_id.
advertising_id no es un identificador de dispositivo válido. Utiliza app_instance_id si usas Firebase y client_id si usas gtag.js.
IDs no válidos
Dado que en la función Measurement Protocol se pueden usar los IDs del SDK de Google Analytics for Firebase y de gtag.js, no es fácil saber qué IDs se deben usar. Los IDs que se deben usar cambian en función de si se usa el SDK de Google Analytics for Firebase o gtag.js. A continuación se describen los IDs que se deben usar:
SDK de Google Analytics for Firebase
Si utilizas el SDK de Google Analytics for Firebase, los IDs que debes usar son:
firebase_app_id: incluye este ID en los parámetros de consulta de la solicitud. Este ID identifica de forma única tu aplicación de Firebase. Todos los usuarios de tu aplicación tendrán el mismo firebase_app_id. Se encuentra en la consola de Firebase. Para ello, ve a: Configuración del proyecto > General > Tus aplicaciones > ID de aplicación.
app_instance_id: incluye este ID en el cuerpo de la solicitud POST. Este ID identifica de forma exclusiva una instalación determinada de una aplicación de Firebase. Este valor será distinto en cada instalación de la aplicación. Los métodos para solicitar este valor en cada plataforma de Firebase son los siguientes:
firebase_instance_id: este ID no debe incluirse en la solicitud.
Este ID se usa para identificar una instancia determinada de la aplicación, pero es específico de Firebase. Se usa con tareas como los mensajes de FCM.
gtag.js
Si usas gtag.js, debes usar los IDs siguientes:
measurement_id: incluye este ID en los parámetros de consulta de la solicitud. Este ID identifica de forma exclusiva un flujo de datos. Todos los usuarios de tu sitio web tendrán el mismo measurement_id. Se encuentra en la interfaz de Google Analytics, en: Administrar > Flujos de datos > elige un flujo > ID de medición.
client_id: incluye este ID en el cuerpo de la solicitud POST. Este ID identifica de forma única una instancia de usuario determinada de un cliente web. Este valor será
distinto para cada usuario de la aplicación. Consulta estos ejemplos para saber cómo obtener este valor.
[null,null,["Última actualización: 2024-04-17 (UTC)."],[[["\u003cp\u003eThis guide helps troubleshoot common Google Analytics 4 Measurement Protocol implementation errors, focusing on missing events and invalid user/device IDs.\u003c/p\u003e\n"],["\u003cp\u003eIf events aren't appearing, ensure your \u003ccode\u003eapi_secret\u003c/code\u003e is correct, valid, accurately copied, and you're using the appropriate device identifier (\u003ccode\u003eapp_instance_id\u003c/code\u003e or \u003ccode\u003eclient_id\u003c/code\u003e, not \u003ccode\u003eadvertising_id\u003c/code\u003e).\u003c/p\u003e\n"],["\u003cp\u003eWhen using the Measurement Protocol, select the correct IDs based on whether you're implementing via Firebase or gtag.js, as outlined in the guide.\u003c/p\u003e\n"],["\u003cp\u003eFor Firebase, utilize \u003ccode\u003efirebase_app_id\u003c/code\u003e and \u003ccode\u003eapp_instance_id\u003c/code\u003e, avoiding \u003ccode\u003efirebase_instance_id\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eFor gtag.js, use \u003ccode\u003emeasurement_id\u003c/code\u003e and \u003ccode\u003eclient_id\u003c/code\u003e for proper event tracking.\u003c/p\u003e\n"]]],["To resolve event visibility issues in Google Analytics, verify the correct `api_secret` is used, valid, and copied accurately, and avoid using `advertising_id`. For Firebase, use `firebase_app_id` in query parameters and `app_instance_id` in the POST body; retrieve `app_instance_id` using the appropriate platform's method. For gtag.js, utilize `measurement_id` in query parameters and `client_id` in the POST body. Both `client_id` and `app_instance_id` should differ for each user.\n"],null,["# Troubleshooting\n\nThis guide outlines common troubleshooting steps to fix common implementation\nerrors.\n\nNo events\n---------\n\nIf your events aren't showing up in Google Analytics, there are a few common\nissues you should look for.\n\nFirst choose your client: \nFirebase gtag.js\n\n\u003cbr /\u003e\n\n- Are you using the correct [api_secret](/analytics/devguides/collection/protocol/ga4/reference#api_secret)?\n\n Check that you're using the `api_secret` for the right stream. If you set up\n the measurement protocol for multiple streams, each stream will have its own\n secret.\n- Is your [api_secret](/analytics/devguides/collection/protocol/ga4/reference#api_secret) still valid?\n\n In order to help combat spam, you're able to revoke `api_secret`s. Make sure\n that the `api_secret` you are using is still valid. It's possible that\n another user with access to your stream may have revoked access to it by\n mistake.\n- Is your [api_secret](/analytics/devguides/collection/protocol/ga4/reference#api_secret) copied correctly?\n\n `api_secret` is case-sensitive. Double check that the `api_secret` in the\n Google Analytics UI is *exactly* the same as the one you're using in your\n code.\n- Don't use `advertising_id`.\n\n `advertising_id` is not supported as a valid device identifier. Use\n `app_instance_id` if you're using Firebase and `client_id` if you're using\n gtag.js.\n\nInvalid IDs\n-----------\n\nSince the Measurement Procotol supports IDs from the Google Analytics for\nFirebase SDK and gtag.js, make sure you use the right ID. **The IDs you should\nuse changes depending on whether you are using the Google Analytics for Firebase\nSDK or gtag.js.** The following outlines which IDs you should be using:\n\n**Google Analytics for Firebase SDK**\n\nIf you're using the Google Analytics for Firebase SDK the IDs you *should* use\nare:\n\n- [`firebase_app_id`](/analytics/devguides/collection/protocol/ga4/reference?client_type=firebase#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: \n **Project Settings** \\\u003e **General** \\\u003e **Your Apps** \\\u003e **App ID**\n- [`app_instance_id`](/analytics/devguides/collection/protocol/ga4/reference?client_type=firebase#app_instance_id) - Include this ID in the POST body for the request. This\n ID uniquely identifies a given installation of a Firebase App. This value\n will be different for every installation of your app. The methods to request\n this value for each Firebase platform are as follows:\n\n - [Android - getAppInstanceId()](https://firebase.google.com/docs/reference/android/com/google/firebase/analytics/FirebaseAnalytics#public-taskstring-getappinstanceid)\n - [Kotlin - getAppInstanceId()](https://firebase.google.com/docs/reference/kotlin/com/google/firebase/analytics/FirebaseAnalytics#getappinstanceid)\n - [Swift - appInstanceID()](https://firebase.google.com/docs/reference/swift/firebaseanalytics/api/reference/Classes/Analytics#appinstanceid)\n - [Objective-C - appInstanceID](https://firebase.google.com/docs/reference/ios/firebaseanalytics/api/reference/Classes/FIRAnalytics#+appinstanceid)\n - [C++ - GetAnalyticsInstanceId()](https://firebase.google.com/docs/reference/cpp/namespace/firebase/analytics#getanalyticsinstanceid)\n - [Unity - GetAnalyticsInstanceIdAsync()](https://firebase.google.com/docs/reference/unity/class/firebase/analytics/firebase-analytics#getanalyticsinstanceidasync)\n\nYou should *not* use the following:\n\n- `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.\n\n**gtag.js**\n\nIf you're using gtag.js, the IDs you *should* use are:\n\n- [`measurement_id`](/analytics/devguides/collection/protocol/ga4/reference?client_type=gtag#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: \n **Admin** \\\u003e **Data Streams** \\\u003e **choose your stream** \\\u003e **Measurement ID**\n- [`client_id`](/analytics/devguides/collection/protocol/ga4/reference?client_type=gtag#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](/gtagjs/reference/api#get) for how to retrieve this value.\n\nServer-side tagging events missing\n----------------------------------\n\nA [Server-side Tag Manager installation with a Measurement Protocol\nclient](/tag-platform/tag-manager/server-side/send-data#server-to-server_apps) lets you send events in the Measurement Protocol *format* to a\ncontainer. The container then sends those events to Google Analytics using the\nsame mechanism as all other SGTM events.\n| **Note:** It *doesn't* send those events to the Measurement Protocol endpoint, and therefore doesn't support all the features of the Measurement Protocol endpoint, such as deriving [geographic and device information](/analytics/devguides/collection/protocol/ga4#geo_device) from tagging events.\n\nIf you want all the features of the Measurement Protocol, send events directly to the\nMeasurement Protocol instead of your container."]]
