Configure a project in Setup
Choose the Setup tab for tracking, lead capture, and integrations.
Setup is the project area for collecting data and connecting the tools that use it. In the Italian interface, its page title is Configurazione. It does not change the reports already shown in the Dashboard; it prepares the sources and destinations that make those reports possible.
You do not need every tab. Choose the one that matches the result you need.
Choose the right tab
| If you need to… | Open | Before you start | Next step |
|---|---|---|---|
| Collect activity from a website | Pixels | Access to the website | Create and install a Pixel |
| Read and qualify form submissions | Lead forms | A website, Meta, or HubSpot form | Configure Lead Forms |
| Import campaigns or connect advertising platforms | Channels | Access to the advertising account | Connect marketing channels |
| Send a selected Pixel event to an advertising platform or GA4 | Server tracking | A connected destination and a received Pixel event | Create server delivery rules |
| Send CRM qualification and stage progress to advertising platforms | Offline conversion | A connected platform and mapped CRM stages | Configure offline conversions |
| Receive Pixel events through your own subdomain | Domains | Access to DNS records | Connect a custom domain |
| Notify your own endpoint when project events happen | Webhook | A public HTTPS endpoint | Configure an outbound webhook |
Use the recommended order
For a website that must collect and use marketing data, follow this order:
- Create a Pixel, install it on the published website, and verify that an event reaches CJM.
- Configure the useful events or Lead forms. A click is not necessarily a successful form submission or purchase, so use the configuration that matches the real business result.
- Connect Channels only for the advertising platforms you use.
- Create Server tracking rules for selected website events.
- If the CRM manages sales progress, map its pipeline, then configure Offline conversion for qualifications and stages.
- Add a Domain or Webhook only when you have the respective DNS or receiving-endpoint requirement.
This order separates three different outcomes: collecting website activity, understanding commercial progress, and sending selected data elsewhere. It prevents a channel connection or a saved rule from being mistaken for proof that the website is already sending data.
Two commonly confused choices
Choose Server tracking when the source is a particular Pixel event, such as
purchase. Choose Offline conversion when the source is a qualification or
CRM stage, such as SQL, Opportunity, or Won. Configure both only if you need
both signals; otherwise you can create duplicate or misleading conversion data.
Choose Domains when you want a first-party collection endpoint. It changes where Pixel events are sent after DNS verification; it does not replace the Pixel installation or make the JavaScript file load from that domain.
Check the configuration worked
Saving a Setup form only confirms that CJM stored the configuration. Verify the next real outcome instead:
- use Pixel installation verification for website collection;
- use Signals for Meta, Google Ads, and GA4 sends;
- use the receiving service's logs for an outbound webhook;
- check the DNS status before relying on a custom domain.
When a result is missing, start with its source: first make sure CJM received the original website event or CRM update, then check the relevant Setup tab and destination.