The Google Analytics Platform lets you measure user interactions with your business across various devices and environments. Google Analytics provides the resources to collect, store, process, and report on these user-interactions.
You can collect analytics on the client side and on the server side.
Client-side analytics collection
Use the Google Analytics APIs and SDKs to measure how users interact with your content and marketing initiatives. You can view user-interaction data in the Google Analytics user interface or use the Reporting APIs to fetch the data. For more details on client-side analytics collection, select the link below based on the type of your client:
- Web Tracking (analytics.js) - Measure user interaction with websites or web applications.
- Android - Measure user interaction with Android applications.
- iOS - Measure user interaction with iOS applications.
- Measurement Protocol - Measure user interaction in any environment with this low-level protocol.
Server-side analytics collection
Although App Engine provides a mechanism for logging events in your application, you can use Google Analytics to track specific server-side events in Google Analytics so that you can:
- Analyze historical data - App Engine allows you to configure the maximum number of days, or size, of your log file. After that limit has been passed, you no longer have access to those log files. Tracking events in Google Analytics provides you a much longer lifespan into the visibility of past events.
- Track key events - Log files can be verbose with various components of your application writing data to them. By using event tracking, you can pinpoint key events and track them, along with some metadata.
- Work in the user interface - Take advantage of the rich user interface that Google Analytics provides to visualize, report, and export these server-side events.
To enable server-side analytics collection, you can use an HTTP client and make HTTP requests using the Google Analytics Measurement Protocol. For additional information, consult the Google Analytics developers guide for Event Tracking.
The sample application below shows how to track events in your App Engine application. The application makes an HTTP request and posts data about the event to Google Analytics.
Before you use the Google Analytics Measurement Protocol on App Engine, follow these steps:
Include the environment variables with your Tracking ID in the relevant configuration file for your runtime. For example:
env_variables: GA_TRACKING_ID: YOUR-GA-TRACKING-ID
replace YOUR-GA-TRACKING-ID with the ID that you obtained from Google Analytics.
Before running the sample app locally, set the environment variables required by the app:
Run the sample code locally. For example, you can use the command line:
Post event tracking data to Google Analytics by updating your application to send HTTP requests that include Google Analytics payloads.
If you set the
GA_TRACKING_IDwhile testing your application locally, update the ID before deploying.
If you have enabled the setting in your Google Analytics Admin console to exclude traffic from spiders and bots, or if you are using Google Analytics 4 (which filters this traffic automatically), you might not see Analytics results from App Engine clients. These scenarios filter out the default App Engine user agent. To see App Engine results, include the
uaparameter in your tracking data and set it to a custom value.