Events

What this page is for

TrueMetriks already tracks the built-in events (PageView, Lead, Purchase, and so on). The Events page is for everything else you want to measure: a newsletter signup, a "Get started" click, someone reaching the bottom of a sales page. You define the event once here, and the tracker on your site starts firing it whenever its condition is met.

Where each event is sent (Facebook, Google Ads, GA4, TikTok) is handled separately, inside each ad integration card under Settings - Tracking. This page is only about defining the event itself.

Creating an event

Click Create event in the top right. The dialog asks for a few details:

• Event name - the technical name for the event, like MyCustomEvent. This is the name your integrations use, so keep it short and consistent.
• Display name (optional) - a friendly label shown in the dashboard, like "Newsletter Signup". Purely cosmetic.
• Description (optional) - a note to yourself about what this event represents.
• Active - the on/off switch. Leave it on and the tracker fires the event; switch it off to pause it without deleting it.

Choosing how the event fires

Every event has exactly one firing condition. The Condition type dropdown decides what triggers it, and the fields below it change to match your choice.

• URL match - fires when the visitor lands on a matching page. You pick a URL operator (contains, equals, starts with, or regex) and a URL value like /thank-you. For example, "contains /thank-you" fires on any page whose address includes /thank-you, which is the usual way to catch a confirmation page.
• Button click - fires when a visitor clicks an element. You target it either by CSS selector (like #cta-button) or by Visible text (like Get Started).
• Scroll depth - fires once the visitor scrolls a set percentage down the page (for example 50%). Good for measuring real engagement on long pages.
• Time on page - fires after the visitor has stayed a set number of seconds (for example 30). Another simple engagement signal.
• Fires when another event fires - fires whenever a built-in event fires. This is how you give an existing action a second, custom name.

Fires when another event fires

When you pick this option, you choose a Source event - one of the built-in events. Your custom event then fires every time that source event does, and it carries all of the source event's parameters along with it.

This is handy when an advertiser needs a differently named event for a platform's rules. For example, point a custom event at the built-in Purchase so the same sale also fires under your own name, without changing anything in your checkout.

After you save

Hit Save and the event joins your Custom events list, ready to fire. To decide where it gets sent, open the relevant ad integration card under Settings - Tracking and map it there. The built-in events that can power conversions are explained in the Facebook and Google Ads guides.