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

# Appcues

Connect Appcues to Coupler.io to export flows, banners, checklists, and segments into Google Sheets or BigQuery for product adoption analysis.

Appcues is a product adoption platform that lets you create in-app experiences — onboarding flows, banners, checklists, tooltips, and more — without writing code. It helps product and growth teams guide users through key moments in the product lifecycle. Connecting Appcues to Coupler.io lets you pull all your experience data into the tools you already use for analysis and reporting.

**Why connect Appcues to Coupler.io?**

* Export flows, banners, checklists, pins, launchpads, segments, and tags into a single destination
* Combine Appcues data with other sources (e.g., your CRM or analytics tool) using Join or Append transformations
* Keep dashboards in Google Sheets, Looker Studio, or BigQuery automatically updated with the latest experience data
* Send Appcues content metadata to AI destinations like ChatGPT or Claude for content audits or optimization suggestions

## Prerequisites

* An active Appcues account
* Access to your Appcues API key (available under account settings)
* A Coupler.io account (free plan works to get started)

## Quick start

{% hint style="success" %}
If you want a broad content audit, start by connecting the **Flows** and **Checklists** entities together in one data flow. Use the Append transformation to stack them and get a unified view of all active onboarding experiences.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account, go to the Data Flows section, and click **Add data flow**. Search for and select **Appcues** as your source.
{% endstep %}

{% step %}
**Enter your Appcues API key.** In your Appcues account, navigate to **Settings > API** and copy your API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose the Appcues entity you want to export — Flows, Banners, Checklists, Pins, Launchpads, Segments, or Tags. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, Gemini, Cursor, Perplexity, or OpenClaw.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your Appcues data will appear in the destination you selected.
{% endstep %}
{% endstepper %}

## Available entities

| Entity     | What it contains                                            |
| ---------- | ----------------------------------------------------------- |
| Flows      | Multi-step user guides and tutorials with targeting details |
| Banners    | In-app announcement and promotional messages                |
| Checklists | Task-based onboarding lists                                 |
| Pins       | Tooltip-style UI elements pointing to specific features     |
| Launchpads | In-app hubs collecting multiple Appcues experiences         |
| Segments   | User groups targeted by behavior or attributes              |
| Tags       | Labels used to categorize and organize Appcues content      |

## Appcues data overview

Appcues exposes metadata about your in-app experiences and the targeting rules behind them. Through Coupler.io, you can export seven entities that cover the full range of experience types — from guided flows to passive banners — as well as the organizational layer (tags, segments) that controls who sees what.

## Entities summary

| Entity     | Best used for                                                |
| ---------- | ------------------------------------------------------------ |
| Flows      | Auditing multi-step onboarding guides and step-level content |
| Banners    | Tracking announcements and promotion configurations          |
| Checklists | Monitoring task-based onboarding completion structures       |
| Pins       | Reviewing tooltip placement and feature callouts             |
| Launchpads | Understanding how experiences are bundled for users          |
| Segments   | Analyzing audience targeting rules and user groupings        |
| Tags       | Organizing and filtering content by label                    |

## Available fields

#### Flows

| Field           | Description                              |
| --------------- | ---------------------------------------- |
| Flow ID         | Unique identifier for the flow           |
| Name            | Display name of the flow                 |
| State           | Published, draft, or archived status     |
| Steps           | Number of steps in the flow              |
| Targeting rules | Conditions controlling who sees the flow |
| Created at      | Date the flow was created                |
| Updated at      | Date the flow was last modified          |

#### Banners

| Field           | Description                             |
| --------------- | --------------------------------------- |
| Banner ID       | Unique identifier for the banner        |
| Name            | Display name of the banner              |
| State           | Published, draft, or archived status    |
| Content         | Text or message displayed in the banner |
| Targeting rules | Audience and trigger conditions         |
| Created at      | Creation date                           |
| Updated at      | Last modification date                  |

#### Checklists

| Field           | Description                             |
| --------------- | --------------------------------------- |
| Checklist ID    | Unique identifier                       |
| Name            | Display name                            |
| State           | Current publish state                   |
| Items           | List of tasks included in the checklist |
| Targeting rules | Who the checklist is shown to           |
| Created at      | Creation date                           |

#### Pins

| Field           | Description                           |
| --------------- | ------------------------------------- |
| Pin ID          | Unique identifier                     |
| Name            | Display name                          |
| State           | Publish state                         |
| Target element  | The UI element the pin is attached to |
| Tooltip content | Text shown when the pin is clicked    |
| Created at      | Creation date                         |

#### Launchpads

| Field              | Description                                        |
| ------------------ | -------------------------------------------------- |
| Launchpad ID       | Unique identifier                                  |
| Name               | Display name                                       |
| State              | Publish state                                      |
| Linked experiences | Flows, checklists, and banners included in the hub |
| Created at         | Creation date                                      |

#### Segments

| Field      | Description                       |
| ---------- | --------------------------------- |
| Segment ID | Unique identifier                 |
| Name       | Segment label                     |
| Conditions | Rules defining segment membership |
| Created at | Date the segment was created      |

#### Tags

| Field              | Description                     |
| ------------------ | ------------------------------- |
| Tag ID             | Unique identifier               |
| Name               | Tag label                       |
| Associated content | Content items carrying this tag |

## Common field combinations

* **Flows + Tags**: Map each flow to its tags to categorize your content library by theme or product area
* **Flows + Segments**: Cross-reference which segments are targeted by which flows to spot coverage gaps
* **Banners + Checklists** (Appended): Stack both entities to get a unified list of all active user-facing experiences
* **Launchpads + Flows**: See which flows are surfaced through launchpads versus standalone triggers

## Use cases by role

{% tabs %}
{% tab title="Product managers" %}

* Audit all published flows and checklists to identify outdated or duplicate onboarding content
* Cross-reference segments with experience assignments to verify personalization coverage
* Track how many steps each flow contains and flag overly long guides for simplification
  {% endtab %}

{% tab title="Growth & marketing" %}

* Export banner configurations to review messaging and promotion schedules across the product
* Use tags to filter experiences by campaign or initiative and measure content volume per theme
* Send flow and banner content to ChatGPT or Claude via AI destinations for copy quality reviews
  {% endtab %}

{% tab title="Data & analytics" %}

* Load flows, segments, and tags into BigQuery to join with event-level analytics data from your warehouse
* Use the Aggregate transformation in Coupler.io to count experiences per state (draft vs. published) for a content health report
* Schedule exports to Looker Studio to build a live Appcues content inventory dashboard
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Appcues data exported through Coupler.io reflects **configuration and metadata** — engagement metrics like views or completion rates are not included in these entities
* The **start date** parameter filters by creation or modification date depending on the entity; leave it blank if you need a full content inventory
* Segment conditions are exported as-is from the Appcues API and may include nested rule logic
* Archived experiences are included in exports unless you filter them out in Coupler.io's transformation step

## Appcues common issues

### Connection issues

<details>

<summary>API key is not accepted</summary>

Double-check that you copied the full API key from **Appcues Settings > API** without any leading or trailing spaces. API keys are account-scoped, so make sure you're using the key from the correct Appcues account if you manage multiple. If the key was recently regenerated, update it in your Coupler.io data flow settings.

</details>

<details>

<summary>Data flow fails immediately after connecting</summary>

This usually means the API key has insufficient permissions or belongs to a user role that doesn't have API access. Verify that your Appcues plan includes API access — some lower-tier plans restrict it. Contact Appcues support to confirm API availability for your account.

</details>

### Missing data

<details>

<summary>Some flows or banners are missing from the export</summary>

Archived experiences are included by default, but if you applied a start date filter, content created before that date won't appear. Try clearing the start date field to pull all historical records. Also confirm in Appcues that the missing items aren't in a draft state that the API excludes.

</details>

<details>

<summary>Tags or segments export is empty</summary>

If you haven't created any tags or segments in Appcues yet, the export will return an empty table — this is expected behavior. Check your Appcues account to confirm that tags or segments exist before troubleshooting further.

</details>

<details>

<summary>Checklist items are missing or incomplete</summary>

Checklist item details depend on how the checklist was configured in Appcues. If items appear truncated, it may be because the API returns a summary structure for complex checklists. Try exporting the Checklists entity alongside the Flows entity using Append in case some content overlaps.

</details>

### Permission errors

<details>

<summary>"Unauthorized" error when running the data flow</summary>

This error means the API key is either invalid or has expired. Regenerate the API key in Appcues and update it in your Coupler.io source settings. If the error persists, confirm with your Appcues account admin that API access is enabled for your account tier.

</details>

### Data discrepancies

<details>

<summary>Experience counts don't match what I see in the Appcues dashboard</summary>

The Appcues dashboard may apply default filters (e.g., showing only published content) that differ from the unfiltered API export. The Coupler.io export includes all states — published, draft, and archived — unless you filter them yourself. Use the transformation step in Coupler.io to filter by state if you want to match the dashboard view.

</details>

### Rate limits

<details>

<summary>Sync fails or returns partial data on large accounts</summary>

Appcues enforces API rate limits that can affect large exports. If you're pulling multiple entities in a single data flow run, try splitting them into separate data flows. Scheduling refreshes at off-peak hours can also reduce the chance of hitting rate limits during automated syncs.

</details>

## Appcues FAQ

<details>

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

Log in to your Appcues account and go to **Settings > API**. Your API key will be listed there. If you don't see an API section, your Appcues plan may not include API access — check with your account admin or Appcues support.

</details>

<details>

<summary>Does Coupler.io export engagement metrics like flow completion rates or banner views?</summary>

No. The Appcues source in Coupler.io exports **content configuration metadata** — details about how your flows, banners, and checklists are set up and targeted. Engagement metrics like views, completions, and dismissals are not available through this integration. For that data, you'd need to connect a product analytics tool separately.

</details>

<details>

<summary>Can I export data from multiple Appcues accounts into one destination?</summary>

Yes. Add multiple Appcues sources to a single data flow — one per account, each with its own API key — and use the Append transformation to combine them. This is useful if you manage Appcues across different products or environments (e.g., staging vs. production).

</details>

<details>

<summary>Why does my export include archived experiences I didn't want?</summary>

The Appcues API returns all content regardless of state by default. Use the **Filter** step in Coupler.io's transformation settings to exclude rows where the state field equals "archived" before the data lands in your destination.

</details>

<details>

<summary>Can I use Appcues data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your Flows or Banners export directly to these tools for tasks like content audits, copy improvement suggestions, or identifying gaps in your onboarding sequences.

</details>

<details>

<summary>How do I build a full content inventory across all experience types?</summary>

Add Flows, Banners, Checklists, and Pins as separate sources in one data flow. Apply the Append transformation to stack them into a single table with a consistent schema. You can then load this into Google Sheets or Looker Studio for a unified Appcues content library view.

</details>

<details>

<summary>What happens if I leave the start date blank?</summary>

Leaving the start date blank tells Coupler.io to export all available historical data from your Appcues account. This is fine for smaller accounts but may slow down runs significantly on large accounts with years of content history. Use the date picker to set a start date if you only need recent data.

</details>

{% hint style="info" %}
For details on what fields are available per entity, see [Data Overview](#appcues-data-overview). For connection errors and missing data, check [Common Issues](#appcues-common-issues). For setup recommendations and pitfalls, visit [Best Practices](https://docs.coupler.io/sources/category/marketing/appcues/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/marketing/appcues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
