> 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/sales/clazar/common-issues.md).

# Common Issues

## Connection issues

<details>

<summary>My API key is rejected during setup</summary>

Double-check that you're copying the full API key from Clazar without any leading or trailing spaces. API keys are case-sensitive. If the key still doesn't work, try regenerating it in Clazar under Settings > API and entering the new one in Coupler.io.

</details>

<details>

<summary>The data flow connects but returns no rows</summary>

Some Clazar analytics entities — especially GCP and Azure — only return data once transactions or activity have occurred on that marketplace. If you've never sold on a particular platform, the corresponding analytics entity will be empty. Try a different entity like Buyers or Opportunities to confirm the connection is working.

</details>

## Missing data

<details>

<summary>GCP incremental insights are missing historical data</summary>

Incremental entities (GCP daily incremental insights, GCP monthly incremental insights) are designed to return changes since the last sync, not full historical datasets. If you need historical data, use the non-incremental GCP daily insights or GCP monthly insights entities instead.

</details>

<details>

<summary>Azure metered usage data is empty</summary>

The Azure metered usage entity only contains data if your Azure Marketplace listing uses consumption-based (metered) billing. If your listing uses a flat-rate or subscription model, this entity will always be empty.

</details>

<details>

<summary>Co-sell opportunities are missing deals I can see in Clazar</summary>

Co-sell opportunity entities (AWS and Azure) reflect only partner-referred deals, not all opportunities. Standard opportunities that originated outside a co-sell motion won't appear here. Check the main Opportunities entity for a complete pipeline view.

</details>

## Permission errors

<details>

<summary>I get a permission error when pulling analytics entities</summary>

Analytics access in Clazar may require elevated API permissions. Check that your API key belongs to a user role with analytics access enabled. If you're unsure, ask your Clazar account admin to verify the permissions associated with your API key.

</details>

## Data discrepancies

<details>

<summary>AWS revenue and disbursements don't match</summary>

This is expected behavior. AWS Marketplace collects revenue from buyers and disburses it to vendors on a separate schedule, typically with a delay of 30–60 days. Revenue records the transaction date; disbursements record when funds were paid out. These will rarely match within the same period.

</details>

<details>

<summary>GCP daily and monthly insights show different totals for the same period</summary>

GCP computes daily and monthly insights independently, and rounding or attribution differences can produce small variances. For financial reporting, use monthly insights as the authoritative source. Daily insights are better suited to trend monitoring.

</details>

## Rate limits

<details>

<summary>My data flow fails with a rate limit error</summary>

Clazar's API has rate limits that apply per key. If you're running multiple data flows using the same API key simultaneously, you may hit these limits. Stagger your data flow schedules by at least a few minutes between runs, or reduce the number of entities in a single data flow.

</details>


---

# 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/sales/clazar/common-issues.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.