Attributes

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 attributes /#native app or attributes /#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 android / ios this attribute is always updated when attributes /#update all attributes or when a subscription is purchased 310 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type default "has active subscription" { "templates" { "name" "has active subscription" } } firebase "has active subscription" { "templates" { "name" "has active subscription" } } has active subscription code this attribute indicates if the user has any active subscription code android / ios this attribute is always updated when attributes /#update all attributes or whenever a subscription code is added or removed 310 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type default "has active subscription code" { "templates" { "name" "has active sub code" } } firebase "has active subscription code" { "templates" { "name" "has active sub code" } } has bookmarks this attribute indicates if the user has any bookmark on his device android / ios this attribute is always updated when attributes /#update all attributes or whenever a bookmark is added or removed 310 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type default "has bookmarks" { "templates" { "name" "has bookmarks" } } firebase "has bookmarks" { "templates" { "name" "has bookmarks" } } has entitlement login this attribute indicates if the user is currently logged in or logged out android / ios this attribute is always updated when attributes /#update all attributes or when a user logs in or logs out 310 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type default "has entitlement login" { "templates" { "name" "has entitlement login" } } firebase "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 android / ios this attribute is always updated when attributes /#update all attributes or when an issue is purchased 310 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type default "has purchased issue" { "templates" { "name" "has purchased issue" } } firebase "has purchased issue" { "templates" { "name" "has purchased issue" } } experience currently no specific experience attributes are existing