Create an AI tracking plan
Analyze the website, review every proposal, and apply only useful changes.
An AI tracking plan helps you choose the most useful website actions to measure. CJM analyzes public pages, prepares editable proposals, and does not change the Pixel until you approve the selected changes.
Before you start
You need a created Pixel and project access. People who can view the project can read plans and event flows; people who can edit it can create and analyze plans; only a project administrator can apply or revert one.
If CJM says the Pixel agent is unavailable, ask a project administrator to enable it. There is no automatic fallback, but you can still add events manually in Events.
The analysis sees only content publicly reachable from the website. It does not assume it can inspect logged-in pages, private areas, steps available only after JavaScript interactions, or CRM data.
Create and review a plan
- Open Setup → Pixels, select the Pixel, and open Events.
- Fill in Business goals in Tracking plan. Separate multiple goals with commas, for example
Demo requests, online sales. - Use Context for private steps or important conversions that the analysis cannot see, such as a request confirmation page.
- Select the items under Destinations that you want to consider: Meta, Google Ads, Google Analytics 4, or Google Tag Manager.
- Select Analyze website and wait for the result. The plan remains saved while analysis runs.
- Review analyzed pages plus each proposal's name, trigger, selector, and reason. Always check on the real website that the selector identifies the right element.
- Deselect unwanted changes and select Apply selected changes. Confirm the action again when the selection disables an event.
- Reload the website and test configured actions in Installation & test → Live verification.
Selecting destinations in a plan does not connect accounts, create tags, or prove that a platform received an event. Configure integrations in Destinations, then create rules in Setup → Server tracking and verify each platform directly.
Understand proposals
| Proposal | What happens if you apply it |
|---|---|
| create | Adds a new AI-managed event. |
| update | Updates an existing AI-managed event. |
| unchanged | Does not change an already matching or protected manual event. |
| disable | Stops an AI-managed event no longer supported by public website evidence. |
Events created or changed manually remain protected: the plan does not replace or disable them. Still review names and selectors before applying a plan, because a proposal describes what CJM detected, not a confirmed business outcome.
Each plan includes a standard baseline: page_view, 25%, 50%, and 90% scroll depth, and 30 seconds on page. It also adds relevant interactions found by analysis. This configuration does not derive products, orders, contact details, or form answers; use ecommerce events and lead capture for those data.
If the plan cannot be applied or you need to revert it
If the Pixel changes after a plan is created, CJM stops the application and asks for a new plan. Run the analysis again so you can review proposals based on the latest configuration.
After application, use Revert to restore previous events. Revert works only while the Pixel remains unchanged; later manual changes stay protected.
If analysis fails, make sure the Pixel website address is public and reachable, then select New analysis. For a missing or overly broad element, use Add event under Configured events and follow Configure dashboard events.
Follow an event flow
Under Configured events, you can search for an event, open it to edit it, or select Flow. The view shows the configured path: trigger, consent, validation, enrichment, deduplication, and applicable destinations or server rules.
The diagram explains expected configuration; it does not prove that an event arrived or was delivered to a platform. Use Live verification and check the destination directly for proof.