Tag Features in your mobile app

Last updated:

This article details how to tag Features in your mobile application, and how to troubleshoot Feature tagging.

Tag a new Feature

Feature tagging can either be done when tagging a Page or by accessing the designer via Tag Pages:

  1. Go to Pages and select Tag Pages.
  2. Filter to your mobile app.
  3. Select the Page you want to tag Features on.
  4. Select Manage Page and start tagging your Features in the screenshot on the right, or select the button to let Pendo tag all the Features on the page for you. Each Feature shows up in a table on the left, where you can name it, group it, edit its attributes, and then save it.

image_2.gif

Suggested Features

The Suggested Features list generates recommended Feature tags for UI elements in your application that receive high engagement. It gives you an overview of how users engage with UI elements in your application and the ability to prioritize tags based on engagement data.

Pendo detects UI elements in your application that are buttons, links, and input boxes (not the text inside an input box) and identifies the relevant rule tagging these elements. Pendo then populates the Suggested Features section based on the number of clicks over the last 36 hours.

Additionally, a heatmap of your UI provides a visual display of elements in your application that Pendo has detected based on this engagement.

Pendo only begins processing Feature data after you've tagged it. Suggested Features haven't been tagged or processed yet. You can't see full retroactive analytics and you can't use suggested Features in reports or tagging until after suggested Features are accepted (tagged) and data processing is complete.

You can either accept and finish creating a suggested Feature or delete it. Once you accept or delete a suggestion, Pendo doesn’t suggest the Feature again.

Review suggested Features

Open the Suggested Features table for a list of untagged Features that appeared in your events in the previous 36 hours for both public and staging environments. If a UI element isn't used in the last 36 hours, it disappears from the list until it's used again.

Hover over items in the list to see what elements they correspond to in your application. Elements corresponding with a suggested Feature are highlighted as you hover over each one in the Suggested Features table.

Turn on the heatmap using the toggle at the bottom of the Page for a visual representation of how much engagement each of the suggested Features has received. You can select a heatmap item to highlight it in the suggested Features list.

Toggle on heatmap.png

The data you see in the Suggested Features list can be different from the data you see when you tag them to add them to your Features list. This is because suggested Features includes data from both your public and staging environments, whilst tagged Features include data only from your public environment.

Accept suggestions

Before making a decision to accept or delete a suggestion, hover over a suggested Feature from the list to see which UI element you would be tagging and how much usage that UI element has gotten.

To accept the suggested Feature, select Tag at the end of the suggested Feature's row. This moves the rule into the Features list with a processing status. Processing can take up to an hour.

tagsuggested features.png

Delete a suggestion

To delete the suggested Feature, select the trash icon at the end of the suggested Feature's row. This removes the suggested Feature from the list and doesn't suggest the Feature again. Deleted suggestions don't reappear in the list, but can be created manually following the instructions outlined in Tag a new Feature.

Edit tagged Features

  1. In the Tagged Features list, select the Feature name to rename it.
  2. Select a product area from the dropdown list.

    editfeaturename and product area.png

    You can always see how the changes affect the Feature rule before applying them:Screen_Shot_2022-02-06_at_14.17.01.png

Code-base solution for tagging Features

Note: Currently available for native iOS and Android apps, and React-Native apps only. We plan on adding this feature to Xamarin Forms in the future.

Pendo might not always recognize a Feature in your apps. It can either render it as untaggable in Pendo, or it does show as taggable but doesn't show any analytics. Our code-based solution solves this problem by allowing your mobile developers to tag and get analytics for any Feature using an API.

To implement this, your developer must set this up. See Setting up a code-based solution for Mobile Tagging.

 

Frequently asked questions

How are my Features identified?

  • A Feature is always tagged in the context of a Page.
  • A rule is created for each tagged Feature that relates to the "class" of the element, the element's text if such exists, its position in the list, its position on the Page, and many other parameters.
  • If a Feature is not identified correctly, contact Pendo Support so that we can modify the Feature's rule to match your needs.
  • Features will usually be identified correctly across your app versions. However, if you performed User Interface changes to your app and specifically changed button texts, you might need to Update the Mobile Page to make sure all Features are identified correctly and fix the tagging if needed. 

I hover above a Feature, but more than one Feature is highlighted instead of the desired one. What should I do? 

We now highlight all matching Features upon tag to prevent situations where Pendo's automatic feature identifier (rule) isn't enough to distinguish between several Features on the Page. This means, that without refining the automatic rules, these Features would count as the same Feature.
To fix this, tag the first C, refine its rules to be more specific to this Feature, and then tag the other Feature.

I can’t tag some of the Features in my application. What do I do?

There are many ways to implement mobile buttons within an App and we are optimizing the way our SDK identifies Features. However, if you’re unable to tag and receive analytics for specific mobile Features, contact Pendo Support. A possible workaround is using Track Events to track specific Features to collect that data.

Note: Pendo automatically tracks events for back button clicks on Android devices. This is relevant only when the app is in the foreground and in focus. These events are included in the path data, so you can see if the back button was clicked when navigating between pages. This event is not available for Guides and other analytics reports.

I stopped getting new analytics for some of the tagged Pages. Why is that?

Have you released a new app version to the store recently? If some of your Pages/Features changed in the newly released app version, you can update them by Updating the Mobile Page.

 

Was this article helpful?
1 out of 1 found this helpful