Each of your users can have a set number of custom tags at one time. Check your plan limits, for the number of custom data tags per user.
There is no limit to the number of tag
key : value combinations you can set per user. For example, you can have any amount of different keys with an equally infinite amount of different values per key, but if you are on a free plan, only 2 of those keys can be set per user while professional plans can have up to 20 and enterprise can have up to 1,000. If you need more, contact our sales team to discuss more options.
Navigate to Audience > Users page "Tags" column or see Exporting User Data.
You can export the specific users over the plan limit within the dashboard Audience > Users > Export. Details in Bulk Updating User Attributes or Data Tags.
There are several options including API updates to uploading a CSV. See Tags: Tracking User Events and Attributes for a list of all options.
Your application will continue to have the data tags set per user. When adding or updating tags, you won't be able to make changes to users over your plan limits. This means if a user is at or over their tag limit, you will first need to delete the unwanted tags, then make another request to add or update the desired tags.
For example, if your account tag limit is 20 custom tags per user, then each user can only have 20 unique tag "keys" set at once.
If a user has 0 tags:
- Any request to set 1-20 tag keys, will succeed.
- Any request to set 21+ tag keys, will fail, no tags will be set.
If a user has 19 tags:
- A request to set 1 new tag key will succeed.
- A request to set 2+ new tag keys will fail, no new tags will be set.
- A request to update 1-19 of the currently set tag values and set 1 new tag will succeed.
- A request to update 1-19 of the currently set tag values and set 2+ new tag will fail. You need to make 2 requests. 1st to delete the unwanted tag keys, 2nd to set the new tag keys.
There are a few reasons why tags may not be set listed below.
The most common reason for tags not showing on a device is due to unstable or no network connection where the request to update the tags does not make it to OneSignal.
Android Mobile SDKs will cache data tags and will retry adding the tag upon detecting a stable internet connection.
iOS Mobile SDKs provides a callback for you to handle this case.
Web SDK, the user must be subscribed before the tag is added to the device record. Once the user registers, the tags will automatically be sent to our server as long as the page session is the same (the user has not navigated to another page).
Web SDK - If the person leaves the page before the tags are set, they will not get the tags.
When web subscribers clear their browser data/cookies/cache it destroys the push records for al sites that the user is subscribed under. OneSignal provides a feature to automatically resubscribe the user upon returning to the site with our SDK, but this will not add the tags back unless some additional steps are taken. See What happens when I clear browser cookies? for more details.
If you are having issues, plug the device into your IDE and use our
setLogLevelSDK method set to Verbose. Then attempt to reproduce the issue you are seeing. This will help log any issues to your IDE console to debug.
Updated 7 months ago