Create server delivery rules
Send events received by CJM to Meta, Google Ads, and GA4.
A delivery rule tells CJM: “when this event arrives from the site, forward it to this platform”. Delivery starts from the CJM server, so it works even if the visitor's browser blocks ad pixels. It can't recover events that never reached CJM, for example because the Pixel script was blocked.
Before you start
- The Pixel is installed and receiving events.
- The destination platform is connected in Setup → Channels. Meta needs at least one connected Meta pixel; Google Ads needs imported conversion actions.
Where rules live
Open Setup → Pixels, select the Pixel, then Destinations. For each platform you see the connection status, how many rules are active and the Last delivery; further down, the Server delivery rules section lists the rules, with New rule and Suggest rules buttons.
The same rules are also available in Setup → Server tracking.
Create a rule
Open a new rule
Select New rule. The New delivery rule window has two steps: When and Send to. At the bottom you always see the rule summary, which describes in plain words what it will do.
When: choose the Pixel
In CJM pixel, choose which site the events come from, or All pixels.
When: choose what starts the rule
In What starts the rule? choose one of two modes:
| Mode | When to use it |
|---|---|
| Specific pixel events (recommended) | Pick one or more events configured on the Pixel, for example “Click on Book”. Purchases and other ecommerce events are under Show ecommerce events. |
| Every event of a kind | Pick an interaction type, for example Form submitted or Page viewed, whatever the event is called. |
If an event you picked earlier no longer exists on the Pixel, it appears under Events no longer on the pixel: remove or replace it.
When: limit the pages (optional)
In On which pages? keep All pages or choose URL contains, URL starts with or Exact URL and enter the address, for example /thank-you.
Send to: choose the platform
Select Next and choose the Destination platform, then fill in its fields:
| Platform | Fields |
|---|---|
| Meta (Conversions API) | Meta event: use a standard event such as Lead or Purchase to optimise campaigns. Meta pixel: the pixel (dataset) that receives the event. |
| Google Ads (Conversions) | Conversion action: the conversion to record. Works for visitors who came from an ad. |
| Google Analytics 4 (Measurement Protocol) | GA4 event: the name the event gets in GA4, converted to snake_case (for example generate_lead). |
Send to: set the value
In Conversion value choose:
- No value: the event is sent without a monetary value;
- Fixed amount: every conversion is worth the same Amount, in the chosen Currency (for example
EUR); - Contact value: uses the contact's deal value, when available.
For ecommerce events, the value and currency inside the event take precedence over the rule's.
Save
Check the Rule active / Rule paused switch and select Create rule. To edit an existing rule, open it from the list and select Save changes.
Examples
Page filter
URL contains, URL starts with and Exact URL compare plain text, not regular expressions. Use the address as it actually arrives in the event, including any query string: with Exact URL, /checkout and /checkout?step=2 are different addresses.
Current limitation: if an event has no URL, the filter doesn't exclude it. Don't use this filter as an access control.
Consent and verification
Rules respect the visitor's consent: Meta requires adUserData and adPersonalization granted, GA4 requires analyticsStorage. Google Ads applies consent signals and limits the personal data sent. See Connect your cookie banner.
After creating a rule, trigger a test event and check:
- that the event reached CJM;
- that in Destinations the platform's Last delivery shows Delivered (or Processing or Rejected);
- that the event appears in the destination platform.
What we send (Meta and Google Ads) shows an example of the data sent. The Test button checks the connection to the platform, but doesn't prove every event is delivered. If the event is missing, check in order: rule active, Pixel, chosen events, page filter and platform configuration. For Meta browser and server delivery, also check identifier consistency.
Automatic suggestions
Suggest rules proposes one rule for each destination already set on the Pixel's events, for example after applying the AI tracking plan. Proposals aren't created on their own: review them and confirm only the ones you need.