Documentation Index

Fetch the complete documentation index at: https://supporthub.usheru.com/llms.txt

Use this file to discover all available pages before exploring further.

Manual Tracking

Prev Next

Introduction

Manual tracking rules are used when tracking cannot be configured easily from Elementor, like complex selectors, third-party widgets or pages not built with Elementor.

Steps

Go to: Settings > Usheru Tracking > Manual tracking rules


Manual rule fields

Active

Turns Using Tracking in Elementorthe rule on or off.


Rule name

Internal name for the rule.

Example:

Premium request info CTA


CSS selector

The CSS selector of the element to track.

Example:

.trackeable_btn

or:

.premium-card .elementor-button


Trigger

Choose the action to track


Load on

Controls where the rule is loaded.

Available options:

Entire site

Specific pages/posts

Post type

URL contains

URL regex

Entire site

The rule loads everywhere.

Use carefully.

Best for global elements.


Specific pages/posts

Use page or post IDs separated by commas.

Example:

12, 34, 56

Use this when the rule is only needed on known pages.


Post type

Use post type slugs separated by commas.

Example:

page, post, tribe_events

Use this when the rule should apply to all posts of a specific type.


URL contains

Use a partial URL path.

Example:

/premium/

This rule will load on URLs that contain /premium/.

Useful for grouped landing pages.


URL regex

Use a regular expression for advanced matching.

Example:

^https://example.com/events/

Use only when simpler conditions are not enough.


Datalayer values

Manual rules can also use DOM tokens:

[value:CSS_SELECTOR]

[attr:ATTRIBUTE_NAME]

[closest_attr:CSS_SELECTOR:ATTRIBUTE_NAME]

[closest_text:CSS_SELECTOR|TEXT_SELECTOR]


Testing and QA

1. Temporarily enable debug mode in:

Settings > Usheru Tracking

  1. Then open the page in the browser and inspect the console.

You should see logs like:

[Usheru Tracking] Pushed

  1. Check the dataLayer manually

Open the browser console and run:

window.dataLayer

  1. Look for objects like:

{

 event: 'usheru',

 tracking_event: 'cta_click',

 tracking_source: 'premium_home',

 tracking_engagement: 'Interest',

 content_type: 'Premium Hospitality',

 content_name: 'premium_requestinfo_button'

}


Best practices

Naming convention

Use lowercase and underscores.

Recommended:

cta_click

form_view

form_start

form_submit

premium_home


Use a small controlled list:

Interest

Intent

Action

Conversion

Example usage:

CTA click: Interest

Form start: Intent

Form submit: Action

Purchase or lead confirmation: Conversion


Keep content_name specific

Good:

premium_requestinfo_button

premium_joinwaitlist_button

premium_requestaccess_button

Too vague:

button

cta

click_here