# Pendo: Feature

## Description

* Table capturing features - their latest state enhanced with metrics and relational information.

## Supported Data Sources

* <img src="https://fivetran.com/integrations/pendo/resources/pendo.svg" alt="" data-size="line"> Pendo

## Columns

| Type     | Name                                | Description                                                                                           |
| -------- | ----------------------------------- | ----------------------------------------------------------------------------------------------------- |
| STRING   | feature\_id                         | Unique identifier of the feature.                                                                     |
| INTEGER  | app\_id                             | Foreign key referencing the `APPLICATION` that the feature is a part of.                              |
| DATETIME | created\_at                         | Timestamp of when the feature was created.                                                            |
| INTEGER  | created\_by\_user\_id               | Foreign key referencing the `USER` that created the feature.                                          |
| BOOLEAN  | is\_dirty                           | Boolean value returned if feature is processing at the time of request.                               |
| STRING   | group\_id                           | Foreign key referencing the `GROUP` (product area) that the feature is tagged under.                  |
| BOOLEAN  | is\_core\_event                     | Boolean that is true if the feature is tagged as a core event/key feature of the product.             |
| STRING   | last\_updated\_at                   | Timestamp of when the feature was last updated.                                                       |
| INTEGER  | last\_updated\_by\_user\_id         | Foreign key referencing the `USER` that last updated the feature.                                     |
| STRING   | feature\_name                       | Name of the feature.                                                                                  |
| STRING   | page\_id                            | Foreign key referencing the `PAGE` that the feature is placed on.                                     |
| STRING   | root\_version\_id                   | The unique identifier of the root entity, which nominally matches the public id field of the feature. |
| STRING   | stable\_version\_id                 | The unique identifier for the current version of the feature.                                         |
| DATETIME | valid\_through                      | Timestamp that indicates when data was last processed.                                                |
| DATETIME | \_fivetran\_synced                  | UTC timestamp that indicates the time when Fivetran last successfully synced the row.                 |
| STRING   | product\_area\_name                 | Name of the product area (ie `GROUP`) that the feature is tagged under.                               |
| STRING   | page\_name                          | Name of the page that the feature lives on.                                                           |
| DATETIME | page\_created\_at                   | Timestamp of when the feature's page was created.                                                     |
| DATETIME | page\_valid\_through                | Timestamp that indicates when data was last processed for the feature's page.                         |
| STRING   | app\_display\_name                  | Display name of the application that the feature is a part of.                                        |
| STRING   | app\_platform                       | Platform on which the feature's application is served.                                                |
| STRING   | created\_by\_user\_full\_name       | Full name of the internal user who first created the feature.                                         |
| STRING   | created\_by\_user\_username         | Username (probably email) of the internal user who first created the feature.                         |
| STRING   | last\_updated\_by\_user\_full\_name | Full name of the internal user who last updated the feature.                                          |
| STRING   | last\_updated\_by\_user\_username   | Username (probably email) of the internal user who last updated the feature.                          |
| INTEGER  | count\_visitors                     | Count of distinct visitors who have clicked on this feature.                                          |
| INTEGER  | count\_accounts                     | Count of distinct accounts who have been tracked clicking this feature.                               |
| INTEGER  | sum\_clicks                         | The total sum of click interactions with this feature (based on `num_events`).                        |
| INTEGER  | count\_click\_events                | Count of records in `feature_event` logged for this feature.                                          |
| DATETIME | first\_click\_at                    | Timestamp of when a visitor first clicked on this feature.                                            |
| DATETIME | last\_click\_at                     | Timestamp of when a visitor last clicked on this feature.                                             |
| INTEGER  | avg\_visitor\_minutes               | Average total time spent on this feature per visitor (ignoring 0-event visitors).                     |
| INTEGER  | avg\_visitor\_events                | Average sum of feature click events per visitor (ignoring 0-event visitors).                          |


---

# Agent Instructions: 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:

```
GET https://endash-guidance-docs.gitbook.io/cigro-data-templates/data-model-templates/pendo-feature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.