Tracking Limitations
Overview
Tracking features depend on technical conditions such as supported pages, enabled settings, available hooks, browser behavior, email client behavior, and third-party integrations.
What this feature does
This article explains why some view or notification events may not appear in every situation.
Why it is useful
- It prevents unrealistic expectations.
- It helps support teams troubleshoot missing events.
- It reduces confusion around email opens, view events, and custom pages.
Who should read this?
RISE Admin, Support Engineer, System Owner.
Where to find it
This applies to View Log, Notification Log, embedded tools, and email tracking features.
How to use it
- Check whether the page or entity is supported.
- Check whether tracking is enabled in settings.
- Check whether the current user has permission.
- Check whether a browser, email client, or third-party plugin may be blocking or bypassing tracking.
Example workflow
An email open event does not appear because the recipient’s email client blocks remote images. This does not necessarily mean the user did not read the email.
Common mistakes
- Assuming missing tracking always means a bug.
- Expecting third-party plugin pages to be tracked automatically.
- Using view or email tracking as the only evidence in an investigation.
Related articles
- Email Open Tracking
- What Rise Audit Pro Does Not Track Automatically
- Does Rise Audit Pro Track Third-Party Plugins
