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

# 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


---

# 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/appcues/data-overview.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.