Custom events

Rage clicks, dead clicks, errors and chats are marked on every recording already. A custom event is one you define: "Added to cart", "Opened pricing", "Checkout failed".

Open Settings, Events and add one. Give it a name, a colour for the timeline, and one of three triggers:

• Click on - a CSS selector. It fires when a visitor clicks something that matches, for example #buy-now or .pricing .cta.
• Page path contains - part of a path. It fires when a visitor opens a page whose address contains it, for example /checkout/success.
• Your code calls it - a name your own code sends:

rc("event", "checkout_failed");

The name in the code is the trigger value, not the display name, so you can rename the event in the dashboard without touching your site. Names are cut at 120 characters.

Where they show up. As a mark on the recording's timeline, on the dashboard's events card with this period against the last, and as a trigger for an alert.

The four built-in kinds can be switched off on the same page. An event that is off is not stored at all.