> 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/finance-and-accounting/chartmogul/faq.md).

# FAQ

<details>

<summary>Where do I find my ChartMogul API key?</summary>

Log into ChartMogul and go to **Profile → API Keys**. Your secret key is listed there. If you haven't generated one yet, click **Create API Key**. Copy the secret key (not the account token) and paste it into Coupler.io when setting up the data flow.

</details>

<details>

<summary>Which entity should I use for MRR reporting?</summary>

For trend reporting, **Customer monthly counts** gives you a clean time series of active customer numbers, but it doesn't include MRR directly. For MRR values, use the **Customers** entity — each record includes the customer's current `mrr` contribution. To see MRR movements over time (new, expansion, churn), use the **Activities** entity filtered by event type.

</details>

<details>

<summary>Can I combine data from multiple ChartMogul accounts?</summary>

Yes. Create a separate source connection in Coupler.io for each ChartMogul account, then use the **Append** transformation to merge the data into a single output. This is useful if you run multiple products or brands under separate ChartMogul workspaces.

</details>

<details>

<summary>Why do my customer counts not go back to our company's founding date?</summary>

ChartMogul calculates customer counts from the date your billing integration was first connected, not from your company's founding date. Historical data before the integration was set up may not be available unless you performed a historical data import in ChartMogul.

</details>

<details>

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

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can pipe your Activities or customer count data directly into these tools to generate automated insights, churn commentary, or revenue summaries on a scheduled basis.

</details>

<details>

<summary>How do I track churn specifically?</summary>

Use the **Activities** entity and filter by `type = churn`. Each churn event includes the customer UUID, the date, and the MRR lost. You can Join this with the Customers entity on `customer_uuid` to add plan, country, or LTV context to each churn event.

</details>

<details>

<summary>What's the difference between the four customer count cadences?</summary>

All four entities (daily, weekly, monthly, quarterly) return the same two fields — a date and a customer count — but at different time granularities. Use daily for operational monitoring, weekly for team standups, monthly for MRR reports, and quarterly for investor or board presentations.

</details>

{% hint style="info" %}
For a full breakdown of available fields and metric combinations, see the [Data Overview](/sources/category/finance-and-accounting/chartmogul/data-overview.md) article. For sync errors and missing data, check [Common Issues](/sources/category/finance-and-accounting/chartmogul/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/finance-and-accounting/chartmogul/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.