Tags

Play

Tags are one of the most useful tools we offer — a lot of sophisticated Pushwoosh functionality is based on this feature. Using tags, you can segment your audience and send push notifications to some users, but not others.

Deciding which tags to use

First, think about your business needs and decide how you want to segment your audience. Do you need to target users based on age, location, in-app purchase history, etc.? Once you’ve decided on segmentation logic, your developers can add tags to your app’s code, which will then allow you to send targeted messages to your users.

Tags contain any arbitrary data that you associate with a particular user or device, whether it’s username, ID, city, favorite football team, preferred news categories, or any other piece of information about your users. Let’s take a closer look.

Tag Values

Tag values can help you make your push campaigns smarter. Each tag is capable of storing nearly limitless number of values. Basically, this means that one tag would be enough to record a specific type of information about each end-user in your database.

There are only a few tags available for each account, but considering the nearly-infinite space for each tag, just a couple of tags are enough to gather an enormous amount of information about your users and set up very complex targeting patterns.

Types of Tags

• Integer — used for the integer data (amount of in-game cash acquired, level achieved, age).
• String — used for string values (username, e-mail, identifiers).
• List — the same as String type, but each user may have multiple values set simultaneously (music preferences, news categories, cuisine preferences).
• Boolean — true / false type of Tag.
• Date — used for calendar dates. Basically, this is an integer type tag which stores Unix Epoch timestamps (automatically converted from/into Gregorian date).
• Price — allows to set values according to specified currency in the “*.XX” format (https://en.wikipedia.org/wiki/ISO_4217).
• Version — used for versioning. The example of allowed format is w.x.y.z (Major.Minor.Patch.Build). Max value for each version part is 9999, so the max version number cannot be greater than 9999.9999.9999.9999.

Tag operators

Each Tag type has a specific set of operators applicable. Tag operators define the relationship between the Tag and its values for segmentation purposes.

• Integer Tag operators: is, is not, are, not in, not set, any
• String Tag operators: is, is not, are, not in, not set, any
• List Tag operators: in, not in, not set, any
• Boolean Tag operators: is (true/false), not set, any
• Date Tag operators: exactly on, on or after, on or before, between, not set, any
• Price Tag operators: is, is not, greater or equals, less or equals, between, in, not in, not set, any
• Version Tag operators: is, is not, greater or equals, less or equals, between, in, not in, not set, any

Note

“Not set” and “any” operators are available for all types of Tags.

Application Specific / Nonspecific Tags

This parameter describes tags’ behavior in relations to different apps in the same account. Application specific tags can have different sets of values for each app on the same account. Application nonspecific tags, on the contrary, store the same value for all apps that use this Tag.

Example

Let’s say you have two apps, a News app and a Game, and you want to target only those users who have explicitly agreed to receive pushes from you. So, you create a boolean tag called “Subscribed” and set "true" value for users who want to receive pushes from you, and "false" for those who don’t want to be notified.

One of your users, Anna, have installed both of your apps. She is okay with being notified about some breaking news, but opted out of any pushes from the Game app.

If the “Subscribed” tag is application specific, everything will go as planned. However, in case this tag was application nonspecific, then each of your apps will overwrite the value set by another app, which can ruin your targeting and cause frustration.

On the other hand, application nonspecific tags might come in handy if you want to perform cross-application targeting and trace users who have the same username in different applications.

User-specific Tags

All Tags in Pushwoosh are user-specific by design and are assigned for all user’s devices when set by UserID instead of HWID.

Default Tags

These tags are available by Pushwoosh out-of-the-box, so you don’t have to (and, in fact, should not) set them manually. Most of them are set from the application and sent over to our server via registerDevice and other API calls, and some are set by the server itself.

Name	Type	Where it’s set	Description
Application Version	Version	SDK	Current version of the app installed on a device
Browser Type	String	SDK	When a device is registered for your web project, its type – mobile or desktop – is tracked automatically
City	String	Server	Latest registered geographical location of a device
Country	String	Server	Latest registered geographical location of a device
Device Model	String	SDK	Indicates the device model whereon the app is installed
First Install	Date	Server	Indicates the time when a device was registered for notifications for the first time
In-App Product	List	SDK	The in-app products purchased by a user of the app
Last In-App Purchase Date	Date	SDK	The date of the latest in-app purchase made on a device
Language	String	SDK	Two-letter lowercase abbreviation of a device’s locale according to ISO-639-1; taken from device settings
Last Application Open	Date	Server	The time of the most recent app launch on a device
OS Version	Version	SDK	The version of an operating system running on a device
Platform	String	SDK	The platform on which the user is using your project.
Push Alerts Enabled	Boolean	SDK	Indicates whether push alerts are allowed in device settings
SDK Version	Version	SDK	The version of the Pushwoosh SDK implemented on a device
Unsubscribed Emails	Boolean	SDK	Indicates whether a user has unsubscribed from receiving emails from your app
Live Activity ID	String	SDK	Used to manage live activities by associating a Live Activity ID with the device. Automatically cleaned up after 12 hours.

Custom Tags

This is where your creativity comes in to achieve your specific business goals. Custom tags can be created based on the segmentation logic or targeting pattern that is appropriate for your unique business needs.

How to set up a custom tag

Developer assistance needed

You’ll need help from your development team to set up custom tags.

To begin, create and configure tags in the Pushwoosh Control Panel:

1. Go to the Tags page of your Control Panel and click Add tag.
2. Name your tag, pick the type, and decide whether it should be app-specific or not.
3. Click Save Tag.

Developer assistance needed

At this point, the custom tag is ready, but it will require your developer to implement it in the app to start collecting information from users. Please share this guide with your development team.

Using the default City tag

Device’s location is determined based on its IP address at the moment your app was launched on that device for the last time. GeoIP submits the location data to Pushwoosh, and Pushwoosh saves the location received from GeoIP as a City tag value for a particular device.

In some cases, the location submitted by the GeoIP differs from the city name — for example, when it refers to an area of a city or other administrative unit. Please be careful when using the default City tag for segmentation purposes: make sure to select the proper values.

For example, if you’re going to target users from Munich, you have to cover it with a bunch of City tag values, including “Munich” itself (with all the corresponding values, such as different variants of spelling which could be returned by GeoIP and saved as tag values) and several nearby areas.

Tags Statistics

Once your application sets Tag values, you can view and analyze the statistics about these values, presented in the Control Panel using either a pie chart, bar chart, or table view.