ClickSight
Log in Get a demo Try it free
Help Center

Choose the right event setup option for the action you want to measure.

ClickSight event templates help you track common user actions without writing heavy custom rules from scratch. Use this guide to understand when each option is the right fit and what to configure before saving it.

Help Center / Events

Before creating an event

  • Confirm the ClickSight tracking script is installed on the website you want to measure.
  • Each event card in the modal usually shows three fields: event name, event type + key field, and an optional selector or trigger hint.
  • Use a clear event name so your saved event list stays easy to scan later.
  • After saving the rule, trigger it once on your live site and confirm it starts counting in the Events page.
Lead Generation

Use this for forms and contact actions

Choose this option when you want to track lead capture steps such as someone starting a form, submitting a form, clicking WhatsApp, clicking a phone number, or clicking an email link.

Lead Generation modal image placeholder

What to put in each field

  • Event name: Use a short name that explains the action, such as lead_form_start or lead_form_submit.
  • Event type: Use custom_event for form actions and clicked_css_selector for WhatsApp, call, and email links.
  • Custom event name / CSS selector field: For form steps, use the page path like / if you want to track the homepage form. For click rules, enter the CSS selector that matches that link.
  • Selector or trigger hint: Use this to remind yourself what element the rule should watch, such as “homepage contact form submit button”.

Examples

  • lead_form_start → type custom_event → value /
  • lead_form_submit → type custom_event → value /
  • whatsapp_click → type clicked_css_selector → value a[href*="wa.me"], a[href*="whatsapp"]
  • call_click → type clicked_css_selector → value a[href^="tel:"]
  • email_click → type clicked_css_selector → value a[href^="mailto:"]
CTA Engagement

Use this for key buttons and call-to-action links

This option is for important buttons that move users toward conversion, such as hero buttons, pricing buttons, and demo buttons.

CTA Engagement modal image placeholder

What to put in each field

  • Event name: Name the click after the button, for example hero_cta_click.
  • Event type: Use custom_event for these preset CTA templates in the current modal.
  • Custom event name field: Enter the page path where the CTA appears, such as / for the homepage or /pricing for the pricing page.
  • Selector or trigger hint: Describe the exact button, such as “primary hero button” or “pricing card start free button”.

Examples

  • hero_cta_click → type custom_event → value /
  • pricing_cta_click → type custom_event → value /pricing
  • demo_cta_click → type custom_event → value /
Scroll Depth

Use this to measure content depth

This option tracks how far people scroll on a page. It is useful for long landing pages, blog posts, pricing pages, or content-heavy service pages.

Scroll Depth modal image placeholder

What to put in each field

  • Event name: Use the milestone names exactly as shown: scroll_25, scroll_50, scroll_75, scroll_100.
  • Event type: Use custom_event.
  • Custom event name field: Enter the page path you want the scroll depth to apply to, such as / or /pricing.
  • Selector or trigger hint: You can leave a note like “homepage long-form landing page” if helpful.

Examples

  • scroll_25 → type custom_event → value /
  • scroll_50 → type custom_event → value /
  • scroll_75 → type custom_event → value /pricing
  • scroll_100 → type custom_event → value /pricing
Navigation Tracking

Use this for menu, footer, and logo clicks

This option helps you understand whether visitors are using your main navigation to move around the site.

Navigation Tracking modal image placeholder

What to put in each field

  • Event name: Use clear names like menu_click, footer_click, and logo_click.
  • Event type: Use custom_event in the current modal template.
  • Custom event name field: Use the page path where you want the rule to be counted, usually / if the nav exists site-wide.
  • Selector or trigger hint: Write a reminder such as “header navigation links” or “site logo in top-left corner”.

Examples

  • menu_click → type custom_event → value /
  • footer_click → type custom_event → value /
  • logo_click → type custom_event → value /
E-commerce

Use this for shopping and checkout milestones

This option is designed for product and checkout journeys, from product views through purchase completion.

E-commerce modal image placeholder

What to put in each field

  • Event name: Use names like product_view, add_to_cart, checkout_start, and purchase_complete.
  • Event type: Use visited_url for page-based milestones and custom_event when the action is button or interaction based.
  • Visited URL / path field: Enter the page path that confirms the action, such as /product, /checkout, or /thank-you.
  • Selector or trigger hint: Use a note if needed, such as “Add to cart button on product page”.

Examples

  • product_view → type visited_url → path /product
  • add_to_cart → type custom_event → value /product
  • checkout_start → type visited_url → path /checkout
  • purchase_complete → type visited_url → path /thank-you
Video Engagement

Use this for video play and watch milestones

This option is for pages where video is an important part of the customer journey, such as tutorials, demos, or sales videos.

Video Engagement modal image placeholder

What to put in each field

  • Event name: Use names like video_play, video_50_percent, and video_complete.
  • Event type: Use custom_event.
  • Custom event name field: Use the page path where the video appears, such as / or /demo.
  • Selector or trigger hint: Add a note like “hero demo video” or “product walkthrough video”.

Examples

  • video_play → type custom_event → value /
  • video_50_percent → type custom_event → value /
  • video_complete → type custom_event → value /
Custom Event

Use this when you need to build the rule yourself

This option is for actions that do not fit the preset templates. It gives you full control over the event name, event type, scope, and matching rules.

Custom Event modal image placeholder

What to put in each field

  • Event name: Use a clear name like contact_form_success or package_card_click.
  • Event type: Choose the type that matches the action, such as visited_url, clicked_text, or clicked_css_selector.
  • Folder: Optional. Use it if you want to group related events together.
  • URL scope: Choose All URLs if the rule should work site-wide, or Only specific URLs if it should only count on certain pages.
  • Matching rules: Add the rule that identifies the action. For example, use path contains / or a selector rule that matches the exact element.
  • Active: Keep this checked if the event should begin tracking immediately.
  • Monitor anomalies: Turn this on only if you want ClickSight to watch for unusual changes in the event later.

Example setup

  • Event name: homepage_visit
  • Event type: Visited URL
  • URL scope: All URLs
  • Matching rule: field path → operator contains → value /