The Test Tool allows you to immediately test the implementation of a page after you deploy a deployment group to the test environment. Before you start testing, check out these sections:
After reviewing these concepts, you're ready to start testing. Check out Test tags by URL and then Analyze test results.
Test considerations
Testing is performed based on the most recent deployment group logic that you deploy to the test environment. Additional information to consider:
-
To use the page testing feature, your browser must be HTML5-compliant.
- The ability to open the test page and test tool in separate windows is not supported in Internet Explorer. To activate test reports on the Digital Analytics test system, contact Acoustic Support.
-
If your deployment group uses Digital Analytics tags, when you deploy it to the test environment, the cookie domain for the group's pages is overridden to testdata.coremetrics.com. Tag data from those pages is sent to your test client ID.
Reporting environments
Two reporting environments are available to you: test and production.
- Use the test environment while tags are in development (your development and staging environments).
- Use the production environment after the tags are moved to the live production site.
The data collection domain and reporting URL for the test environment are shown in the following table.
| Parameter | Description |
|---|---|
| Client ID | Your 8-digit 9-series production Client ID, with the first digit replaced by "6".
Example: The production client ID "92345678" has a corresponding test client ID "62345678" . |
| Data Collection Domain | The data collection domain for the test environment is testdata.coremetrics.com. |
| Reporting URL | The reporting URL for the test environment is http://welcome.coremetrics.com. |
To test tags by URL:
- Select Test tool in the main navigation of Exchange Capture.
- Enter a URL where you want to test tags.
- Specify where you want to view site and page analysis:
- Single window provides a single window for analysis.
- Separate windows provides a more flexible choice as it separates the page tested with the diagnostic windows.
- Select an option for analyzing tags:
- Analyze tag only verifies that the tag field data is available and correct without actually sending the data.
- Analyze tag and send tag data sends the tag data to its target. This is useful if the first option confirms the tags are set up correctly but it is not known if the actual data is being sent correctly.
- Click Run test. If you encounter errors, check out Test tool error messages.
- Navigate in the displayed page as you would in any web browser. When you click links on the displayed page, or enter another page URL, the tag results table refreshes to show test results for the current page tags. For information about analyzing test results, check out Analyze test results.
Analyze test results
The Tag Results Table displays at the bottom of the browser window when you test deployment groups, showing the results of the tags that executed on the current page. Use the controls above the table to filter or customize your view of the results.
- Deployment Groups
- Select whether to view the results for all deployment groups that are deployed in the test environment, or select a specific deployment group to view only its tag execution results.
- Partners
- Select whether to view the results for all partner tags deployed in the test environment, or select a specific partner to view only its tag execution results.
- Show Errors Only
- Select this option to show only errors, such as invalid datatype in the tag results table. If tags are executed successfully, with no errors, they are not displayed in the table.
- Suppress Duplicates
- This option suppresses the display of duplicate data for multiple rows. For example, if a tag has multiple tag data item rows, but the Date/Time, Deployment Group, Category, Partner, Tag Function, and Tag Name are identical for each of those tag data items, they are displayed only once, in the first row for that tag. This option is selected by default.
- Encyclopedia
- Click the Encyclopedia link to view a summary of elements, functions, and tags that execute on the test page. To refresh the display after changes are made to your pages, you might need to close and reopen the Encyclopedia window.
- Tags that not found or are unable to be syndicated are displayed with X in the Encyclopedia. Tags returning values with invalid datatypes (for example, if the tag value does not match the tag's expected data type) are displayed with alerts.
- Settings
- Click this link to display the current global settings.
Tag Results Table Columns and Descriptions
| Column | Description |
|---|---|
| Date/Time | The date and time at which the tag was executed. |
| Deployment Group | The name of the deployment group to which the tested page belongs. |
| Category | The category of deployment groups to which the tested page belongs. |
| Partner | The name of the partner that manages or hosts the tag. |
| Tag Function | The name of the function that is called by the tag. |
| Tag Data Item | The name of the tag data field that is associated with the tag. There can be several tag data fields for each tag. |
| Value Returned |
The value that is captured by the tag for the tag data item.
|
Encyclopedia page
When you run the test tool, results are shown in the test results table in the main test window. Click the Encyclopedia link in the test results table to open the Encyclopedia page. You can view details of tag execution and of elements or objects that are referenced by the tags.
- Active Deployment Groups
- Only deployment groups whose page rules were satisfied are displayed in this table.
- Tag Counter
- Tags that were run are displayed in this table. The check column indicates the number of times that a tag was syndicated successfully. The X column indicates the number of times that a tag failed to run or syndicate.
- HTML Elements
- This table lists the HTML elements found on the web page. The icons in the first column indicate whether the tag parameter is invoked through a function (
), bound to an event handler (
), or if the tag parameter is not bound, but executes immediately as the page loads (
). The element ID, attribute, the value of the attribute, and the result are shown for each element. - A blank in the Result column indicates that the element exists on the page but was not invoked; an X in the Result column indicates that the element was not found. If one element of a tag is not found, the remaining parameters for the element are not check, and gives blank results. When the same parameter is used in multiple tags, only the first occurrence is searched for and recorded. When the same parameter is found in another tag, it will not be searched for, and blank results are shown for occurrences after the first.
- JavaScript Objects
- This table lists the JavaScript objects found on the web page, in the order in which they are looked for. The icons in the first column indicate whether the tag parameter is invoked through a function (), bound to an event handler (), or if the tag parameter is not bound, but executes immediately as the page loads (). The value (including any modifier detail) and the result are shown for each object.
- A blank in the Result column indicates that the object exists on the page but was not invoked; an X in the Result column indicates that the object was not found. If any tag parameter is not found, the remaining parameters for that tag are not searched for, and gives blank results. When the same parameter is used in multiple tags, only the first occurrence is searched for and recorded. When the same parameter is found in another tag, it will not be searched for, and blank results are shown for occurrences after the first.
- URL Parameters
- This table lists any parameters in the page URL, and the results for each parameter.
- The icons in the first column indicate whether the tag parameter is invoked through a function (), bound to an event handler (), or if the tag parameter is not bound, but executes immediately as the page loads (). The value (including any modifier detail) and the result are shown for each object.
- A blank in the Result column indicates that the object exists on the page but was not invoked; an X in the Result column indicates that the object was not found. If any tag parameter is not found, the remaining parameters for that tag are nit searched for, and gives blank results. When the same parameter is used in multiple tags, only the first occurrence is searched for and recorded. When the same parameter is found in another tag, it will not be searched for, and blank results are shown for occurrences after the first.
- JavaScript Modifier Functions
- This table lists any functions that are referenced in tag modifiers. The Result column shows whether each function or modifier expression was successfully resolved.
- JavaScript Bound Functions
- This table lists any functions that are bound to elements on the web page. The Result column shows whether each function was successfully resolved.
- HTML Callback Element
- This table lists any callback elements on the web page. The Callback and the Result are shown for each element.
Browser testing
After the tags have been verified, it may be necessary to take a closer look at exactly what the tag code is doing on the page.
Browser testing is useful when determining if the:
- Library, loaded by the tag, loaded successfully
- Tag field modifiers produced the expected data value format
- Tag code is creating the proper objects on the page
Usually this browser testing is done in conjunction with help from the appropriate support staff for the partner in question.
The decision as to what browser debug tool to use is up to the partner. This tool should be applied to the Test Tool test page.
Test tool error messages
While running the Test Tool, you might encounter some error messages.
| Error message | Possible cause for the error condition |
|---|---|
| An error occurred [NO_SUCH_HS_VARIABLE] when assigning a value to the page identifier. As a result, the Tag manager rules will not execute and tag syndication will not occur. | This error occurs when the page identifier as defined in Global Settings is not found on the page. The message in brackets [] may vary depending on the page identifier type; for example, url, JavaScript variable. |
| The Tag manager container code is not present on this page or cannot otherwise be identified. | This error occurs when:
|
| The tag container has not been found. No tags have been syndicated as yet. | This message occurs when the page is properly identified by the deployment group code, but no tag is found. In the case of deployment groups that only load a library or a code snippet, this is not an error. If a tag is expected, the Encyclopedia link is displayed with the error message. Click the Encyclopedia link to review a list of tags and dependencies for the page. Tags assigned to the deployment group are listed with their fields and whether the field was instantiated correctly. |