> 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/faq.md).

# FAQ

<details>

<summary>Can I combine AWS, Azure, and GCP revenue into one report?</summary>

Yes. Add all three revenue entities (AWS marketplace revenue, Azure marketplace revenue, and GCP charges and usage) as sources in a single data flow, then use the **Append** transformation to merge them into one table. Make sure the field names align — you may need to rename a few columns in the transformation step.

</details>

<details>

<summary>What's the difference between opportunities and co-sell opportunities?</summary>

The standard **Opportunities** entity covers all potential deals across your marketplace channels, regardless of how they originated. The **co-sell opportunities** entities (available for both AWS and Azure) contain only deals that involve a cloud provider's sales team — where AWS or Microsoft is actively co-selling with you. Keep both in your pipeline reporting to get the full picture.

</details>

<details>

<summary>How do private offers relate to contracts?</summary>

A **private offer** is a custom pricing proposal sent to a specific buyer. A **contract** is the executed agreement after the buyer accepts. Not all private offers become contracts. Joining these two entities lets you calculate private offer acceptance rates.

</details>

<details>

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

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. This is particularly useful for feeding GCP insights or cross-cloud revenue data to an AI tool to identify trends, anomalies, or forecasting signals without building a dashboard.

</details>

<details>

<summary>Why does my GCP disbursements summary show different totals than the detailed disbursements entity?</summary>

The disbursements summary entity aggregates and rounds values for high-level reporting. The detailed disbursements entity contains individual transaction records. Use the detailed entity when you need precision (e.g., finance reconciliation) and the summary for executive-level dashboards.

</details>

<details>

<summary>How many entities can I add to a single data flow?</summary>

There's no hard cap, but adding too many entities — especially large analytics streams — can slow down your runs. A good rule of thumb is to group related entities (e.g., all AWS analytics together) and keep each data flow focused on a specific reporting use case.

</details>

<details>

<summary>Do I need a separate API key for each marketplace (AWS, Azure, GCP)?</summary>

No. Clazar uses a single API key that covers all the marketplaces you've connected within your Clazar account. One key in Coupler.io gives you access to all available entities across AWS, Azure, and GCP.

</details>

{% hint style="info" %}
For a full list of available entities and fields, see the [Data Overview](/sources/category/sales/clazar/data-overview.md) page. If you're running into connection or sync errors, check [Common Issues](/sources/category/sales/clazar/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/sales/clazar/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.