Skip to main content
Tag tester

Debug tags to ensure functionality.

Updated over a week ago

Tag tester (also known as tag review in Fluency) allows you to review and debug individual tags or tag queries for specific accounts on a Blueprint. Use tag tester to ensure tags function correctly and troubleshoot errors before launching campaigns.


How to test tags

Via Blueprints

  1. Go to Blueprints in the top menu.

  2. Select a Blueprint, campaign, ad group, or creative.

  3. Hover over any field that contains a tag, and click the eye icon that appears above the tag.

  4. The tag tester will open on the right, automatically populating the account and tag for testing.

  5. (Optional) Include a data filter for a specific tag preview.

  6. Click Submit Tags for Debugging.

Via Settings & Tools

  1. Go to Settings & Tools in the top menu.

  2. Select Tag Tester in the dropdown.

  3. Select an account and Blueprint. Note: Clicking the Tag Tester icon defaults to your current Blueprint.

  4. Enter a tag in the Tag to Evaluate field, which should already contain the tag that you previously selected.

  5. (Optional) Add a data filter under Optional Filters.

  6. Click Submit Tags for Debugging.


Reviewing tag tester results

After testing your tags, you will receive results in two dropdowns:

  1. Generation Trace:

    • Inputs: Contains all the content within the tag.

    • Outputs: The result of the content within the tag and its function(s) for the given account and Blueprint. Each tag output will have its own respective line.

  2. Final Output: The final tag result based on the inputted tag or tag query.


Resolving tag tester errors

If tag tester comes back with errors or displays ##UNDEF##, follow this guidance to resolve the issues:

  • Understanding the "##UNDEF##" output: The ##UNDEF## output indicates that the tag inputs are not matching the tag. Review the tag that is generating the error.

  • Potential sources of errors:

    • Data source discrepancies: Check for inconsistencies in the data source, such as the account ingestion sheet.

    • Missing information: Ensure that the selected account for testing the tag has all the necessary information associated with the tag. It could be as simple as an edited input in the source or missing data from the desired tag.

Did this answer your question?