# Common Issues

## Connection issues

<details>

<summary>"OAuth connection failed" or "Access denied"</summary>

Vimeo's OAuth may fail if:

* Your Vimeo account doesn't have permission to access video data
* You accidentally denied permission during the sign-in flow
* Your Vimeo session has expired

**Fix:** Disconnect and reconnect the Vimeo account. When prompted, explicitly approve all permissions. If the issue persists, check that you're signing in with the correct Vimeo account.

</details>

<details>

<summary>"No videos found" in "My account videos"</summary>

This typically means your Vimeo account has no videos, or the data flow is looking at a Vimeo organization account.

**Fix:** Sign in to the personal Vimeo account that contains your videos. If you manage an organization, use the account associated with the videos you want to export.

</details>

## Missing data

<details>

<summary>"Search keywords" field is disabled or hidden</summary>

The search keywords field only appears when you select "Public videos search" as the report type.

**Fix:** Scroll up and change the report type to "Public videos search," then the keywords field will appear.

</details>

<details>

<summary>User location or website data is empty</summary>

Vimeo users control whether their location, website, and bio are public. If a field is blank, it means the video creator has not made that information public.

**Fix:** This is expected behavior and not an error. You can filter out rows with missing location data using advanced filters in your destination (Google Sheets, BigQuery, etc.).

</details>

<details>

<summary>Video stats (plays, likes, comments) are zero or missing</summary>

New videos or videos with low visibility may not have any stats yet. Also, if a video is private or in draft status, stats may not be available.

**Fix:** Check the video's status ("Video: Status" column) and play status. Only published, playable videos will have reliable stats. Wait 24 hours after publishing for stats to populate.

</details>

## Permission errors

<details>

<summary>"You don't have permission to access this data"</summary>

Your Vimeo account may not have the right permissions, or Coupler.io's access has been revoked.

**Fix:** Check your Vimeo account settings to ensure you're the account owner or have admin privileges. Then disconnect and reconnect Coupler.io in your Vimeo account settings (Settings > Applications > Connected Apps).

</details>

## Data discrepancies

<details>

<summary>Play counts or engagement metrics don't match Vimeo's dashboard</summary>

Vimeo's public data API may lag slightly behind real-time stats, and different time zones can affect date-based filtering.

**Fix:** Allow 1–2 hours for stats to sync. If discrepancies persist, check that you're using the same date range and filters in both places. Date-based comparisons should use the same time zone in your destination tool.

</details>

<details>

<summary>Video appears in search but not in "My account videos"</summary>

Public videos search shows all public videos matching your keywords, including videos from other creators. "My account videos" shows only videos you've uploaded.

**Fix:** This is expected. Use "My account videos" for your library and "Public videos search" for research.

</details>

## Rate limits

<details>

<summary>Data flow is slow or timing out on large searches</summary>

Searching for very popular keywords (e.g., "video") can return thousands of results, which may take longer to process.

**Fix:** Use more specific keywords to narrow results. If you're exporting a large number of your own videos, split them into multiple data flows by date range using advanced filters.

</details>


---

# Agent Instructions: 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:

```
GET https://docs.coupler.io/sources/category/marketing/vimeo-public-data/common-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.