CJM
Browser extension

Install the extension and select your Pixel

Download the extension from the dashboard, sign in, and check where your changes will be saved.

With the extension open alongside your website, you can select elements and work on the correct Pixel's configuration.

Before you start

You need Chrome, dashboard access to download the extension, and a website to test. To save configurations, you also need a CJM account with project access and a Pixel already created.

Install the downloaded file

  1. In the dashboard, open Setup → Pixels, select your Pixel, and go to Events.
  2. Under Configured events, open an event that requires an element, such as a Click event.
  3. In Selector of the element, select Download extension (.zip).
  4. Extract the ZIP into a folder you will keep on your computer.
  5. In Chrome, open chrome://extensions and enable Developer mode.
  6. Select Load unpacked and choose the extracted folder containing manifest.json.
  7. Open the website to check and reload it, especially if it was already open during installation.
  8. Open CJM Pixel Extension from Chrome's extensions menu. You can pin it to the toolbar for easier access.

In browsers supporting the side panel, the icon opens the extension alongside the page. Use this mode to keep the panel open throughout selection and form mapping. The code also includes a popup fallback, but closing it during these operations can interrupt selection or lose the result.

The procedure provided by the dashboard uses a ZIP and manual loading. Do not select the ZIP file itself at the Load unpacked step.

With the current Control Center, the download link appears only in an event editor with a CSS Selector. If the Pixel contains only page_view, the dashboard does not yet offer a direct trigger choice to create another event: use an already configured event or request support before proceeding.

Sign in to CJM

  1. Open Account in the extension.
  2. If the sign-in form appears, enter your CJM account's Email and Password.
  3. Select Sign in and check the account displayed.

If you are already authenticated, check that this is the correct account. This screen offers email and password sign-in; it has no registration, password recovery, or external sign-in provider buttons.

Choose where to save

  1. Press the Pixel indicator at the top of the panel to open Change context.
  2. If there is an automatic match, check the Pixel name, project, and website address.
  3. If Multiple pixels match this site appears, choose the correct one. You can also use Manual selection.
  4. For manual selection, choose Organization, Project, and Pixel, in that order.
  5. Reopen Change context to check the Pixel card and Configured events.

The Pixel selection determines where changes are saved. It does not install that Pixel on the page or filter local events to that Pixel alone. Check it again when switching websites or projects.

Language and sign-out

In More → Settings → Language, choose Italian or English. Some overlays on the website, such as Copia selector, remain in Italian even when the panel is in English.

To sign out, select Account → Sign out. After signing in again, check the selected project and Pixel.

Troubleshooting

ProblemWhat to do
Chrome cannot load the folderCheck that you extracted the ZIP and selected the folder containing manifest.json, rather than its parent.
The download failsDownload again from the dashboard. If it remains unavailable, report it to the team managing CJM.
Selection does not startOpen a normal website page, reload it after installation, and reopen the extension. Internal Chrome pages and browser-protected pages are unsuitable for this test.
You cannot find an organization, project, or PixelCheck Account and try manual selection. Ask your administrator if you lack project access.
Pixel not found or a configuration error appearsCheck the selection and use Retry. Sign in again if the session expired.
A Pixel is selected but no events appearSaved configuration and a Pixel installed on the website are separate. Follow Check events.

On this page