What happens if I set application_specific to false when creating a tag via the API?

The current /addTag reference documents only three tag parameters - tag.name, tag.type and tag.user_specific. There is no supported application_specific parameter, so passing it has no documented effect; if you send it against a legacy account, treat the behaviour as unsupported.

What actually controls scope is user_specific:

user_specific: false (default) - a General tag. The value is stored per device (HWID), so each device of the same person can hold a different value.
user_specific: true - a User-specific tag. The value is stored on the user profile (UserID) and applies to all of that user's devices when set by UserID.

So setting anything to false never makes a tag user-specific - you must explicitly pass user_specific: true.

Example:

{
  "request": {
    "auth": "API_ACCESS_TOKEN",
    "tag": {
      "name": "subscription_tier",
      "type": 2,
      "user_specific": true
    }
  }
}

If you need existing device-level values moved onto user profiles, contact support - the conversion is a backend migration, not a Control Panel setting.

Comments

Have a question?

Articles in this section