Agencies can participate in the Digital Analytics Program (DAP) by implementing the DAP script block. It’s a simple line of of code that enables you to take advantage DAP:
You can use this line to enhance the Web analytics solution with additional query string parameters. The query string parameters pass data that enable features within the code. They can also help configure settings in the code. It allows you to leverage more features in DAP or extract more data out of DAP. In the example above, we have the query string parameters “agency” and “subagency” that pass data into DAP for reporting purposes.
Let’s go through some useful options.
Our recommended implementation is to call the DAP code from a central location hosted by DAP. This allows you to implement the code once without having to worry about updating it manually for new versions.
Instead of setting the “src” attribute to a local directory, set the value to the centrally hosted URL as follows:
Remember, the script block won’t work properly unless src is specified with https://. The central host URL has been configured to only be called securely over SSL.
When DAP updates the code file, the new version will take effect immediately. If we update the code to include any bug fixes or additional features, you’ll see those updates automatically without revisiting the script block code.
If you have your own additional implementation of Google Analytics (GA), you may have a bit more flexibility in configuring the settings. However, you may be missing some of the features in DAP: for example, download tracking. You might want to consider running the two analytics codes simultaneously. Parallel tracking allows the DAP code to send DAP data to your separate account of GA.
This differs from a completely independent GA account in that the only GA code needed is the DAP code, which will collect data and send it to both accounts. A completely independent account means that you run both the DAP code and the out-of-the-box GA code, in which both will collect data mutually exclusively.
While DAP is a great Web analytics solution on its own, you can still take advantage of running your own GA account in parallel by adding the PUA parameter to the source file location:
where UA-000000-0 would be replaced with your own UA ID.
Now, you can create and track your own Goals and configure other administrative settings to your own account while receiving data from DAP.
The DAP code will allow you to track a number of download extensions by default. You may have unconventional extensions that may not be included in our list. If you look at the DAP code and search for “EXTS”, the first instance of “EXTS” is followed by the list of extensions that are tracked in DAP by default.
If you don’t find your extension in that list, you can add your own with “exts” parameter:
DAP will now help you track downloads with “f90” extensions.
You might interested in the demographics of your website users. Remember, DAP doesn’t collect any PII, but DAP does use data that Google collects based on Google profiles and users’ browsing habits across the Web (apart from DAP), either from surveys or ads that they serve.
Add a “dclink” parameter and set the value to true:
You can find the demographic data in the Audience section of GA and discover the characteristics of your users.
Other potential options you can enable or change with querystring parameters in the DAP script tag include:
- Cookie expiration time period (to determine new vs. returning users)
- Adding search parameters (for internal search queries)
- Embedded Youtube video metrics tracking
You don’t need to be a code junkie to enable tracking of these additional features. You can take a look at the implementation guide for other parameters that you might want to add. If you’re interested in implementing DAP for your website, the guide provides instructions as well. For more information or if you have questions while implementing, contact us!
Have feedback or questions? Send us an email »