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

# FAQ

<details>

<summary>Where do I find my Amplitude API key and Secret key?</summary>

In Amplitude, go to **Settings → Projects**, select your project, and open the **General** tab. You'll see both the **API key** and **Secret key** listed there. Note that these are project-level credentials — each project has its own unique pair.

</details>

<details>

<summary>Can I pull data from multiple Amplitude projects into one destination?</summary>

Yes. Add multiple sources to the same data flow — one per Amplitude project, each with its own API credentials. Use the **Append** transformation to combine the data into a single table. This is useful if you have separate Amplitude projects for iOS and Android apps and want a unified view.

</details>

<details>

<summary>Why does the Events entity take so long to load?</summary>

The Events entity uses Amplitude's Export API, which can be slow for large date ranges or high-volume projects. Reduce the **request time range** parameter to a smaller number of hours to break the request into smaller batches. Start with 6 hours and go lower if you still experience timeouts.

</details>

<details>

<summary>Can I use Amplitude data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including **ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw**. You can pipe your Amplitude events or active user data directly into these tools and ask natural language questions about user behavior, drop-off points, or engagement trends.

</details>

<details>

<summary>Why are my event_properties showing as a long string instead of separate columns?</summary>

Amplitude stores event and user properties as nested JSON objects. Spreadsheet destinations like Google Sheets display these as raw JSON strings. If you need individual property values as separate columns, consider exporting to BigQuery where JSON is natively supported, or use Coupler.io's transformation features to extract specific fields.

</details>

<details>

<summary>What's the difference between Events and Events list?</summary>

**Events** returns raw event records — every individual action a user took, with timestamps and properties. **Events list** returns the catalog of event *types* defined in your project (e.g., `page_viewed`, `purchase_completed`) along with total occurrence counts. Use Events list to audit your tracking taxonomy; use Events for behavioral analysis.

</details>

<details>

<summary>Can I join Amplitude data with data from another source?</summary>

Yes. Coupler.io's **Join** transformation lets you combine Amplitude data with data from other sources — for example, joining Amplitude Events with Salesforce or HubSpot CRM data on a shared user ID, or joining Active users with ad spend data from Google Ads to calculate cost per active user.

</details>

<details>

<summary>Does Coupler.io support historical backfills for Amplitude data?</summary>

Yes — set your start date using the date picker to any date after your Amplitude project was created. Keep in mind that very long historical ranges can trigger timeout errors for the Events entity. Pull history in chunks by adjusting the request time range parameter.

</details>

{% hint style="info" %}
For details on what fields are available per entity, see [Data Overview](/sources/category/marketing/amplitude/data-overview.md). If you're hitting timeout or connection errors, check [Common Issues](/sources/category/marketing/amplitude/common-issues.md) for specific fixes. For tips on structuring your data flow efficiently, see [Best Practices](/sources/category/marketing/amplitude/best-practices.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/amplitude/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.