Configure an event from your website

This guide configures a click on a “Request a demo” button. You need the extension open with the correct Pixel and the website with the Pixel installed. The button must be present on the page.

Select the button

Open Selector in the side panel and choose Click.
Press Select element, then click the “Request a demo” button on the page.
In the Elemento selezionato overlay, check the description and number of matching elements. For this example, the selection should identify the intended button.
Press Copia selector in the website overlay. The reference is copied and the result appears in the extension panel.

The click during selection chooses an element and is intercepted by the extension. Perform the real test after leaving selection mode.

Affidabilità is an estimate of selector stability, not event verification. If several elements match or the reference looks fragile, use Riprova. To stop selection, press Annulla or, while choosing an element, Esc. These website overlay labels remain in Italian.

Save the event to CJM

In the panel's selection result, select Configure event.
Enter richiesta_demo_click in Event name.
Check that Trigger is Click and CSS Selector matches the selected button.
Leave Destinations blank for this first test. You can add comma-separated Tags to classify the event.
Press Save and wait for Event configuration saved.
In the dashboard, open Setup → Pixels → Pixel → Events → Configured events and verify that the event is present.
Reload the website, click the button outside selection mode, and check the event.

Saving changes the Pixel configuration in CJM. It is not a local simulation. Avoid editing the same Pixel simultaneously in the dashboard and extension: saving sends the event list loaded in the panel.

If you prefer configuring in the dashboard, after Copia selector, paste the reference into the event's CSS Selector field and follow Configure events in the dashboard.

Choose a selection type

Type	How to use it
Click	Select the button or link directly. The suggested trigger is `click`.
Submit	Select the HTML form that emits the submission. Selecting only a button does not select the form; this mode does not automatically move to the container.
Form	Select the form or one of its fields: the extension looks for the containing form and proposes `form_submit`. It does not register contacts by itself.
Visibility	Select the section to observe and complete the `intersection` trigger settings.
Video / Audio	Select a native video or audio element, or its container. The initial trigger is `play`; check that the correct content was found.
Custom	Copy a generic reference. Before saving, choose a trigger actually available in the editor; the proposed `custom` value is not a ready-to-use event call.

Additional fields depend on the selected trigger. Complete the required fields and check the stated units: numeric fields in the extension do not necessarily use the same controls as the dashboard. Enter threshold lists as comma-separated numbers. For trigger behavior, see the events guide.

CSS Selector is read-only in the extension editor. Use the dashboard to correct a saved selector; selecting a new element prepares a new event. Advanced fields requiring structured objects have no editor in the extension.

Edit and remove

On the initial Selector screen, Configured events has a pencil for editing and a trash icon for removing events. To return to the initial screen after a selection, you can close and reopen the panel.

The pencil opens the editor; Save sends the change.
The trash icon sends the removal immediately, without another confirmation. The extension prevents removing the last event.
After an error, check the dashboard configuration: the local list can already show a change even when saving failed.

Use AI suggestions

On the initial Selector screen, press Suggest with AI.
Check URL to analyze and press Analyze.
Review Suggested events. Use Edit on a proposal, check its name, trigger, selector, and destinations, then Save.
Verify the rule in the dashboard and repeat the website test. A saved proposal can remain in the suggestions list: avoid saving it again by mistake.

Add all adds proposals to the local list but does not save them. For a verifiable workflow, review and save proposals individually. Closing the panel can lose unsaved proposals.

Suggestions analyze the given URL; they do not guarantee that elements exist on the page you are viewing. For analysis limitations, see AI suggestions.

Destinations and common problems

Meta event name, Standard Meta event, and GTM event name configure browser forwarding. They do not install Meta Pixel or Google Tag Manager or create server rules. Before using them, follow Destinations and deduplication.

Problem	What to check
Configure event is disabled	Sign in, select an organization, project, and Pixel, and wait for configuration to load.
The result does not appear in the panel	Press Copia selector in the website overlay and keep the side panel open.
The event does not fire after saving	Reload the website and check consent, selector, and element presence. An element added after page load may require specific handling.
You cannot select embedded content	Selection works on the main page and does not enter iframe content, an embedded page. Components with isolated internal structures may also be inaccessible.