New section in common_issues.md covering:
- How RegEx Table content grouping works in GTM
- Common pitfall: new page paths falling to "Other"
- Gotcha: parallel Path/URL variables must stay in sync
- JHR content group category reference table
- Audit checklist for content grouping
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
gtm-audit (60):
- Added Mode D rule: check elements for IDs before designing CSS triggers
gtm-editor (61):
- Added "Tagging Workflow: dataLayer First" section — always suggest
dataLayer push code for developers before creating GTM triggers
- Added multi-language snippets (JS, React, Vue, PHP)
- Added "Trigger Design: IDs First" section — prefer element IDs,
ask user to add IDs before falling back to CSS selectors
- Added ID naming convention: [section]-[element]-[action]
- Added decision tree for trigger selection
gtm-validator (62):
- Flag CSS-based triggers as fragility risk during QA
- Recommend adding IDs instead of finding alternative CSS selectors
Based on field testing with ourdigital.org GTM-N9TPJW container.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
