You can use these methods to confirm that the correct tag requests were sent from a device and received by Digital Analytics.
When you send tag data to a Standard 6-series test client ID, you can use the TagBar or another 3rd party tool.
Sending tag data to a multisite 8-series test client ID or any production client ID.
To validate outbound tag requests sent from your application, inspect the outgoing HTTP/HTTPS GET Image requests. If you are testing iOS/Android apps in the development stage by using the iOS/Android SDK simulators that run on a laptop or desktop OS (macOS or PC), view the requests by using any desktop HTTP request log tool such as Firebug, Chrome or Safari Developer Tools, Wireshark, Fiddler, or Charles. Inspect the generated request parameters for correct data by comparing them to the tag request specifications in this document.
To examine tag requests that are sent from a native application that is running on a physical mobile device or another device that does not have the ability to log and inspect outgoing HTTP requests, route the device traffic through a desktop-OS device that is running web proxy, and request log software, such as Fiddler or Charles. This allows the remote device requests to be inspected in the desktop web proxy request log. For example, instructions for iOS and Telerik Fiddler are http://docs.telerik.com/fiddler/configure-fiddler/tasks/ConfigureForiOS.
Tag requests start with http or https://testdata.coremetrics.com/cm (legacy: /eluminate), http or https://data.coremetrics.com/*, or if you are sending to an Acoustic-managed delegated data collection subdomain, http or https://<dcd>.yoursite.com/*.
For data sent to all types of test or production client IDs.
Observe the collected tag data in daily reports for Digital Analytics (https://welcome.coremetrics.com) or Digital Analytics Explore (https://explore.coremetrics.com) to verify the tag data was received and is correct in final reporting.
Article is closed for comments.