Event aliases and rules
Both live on a pixel's Events tab and apply to that pixel only.
Event aliases
Each of your events is listed with the platform event it is sent as. Pick another of the platform's events, or type a name of your own where the platform takes one. Switch a row off to stop sending that event to this pixel. Some platforms also need an id per event.
| Platform | Names of your own | Also needs, per event |
|---|---|---|
| Google Ads | Its own events only | In a rule, a conversion action: An “Import from clicks” conversion action of the same Google Ads account: its id (digits, in its details URL) or resource name customers/<account>/conversionActions/<id>. |
| Meta | letters, digits, spaces, _ and -, 40 at most | — |
| Its own events only | — | |
| letters, digits, spaces, _ . and -, 64 at most | — | |
| Snapchat | Its own events only | — |
| TikTok | letters, digits and _, 50 at most | — |
| Microsoft Advertising | letters, digits, spaces, _ . and -, 60 at most | — |
| Google Analytics 4 | starts with a letter; letters, digits and _, 40 at most | — |
| Its own events only | Conversion rule id: Campaign Manager → Conversions → the rule → its id (digits). | |
| X | Its own events only | X event id: Events manager → the event → its id (tw-…). |
| Quora | Its own events only | — |
| OpenAI Ads | letters, digits, _ and -, 64 at most; sent in lower case | — |
| Google Enhanced Conversions | Its own events only | — |
How a rule reads
| Part | What you pick |
|---|---|
| When | One of your events (a row of the Events tab). |
| Matches | Groups of conditions. Every condition in a group must match; the rule fires when any group matches. Up to 10 groups of 10 conditions. No conditions: every such event. |
| Then |
|
| As | One of the platform's events, or a name of your own where the platform takes one, with its per-event id where needed. On Google Ads: a conversion action (purchases only), picked from the ones the pixel already sends to or entered as its id or resource name. |
Examples:
- When Purchase matches (page path starts with “/gift-cards”) or (currency equals “EUR”), also send GiftCardPurchase.
- When Lead matches query parameter plan equals “annual”, send SubmitApplication instead.
Up to 20 rules per pixel, numbered and applied in that order. The first matching Send instead rule wins: move a rule up or down (the arrow buttons beside it, which also work from the keyboard) to change which one. An event that matches several rules sends each name once (a name with its own id, such as a conversion action, counts as its own). Rules apply to events from now on, not to past ones. Order rules, match keys, product details and once per visit apply to rule events as to any other.
Rules on Google Ads
Google Ads counts each conversion action on its own. Funnel steps (intake, sign-up, checkout started) are sent from the Events tab as “conversion”, each with its own conversion action. A rule on a Google Ads pixel is for the purchase and sends it to a conversion action: pick one the pixel already sends to (its own, from the Settings tab, or one another rule uses), or enter its id (digits) or resource name customers/<account>/conversionActions/<id>. The action must be in the same Google Ads account, an “Import from clicks” action like the pixel's own. Also send to the pixel's own action is refused (it already gets every purchase); Send instead to another action moves matching purchases there.
Conditions
| Field | Compare with | What it is |
|---|---|---|
| Page URL | equals, does not equal, contains, starts with, ends with | The page the event was sent from, as host and path (no https://, www., query or #). Browser events only. |
| Page path | equals, does not equal, contains, starts with, ends with | The path of the page the event was sent from. Browser events only. |
| Query parameter | equals, does not equal, contains, starts with, ends with | A query parameter of the page the event was sent from (utm_campaign, plan…). Browser events only. |
| Referrer | equals, does not equal, contains, starts with, ends with | The page before it (document.referrer), as host and path. Browser events only. |
| Event value | equals, does not equal, is greater than, is less than | The event's value, or its order's, in the event's currency (149 = 149.00). |
| Currency | equals, does not equal, contains, starts with, ends with | The event's or order's currency code. |
| Customer's order count | equals, does not equal, is greater than, is less than | The customer's orders up to and including this one (test orders never count). 1 = first order. |
| New customer | is yes, is no | The order is the customer's first, as the source said or Trakbolt counted. |
| Order status | equals, does not equal, contains, starts with, ends with | The status the source sent with the event, else the order's. |
| Product id | equals, does not equal, contains, starts with, ends with | Any item of the order, or of a view / cart / checkout event that lists items: product id, variant id or SKU. Not offered on healthcare workspaces. |
| Event property | equals, does not equal, contains, starts with, ends with | An extra field your source keeps on the event (properties.<name>). Case-sensitive name. |
- Text ignores case. Addresses compare as host and path: no https://, www., query, # or trailing slash.
- Numbers: 149.00 equals 149.
- A list (the order's product ids) matches when any item does; does not equal matches when none does.
- A missing value never matches, not even does not equal.
- Page conditions (page URL, page path, query parameter, referrer) match browser events only. Server events have no page, so these conditions never match them.
- Values are up to 500 characters. A value that looks like an email address is refused: no contact data in rules.
Purchase names
A platform's purchase event can only come from a purchase. A rule on any other event that sends one of these names is refused when you save it, and skipped if it was stored before:
| Platform | Purchase names |
|---|---|
| Google Ads | purchase |
| Meta | purchase, order_complete |
| checkout, purchase | |
| purchase | |
| Snapchat | purchase |
| TikTok | completepayment, purchase |
| Microsoft Advertising | purchase, order_complete |
| Google Analytics 4 | purchase |
| purchase | |
| X | purchase |
| Quora | purchase |
| OpenAI Ads | order_created, purchase |
| Google Enhanced Conversions | purchase |
Healthcare workspaces
- Conditions can compare page addresses and query values, but those values are never sent: the page still goes out as its domain only.
- The product id condition is not offered.
- Event names must be neutral: a standard platform name that can be restricted for health businesses is refused, for aliases and rules alike.
Built-in rules
These are set elsewhere and listed with your rules, read-only, with an Edit link to their own controls: new customers only, the event sent for returning customers, high-value customers (an extra event when lifetime spend reaches a threshold) and later stages (an event when an order's status changes).