How to Use the PixelYourSite Event Setup Tool (EST)

Overview

The Event Setup Tool (EST) allows you to create custom tracking events visually, directly on your website front-end, without writing code or manually finding CSS selectors. Watch this video to learn how to use it:

Note: The Event Setup Tool is a Pro feature.

The Event Setup Tool (EST) is a visual, point-and-click editor for building Custom Events in PixelYourSite Pro. Instead of typing CSS selectors and URL patterns into the Custom Event form, you open a page from your own site inside an overlay, click the element you want to track, pick a trigger type, choose which pixels the event fires to — and PYS creates the Custom Event for you.

It’s the fastest way to set up click, hover, copy, form-field, and video events, because you select the element directly on the rendered page rather than guessing at selectors from the source.

The EST builds the same kind of Custom Event you’d build by hand. Once saved, the event appears in the Events List and is fully editable in the standard Custom Event editor — so if you later need to add Conditions, additional triggers, or tweak the per-platform parameters, you do that in the regular editor.

When to use the EST (and when not to)

Use the EST when:

• You want to track a click, hover, scroll, copy, video interaction, or form-field interaction on a specific element of a specific page.
• You’re more comfortable pointing at the element than working out the right CSS selector or URL pattern.
• You’re setting up a single straightforward event and want the fastest path to having it live.

Use the manual Custom Event editor when:

• The trigger is a Post type, Home page, WooCommerce add-to-cart, or WooCommerce purchase — these don’t benefit from the visual overlay because there’s no specific element on the page to click.
• You’re cloning or batch-editing many events at once.
• You want to add or edit Tags (the only Custom Event feature the EST doesn’t expose).
• You’re already comfortable enough with the manual editor that pointing-and-clicking isn’t faster.

The EST and the manual editor are fully interchangeable — events you create with the EST are normal Custom Events and can be opened, edited, and extended in the manual editor at any time. A common workflow is to scaffold the event with the EST (because the element selection is so fast), then jump into the manual editor afterward only if you want to add Tags or fine-tune a CSS selector by hand.

Requirements

• PixelYourSite Professional installed and active.
• At least one ad/analytics platform configured in PYS (Meta, Google Tag for GA4/Google Ads, TikTok, Pinterest, Bing, Reddit, or GTM). The EST shows only platforms that are enabled and have at least one pixel ID configured — there’s nothing to send an event to otherwise.
• The user opening the tool needs the manage_pys capability (administrators have this by default).
• You must be able to open your site’s front end as a logged-in admin in the same browser session. The EST overlay is rendered on the live page, so it loads with your admin auth cookie.

Launching the tool

1. Go to PixelYourSite Pro → Events.
2. Scroll to the Start Event Setup Tool card.
3. In the Enter a URL on this site to open the visual tool on that page field, type the URL (or a relative path) of the page where the element you want to track lives. The placeholder shows the format: https://yoursite.com/sample-page/. The helper text under the field reads “Supports both http:// and https:// URLs, or a relative path like /sample-page/”.
4. Click Open Tool.

The tool opens that URL in a new tab with the EST overlay injected on top. A confirmation line below the URL field reads “Only pages from this site are allowed: https://yoursite.com/“ — the EST won’t open external URLs, by design.

Inside the EST overlay

The overlay sits on top of your live page. You can browse, scroll, and click links as a normal visitor — until you switch the EST into selection mode, at which point clicking an element captures it as the trigger target instead of activating it.

The flow is the same regardless of trigger type:

1. Pick the trigger type from the side panel — Click on CSS selector, Mouse over CSS selector, Copy element (text copy), Click on HTML link, Email Link, Page Scroll, Embedded Video View, Embedded Video speed, Filling out a form field, Page visit, Number of Page Visits, Home page, Post type, WooCommerce add to cart, WooCommerce purchase. The full list mirrors the trigger types in the Custom Event editor.
2. Select the target on the page. For click, hover, copy, link, and form-field triggers, the EST switches into selection mode and highlights elements as you mouse over them — click the one you want and the EST captures its CSS selector for you.
3. Configure trigger-specific options in the side panel:
   • Click on CSS selector — set Number of clicks required (1 by default) and Time limit between clicks in milliseconds (for double-click, rage-click, or N-clicks-in-window detection).
   • Page Scroll — set the percentage threshold (default 50%).
   • Embedded Video View / Embedded Video speed — the EST scans the page for embedded YouTube and Vimeo videos; pick which detected video to track, and for video-speed pick the speed-change type (Increase / Decrease / Any).
   • Filling out a form field — pick the form, then the field within it.
   • Page visit / Number of Page Visits — set the URL rule (contains / match) and, for Number of Page Visits, the operator (=, >=, <=, >, <) and the count.
   • Post type — pick the WordPress post type from the dropdown.
   • Any trigger — optional delay in seconds before the event fires once the trigger is satisfied.
4. Add more triggers if you need them. The EST isn’t limited to one trigger per event — add as many as you want and choose the Trigger Logic (OR or AND) for how they combine, plus a Fire Frequency of Every time or Once per page. Same model as the manual editor.
5. Add Conditions (optional). Open the Conditions block, flip the switch on, and pick the logic (AND or OR). Then add one or more conditions of any of the six supported types — URL filters, URL parameters, Landing page (including the variants that match query-string parameters of the landing URL), Source (the referrer captured at session start), Device (Desktop / Mobile), and User role (any WordPress role plus Guest for not-logged-in visitors). Conditions decide whether the event is allowed to fire on this pageview, for this visitor — see the Custom Events doc for the deep-dives on each type.
6. Pick the destinations. The side panel lists every ad/analytics platform you have configured. For each one you want to fire to: enable it, pick the Event type from the platform’s catalogue, and select which Pixel IDs receive the event (a specific one or all pixels). The platform catalogues match what the regular Custom Event editor shows.
7. Set the event name and (optional) parameters. Give the event a name (this is what appears in the Custom Events list and in the GTM data layer). For platforms that support custom parameters (Meta, Google Tag, GTM, TikTok, Pinterest, Bing) you can add key/value pairs. Each parameter can take a literal value or a dynamic value from page — give it a CSS selector and PYS reads the matched element’s text (or the input’s value, for form fields) at fire time. Optionally turn on Fire this event only once in N hours under General to throttle per visitor.
8. Save. The EST sends the event back to your WordPress admin via AJAX. A new Custom Event is created with the trigger(s), conditions, destinations, and parameters you configured, and you’re redirected to the Events List where the new event is now visible.

Defaults the EST applies when you don’t set them

If you don’t touch a particular field, the EST creates the event with these defaults:

• Enabled: on
• Fire only once in N hours: off
• Trigger Logic: OR
• Fire Frequency: Every time
• Conditions: disabled, with default logic of OR
• Delay: 0 seconds

All of these can be overridden inside the EST itself — you don’t have to jump to the manual editor for any of them.

Which platforms appear in the EST

The EST shows a card for every platform that is enabled in PYS Pro and has at least one pixel ID configured. The exact list:

Platform	Card name	Configures
Meta (Facebook)	Meta	Standard or custom event name + Meta pixels (incl. Super Pack conditional pixels)
Google Analytics + Google Ads	Google Tag	GA4 + Google Ads action + pixel/conversion IDs
Google Tag Manager	Google Tag Manager	GTM event action + container IDs
TikTok	TikTok	TikTok event type + pixels
Pinterest	Pinterest	Pinterest event type + tag IDs
Bing	Bing	Bing event type + UET tags
Reddit	Reddit	Reddit event type + pixels

Platforms that aren’t enabled, or that have no pixel ID saved in PYS, are hidden from the EST. If a platform you want is missing, configure it under the corresponding settings page in PYS Pro first, then reopen the EST.

What the EST does not configure

In practice the EST is a full Custom Event editor with a visual layer on top. The one Custom Event feature that lives only in the manual editor is:

• Tags — the free-text labels used to organize and filter events in the Events List. They don’t affect firing behaviour, so this is a low-impact gap; add them in the regular editor after saving if you need them.

Everything else — Conditions of all six types, multiple triggers with AND/OR, Once per page fire frequency, per-trigger delay, the Fire only once in N hours throttle, and dynamic-value-from-page parameters — is available inside the EST itself.

Tips and gotchas

Use the EST on the page you actually want to track. Selectors generated by the EST are based on the DOM of the page you have open. If your CTA button has a different class on the home page vs. the pricing page, you’ll need a separate event for each — or you’ll need to generalise the selector by hand in the editor afterward.

Cookie banners, consent overlays, and other floating UI can intercept clicks. If the EST captures the wrong element, dismiss the overlay first and try again, or switch into the editor afterward and replace the captured selector with a more specific one.

Test before relying on the event. After saving, open the page in a fresh browser tab and trigger the action (click, hover, copy, scroll, video play, form fill). Browser-side events show up in the PixelYourSite Pixel Helper extension; server-side events go to Meta Events Manager → Test Events, GA4 Admin → DebugView, or the TikTok / Pinterest event log.

Sites with aggressive caching can block the overlay from loading. If clicking Open Tool takes you to the page but no EST overlay appears, clear your page cache and CDN cache for that URL, then retry.

The EST has to load on the front-end with your admin auth. If you’re using a security plugin that strips cookies on the front-end, or you’ve logged out in another tab, the EST won’t be able to authenticate the save call back to wp-admin. Log back in and reopen the tool.

Editing or removing an EST-created event

Events created via the EST are normal Custom Events. To edit:

1. Go to PixelYourSite Pro → Events.
2. Scroll to the Events List.
3. Click the event’s name to open the standard Custom Event editor.

From there you can rename, add or remove triggers, add or change Conditions, add Tags, change per-platform parameters, change pixel selection, or delete the event. Form-field triggers created via the EST keep a created_via_est marker internally so PYS knows not to re-derive form metadata it already has from the EST capture.

Verifying the event after launch

Same playbook as any Custom Event:

• Meta — open Meta Events Manager → Test Events (or the Server tab for CAPI) and look for your event name.
• GA4 — open Admin → DebugView during a test interaction; the event arrives with its parameters.
• TikTok / Pinterest / Bing / Reddit — each platform’s Events Manager has an event log.
• Browser-side — the PYS Pixel Helper extension shows everything that fires client-side, with the parameter payload expanded.

If the event isn’t showing up: confirm it’s enabled in the Events List, confirm the page you’re testing matches what the EST captured (URL and DOM), and confirm the destination platform’s pixel is firing at all (a misconfigured pixel ID will block every event, not just this one).