What types of Tags should I set in Airship?

The types of tags and Custom Events can differ depending on your vertical and your use case. However, we've found the following use cases to be fairly common amongst several verticals that will be useful as you implement Tags into your application.

To help alleviate some of the confusion around tagging, below we've provided a list of tags and the associated code you can use to set tags based off of your app vertical.

Some tags cannot be set on app launch, so you'll need the app to determine when and where to set the tags, such as page views, for tagging certain features.  
With tag groups, it is possible to set tags from both the client and the server. However, you must ensure that both sources are not setting tags in the same tag group. By default, the client sets tags in the device_tags group, so any tags set via the API should be placed in a different tag group. Failure to do so may result in the accidental deletion of tags.  

Setting Tags requires very little code. As an example, you can add and remove a tag by making the following method call:

Airship.channel.editTags { editor in
    editor.add("a_tag")
    editor.remove("three")
}

More importantly, when you're setting tags, it's important to note when and where you add or remove tags within your app as you build your campaigns in Airship. This will help you build and automate more sophisticated campaigns as you grow your app.

Pairing tags with custom events

In some cases, you may also want to track the occurrences of an action in addition to setting a tag. By pairing a custom event with a tag you can track user activities and tie them back to corresponding push messaging campaigns. For example, you would track a user registration event by adding a custom event at the point of user registration.

Retail Tags

For retail, consider adding a tag whenever your users engage with a particular product or app feature. For example, when your users add an item to their cart, you may wish for that to be a tag that indicates that that user took that action. Below is a list of some possible scenarios you would wish to track user engagement.

  • Registered User/Authenticated
  • Visited Product category
  • Used App Feature
  • Favorited an item
  • Added an item to cart/wishlist
  • Purchased an item

Media Tags

For media, consider adding a tag whenever a user engages with your platform, whether it is browsing a particular article or viewing a video, or simply using some other feature in your app. Below is a list of some possible scenarios you may wish to track.  

  • Registered User/Authenticate
  • Browse a particular article/section
  • Subscriber or Non-subscriber
  • Watched Video
  • Shared or favorited an article/video
  • Used App Feature

Travel Tags

For travel and hospitality, consider tags where you can track user engagement but also user preferences and transactional behavior. Consider the following use cases:

  • Registered User/Authenticate
  • Home city/Airport 
  • Used App Feature
  • Favorites a location, resort, etc.
  • Loyalty member vs. Non Loyalty Member 
  • Added an item to cart/wishlist
  • Business vs. Personal travel
  • Completed Checkout 

Related Content:

Was this article helpful?
0 out of 0 found this helpful
Submit a request