> ## Documentation Index
> Fetch the complete documentation index at: https://domoinc-openapi-sync-dataflows.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Pendo Connector

## Intro

Pendo captures user behavior, gathers feedback and provides contextual help beyond your service or platform. To learn more about the Pendo API, visit their page ([https://help.pendo.io/resources/supp...dev/index.html](https://help.pendo.io/resources/support-library/api-dev/index.html "https://help.pendo.io/resources/support-library/api-dev/index.html") ).

You connect to your Pendo account in the Data Center. This topic discusses the fields and menus that are specific to the Pendo connector user interface. General information for adding DataSets, setting update schedules, and editing DataSet information is discussed in [Adding a DataSet Using a Connector](https://domo-support.domo.com/s/article/360042926274?language=en_US "Adding a DataSet Using a Connector").

## Prerequisites

To connect to your Pendo account and create a DataSet, you must have a Pendo integration key. You can generate an integration key by doing the following:

1. Log into Pendo.
2. Click your username.
3. Select **Integration Keys**.
4. Select **Add Integration Key**.
5. Name your new key.

## Connecting to Your Pendo Account

This section enumerates the options in the **Credentials** and **Details** panes in the Pendo Connector page. The components of the other panes on this page, **Scheduling**, and **Name & Describe Your DataSet**, are universal across most connector types and are discussed in greater length in [Adding a DataSet Using a Connector](https://domo-support.domo.com/s/article/360042926274?language=en_US "Adding a DataSet Using a Connector").

### Credentials Pane

This pane contains fields for entering credentials to connect to your Pendo account. The following table describes what is needed for each field:

<table border="1" cellpadding="1" cellspacing="1" data-aura-rendered-by="33:201;a"><thead><tr><th colspan="1" rowspan="1"><p><span class="s1"> Field </span></p></th><th colspan="1" rowspan="1"><p><span class="s1"> Description </span></p></th></tr></thead><tbody><tr><td colspan="1" rowspan="1"><p> Integration Key </p></td><td colspan="1" rowspan="1"><p> Enter your Pendo integration key. For information about generating a key, see "Prerequisites," above. </p></td></tr><tr><td colspan="1" rowspan="1"><p> Region </p></td><td colspan="1" rowspan="1"><p> Select the region from the drop-down list. </p></td></tr></tbody></table>

Once you have entered valid Pendo credentials, you can use the same account any time you go to create a new Pendo DataSet. You can manage connector accounts in the **Accounts** tab in the Data Center. For more information about this tab, see [Manage Connector Accounts](https://domo-support.domo.com/s/article/360042926054?language=en_US "Manage Connector Accounts").

### Details Pane

This pane contains a primary **Reports** menu, along with various other menus which may or may not appear depending on the report type you select.

<table border="1" cellpadding="1" cellspacing="1" data-aura-rendered-by="33:201;a">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">
        <p> Menu </p>
      </th>

      <th colspan="1" rowspan="1">
        <p> Description </p>
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colspan="1" rowspan="1">
        <p> Report </p>
      </td>

      <td colspan="1" rowspan="1">
        <p> Select the report you want to run. The following reports are available: </p>

        <table border="1" cellpadding="1" cellspacing="1">
          <tbody>
            <tr>
              <td colspan="1" rowspan="1"><b> Report Name </b></td>
              <td colspan="1" rowspan="1"><b> Description </b></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Contents of Reports </td>
              <td colspan="1" rowspan="1"> Returns the contents of a selected Pendo report. </td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Get Change History for Guide </td>
              <td colspan="1" rowspan="1"> Returns the change history for a specified guide. </td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Guides Seen </td>
              <td colspan="1" rowspan="1"> Returns the Change History for Guide. </td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Row Aggregation </td>
              <td colspan="1" rowspan="1"> Returns row aggregation data for a given source and timeframe. </td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Public Reports </td>
              <td colspan="1" rowspan="1"> Returns a list of public Pendo reports. </td>
            </tr>
          </tbody>
        </table>
      </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Pendo Report </td>
      <td colspan="1" rowspan="1"> Select the Pendo report you want to pull into Domo. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Source </td>

      <td colspan="1" rowspan="1">
        <p> Select the desired source for the <b> Row Aggregation </b> report. The following table describes the
        available sources: </p>

        <table class="mt-responsive-table">
          <thead>
            <tr>
              <th colspan="1" rowspan="1"> Source </th>
              <th colspan="1" rowspan="1"> Description </th>
              <th colspan="1" rowspan="1"> Date Filter Field </th>
            </tr>
          </thead>

          <tbody>
            <tr>
              <td colspan="1" rowspan="1"> Accounts </td>
              <td colspan="1" rowspan="1"> The accounts your users (usually your customers) belong to. </td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> metadata.auto.lastvisit </span></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Custom </td>
              <td colspan="1" rowspan="1"> Lets you define your own request JSON in the <b> Custom Aggregation </b>
              field. For more information, see <a href="http://help.pendo.io/resources/support-library/api-dev/aggregation-row-sources.html" target="_blank" title="http://help.pendo.io/resources/support-library/api-dev/aggregation-row-sources.html">
              [http://help.pendo.io/resources/suppo...w-sources.html](http://help.pendo.io/resources/suppo...w-sources.html) </a>. </td>
              <td colspan="1" rowspan="1"> You define your own </td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Events </td>
              <td colspan="1" rowspan="1"> All recorded click and pageview events (tagged or untagged). </td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> timeSeries dayRange </span></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Features </td>
              <td colspan="1" rowspan="1"> Sets of rules that identify individual product features (defined by a DOM
              rule). </td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> lastUpdatedAt </span></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Feature Events </td>
              <td colspan="1" rowspan="1"> All recorded click events matching tagged features. </td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> timeSeries dayRange </span></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Guides </td>
              <td colspan="1" rowspan="1"> The in-app messages you show visitors. </td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> lastUpdatedAt </span></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Pages </td>
              <td colspan="1" rowspan="1"> Sets of rules that idenfity individual pages in your product (defined by a
              URL rule). </td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> lastUpdatedAt </span></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Page Events </td>
              <td colspan="1" rowspan="1"> All recorded pageviews matching tagged pages. </td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> timeSeries dayRange </span></td>
            </tr>

            <tr>
              <td colspan="1" rowspan="1"> Visitors </td>
              <td colspan="1" rowspan="1"> Your product's users (including internal users who access customer accounts).</td>
              <td colspan="1" rowspan="1"><span class="mt-font-courier-new"> metadata.auto.lastvisit </span></td>
            </tr>
          </tbody>
        </table>

        <p />
      </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Guide ID </td>
      <td colspan="1" rowspan="1"> Enter the ID of the guide you want to retrieve information for. To find the ID for a
      desired guide, navigate to the page for that guide (from the <b> Guides </b> page in Pendo), then copy the last
      portion of the URL. For example, in the URL <span class="mt-font-courier-new"><span class="nowiki"><a href="https://app.pendo.io/guides/abcd_xyz1234" rel="noopener" target="_blank">
      [https://app.pendo.io/guides/abcd\_xyz1234](https://app.pendo.io/guides/abcd_xyz1234) </a></span></span>, the guide ID would be <span class="mt-font-courier-new"><span class="nowiki"> abcd\_xyz1234 </span></span>. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Poll ID </td>
      <td colspan="1" rowspan="1"> Enter the Poll ID to get the details for a specific poll. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Guide Step ID </td>
      <td colspan="1" rowspan="1"> Enter the Guide Step ID to get the details for a specific guide or step. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Custom Aggregation </td>

      <td colspan="1" rowspan="1">
        Enter the request json. For example:

        ```json theme={"dark"}
        {
           "pipeline": [
              {
              "limit": 5
              }
           ],
           "source": {
              "pageEvents": null
           },
           "timeSeries": {
              "count": 1,
              "first": 1493596800000,
              "period": "dayRange"
           }
        }
        ```

        <br />

        <b> Specifying dates - Common examples: </b><br />`'now()', 'date(yyyy,MM,dd)', '1693540800000' (epoch timestamp), 'yyyy-MM-dd'`
      </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> All Guides </td>
      <td colspan="1" rowspan="1"> Select 'Yes' if you wish to query for all guides. 'No' to select specific ones. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Guides </td>
      <td colspan="1" rowspan="1"> Select the guides to query. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Do not hash the Visitor ID? </td>
      <td colspan="1" rowspan="1"> Select this checkbox to NOT use hashing for the visitor ID, by default. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Application Id Selection Type </td>
      <td colspan="1" rowspan="1"> Select whether to retrieve data from all or only specific application id. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Enter Application IDs </td>
      <td colspan="1" rowspan="1"> Enter the Application ID for which we need to retrieve the data. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Handle Records </td>

      <td colspan="1" rowspan="1">
        <p>
          <span> This field appears when you select the <b> Row Aggregation </b> report and the source as <b> Guides
          </b>. </span>
        </p>

        <p>
          <span> If you encounter an error when the columns exceeds the allowed limit, you can use one of the following
          options to handle the records. </span>
        </p>

        <p>
          <span>
            <b> None </b> – This option is selected by default. It does not handle the error when the column
            exceeds the specified limit.
          </span>
        </p>

        <p>
          <span>
            <b> Skip Step\_Translations Data </b> – The stepTranslations data will be skipped and not added to the
            dataset.
          </span>
        </p>

        <p>
          <span>
            <b> Handle Step\_Translations Data </b> – The data will be flattened to reduce the row count.
          </span>
        </p>
      </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Duration (GMT) </td>
      <td colspan="1" rowspan="1"> Select the duration for the report (a Single Date, or a Date Range). </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Report Date </td>
      <td colspan="1" rowspan="1"> Select the report date using relative or specific dates. Relative indicates the
      number of days from today or a specific date using the date selector. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Select Specific Date </td>
      <td colspan="1" rowspan="1"> Select the report date using the date selector. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Days back </td>
      <td colspan="1" rowspan="1"> The number of days back that you would like to get data for. Specify either today or
      0, yesterday or 1, or today-7 or 7 to get data for 7 days into the past. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Start Date </td>
      <td colspan="1" rowspan="1"> Select the report start date using relative or specific dates. Relative indicates the
      number of days from today or a specific date using the date selector. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Select Specific Start Date </td>
      <td colspan="1" rowspan="1"> Select the report date using the date selector. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Days back to start from </td>
      <td colspan="1" rowspan="1"> The number of days back that you would like to get data from (start day). Specify
      either today or 0, yesterday or 1, or today-7 or 7 to get data for 7 days into the past. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> End Date </td>
      <td colspan="1" rowspan="1"> Select the report end date using relative or specific dates. Relative indicates the
      number of days from today or a specific date using the date selector. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Select Specific End Date </td>
      <td colspan="1" rowspan="1"> Select the report date using the date selector. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Days back to end at </td>
      <td colspan="1" rowspan="1"> The number of days back that you would like to get data to (end day). Specify either
      today or 0, yesterday or 1, or today-7 or 7 to get data for 7 days into the past. </td>
    </tr>

    <tr>
      <td colspan="1" rowspan="1"> Use Report Schema </td>
      <td colspan="1" rowspan="1"> Select the checkbox if you want to have report schema as column names. </td>
    </tr>
  </tbody>
</table>

### Other Panes

For information about the remaining sections of the connector interface, including how to configure scheduling, retry, and update options, see [Adding a DataSet Using a Connector](https://domo-support.domo.com/s/article/360042926274?language=en_US "Adding a DataSet Using a Connector").
