Analytics Tracking

Explore requirements around analytics tracking for Office of Head Start (OHS) websites and mobile application (apps). Please contact the Head Start Information and Communications Center (HSICC) with any questions.

Mobile Apps

Firebase stores all apps developed on behalf of OHS. Versions of the same app for different platforms should be in the same Firebase project because it allows for unified analytics reporting. Before it is posted, the developer must add the Google Analytics tracking code snippet to each app.

Please read the Firebase documentation on Google Analytics for more information. Contact HSICC to have Firebase and Google Analytics accounts created for your application. Once created, co-ownership and other access will be granted to the appropriate users identified in the request.

Google Analytics Events

Events provide insight on what is happening in your app, such as user actions, system events, or errors. Analytics automatically logs some events for you, and you don't need to add any code to receive them. To collect additional data, you can log up to 500 different analytics event types in your app.

See Log Events for specific guidance on coding events in apps.

Webpages

All OHS pages created in Drupal using existing templates automatically include the Google Analytics tracking code. Content authors do not need to take any action to track basic analytics for most webpages. However, any interactive features, such as accordion menus or files to download, should be tracked with Events in Google Analytics.

Events measure user interactions with content that can be tracked independently from a webpage or a screen load. Most existing OHS interactive site features are already set up to be tracked, and each event only needs to be set up once in Google Analytics to track it everywhere on the OHS websites.