Custom Events via MCP
Custom events are events you create when you want to track a specific action or optimize ads for it — a visit to a key page, a button click, a form submission on a particular page, a purchase from a specific traffic source. Your AI assistant can manage the full lifecycle: list, read, create, update, enable, disable, duplicate, and delete.
Start with:
“What custom events do I have?” — the assistant lists every event with its title, enabled state, trigger types, active platforms, and whether the feature master switch is on.
“Show me the full configuration of my contact form event” — returns every trigger, every condition, every platform setting, and the event parameters in one response.
Custom events are managed in PixelYourSite → Events.
Master switch
One switch controls all custom events. When it is off, no event fires regardless of its individual enabled state. Individual event configurations are preserved.
“Enable custom events” or “Disable custom events” — the assistant toggles the master switch with a confirm step.
What you can read
“Do I have any events with no triggers?” — the assistant flags events that will never fire because no trigger has been added.
“Which events are active on Facebook?” — reads every event and filters by platform state.
“What triggers does my pricing page event have?” — full trigger list with all parameters.
“What event types are available for TikTok?” — the assistant reads the authoritative event type menu for each platform from the event configuration itself. It never guesses event names or parameters.
What you can create and edit (Pro)
All writes use a two-step confirm: the assistant shows a preview first, then waits for your explicit confirmation before saving. It never writes in the same turn as the preview.
Creating a new event
Describe what you want:
“Create an event that fires when someone visits my pricing page and send it to Facebook as a ViewContent event”
The assistant:
- Asks about optional trigger settings you may want (delay, URL match rules)
- Asks about optional condition settings if relevant
- Shows a full preview of the event to be created
- Waits for your confirmation
- Creates the event — paused by default if you want to review it first
A new event has no triggers until you add them, so it will not fire until that step is complete.
Updating an existing event
“Add a condition to my lead form event — only fire for logged-out visitors” “Change the URL rule on my blog event to match /blog/ instead of /articles/” “Add Pinterest to my purchase event”
Updates are surgical. Only what you specify changes. Everything else is preserved.
Enabling and disabling
“Pause the newsletter signup event” — sets it to Paused. Configuration is kept intact. “Re-enable the Black Friday event” — sets it back to Active.
Duplicating
“Duplicate my contact event” — creates a paused copy with all triggers, conditions, and platform settings. Useful for building variations without starting from scratch.
Deleting
“Delete the old test event”
Deletion is permanent. The assistant states the event name, confirms it cannot be undone, and requires your explicit confirmation before proceeding.
Triggers
Triggers define the visitor action that fires the event. Multiple triggers can be combined with OR (any trigger fires the event) or AND (all triggers must match).
Configurable through the assistant:
| Trigger | When it fires |
|---|---|
| Page visit | Visitor lands on a URL matching your rules |
| Home page | Visitor lands on the home page |
| Post type | Visitor views any post of a chosen WordPress post type |
| Number of page visits | Visitor has viewed a set number of pages in the session |
| URL click | Visitor clicks a link matching a URL rule |
| CSS click | Visitor clicks an element matching a CSS selector |
| CSS mouseover | Visitor hovers over an element matching a CSS selector |
| Scroll depth | Visitor scrolls to a percentage you set |
| Email link | Visitor clicks an email link |
| Copy element | Visitor copies text from a matching element |
| Add to cart | WooCommerce add to cart action |
| Purchase | WooCommerce or EDD purchase |
| Google Ads phone conversion | Visitor on a matching page clicks a tracked phone number |
| Form plugin | Submission of a specific named form (CF7, WPForms, Gravity Forms, Ninja Forms, and others) |
Require the visual Event Setup Tool in the admin: video view, video speed, form field interaction, Elementor form. These are scan-driven — they require pointing at a specific element on a live page. If an event already has these triggers, the assistant preserves them when editing other parts.
Google Ads phone conversion is exclusive: an event with this trigger can have no other triggers and fires to Google Ads only. The assistant tells you exactly what will be removed before proceeding and requires confirmation.
Conditions
Conditions gate the event — they control where and for whom it fires. Conditions are optional and must be enabled separately on the event.
| Condition | Filters by |
|---|---|
| URL filters | Current page URL |
| URL parameters | Query parameters in the current URL |
| Landing page | The URL the visitor first arrived on |
| Traffic source | Where the visitor came from |
| Device | Desktop or Mobile |
| User role | WordPress user role (including guest) |
Conditions combine with OR or AND logic. If conditions are not enabled, the event ignores them and fires for everyone who matches a trigger.
Platforms
Each event targets platforms independently. Each platform gets its own event name, parameters, and pixel selection.
Available: Facebook, TikTok, Pinterest, Bing, Reddit, GTM, and Google (GA4 + Google Ads as a unified block — G-pixel IDs route to Analytics, AW- to Ads).
The assistant only offers platforms that are active and have a pixel configured on your site.
Event names are platform-specific. The same action has different names per platform — for example, add to cart is AddToCart on Facebook, TikTok, Bing, and Reddit, addtocart on Pinterest, and add_to_cart on GA4/GTM. The assistant reads the authoritative event type menu from the live configuration and maps your request to the correct value. It never guesses.
Standard ecommerce events on platforms that fire them automatically: if you create a custom event using a name like Purchase or AddToCart on a platform that already fires it via WooCommerce or EDD event tracking, it will fire twice. The assistant warns you before confirming and asks you to verify your intent.