Reading the Console output
How to read the lines Quadrano writes to the browser Console, and what to do when a push fails.
This page describes Console format version 1.
What you'll need: a site with your snippet installed, and its browser Console open.
What you'll have at the end: you can tell a passing push from a failing one, and you know where to look next.
The banner
Quadrano writes one banner per page load, before anything else. It names the Specification, the Version, and the data layer it is watching.
One group per push
For each push Quadrano checks, it opens one group. The group's first line is the verdict and the event name. Its last line is Pushed:, followed by the push itself — click the line in the Console to inspect what the page sent.
A passing push starts with ✓:
Quadrano · Specification bannerpushab · Version local · Console format v1 · watching dataLayer ✓ add_to_cart Pushed:
The banner is written once. The group below it is the checked push: ✓ means every Attribute passed.
A failing push starts with ✗ and says how many errors there are:
Quadrano · Specification invalidpushab · Version local · Console format v1 · watching dataLayer ✗ purchase · 2 errors ecommerce.transaction_id is required, but is missing. ecommerce.value should be a number, but got "12.99". Pushed:
Read each error line as a sentence about one Attribute:
ecommerce.transaction_id is required, but is missing.— the Attributetransaction_id, inside theecommerceGroup of Attributes, is required, but the push did not include it.ecommerce.value should be a number, but got "12.99".— the Attributevalueshould be a number, but the push sent the text12.99.
A warning push starts with ⚠. It means the push had keys that are not in the Event Definition — extra keys only, nothing else wrong.
Attribute paths
When an Attribute is nested, its line names the path, with [n] for a list index. For example, ecommerce.items[0].price points at the price inside the first item of the ecommerce.items list.
No Event Definition
If the event name is not in your Specification, Quadrano says so, and suggests the closest name when one is close:
Quadrano · Specification unknownevent · Version local · Console format v1 · watching dataLayer Quadrano · No Event Definition for "purchas". Did you mean "purchase"?
Here the site pushed purchas, a typo for purchase. Add or fix the Event Definition, then get the snippet again.
Other messages
Two Specifications loaded. Two Quadrano tags fired on the same page. The first stays in charge; the second checks nothing:
Quadrano · Two Specifications loaded: <first spec ID> is validating, <second spec ID> was ignored. Check your tag triggers.
See One Specification per site, and Troubleshooting.
No data layer. The page has no window.dataLayer array, or it uses another name:
Quadrano · No data layer found at window.dataLayer, so nothing is being checked. Check the data layer name in your Quadrano tag.
Quadrano Local always reads window.dataLayer. See Troubleshooting.
A check could not finish. If a push's value cannot be read, Quadrano passes it on unchanged and writes one warning:
Quadrano · Couldn't check this push, because one of its values can't be read. It was passed on unchanged.
Log levels
Quadrano Local's snippet always shows every message. It does not offer a quieter setting.
What to do on ✗
Fix either the push or the Event Definition:
- If the site pushed the wrong value, that is a developer task: fix the site's push.
- If the Specification was wrong, fix the Event Definition in Quadrano Local, then choose Get snippet and replace the tag's text (Installing the snippet in GTM, step 6).
Next
Continue to Troubleshooting.