> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/bitly/faq.md).

# FAQ

<details>

<summary>Where do I find my Bitly API token?</summary>

Log in to Bitly and go to **Settings → Developer settings → API**. You'll see your personal access token there. If you haven't generated one yet, click the button to create it. Copy the full token and paste it into Coupler.io when setting up the connection.

</details>

<details>

<summary>Which Bitly plan do I need to use all entities?</summary>

Basic entities like Bitlinks, Bitlink clicks, Groups, and Organizations are available on most plans including Free. However, **Campaigns**, **Channels**, and **Bsds** require a paid plan (Teams or higher). If you get a 403 error on those entities, your plan likely doesn't include them.

</details>

<details>

<summary>Can I pull click data for all my Bitlinks at once?</summary>

Yes, but with caveats. The Bitlink clicks entity returns click counts across your links for the date range you specify. For accounts with a large number of links, pulling a very wide date range in one go can run into rate limits. It's better to use monthly date ranges and Append mode to build up history incrementally.

</details>

<details>

<summary>Can I combine Bitly data with data from other marketing tools?</summary>

Absolutely. Coupler.io supports multiple sources in a single data flow. You can use **Join** to merge Bitly click data with, say, campaign data from HubSpot or UTM data from Google Analytics. Use **Append** to stack data from multiple Bitly groups or accounts side by side.

</details>

<details>

<summary>Can I send Bitly data to an AI tool for analysis?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can route your Bitlink clicks or campaign data directly to these tools to generate summaries, spot trends, or draft reports automatically.

</details>

<details>

<summary>Why does my Bitlink clicks entity return empty rows?</summary>

This is almost always a date range issue. Bitly's clicks API requires explicit start and end dates — if your date range doesn't cover any period with click activity, you'll get an empty result. Double-check your date pickers and make sure the range overlaps with when your links were active.

</details>

<details>

<summary>What's the difference between Group shorten counts and Organization shorten counts?</summary>

Both track how many links were shortened, but at different levels. **Group shorten counts** shows activity per team or group within your org — useful if you want to see which team is creating the most links. **Organization shorten counts** rolls that up to the top level for an org-wide view.

</details>

<details>

<summary>Can I track QR code clicks through Coupler.io?</summary>

The **QR codes** entity returns QR code metadata and their associated Bitlink IDs. Click-level data for QR codes flows through the **Bitlink clicks** entity — join on `bitlink_id` to connect QR code info to its click performance.

</details>

{% hint style="info" %}
For a full breakdown of available fields per entity, see the [Data Overview](/sources/category/marketing/bitly/data-overview.md) article. For help with connection errors or missing data, check [Common Issues](/sources/category/marketing/bitly/common-issues.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/marketing/bitly/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.