Bitly ProfileData provides useful account-level metadata that supports personalization, analytics, and team workflows. Because it often contains PII and usage metrics, careful attention to access control, encryption, token management, and compliance is essential to mitigate privacy and security risks.
An example of ProfileData from an authenticated API response (fields illustrative): bitly profiledat
"id": "123456",
"login": "exampleuser",
"name": "Example User",
"email": "user@example.com",
"avatar_url": "https://bit.ly/avatars/123.png",
"plan": "enterprise",
"created_at": "2021-05-01T12:00:00Z",
"timezone": "America/Los_Angeles",
"total_links": 482,
"total_clicks": 125432,
"default_domain": "bit.ly",
"team":
"id": "team_789",
"members_count": 5,
"roles": ["admin","member"]
,
"integrations": [
"name":"slack","enabled":true,
"name":"zapier","enabled":false
]
Use the GET /v4/bitlinks/bitlink/clicks endpoint to retrieve raw click data. Example request: the field returns null .
curl -X GET "https://api-ssl.bitly.com/v4/bitlinks/bit.ly/example/clicks?unit=day&units=30" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
Response includes timestamps, referrers, and geolocation data suitable for feeding into a data warehouse or BI tool like Tableau, Power BI, or Google Looker Studio. Response includes timestamps
If you wish to remove your profile data entirely:
Only if you are on an enterprise plan and have enabled “detailed click tracking” in your group settings. Otherwise, the field returns null.