SELECT profiledat->>'country' AS country, profiledat->>'device_type' AS device_type, COUNT(*) AS clicks FROM bitly_click_logs WHERE click_date = '2025-04-01' GROUP BY 1, 2 ORDER BY clicks DESC; This returns real-time device/country breakdowns without touching Bitly’s UI. If you cannot access Bitly Enterprise, consider these tools with comparable profile data:
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:
"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" ]
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.
