Tracking Plan
Manage Behavior Intelligence tracking targets: coverage score, site crawl, SiteAnalyze AI proposals, manual target forms, and component registry alignment.
Tracking Plan purpose
The Tracking Plan (catalog) ensures important interactive elements—buttons, links, forms, zones—map to stable Component Registry UUIDs. Without targets, clicks on redesigned CTAs vanish from metrics even though page views still accrue. Coverage score quantifies how much of your intended instrumentation exists vs gaps.
Coverage score
Coverage compares active tracking targets against discovered interactive elements from crawls and page manifests. Aim for high coverage on conversion-critical templates first (homepage hero, pricing CTAs, checkout buttons) before chasing long-tail blog buttons.
Crawl and SiteAnalyze
Run a site crawl to fetch public pages and extract clickable elements. SiteAnalyze (AI-assisted) proposes labels and selector strategies, especially on complex builders (Elementor, blocks). Jobs require manage capability and may take minutes on large sites.
Results appear in proposals panel with confidence hints. Accept proposals to create targets; reject false positives (duplicate nav items, cookie banners).
Manual target entry
Add targets manually when you know the selector: CSS selector, component slug, page scope, and human-readable name. Manual entry suits new launches before crawl indexes them.
Component Registry stability
UUIDs persist across DOM changes when selectors remain valid. Prefer data attributes or stable IDs over brittle nth-child selectors.
Proposals and approval
Proposals queue until approved. Bulk-approve high-confidence items, manually review ambiguous ones. Approved targets appear in active targets list and begin receiving events on next page load with updated manifest.
Maintaining coverage over time
- Define coverage goals per template type in team runbooks.
- Block releases if hero CTA coverage regresses.
- Cross-check Funnels drop-offs with missing click targets.
- Export target list periodically for disaster recovery documentation.
Selector best practices
Prefer data-imaginit-bi attributes added in theme templates over auto-generated CSS paths. Document selector ownership in theme README so freelancers do not remove attributes during refactors.
Coverage milestones
Phase 1: homepage, pricing, contact. Phase 2: blog CTAs and lead magnets. Phase 3: account and checkout flows. Score improvements per phase in sprint retros.
Additional best practices
Behavior Intelligence works best when tracking coverage, funnel definitions, and team review rituals stay aligned. Revisit this guide after major site changes—new theme, consent plugin, or checkout provider—and confirm Realtime, Data Quality, and Tracking Plan still agree.
Share direct help links from the in-app help panel so teammates read the same canonical definitions. Press Ctrl+K in the help center to jump between related guides quickly.
- Align date ranges before comparing metrics across pages.
- Document segment names when sharing screenshots.
- Verify fixes in Realtime before closing Growth Plan items.
- Keep UTM conventions consistent for Marketing and Traffic.
- Schedule AI analysis after enough post-change data accumulates.
Working with the global toolbar
Every major Behavior Intelligence report page shares a global toolbar controlling date range, comparison mode, saved views, and active segments. Understanding this toolbar prevents the most common reporting mistake: discussing metrics that look contradictory because two pages use different ranges or filters.
Date ranges support presets (last 7, 28, 90 days) and custom intervals. Comparison mirrors the prior period of equal length. When comparison is off, KPI deltas hide—do not assume zero change. Saved views capture all toolbar state; teach teammates to check the view name in the header before screenshotting for leadership.
Connecting insights to action
Analytics value appears when insights change behavior. Behavior Intelligence routes findings through Growth Plan, Anomalies, and AI Intelligence into prioritized work. A metric without an owner becomes wallpaper. Assign DRI (directly responsible individual) per Growth Plan card and set verification dates.
Cross-link investigations: Traffic anomaly → Sessions sample → Journeys path → Tracking Plan coverage → Funnel step fix. This sequence resolves most conversion mysteries without external tools.
Data freshness expectations
Raw events ingest in near real time on Realtime. Daily aggregates power most dashboard KPIs and typically finalize after processor cron completes overnight in site timezone. Intraday numbers on Traffic are directional, not audit-final. Export via Report Builder after period close for finance-adjacent reporting.
Security and access control
Report data stays inside WordPress authenticated admin. REST endpoints require configured capabilities. Do not expose API keys or disable capability checks for convenience. View-only roles should not access Settings, Tracking Plan writes, or AI job triggers unless policy explicitly allows.
Module updates and compatibility
After Imaginit Core or Behavior Intelligence updates, revisit Getting Started verification steps: Realtime test, Data Quality health, one saved report run. Release notes may add event types or metrics—refresh Report Builder definitions if preview validation fails. Theme changes always trigger Tracking Plan re-crawl before trusting click metrics.
Keyboard shortcuts and help search
From any Behavior Intelligence admin page, open in-app help links to jump to the matching guide on the public help center. Within the help site, press Ctrl+K or Cmd+K to open Spotlight search across all articles, headings, and keywords. Search for metric names, page titles, or tasks like "export CSV" to find the right workflow without browsing the sidebar.
Bookmark frequently used guides for your role: content editors often need Content Performance and Organic Search; engineers need Tracking Plan and Data Quality; leadership prefers Overview and Reports email summaries.