Attributes

13min

Getting started
In the graphic below you can see the part that is covered in this chapter:
﻿
A purple application technically consists of a native part and an experience part that runs within a web view. 
The attributes in this documentation are listed under the Native app﻿ or Experience﻿ subchapters based on the origin they occur.
Update all attributes
The values of some attributes depend, for example, on purchase options or user actions and must be updated when changes occur. These conditions are as follows:
Account state did change (e.g. account has been logged out)
Any purchase state did change (e.g. after restoring purchases)
Subscription codes did change (e.g. user added a new one)
Entitlement state did change (e.g. user did log in or did log out)
In addition to the state changes mentioned above all known attributes are always updated when the app started or resumed from background. 
Native app
HAS_ACTIVE_SUBSCRIPTION
This attribute indicates if the user has any active app store subscription.
Trigger
Specification
Examples
Android / iOS: 
This attribute is always updated 
when all are updated﻿ or
when a subscription is purchased.
Key
Type
HAS_ACTIVE_SUBSCRIPTION
Boolean
﻿
Default
Firebase
"HAS_ACTIVE_SUBSCRIPTION": {
    "templates": {
        "name": "has_active_subscription"
    }
}
"HAS_ACTIVE_SUBSCRIPTION": {
    "templates": {
        "name": "has_active_subscription"
    }
}
﻿
﻿
HAS_ACTIVE_SUBSCRIPTION_CODE
This attribute indicates if the user has any active subscription code. 
Trigger
Specification
Examples
Android / iOS: 
This attribute is always updated 
when all are updated﻿ or
whenever a subscription code is added or removed. 
Key
Type
HAS_ACTIVE_SUBSCRIPTION_CODE
Boolean
﻿
Default
Firebase
"HAS_ACTIVE_SUBSCRIPTION_CODE": {
    "templates": {
        "name": "has_active_sub_code"
    }
}
"HAS_ACTIVE_SUBSCRIPTION_CODE": {
    "templates": {
        "name": "has_active_sub_code"
    }
}
﻿
﻿
HAS_BOOKMARKS
This attribute indicates if the user has any bookmark on his device.
Trigger
Specification
Examples
Android / iOS: 
This attribute is always updated 
when all are updated﻿ or
whenever a bookmark is added or removed. 
Key
Type
HAS_BOOKMARKS
Boolean
﻿
Default
Firebase
"HAS_BOOKMARKS": {
    "templates": {
        "name": "has_bookmarks"
    }
}
"HAS_BOOKMARKS": {
    "templates": {
        "name": "has_bookmarks"
    }
}
﻿
﻿
HAS_ENTITLEMENT_LOGIN
This attribute indicates if the user is currently logged in or logged out. 
Trigger
Specification
Examples
Android / iOS: 
This attribute is always updated 
when all are updated﻿ or
when a user logs in or logs out. 
Key
Type
HAS_ENTITLEMENT_LOGIN
Boolean
﻿
Default
Firebase
"HAS_ENTITLEMENT_LOGIN": {
    "templates": {
        "name": "has_entitlement_login"
    }
}
"HAS_ENTITLEMENT_LOGIN": {
    "templates": {
        "name": "has_entitlement_login"
    }
}
﻿
﻿
HAS_PURCHASED_ISSUE
This attribute indicates whether the user purchased an issue purchased through a single purchase product.
Trigger
Specification
Examples
Android / iOS: 
This attribute is always updated 
when all are updated﻿ or
when an issue is purchased.
Key
Type
HAS_PURCHASED_ISSUE
Boolean
﻿
Default
Firebase
"HAS_PURCHASED_ISSUE": {
    "templates": {
        "name": "has_purchased_issue"
    }
}
"HAS_PURCHASED_ISSUE": {
    "templates": {
        "name": "has_purchased_issue"
    }
}
﻿
﻿
Experience
Currently no specific experience attributes are existing. 

Key	Type
HAS_ACTIVE_SUBSCRIPTION	Boolean

Key	Type
HAS_ACTIVE_SUBSCRIPTION_CODE	Boolean

Key	Type
HAS_BOOKMARKS	Boolean

Key	Type
HAS_ENTITLEMENT_LOGIN	Boolean

Key	Type
HAS_PURCHASED_ISSUE	Boolean

Updated 08 Jul 2024

Did this page help you?

Purchase events

Placeholder