Codeless tracking vs Track Events

Last updated:

Pendo supports both codeless tracking and Track Events for collecting data.

Codeless tracking

Codeless tracking refers to the collection of data, and displaying of guides, without manually inserting code for every interaction within your mobile application. The Pendo mobile SDK provides codeless, retroactive analytics across all of your app versions and supports in-app messages, tooltips, and multi-step walkthrough guides built with Pendo’s Visual Design Studio. Retroactive analytics means that data collection begins immediately after installing the Pendo mobile SDK.

The Pendo Mobile SDK automatically tracks user actions, such as screen views, button clicks, and other in-app interactions, without developers needing to code them explicitly. For more information about the frameworks supporting codeless tracking, see Supported mobile frameworks.

Track Events

A Track Event is a specific type of event that you can configure to gain insights into user interactions within your app. Track Events programmatically notify Pendo that a particular action occurred at a specific time and associate this event to a designated visitor and account. You can define custom metrics that are relevant to your app’s functionality or business objectives, then partner with your engineering team to implement tracking code using the Pendo SDK.

Track events can include both client-side (e.g., user actions, app events) and server-side events (e.g., API calls, server responses, error codes). Track Events allows you to record any actions your users perform, together with any properties that describe the action so you can track user behavior in your mobile apps and use Pendo's analytics. Track events can also be used to trigger in-app guidance.

Note: Track Events is supported alongside codeless, retroactive analytics. For more information, see Supported mobile frameworks.

Track Event support is available on frameworks currently not supported by a codeless solution. For more information, see Supported mobile frameworks.

Track Events use cases

Track Events are available in all supported frameworks. In frameworks without codeless support, you can use them to supplement the clicks and page views.

You can use Track Events to report on any event happening in your app, such as:

  • Change of a user's status
  • Actions performed by your user, such as important business transactions.
  • Input fields, such as search terms, to understand the most common searches.
  • Data about elements interacted with.
  • App exceptions & errors (with details. Track(“Error” Type=”400” Description=”[text]”))
  • Events with data fields. For example, when a user taps on a property record in a Real Estate app, and wants to capture details, such as address, price, type, of the viewed record.
  • Field entry values, like a search field input. Avoid collecting any fields that might contain PII or PHI.
  • Background tasks that do not have a UI element, such as Uploaded a File, Downloaded a file.
  • Device metrics, such as signal strength.
  • IoT device status and properties. For example, connected fitness monitor battery level, signal strength or DBM or RSS
  • Displaying guides after a background process starts or completes
  • Any place you may want a guide to display based on a Track Event property at the time of interaction.

In general, you can trigger guides on app launch, page views, clicks and Track Events. If using a Track Events-only framework, you can supplement the codeless events, such as click and page views, with a Track Event to trigger a guide. Tooltips are not available with Track Events.

Track Events for Track Event-only solutions

When planning which track events to have your engineers develop for your mobile app, there are several important considerations. Here are some key points to think about:

  • Strategic objectives. Start by aligning track events with the strategic objectives of your product. What are some key metrics that indicate success of your application? Track events should be directly tied to those metrics to ensure that you’re collecting relevant data.
  • User journey mapping. Understand the user journey within your app. Identify key touch points and interactions that users have with your product. This allows you to determine which events are most important to track to gain insights into your user’s behavior.
  • Feature usage. Monitor how users are interacting with specific features within your app. Track events related to feature usage help to understand which features are most popular and which may require improvement. This can help prioritize development efforts and guide product roadmap decisions.
  • Error tracking. Consider tracking errors within your app. These events are critical for identifying technical issues that may impact the user experience negatively. By monitoring server responses that indicate an error has occurred, you can quickly assess issues and improve overall stability and performance.
Was this article helpful?
0 out of 2 found this helpful