--- title: "No-code event tracking" slug: "no-code-event-tracking" description: "Userflow allows non-technical teams to set up no-code event tracking, enhancing analytics and user engagement while ensuring privacy and security." tags: ["No-code Tracking", "Event Analytics", "Userflow Features"] updated: 2026-11-13T16:29:34Z published: 2026-11-13T16:29:34Z canonical: "help.userflow.com/no-code-event-tracking" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.userflow.com/llms.txt > Use this file to discover all available pages before exploring further. # No-code event tracking No-code event tracking lets you track what users do in your app, such as clicking a button, seeing an element, submitting a form or visiting a page, without adding code. You point at the element in your app, name the event, and Userflow records it each time a user does the action. Developers can still track events in code with `userflow.track()` (see [Userflow.js Installation](/userflow/docs/userflowjs-installation)). > [!NOTE] > Plan availability > > The number of event trackers you can create depends on your plan. To see your limit, check your [billing settings](https://app.userflow.com/app/_/settings/billing). No-code Event Tracking is the foundation of Userflow's [**Product Adoption Insights**](/userflow/docs/product-adoption-insights) suite. The events you track here automatically power your [Chart Builder](/userflow/docs/chart-builder) charts, [Funnel Analysis](/userflow/docs/funnel-analysis), and user targeting conditions, with no extra setup. **What you can track:** - **Button clicks:** Know when users click a call-to-action (CTA) button - **Element visibility:** Capture when important messages, prompts, or features appear on screen - **Form interactions:** Monitor completions, abandonments, and field engagement. - **Page visits:** Understand navigation patterns and page engagement **Example:** Track a *Project Created* event when the *Create project* button is clicked. Or track an *Upgrade Prompt Seen* event when a text prompting the user to upgrade their plan becomes visible on the page. ## What can I do with tracked events? Once an event is tracked, you can chart it in [Chart Builder](/userflow/docs/chart-builder), use it to auto-start flows and checklists, complete checklist tasks, build segments, and send it to your analytics tool through [Integrations](/userflow/docs/integration-old). Trackers run in the user's browser. Userflow receives only that the event happened, not the content of the page or the user's other clicks. ## Video walkthrough > [!NOTE] > Video Note > > In this video, **Event trackers** is in a different menu. It's now in the sidebar; everything else works the same. [Embedded content](https://www.loom.com/embed/4e3bc307a06a42a1b0f89fb5f4bdfba6) ## How do I create an event tracker? 1. Select **Event trackers** in the sidebar. 2. Click **Create event tracker**. ![Create event tracker button on the Event trackers page](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(261).png) 3. Add an event name. ![Event name field on a new tracker](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(266).png) **Event names can include the** **following characters:** - **Lowercase letters:** `a–z` - **Uppercase letters:** `A–Z` - **Numbers:** `0–9` - **Special characters:** - Periods (`.`) - Underscores (`_`) - Dashes (`-`) - Colons (`:`) - Forward slashes (`/`) - Vertical bars (`|`) - Hash signs (`#`) - Parentheses (`(` `)`) - Spaces 4. Determine which conditions to select - these are the circumstances under which the event should be tracked. If you want to track when users click an element, then select **Add condition** **>** **Element,** then click **Select element**, enter your app's URL, then select the specific element in your app. ![Add condition menu with the Element option](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(262).png) 5. Add a **Current page** condition to limit which pages the tracker may run on. > [!WARNING] > **Important:** Optimize performance by adding a URL condition > > **We highly recommend adding a 'Current page (URL)' condition** that indicates the page(s) on which the tracker should run. If a URL is not specified, the tracker will run on all pages of your app as it looks for the event it is instructed to track. Running a tracker on all pages could result in performance issues or latency. Add a URL condition to optimize performance. 6. Select or create the event that should be tracked by entering a name, such as *"Project created,"* in the second column. We recommend using a descriptive format that includes the item and action completed in the event, for example, *Time tracked*, *Project saved*, etc. 7. Click **Test tracker** to verify that the tracker operates as intended. 8. If prompted, enter the URL of the page in your app where you want to test the tracker. 9. A browser tab with your own app will now open. Note that it will display *"Not tracked yet"* in red at the bottom-left corner of the screen. Now perform the action that should track the event. You'll see the text change to *"Tracked 1 time"* in green. You can trigger the event multiple times to see the counter increase. ![Test tracker](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/test-tracker.png) 10. Once satisfied with the event tracker, click **Publish**. *The tracker won't track user events until you publish it.* ## See how often a tracker fires 1. Open the event tracker you want to view. 2. Select the Analytics tab to view the overall performance and individual user tracking. ![Tracker analytics](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/tracker-analytics.png) To chart the event over time or build a funnel with it, use [Chart Builder](/userflow/docs/chart-builder) and [Funnel Analysis](/userflow/docs/funnel-analysis). You can also stream events to tools such as [Mixpanel](/userflow/docs/mixpanel). ## Use tracked events in flow and checklist conditions You can use tracked events to auto-start flows/checklists or mark checklist tasks as completed. > [!WARNING] > Not available for Announcements > > Event trackers are **not** available as an auto-start condition for Announcements. Announcements support Attribute, Segment, Current time, and Logic group conditions only. Event-based auto-start is available for Flows and Checklists. > > **Workaround if you need event-based targeting for an Announcement:** create a user segment based on the event, then use that segment as the Announcement's Segment condition. **Example:** A checklist task is marked as complete as soon as the *"Project Created"* event has been tracked at least once. ![Event condition](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/event-condition.png) **To add an event condition:** 1. Click **Add condition**. This is typically found under the **Auto-start flow/checklist** section or in the checklist tasks' side panel. 2. Select **Event** in the dropdown. 3. Select the name of your event. 4. Choose the frequency and time period. ## Event attributes: defining one versus sending its value These are two different jobs, done in two places. **Defining an event attribute** happens on the event itself, under **Settings → Events**. Open an event, or click **New event**, and use **Add attribute** to define the attributes it carries. On a new event, note that the **Display name** can be changed later but the **Code name** cannot. **Sending an attribute's value** happens when the event is tracked. Two routes can carry attribute values: - **Your app's front end**, via Userflow.js: ```plaintext userflow.track("Project Created", { project_type: "shared", template_used: true }) ``` - **Your back end**, via the REST API: `POST /events`. A no-code event tracker can't carry attribute values. You can use attribute conditions to decide when a tracker fires, but the event it tracks has only its name. If you need values on the event, track it with Userflow.js or the REST API instead. An event won't appear in a user's Activity feed until it's tracked, whether by a no-code event tracker, Userflow.js, or the REST API. Once values are arriving, you can group and filter by them in Chart Builder and Funnel Analysis. See [Standard Attributes](https://help.userflow.com/docs/standard-attributes) for what Userflow provides automatically, and [Userflow-generated events](https://help.userflow.com/docs/userflow-generated-events) for the attributes on Userflow's own events. ## Troubleshooting event trackers ### My event isn't firing Work through these in order: 1. **Confirm the tracker is published.** Open the tracker → check status is Published, not Draft. Trackers don't fire until published. 2. **Test the tracker on the exact page.** Open the tracker → Test tracker → enter the URL where the event should fire. If it shows "Tracked 1 time" in green when you perform the action, the tracker itself works. 3. **Check the URL condition.** Trackers with no Current page (URL) condition run on all pages, which is slow and error-prone. Trackers with a URL condition only run where it matches. Confirm the live page URL matches the condition. 4. **Check the element condition.** If the tracker targets a click on a specific element, the element may have changed in your app. Open the tracker, click Select element, and reselect on the live page. 5. **Check the user's event history.** In Userflow, open Users → find the user → Events tab. If the event fired, it shows here with a timestamp. If it didn't, the tracker isn't matching for that user. ### My event tracker doesn't appear in the conditions dropdown Trackers must be Published to appear in segment conditions, auto-start conditions, or checklist task triggers. If the tracker is still in Draft status, it won't be available. Publish the tracker and reload the conditions panel. ### My event isn't on the Event trackers page The **Event trackers** page only lists no-code trackers built on that page. Events tracked any other way don't create a tracker, so they won't appear there: - a **Track event** action on a flow or announcement button - `userflow.track()` in your app - the REST API (`POST /events`) You'll find all of your events under **Settings → Events**. To see what a particular user has tracked, open them under **Users**. ### My event tracker is slow or affecting page performance The most common cause is a tracker running on every page in your app instead of just the relevant page. Add a Current page (URL) condition to every tracker to limit where it runs. If you have many active trackers (10+), review them and remove any that are no longer needed. See also: [Troubleshooting Userflow.js Performance](/userflow/docs/troubleshooting-userflow-js-performance). ### User and company attribute limitations No-code event trackers fire on user actions. You can add attribute conditions to limit when a tracker fires, but the event it tracks carries only its name, not attribute values. If you want to: - **Track an action that varies by attribute** (e.g., "Project created by admin users only"), set up the tracker for the action, then filter the data in Chart Builder by the relevant attribute using Group By. - **Trigger an action based on combined event + attribute** (e.g., "user clicked Upgrade AND their plan is on a lower tier"), use the event tracker to fire on the click, and add a separate User Attribute condition on the auto-start. ### When to use the API instead of no-code tracking No-code event tracking is the right starting point for most use cases. Use the API (`userflow.track()`) when: - The action happens in code that doesn't correspond to a clickable element (e.g., a backend webhook completing). - You need to send event properties alongside the event (no-code trackers fire the event name but can't attach payload data). - The event needs to fire conditionally based on logic that's hard to express as element + URL conditions. You can mix both approaches in the same account. Events fired via `userflow.track()` can be used in the same conditions and charts as no-code tracker events. They're listed under **Settings → Events**, not on the **Event trackers** page. ## Related - [A/B testing](/ab-testing.md) - [Getting started with Userflow](/about-userflow-engagement-types-2.md)