Adding Tags
Tags are metadata describing the data asset to improve record searchability.
Tags are included in the Title record and describe the represented data asset. Tags improve record searchability and come in handy when bulk searching and filtering licenses.
For example, maybe you have an ETL pipeline to extract a data signal from behavioral data for monetization on the Snowflake Marketplace. With a single API request, you can retrieve a list of all current behavioral data licenses for the use case. Use the Pointer Records in your extract query, or join against your existing results, and you're left with the approved dataset to publish. Slick 🤖.
Tags are an enumerated string, with support for custom tags in the format of custom:<custom_tag>
. Supported Enums:
Enum | Description |
---|---|
Contact Info | |
name | Such as first or last name |
email_address | Including but not limited to a hashed email address |
phone_number | Including but not limited to a hashed phone number |
physical_address | Such as home address, physical address, or mailing address |
contact_info | Any other information that can be used to contact the user |
Health | |
health | Health and medical data or health-related human subject research |
fitness | Fitness and exercise data |
Financial | |
payment_info | Such as form of payment, payment card number, or bank account number |
credit_info | Such as credit score |
financial_info | Such as salary, income, assets, debts, or any other financial information |
Location | |
precise_location | Information that describes the location of a user or device with the same or greater resolution as a latitude and longitude with three or more decimal places |
coarse_location | Information that describes the location of a user or device with lower resolution than a latitude and longitude with three or more decimal places |
Sensitive | |
sensitive_info | Such as racial or ethnic data, sexual orientation, pregnancy or childbirth information, disability, religious or philosophical beliefs, trade union membership, political opinion, genetic information, or biometric data |
Contacts | |
contacts | Such as a list of contacts in the user’s phone, address book, or social graph |
Content | |
messages | Including subject line, sender, recipients, and contents of the email, sms, or other text-based messages. |
photo_video | The user’s photos or videos. |
audio | The user’s voice or sound recordings |
gameplay_content | Such as saved games, multiplayer matching or gameplay logic, or user-generated content in-game |
customer_support | Data generated by the user during a customer support request |
user_content | Any other user-generated content |
Browsing | |
browsing_history | Information about content the user has viewed that is not part of your app, such as websites |
Search | |
search_history | Information about searches performed |
Identifiers | |
user_id | Such as screen name, handle, account ID, assigned user ID, customer number, or other user- or account-level ID that can be used to identify a particular user or account |
device_id | Such as the device’s advertising identifier, or other device-level ID |
Purchases | |
purchase_history | An account’s or individual’s purchases or purchase tendencies |
Usage | |
product_interaction | Such as app launches, taps, clicks, scrolling information, music listening data, video views, saved place in a game, video, or song, or other information about how the user interacts with your app |
advertising_data | Such as information about the advertisements the user has seen |
usage_data | Any other data about user activity in your app |
Diagnostics | |
crash_data | Such as crash logs |
performance_data | Such as launch time, hang rate, or energy use |
diagnostic_data | Any other data collected for the purposes of measuring technical diagnostics related to your app |
Other | |
custom:<xyz> | A custom tag relevant to your business |
If the tags look familiar, it's because we support the Apple Privacy Labels data types. You likely already had to declare these for your app, might as well reuse them.
Example:
TikiSdk.config()
.offer
.tag(TikiSdk.TitleTag.deviceId())
.tag(TikiSdk.TitleTag.custom('CUSTOM TAG'))
try? TikiSdk.config()
.offer
.tag(.deviceId)
.tag(TitleTag("CUSTOM TAG"))
TikiSdk
.offer
.tag(TitleTag.DEVICE_ID)
.tag(TitleTag("CUSTOM TAG"))
await TikiSdk.config()
.offer
.tag(TitleTag.deviceId())
.tag(TitleTag.custom("CUSTOM TAG"))
Updated 8 months ago