No-code Event Tracking

Userflow enables non-technical team members set up event trackers directly from our UI, without code. This is an alternative to asking your developers to instrument your code with userflow.track() calls.

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.

Table of contents

• Table of contents
• Use cases
• Benefits of Userflow’s No-code Event Tracking
• Video walkthrough
• Building an event tracker
• Analytics
• Using events in conditions

Use cases

• Use past events to auto-start flows/checklists. E.g. show a flow once a user has done x 3 times, or if they have not done x in the last 10 days.
• Similarly, mark checklist tasks as completed based on events.
• Do basic analytics in Userflow, e.g. tell how many people click a button or see an element over time.
• Stream tracked events to your analytics provider (such as Amplitude or Mixpanel), where you can perform more advanced analysis.

Benefits of Userflow’s No-code Event Tracking

• Privacy- and security-friendly: Trackers run 100% client-side. We’re not streaming any content or clicks out of the user’s browser. The only signal we get is that the event was tracked. This completely alleviates the regular issues around privacy and security that normally come with no-code event tracking where all clicks and content is implicitly streamed to a third-party database (implicit tracking).
• Accurate and robust: Since trackers run client-side, we’re able to use much more sophisticated algorithms for recognizing elements, and to build more complex conditions, such as a combination of a click and an input field being non-empty.
• No-code explicit tracking: No-code Event Tracking is more like explicit tracking (than implicit tracking), but it gives you a no-code way of getting started with product analytics.

Video walkthrough

Building an event tracker

1. Go to Trackers in the sidebar.
2. Click Create event tracker.

3. Decide what your condition should be, i.e. under which circumstances the event should be tracked. If you want to track when users click an element, then click Add condition, then Element. Then select the element in your app.
4. Optionally, add more conditions. In most cases, we recommend e.g. adding a Current page condition to limit which pages the tracker may run on.
5. Select or create the event that should be tracked by entering a name such as “Project created” in the second column. We recommend using the format of “Noun Verb”.
6. Click Test tracker to verify that the tracker works.
7. If prompted, enter the URL of your app in the dialog that appears, i.e. where you want to test the tracker.
8. A browser tab with your own app will now open up. Notice how it says “Not tracked yet” in red at the bottom of the screen. Now try to perform the action that should track the event. You’ll see that the text changes to say “Tracked 1 time” in green. You can try to trigger the event multiple times to see the counter go up.

9. Once you’re happy with your tracker, go back to the Userflow UI and click Publish. The tracker won’t track anything for real users until you publish it.

Analytics

Go to the Analytics tab under a tracker to see how many and which users have performed the event:

If you’re looking to do more advanced analytics, such as funnel and retention analysis, then we recommend using an analytics platform such as Amplitude or Mixpanel. Events from Userflow can be continually streamed into these providers.

Using events in conditions

You can used tracked events to e.g. auto-start flows/checklists or mark checklist tasks as completed.

Here’s an example of a checklist task being marked completed as soon as the “Project Created” event has been tracked at least once.

To add an event condition:

1. Click Add condition. This is typically found under the Auto-start flow/checklist section or in checklist tasks’ side panel.
2. Choose Event in the dropdown.
3. Pick the name of your event.
4. Choose frequency and time period.