| Tool | Profile Data Field | Available in Free Tier? | |------|--------------------|--------------------------| | Rebrandly | click_metadata | No | | TinyURL (Enterprise) | tracking_details | No | | Short.io | geo , device | Partial (last 7 days) | | ClickMeter | data_extra | Yes (capped) |
Introduction: What is "Bitly Profiledat"? If you’ve recently dug into Bitly’s advanced analytics, examined a JSON payload from Bitly’s API, or reviewed a data export from an enterprise account, you may have stumbled upon an odd field label: profiledat (sometimes seen as profile_dat or profileData ). At first glance, it looks like a typo or a placeholder. In reality, it is one of the most powerful—yet under-documented—components of Bitly’s link intelligence platform. bitly profiledat
"clicks": [ "ts": "2025-04-01T14:32:11Z", "profiledat": "country": "DE", "region": "BY", "city": "Munich", "device": "iPhone14,2", "os": "iOS 17.4", "browser": "Safari", "referer": "https://twitter.com", "campaign_id": "spring_25" ] | Tool | Profile Data Field | Available in Free Tier
However, none use the exact profiledat field name—that remains unique to Bitly’s internal schema. In 2025, Bitly began testing Predictive Profiledat (beta). Instead of just historical data, Bitly’s model appends a predicted_interest array based on click patterns of similar users. For example: At first glance, it looks like a typo or a placeholder
https://api-ssl.bitly.com/v4/bitlinks/bitlink/clicks?unit=day&units=-1&size=1000 Include header: Authorization: Bearer YOUR_TOKEN In the JSON response, each click event contains a profiledat object. Example snippet:
"profiledat": "predicted_interest": ["SaaS", "DevOps", "Cloud Security"]