Common Issues

Connection issues

My API token is not accepted

Make sure you're using a personal access token, not an OAuth client secret. In Bitly, go to Settings → Developer settings → API and generate a new token if needed. Tokens are long strings starting with a mix of letters and numbers — double-check there are no extra spaces when pasting.

The data flow connects but returns no data

Check that your Bitly account has data for the entity you selected. For example, if you selected Campaigns but haven't created any campaigns, the response will be empty. Also verify your date range covers a period when links were active.

Missing data

Bitlink clicks show zero even though I know links were clicked

This almost always comes down to the date range. Bitly's click data API requires an explicit start and end date — if the date range doesn't overlap with when the clicks occurred, you'll get zeros. Use the date pickers to set a range that covers the relevant period.

Some entities return no rows on my paid plan

Certain entities like Campaigns and Channels are only available if you've actually created them in Bitly. An empty result is not an error — it means there's no data of that type in your account yet.

I can't see links from other groups in my organization

Your API token is scoped to your own user permissions. If you don't have access to certain groups in the Bitly UI, the API will not return their data either. Ask your Bitly org admin to grant you the appropriate group access.

Permission errors

I get a 403 error when pulling Campaigns or Channels

Campaigns and Channels are features available on Bitly's paid plans (Teams and above). If your account is on a Free or Basic plan, these endpoints will return a 403 permission error. Upgrade your Bitly plan or use entities available on your current tier.

API returns 401 Unauthorized

Your token may have been revoked or regenerated in Bitly. Go to Settings → Developer settings → API in Bitly, copy the current token, and update it in your Coupler.io data flow connection settings.

Data discrepancies

Click counts in Coupler.io don't match the Bitly dashboard

Bitly's dashboard may apply different date boundaries or time zones than your API query. Make sure your start and end dates in Coupler.io match exactly what you're comparing in the Bitly UI. Also note that the Bitly dashboard sometimes shows real-time data that takes a few hours to appear in the API.

Rate limits

My data flow fails with a rate limit error

Bitly enforces API rate limits that vary by plan. If you're pulling a large number of Bitlinks or running frequent syncs, you may hit these limits. Try narrowing your date range, reducing sync frequency, or splitting entities across separate data flows. Free plan users have significantly lower rate limits than paid plans.