Clearer Validation Warnings in Tracks Explorer

Debugging tracking issues just got faster. We've improved how Tracks Explorer surfaces validation errors. Now, when a validation function flags a track, you'll see exactly which function is responsible instead of a generic message.

The Challenge: Generic Errors Slow Down Debugging

When a validation function failed, Tracks Explorer showed a message like:

"This track presents validation errors with a function."

That tells you something is wrong, but not what or where. If you had multiple validation functions in your setup, you'd have to guess which one triggered the warning, then dig through your configuration to find the culprit. Every extra step between spotting an error and understanding it adds friction to your workflow.

The Solution: Validation Function Names Are Now Visible

We've updated Tracks Explorer to surface the actual function identifier when a validation warning fires. Here's what changes for you:

• See the exact function that failed — instead of a vague message, you'll now read something like: "This track presents validation errors with function validate_ecommerce_items."
• Go straight to the source — the function name gives you an immediate starting point for investigation, no guessing required.
• Keep your aliases when configured — if the function has a human-readable alias defined in your plan settings, that alias is still shown as before. Nothing breaks, everything improves.

How It Works

1. Open Tracks Explorer and navigate to a track with a validation warning.
2. The warning message now displays the function identifier (e.g., validate_ecommerce_items_combination) directly.
3. If that function is configured in your plan settings with a human-readable alias, the alias is shown instead — same experience as before.
4. Use the function name to locate the relevant validation logic in your setup and resolve the issue.

Who Benefits from Clearer Validation Warnings

• Digital analysts monitoring data quality will spend less time deciphering cryptic error messages and more time acting on them.
• Developers maintaining analytics implementations can identify broken validation functions at a glance, without cross-referencing configuration files.
• Marketing and performance teams gain faster confidence that tracking errors are being caught and resolved before they affect campaign data.

Ready to see it in action? Log in at Tackingplan and head to Tracks Explorer to check your validation warnings.

Need further assistance? Our support team is here to help!

Happy Tracking!