Metadata, Custom Issue Fields, and tags are different ways to represent data in Helpshift. Each of these data types has different functions which you should consider when planning your workflow. Metadata Metadata is device information that is collected out-of-the-box by our iOS/Android SDK when it is integrated into your app. This includes the user’s OS […]
HS-Tags are unique values that can be configured and paired with tags in the Dashboard to be automatically applied to new Issues when metadata or Custom Data thresholds are met. These tags appear in your Dashboard and allow you to organize, segment, and prioritize your users. A set of HS-Tags as listed on the metadata tab […]
You will notice a section titled ‘Custom Data’ in your metadata tab for in-app Issues. Custom Data is data that is unique to your app that is not collected by default that your developers can configure our SDK to collect. This data could include $ spent, User ID, install date, number of purchases, and anything […]
When an in-app user submits a new Issue, any metadata that the developers have set up is pulled in with the Issue. If any of the information changes while the Issue is open, such as if the end user updates their version of the app, the metadata associated with the Issue won’t update because it’s […]
Device information associated with Issues can be found within the ‘Metadata’ tab at the top of the Issue details page. This section contains device and OS information, as well as any debug logs and Custom Data sent through the SDK (for example, the metadata and HS-Tags your developer implemented). To learn more about metadata, Custom […]
Helpshift follows the ISO 3166-1 standard for country codes, and ISO-639-1 standard for language codes. A full list of the country and language codes associated with these standards can be found in the Wikipedia article for ISO 3166-1 alpha-2.