Analytics Plays
Check Your Site for Google Analytics (GA4) Tagging
Many USDA web pages are using excessive sets of Google Analytics tags—sometimes up to eight on a single page.
Too many tags will:
- Slow down your site load speed (hurting user experience and SEO).
- Cause inaccurate reporting when users leave before all tags finish loading.
To protect site performance and ensure accurate data, USDA limits each site to a maximum of 3 analytics configurations: required DAP, required USDA Official GA4, and one optional agency-specific stream.
Quick Reference: Required USDA Tag IDs
| Tag Name | Type | Identifier / Code | Status |
|---|---|---|---|
| Digital Analytics Program (DAP) | Central Script | DAP Centrally Hosted Code | Required |
| USDA Official GA4 | Department Measurement ID | G-VYRH7BQ1FL | Required |
| Agency-Specific Stream | Measurement ID or GTM | Agency specific (G- or GTM-) | Optional (Max 1) |
Important DAP Note: Websites cannot send raw hits directly to the DAP Measurement ID via a custom gtag.js setup or GTM event tag. DAP requires loading the official central JavaScript file on your page to ensure standardized federated reporting across government.
How to Audit Your Page Tagging
Tool Note: The legacy Tag Assistant Chrome Extension has been replaced by the web-based Google Tag Assistant.
- Launch Tag Assistant: Go to tagassistant.google.com.
- Connect Your Site: Click Add domain and enter your page URL.
- Verify Active Tags: Review the detected tags to ensure:
- The DAP central script is loading and firing Measurement ID G-CSLL4ZEK4L
- G-VYRH7BQ1FL (USDA Official) is present.
- No unapproved or extra UA- or G- tags are firing.
What to do if you find extra/unauthorized tags:
- Identify the owners of any extra analytics accounts.
- Inform them that unauthorized standalone tags will be removed from the site code.
- Grant them viewer access within the official USDA or agency GA4 property instead.
Implement Digital Analytics Program (DAP) Code
The Office of Management and Budget (OMB) Memorandum M-23-22 (Delivering a Digital-First Public Experience) requires federal agencies to implement the DAP JavaScript code on all public-facing federal websites. While mandatory, DAP provides key benefits:
- No-cost, government-wide web analytics tool
- Training and ongoing help desk support: dap@gsa.gov
- Data reporting support and a public window into DAP data
- Digital metrics guidance and best practices
Once you have verified that your site does not contain the DAP Code, follow these steps to register and implement:
Registration
- Define a POC: Identify a .gov point of contact on your team (typically a Product Owner or Program Manager).
- Register: GSA will send the POC a short sign-up form to register the agency and provide the central tag code.
- Contact DAP: If you don't have an identified POC, email dap@gsa.gov
Implementation & Confirmation
- Placement: Place the central DAP JavaScript snippet in the <head> of all site web pages. Do not send raw data directly to the Measurement ID (G-CSLL4ZEK4L); the central script file must be loaded.
- Detailed Technical Guide: Review the official Digital.gov DAP Implementation Guide for exact script tags and parameters.
- Confirm: Use Google Tag Assistant to confirm the central DAP script is actively loading.
DAP Resources
- analytics.usa.gov: Public window into DAP data
- Digital.gov DAP Guidance: Common FAQs, metrics guidance, and best practices
Implement USDA Official Code
USDA requires all agency sites to implement the Department-wide GA4 code for aggregate reporting to leadership.
- Implementation: Email oc-web@usda.gov for specific guidance on adding the official USDA script (G-VYRH7BQ1FL) to your CMS platform.
- Confirmation: Use Google Tag Assistant to verify Measurement ID G-VYRH7BQ1FL is actively firing.
Previous: Analytics Next: Content
Page last updated: August 2026
