# Data Overview

When you connect Aha to Coupler.io, you can pull data from eight different entities. Each entity maps to a specific area of your Aha workspace — from product features and strategic goals to user ideas and community feedback.

## Available entities

| Entity                    | What it contains                                                         |
| ------------------------- | ------------------------------------------------------------------------ |
| Features streams          | Individual features, their status, release assignments, and details      |
| Products streams          | Product records including names, descriptions, and configuration         |
| Idea categories streams   | The category labels used to organize ideas in your workspace             |
| Ideas streams             | Submitted ideas including title, description, status, and submitter info |
| Idea endorsements streams | Votes and endorsements on ideas, including who endorsed them             |
| Idea comments streams     | Comments left on ideas by users and team members                         |
| Users streams             | Workspace users and their profile information                            |
| Goals streams             | Strategic goals and objectives with status and ownership details         |

## Features streams

#### Key fields

| Field              | Description                             |
| ------------------ | --------------------------------------- |
| `id`               | Unique identifier for the feature       |
| `name`             | Feature name or title                   |
| `reference_num`    | Aha reference number (e.g., PROD-123)   |
| `status`           | Current workflow status                 |
| `created_at`       | Date the feature was created            |
| `updated_at`       | Date the feature was last updated       |
| `product_id`       | The product this feature belongs to     |
| `release`          | Release the feature is assigned to      |
| `assigned_to_user` | Team member responsible for the feature |

## Products streams

#### Key fields

| Field              | Description                                       |
| ------------------ | ------------------------------------------------- |
| `id`               | Unique product identifier                         |
| `name`             | Product name                                      |
| `reference_prefix` | The prefix used in reference numbers (e.g., PROD) |
| `created_at`       | Date the product was created                      |

## Ideas streams

#### Key fields

| Field                   | Description                                            |
| ----------------------- | ------------------------------------------------------ |
| `id`                    | Unique idea identifier                                 |
| `name`                  | Idea title                                             |
| `description`           | Full idea description                                  |
| `status`                | Current idea status (e.g., new, under review, shipped) |
| `created_at`            | Date the idea was submitted                            |
| `updated_at`            | Date the idea was last updated                         |
| `votes`                 | Total vote count                                       |
| `submitted_idea_portal` | Portal through which the idea was submitted            |
| `categories`            | Categories assigned to the idea                        |

## Idea endorsements streams

#### Key fields

| Field        | Description                    |
| ------------ | ------------------------------ |
| `id`         | Unique endorsement identifier  |
| `idea_id`    | The idea that was endorsed     |
| `user_id`    | The user who endorsed the idea |
| `created_at` | Date of the endorsement        |

## Goals streams

#### Key fields

| Field         | Description                 |
| ------------- | --------------------------- |
| `id`          | Unique goal identifier      |
| `name`        | Goal name                   |
| `description` | Goal description            |
| `status`      | Current status of the goal  |
| `created_at`  | Date the goal was created   |
| `product_id`  | Product the goal belongs to |

## Common field combinations

Here are some useful ways to combine fields across entities:

* **Feature progress by product** — join `features_stream` with `products_stream` on `product_id` to see how features are distributed across products
* **Idea traction** — combine `ideas_stream` with `idea_endorsements_stream` on `idea_id` to rank ideas by engagement
* **Idea feedback summary** — join `ideas_stream` with `idea_comments_stream` to see which ideas are generating the most discussion
* **Goal alignment** — link `goals_stream` and `features_stream` via `product_id` to map features back to strategic objectives

## Use cases by role

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

* Track feature status and release assignments across all products in one report
* Monitor how many features are in each workflow stage to spot bottlenecks
* Link features back to strategic goals to demonstrate roadmap alignment
* Export features data to share progress updates with stakeholders outside Aha
  {% endtab %}

{% tab title="Customer success" %}

* Pull ideas and endorsements to understand which customer requests have the most momentum
* Monitor idea comments to stay on top of customer conversations and feedback themes
* Track idea status changes over time to report back to customers when their suggestions are acted on
  {% endtab %}

{% tab title="Leadership" %}

* Report on strategic goals and their current status across all products
* Combine goals and features data to see how well execution aligns with strategy
* Use products and users' data for workspace audits and capacity planning
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Aha uses a subdomain-based URL structure — make sure you enter only the subdomain (not the full URL) when connecting
* API access may be restricted depending on your Aha plan — check that your account has API access enabled before connecting
* Fields like `description` may contain HTML formatting from the Aha editor, which will appear as raw HTML in your export
* Deleted or archived records may not appear in streams depending on your Aha workspace settings
* The `reference_num` field (e.g., PROD-123) is useful as a human-readable, unique key when building reports