---
title: "What are the different Event Trigger Location in Trend Insights?"
slug: "list-of-event-trigger-location-filters"
updated: 2026-09-10T14:32:48Z
published: 2026-09-10T14:32:48Z
canonical: "support.whatfix.com/list-of-event-trigger-location-filters"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.whatfix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What are the different Event Trigger Location in Trend Insights?

Event Trigger Location is an Event Filter that enables you to narrow your Trend Insights data by where an event was triggered from, a Launcher, a Beacon, Self Help, and so on.

For example, for the **Flow started** event, refine the results to show data only for those who fired it from a Launcher.

![trend_insight_event_trigger_location.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/trend_insight_event_trigger_location.png?sv=2026-02-06&spr=https&st=2026-11-10T16%3A55%3A30Z&se=2026-11-10T17%3A55%3A30Z&sr=c&sp=r&sig=s8WmY7YCsbqzzOh8Nd7Jrx0C4CbH%2F6f2FYW7Yysohb8%3D)

The following is a list of all the captured Event Trigger Location filters and their description.

| Event Trigger Location | Event Trigger Description |
| --- | --- |
| Assistant | Triggered from the Whatfix Assist Bot. |
| Auto-exec | Triggered automatically after the end of a Flow. |
| Beacon | Triggered from a Beacon. |
| Blog | Triggered when a Flow is launched as an article. For more information, see [Embed a Flow as article.](/docs/using-the-article-embed-format) |
| Deck | Triggered when a Flow is launched as a slideshow. For more information, see [Embed a Flow as Slideshow](/docs/whatfix-slideshows-1). |
| Editor | Triggered from Whatfix Studio when you preview your content. For more information, see [How to use preview mode to review content?](/docs/how-to-use-preview-mode-to-review-content) |
| End Pop-up | Triggered from the end message Pop-up after a Flow. For example, if you've linked Flow 2 to the end message Pop-up of Flow 1, then the Event Trigger Location of Flow 2 is the end message Pop-up of Flow 1. |
| JS | Triggered automatically as a result of being embedded in the application code. For example, if you have embedded a Smart Tip in your code so that it appears automatically whenever a user opens the page, then the Event Trigger Location of the Smart Tip is JS. |
| Launcher | Triggered from a Launcher. |
| Popup | Triggered from a button in a Pop-up. |
| Site | Triggered when the content is viewed using See live or Preview. |
| Tasker | Triggered from a Task list. |
| URL | Triggered when a Flow is launched as a Whatfix URL. For more information, see [Embed a Flow as a URL](/docs/use-the-url-embed-format). |
| User_action | Triggered when the end user completes a User Action. |
| Widget | Triggered from Self Help. |

> [!WARNING]
> Note:
> 
> Event Trigger Location might have blank values that can be removed from the data. For more information, see [How can I exclude blank filter values from event analysis?](/product-analytics/docs/how-can-i-exclude-blank-filter-values-in-insights)