Pendo

Pendo is a SaaS platform that helps businesses improve product adoption, usage, and satisfaction by providing in-app guidance, communications, and analytics. You can use Pendo as a data source when landing or replicating data.

See the Schema section for a list of objects available for replication.

Présentation générale de ce connecteur, y compris des liens utiles et les fonctions supportées.

Caractéristique/Fonctionnalité	Détails du support
Projets Qlik Talend Data Integration supportés	Projets de réplication uniquement. Les projets de pipeline de données ne sont pas supportés.
Méthodes de mise à jour de la cible	Tâches de réplication : Appliquer les modifications Stocker les modifications Tâches de dépôt temporaire de données dans un lac de données : Change Data Capture (CDC)
Gestion des métadonnées	La génération manuelle de métadonnées n'est pas nécessaire.
Évolution du schéma	Seule l'opération Modifier le type de données de la colonne est supportée.
Réplication de colonnes LOB (NCLOB, CLOB et BLOB)	Non supporté.
Opération CDC planifiée	Requis. C'est ainsi que la cible est mise à jour en fonction des modifications apportées à la source. Pour les tâches de réplication, consultez Planification de CDC pour les tâches de réplication. Pour les tâches de dépôt temporaire dans un lac, consultez Planification de CDC pour les tâches de dépôt temporaire dans un lac.
Notifications	Partiellement supporté Définition de notifications en cas de modifications du fonctionnement
Surveillance	CDC uniquement, car le chargement complet n'est pas pertinent pour ce connecteur. Surveillance d'une tâche de données individuelle
Désimbrication automatique des charges utiles des colonnes JSON	Non supporté. Les charges utiles des colonnes JSON des jeux de données sources ne sont pas automatiquement désimbriquées sur la cible.

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

Assurez-vous que le compte que vous utilisez dispose d'un accès en lecture sur les tables à récupérer.

To generate an integration key:

Make sure you have the Admin privileges in Pendo. You need them to create an integration key.
Log into your Pendo account as a user with Admin privileges.
Go tp Settings > Integrations > Integration Keys.
Click + Add Integration Key.
In Description field of the window that displays, enter a description. For example: Qlik.
Click Create.The integration key will display in the Key column:
Copy the key.

Creating the connection

Pour plus d'informations, consultez Connexion à des applications SaaS.

Complétez les propriétés de connexion requises.
Fournissez un nom pour la connexion dans Nom de la connexion.
Sélectionnez Ouvrir les métadonnées de connexion pour définir les métadonnées de la connexion lors de sa création.
Cliquez sur Créer.

Connection settings
Setting	Description
Data gateway	Sélectionnez une Data Movement gateway si cela est nécessaire pour votre cas d'utilisation. Note Informations Ce champ n'est pas disponible avec l'abonnement Démarreur Qlik Talend Cloud, car il ne supporte pas Data Movement gateway. Si vous avez un autre niveau d'abonnement et si vous ne souhaitez pas utiliser Data Movement gateway, sélectionnez Aucune. Pour des informations sur les avantages de Data Movement gateway et les cas d'utilisation qui la nécessitent, consultez Qlik Data Gateway - Data Movement.
Start Date	Saisissez la date, au format `MM/DD/YYYY`, à partir de laquelle les données doivent être répliquées de votre source vers votre cible.
Period	Select the period from the drop-down list: Days: Data will be aggregated by day. Hours: Data will be aggregated by hour.
X Pendo Integration Key	Pendo integration key.
App IDs	App IDs separated by a comma. Example: `1122, 2345`.
Include Anonymous Visitors	Select the check box if needed. This lets you collect data from visitors that have no assigned Visitor ID and counts toward your total monthly active users.

Schema

Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.

The schema and info displayed below is for version 1.

Depending on your destination, table and column names may not appear as they are outlined below.

accounts

The accounts table contains info about your customer accounts in Pendo.

Replication Method	CDC
Primary Key	account_id
Replication Key	lastupdated
Useful links	Pendo documentation Pendo API method

Join accounts with	on
events	accounts.account_id = events.account_id
feature_events	accounts.account_id = feature_events.account_id
guide_events	accounts.account_id = guide_events.account_id accounts.account_id = guide_events.account_ids
page_events	accounts.account_id = page_events.account_id
poll_events	accounts.account_id = poll_events.account_id accounts.account_id = poll_events.account_ids
track_events	accounts.account_id = track_events.account_id
visitors	accounts.account_id = visitors.metadata_auto.accountid accounts.account_id = visitors.metadata_auto.accountids

account_id

STRING

lastupdated

DATE-TIME

metadata_auto

OBJECT

This is a nested data structure:

firstvisit: DATE-TIME
id: STRING
idhash: INTEGER
lastupdated: DATE-TIME
lastvisit: DATE-TIME

metadata_custom

OBJECT

events

The events table contains info about events recorded in your Pendo account.

Note: The Period setting you define during setup determine how this table is replicated, including the field used as a Replication Key. Refer to the Replication section for more info.

Replication Method

CDC

Primary Keys

account_id

server

remote_ip

Useful links

Pendo documentation

Pendo API method

Join events with	on
accounts	events.account_id = accounts.account_id
feature_events	events.account_id = feature_events.account_id events.app_id = feature_events.app_id events.feature_id = feature_events.feature_id events.visitor_id = feature_events.visitor_id
guide_events	events.account_id = guide_events.account_id events.account_id = guide_events.account_ids events.app_id = guide_events.app_id events.visitor_id = guide_events.visitor_id
page_events	events.account_id = page_events.account_id events.app_id = page_events.app_id events.page_id = page_events.page_id events.visitor_id = page_events.visitor_id
poll_events	events.account_id = poll_events.account_id events.account_id = poll_events.account_ids events.visitor_id = poll_events.visitor_id
track_events	events.account_id = track_events.account_id events.app_id = track_events.app_id events.visitor_id = track_events.visitor_id
visitors	events.account_id = visitors.metadata_auto.accountid events.account_id = visitors.metadata_auto.accountids events.visitor_id = visitors.visitor_id
features	events.app_id = features.created_by_user.app_id events.feature_id = features.id events.page_id = features.page_id
visitor_history	events.app_id = visitor_history.app_id events.feature_id = visitor_history.feature_id events.page_id = visitor_history.page_id events.visitor_id = visitor_history.visitor_id
guides	events.page_id = guides.steps.page_id events.visitor_id = guides.audience.select.visitor_id
pages	events.page_id = pages.id

account_id

STRING

app_id

NUMBER

day

DATE-TIME

feature_id

STRING

hour

DATE-TIME

num_events

INTEGER

num_minutes

INTEGER

page_id

STRING

parameters

STRING

remote_ip

STRING

server

STRING

user_agent

STRING

visitor_id

STRING

feature_events

The feature_events table contains info about feature events recorded in your Pendo account.

Note: The Period setting you define during setup determine how this table is replicated, including the field used as a Replication Key. Refer to the Replication section for more info.

Replication Method

CDC

Primary Keys

account_id

server

remote_ip

visitor_id

day

feature_id

user_agent

Useful links

Pendo documentation

Pendo API method

Join feature_events with	on
accounts	feature_events.account_id = accounts.account_id
events	feature_events.account_id = events.account_id feature_events.app_id = events.app_id feature_events.feature_id = events.feature_id feature_events.visitor_id = events.visitor_id
guide_events	feature_events.account_id = guide_events.account_id feature_events.account_id = guide_events.account_ids feature_events.app_id = guide_events.app_id feature_events.visitor_id = guide_events.visitor_id
page_events	feature_events.account_id = page_events.account_id feature_events.app_id = page_events.app_id feature_events.visitor_id = page_events.visitor_id
poll_events	feature_events.account_id = poll_events.account_id feature_events.account_id = poll_events.account_ids feature_events.visitor_id = poll_events.visitor_id
track_events	feature_events.account_id = track_events.account_id feature_events.app_id = track_events.app_id feature_events.visitor_id = track_events.visitor_id
visitors	feature_events.account_id = visitors.metadata_auto.accountid feature_events.account_id = visitors.metadata_auto.accountids feature_events.visitor_id = visitors.visitor_id
features	feature_events.app_id = features.created_by_user.app_id feature_events.feature_id = features.id
visitor_history	feature_events.app_id = visitor_history.app_id feature_events.feature_id = visitor_history.feature_id feature_events.visitor_id = visitor_history.visitor_id
guides	feature_events.visitor_id = guides.audience.select.visitor_id

account_id

STRING

app_id

NUMBER

day

DATE-TIME

feature_id

STRING

hour

DATE-TIME

num_events

INTEGER

num_minutes

INTEGER

parameters

STRING

remote_ip

STRING

server

STRING

user_agent

STRING

visitor_id

STRING

features

The features table contains info about app features listed in your Pendo account.

Replication Method	CDC
Primary Key	id
Replication Key	last_updated_at
Useful links	Pendo documentation Pendo API method

Join features with	on
events	features.created_by_user.app_id = events.app_id features.id = events.feature_id features.page_id = events.page_id
feature_events	features.created_by_user.app_id = feature_events.app_id features.id = feature_events.feature_id
guide_events	features.created_by_user.app_id = guide_events.app_id
page_events	features.created_by_user.app_id = page_events.app_id features.page_id = page_events.page_id
track_events	features.created_by_user.app_id = track_events.app_id
visitor_history	features.created_by_user.app_id = visitor_history.app_id features.id = visitor_history.feature_id features.page_id = visitor_history.page_id
pages	features.group.id = pages.group.id features.page_id = pages.id features.created_by_user.id = pages.created_by_user.id features.group.created_by_user.id = pages.created_by_user.id features.group.last_updated_by_user.id = pages.created_by_user.id features.last_updated_by_user.id = pages.created_by_user.id features.created_by_user.id = pages.group.created_by_user.id features.group.created_by_user.id = pages.group.created_by_user.id features.group.last_updated_by_user.id = pages.group.created_by_user.id features.last_updated_by_user.id = pages.group.created_by_user.id features.created_by_user.id = pages.group.last_updated_by_user.id features.group.created_by_user.id = pages.group.last_updated_by_user.id features.group.last_updated_by_user.id = pages.group.last_updated_by_user.id features.last_updated_by_user.id = pages.group.last_updated_by_user.id features.created_by_user.id = pages.last_updated_by_user.id features.group.created_by_user.id = pages.last_updated_by_user.id features.group.last_updated_by_user.id = pages.last_updated_by_user.id features.last_updated_by_user.id = pages.last_updated_by_user.id
track_types	features.group.id = track_types.group.id features.created_by_user.id = track_types.created_by_user.id features.group.created_by_user.id = track_types.created_by_user.id features.group.last_updated_by_user.id = track_types.created_by_user.id features.last_updated_by_user.id = track_types.created_by_user.id features.created_by_user.id = track_types.last_updated_by_user.id features.group.created_by_user.id = track_types.last_updated_by_user.id features.group.last_updated_by_user.id = track_types.last_updated_by_user.id features.last_updated_by_user.id = track_types.last_updated_by_user.id
guides	features.page_id = guides.steps.page_id features.created_by_user.id = guides.created_by_user.id features.group.created_by_user.id = guides.created_by_user.id features.group.last_updated_by_user.id = guides.created_by_user.id features.last_updated_by_user.id = guides.created_by_user.id features.created_by_user.id = guides.last_updated_by_user.id features.group.created_by_user.id = guides.last_updated_by_user.id features.group.last_updated_by_user.id = guides.last_updated_by_user.id features.last_updated_by_user.id = guides.last_updated_by_user.id

app_id

NUMBER

color

STRING

created_at

DATE-TIME

created_by_user

OBJECT

This is a nested data structure:

app_id: NUMBER
app_wide: BOOLEAN
event_property_configurations: ARRAY, which is also a nested data structure.
first: STRING
id: STRING
is_core_event: BOOLEAN
last: STRING
role: INTEGER
user_type: STRING
username: STRING
valid_through: NUMBER

dirty

BOOLEAN

element_path_rules

ARRAY

group

OBJECT

This is a nested data structure:

color: STRING
created_at: DATE-TIME
created_by_user: OBJECT, which is also a nested data structure.
- first: STRING
- id: STRING
- last: STRING
- role: INTEGER
- type: STRING
- username: STRING
description: STRING
id: STRING
last_updated_at: DATE-TIME
last_updated_by_user: OBJECT, which is also a nested data structure.
- first: STRING
- id: STRING
- last: STRING
- role: INTEGER
- username: STRING
length: INTEGER
name: STRING

STRING

kind

STRING

last_updated_at

DATE-TIME

last_updated_by_user

OBJECT

This is a nested data structure:

first: STRING
id: STRING
last: STRING
role: INTEGER
type: STRING
username: STRING

name

STRING

page_id

STRING

root_version_id

STRING

stable_version_id

STRING

guide_events

The guide_events table contains info about guide events recorded in your Pendo account.

Note: The Period setting you define during setup determine how this table is replicated, including the field used as a Replication Key. Refer to the Replication section for more info.

Replication Method	CDC
Primary Keys	account_id browser_time guide_id guide_step_id remote_ip type url visitor_id
Replication Key	browser_time
Useful links	Pendo documentation Pendo API method

Join guide_events with	on
accounts	guide_events.account_id = accounts.account_id guide_events.account_ids = accounts.account_id
events	guide_events.account_id = events.account_id guide_events.account_ids = events.account_id guide_events.app_id = events.app_id guide_events.visitor_id = events.visitor_id
feature_events	guide_events.account_id = feature_events.account_id guide_events.account_ids = feature_events.account_id guide_events.app_id = feature_events.app_id guide_events.visitor_id = feature_events.visitor_id
page_events	guide_events.account_id = page_events.account_id guide_events.account_ids = page_events.account_id guide_events.app_id = page_events.app_id guide_events.visitor_id = page_events.visitor_id
poll_events	guide_events.account_id = poll_events.account_id guide_events.account_ids = poll_events.account_id guide_events.account_id = poll_events.account_ids guide_events.account_ids = poll_events.account_ids guide_events.guide_id = poll_events.guide_id guide_events.poll_id = poll_events.poll_id guide_events.visitor_id = poll_events.visitor_id
track_events	guide_events.account_id = track_events.account_id guide_events.account_ids = track_events.account_id guide_events.app_id = track_events.app_id guide_events.visitor_id = track_events.visitor_id
visitors	guide_events.account_id = visitors.metadata_auto.accountid guide_events.account_ids = visitors.metadata_auto.accountid guide_events.account_id = visitors.metadata_auto.accountids guide_events.account_ids = visitors.metadata_auto.accountids guide_events.visitor_id = visitors.visitor_id
features	guide_events.app_id = features.created_by_user.app_id
visitor_history	guide_events.app_id = visitor_history.app_id guide_events.guide_id = visitor_history.guide_id guide_events.visitor_id = visitor_history.visitor_id
guides	guide_events.guide_id = guides.id guide_events.guide_id = guides.steps.guide_id guide_events.visitor_id = guides.audience.select.visitor_id

account_id

STRING

account_ids

ARRAY

app_id

NUMBER

browser_time

DATE-TIME

country

STRING

guide_id

STRING

guide_step_id

STRING

latitude

NUMBER

load_time

INTEGER

longitude

NUMBER

poll_id

STRING

poll_response

STRING

region

STRING

remote_ip

STRING

server_name

STRING

type

STRING

url

STRING

user_agent

STRING

visitor_id

STRING

guides

The guides table contains info about the guides in your Pendo account.

Replication Method	CDC
Primary Key	id
Replication Key	last_updated_at
Useful links	Pendo API method

Join guides with	on
guide_events	guides.id = guide_events.guide_id guides.steps.guide_id = guide_events.guide_id guides.audience.select.visitor_id = guide_events.visitor_id
poll_events	guides.id = poll_events.guide_id guides.steps.guide_id = poll_events.guide_id guides.audience.select.visitor_id = poll_events.visitor_id
visitor_history	guides.id = visitor_history.guide_id guides.steps.guide_id = visitor_history.guide_id guides.steps.id = visitor_history.guide_id guides.steps.page_id = visitor_history.page_id guides.audience.select.visitor_id = visitor_history.visitor_id
events	guides.steps.page_id = events.page_id guides.audience.select.visitor_id = events.visitor_id
features	guides.steps.page_id = features.page_id guides.created_by_user.id = features.created_by_user.id guides.last_updated_by_user.id = features.created_by_user.id guides.created_by_user.id = features.group.created_by_user.id guides.last_updated_by_user.id = features.group.created_by_user.id guides.created_by_user.id = features.group.last_updated_by_user.id guides.last_updated_by_user.id = features.group.last_updated_by_user.id guides.created_by_user.id = features.last_updated_by_user.id guides.last_updated_by_user.id = features.last_updated_by_user.id
page_events	guides.steps.page_id = page_events.page_id guides.audience.select.visitor_id = page_events.visitor_id
pages	guides.steps.page_id = pages.id guides.created_by_user.id = pages.created_by_user.id guides.last_updated_by_user.id = pages.created_by_user.id guides.created_by_user.id = pages.group.created_by_user.id guides.last_updated_by_user.id = pages.group.created_by_user.id guides.created_by_user.id = pages.group.last_updated_by_user.id guides.last_updated_by_user.id = pages.group.last_updated_by_user.id guides.created_by_user.id = pages.last_updated_by_user.id guides.last_updated_by_user.id = pages.last_updated_by_user.id
track_types	guides.created_by_user.id = track_types.created_by_user.id guides.last_updated_by_user.id = track_types.created_by_user.id guides.created_by_user.id = track_types.last_updated_by_user.id guides.last_updated_by_user.id = track_types.last_updated_by_user.id
feature_events	guides.audience.select.visitor_id = feature_events.visitor_id
track_events	guides.audience.select.visitor_id = track_events.visitor_id
visitors	guides.audience.select.visitor_id = visitors.visitor_id

app_id

NUMBER

attributes

OBJECT

This is a nested data structure: badge, OBJECT, which is alaso a nested data structure.

can_change_badge_color: BOOLEAN
color: STRING
height: INTEGER
image_url: STRING
is_only_show_once: BOOLEAN
name: STRING
offsets: OBJECT, which is also a nested data structure.
- left: INTEGER
- right: INTEGER
- top: INTEGER
position: STRING
show_on_event: STRING
use_hover: STRING
width: INTEGER
device: OBJECT, which is also a nested data structure.
- type: STRING
priority: INTEGER
type: STRING

audience

ARRAY

This is a nested data structure:

identified: STRING
select: OBJECT, which is also a nested data structure.
- visitor_id: STRING
source: OBJECT, which is also a nested data structure.
- visitors: STRING

created_at

DATE-TIME

created_by_user

OBJECT

This is a nested data structure:

first: STRING
id: STRING
last: STRING
role: INTEGER
username: STRING

STRING

is_multi_step

BOOLEAN

kind

STRING

last_updated_at

DATE-TIME

last_updated_by_user

OBJECT

This is a nested data structure:

first: STRING
id: STRING
last: STRING
role: INTEGER
username: STRING

launch_method

STRING

name

STRING

published_at

DATE-TIME

reset_at

DATE-TIME

root_version_id

STRING

stable_version_id

STRING

state

STRING

steps

ARRAY

This is a nested data structure:

advance_method: STRING
attributes: OBJECT, which is also a nested data structure.
- auto_height: BOOLEAN
- css: STRING
- height: INTEGER
- width: INTEGER
content_type: STRING
content_url: STRING
content_url_css: STRING
content_url_js: STRING
element_path_rule: STRING
guide_id: STRING
id: STRING
last_updated_at: DATE-TIME
page_id: STRING
rank: INTEGER
regex_url_rule: STRING
reset_at: DATE-TIME
type: STRING

metadata_accounts

The metadata_accounts table contains info about the metadata schema used for account objects in your Pendo account.

Replication Method

Full Table

Useful links

Pendo documentation

Pendo API method

auto

OBJECT

This is a nested data structure:

firstvisit: OBJECT, which is also a nested data structure.
- dirty: BOOLEAN
- display_name: STRING
- element_format: STRING
- element_type: STRING
- is_calculated: BOOLEAN
- is_deleted: BOOLEAN
- is_hidden: BOOLEAN
- is_per_app: BOOLEAN
- never_index: BOOLEAN
- type: STRING
id: OBJECT, which is also a nested data structure.
- dirty: BOOLEAN
- display_name: STRING
- element_format: STRING
- element_type: STRING
- is_calculated: BOOLEAN
- is_deleted: BOOLEAN
- is_hidden: BOOLEAN
- is_per_app: BOOLEAN
- never_index: BOOLEAN
- type: STRING
lastvisit: OBJECT, which is also a nested data structure.
- dirty: BOOLEAN
- display_name: STRING
- element_format: STRING
- element_type: STRING
- is_calculated: BOOLEAN
- is_deleted: BOOLEAN
- is_hidden: BOOLEAN
- is_per_app: BOOLEAN
- never_index: BOOLEAN
- type: STRING

metadata_visitors

The metadata_visitors table contains info about the metadata schema used for visitor objects in your Pendo account.

Replication Method

Full Table

Useful links

Pendo documentation

Pendo API method

agent

OBJECT

This is a nested data structure:

language, OBJECT, which is also a nested data structure:
- dirty: OBJECT
- display_name: STRING
- element_format: STRING
- element_type: STRING
- is_calculated: BOOLEAN
- is_deleted: BOOLEAN
- is_hidden: BOOLEAN
- is_per_app: BOOLEAN
- never_index: BOOLEAN
- type: STRING
auto, OBJECT, which is also a nested data structure:
- accountid: OBJECT, which is also a nested data structure:
  - dirty: OBJECT
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- accountids, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- firstvisit, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- id, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- lastbrowsername, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- lastbrowserversion, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- lastoperatingsystem, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- lastservername, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
- lastvisit, OBJECT, which is also a nested data structure:
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING
pendo, OBJECT, which is also a nested data structure:
- designerenabled: OBJECT
  - display_name: STRING
  - element_format: STRING
  - element_type: STRING
  - is_calculated: BOOLEAN
  - is_deleted: BOOLEAN
  - is_hidden: BOOLEAN
  - is_per_app: BOOLEAN
  - never_index: BOOLEAN
  - type: STRING

page_events

The page_events table contains info about page events recorded in your Pendo account.

Note: The Period setting you define during setup determine how this table is replicated, including the field used as a Replication Key. Refer to the Replication section for more info.

Replication Method

CDC

Primary Keys

account_id

server

remote_ip

visitor_id

day

page_id

user_agent

Useful links

Pendo documentation

Pendo API method

Join page_events with	on
accounts	page_events.account_id = accounts.account_id
events	page_events.account_id = events.account_id page_events.app_id = events.app_id page_events.page_id = events.page_id page_events.visitor_id = events.visitor_id
feature_events	page_events.account_id = feature_events.account_id page_events.app_id = feature_events.app_id page_events.visitor_id = feature_events.visitor_id
guide_events	page_events.account_id = guide_events.account_id page_events.account_id = guide_events.account_ids page_events.app_id = guide_events.app_id page_events.visitor_id = guide_events.visitor_id
poll_events	page_events.account_id = poll_events.account_id page_events.account_id = poll_events.account_ids page_events.visitor_id = poll_events.visitor_id
track_events	page_events.account_id = track_events.account_id page_events.app_id = track_events.app_id page_events.visitor_id = track_events.visitor_id
visitors	page_events.account_id = visitors.metadata_auto.accountid page_events.account_id = visitors.metadata_auto.accountids page_events.visitor_id = visitors.visitor_id
features	page_events.app_id = features.created_by_user.app_id page_events.page_id = features.page_id
visitor_history	page_events.app_id = visitor_history.app_id page_events.page_id = visitor_history.page_id page_events.visitor_id = visitor_history.visitor_id
guides	page_events.page_id = guides.steps.page_id page_events.visitor_id = guides.audience.select.visitor_id
pages	page_events.page_id = pages.id

account_id

STRING

app_id

NUMBER

day

DATE-TIME

hour

DATE-TIME

num_events

INTEGER

num_minutes

INTEGER

page_id

STRING

parameters

STRING

remote_ip

STRING

server

STRING

user_agent

STRING

visitor_id

STRING

pages

The pages table contains info about specific pages in your Pendo app.

Replication Method	CDC
Primary Key	id
Replication Key	last_updated_at
Useful links	Pendo documentation Pendo API method

Join pages with	on
features	pages.group.id = features.group.id pages.id = features.page_id pages.created_by_user.id = features.created_by_user.id pages.group.created_by_user.id = features.created_by_user.id pages.group.last_updated_by_user.id = features.created_by_user.id pages.last_updated_by_user.id = features.created_by_user.id pages.created_by_user.id = features.group.created_by_user.id pages.group.created_by_user.id = features.group.created_by_user.id pages.group.last_updated_by_user.id = features.group.created_by_user.id pages.last_updated_by_user.id = features.group.created_by_user.id pages.created_by_user.id = features.group.last_updated_by_user.id pages.group.created_by_user.id = features.group.last_updated_by_user.id pages.group.last_updated_by_user.id = features.group.last_updated_by_user.id pages.last_updated_by_user.id = features.group.last_updated_by_user.id pages.created_by_user.id = features.last_updated_by_user.id pages.group.created_by_user.id = features.last_updated_by_user.id pages.group.last_updated_by_user.id = features.last_updated_by_user.id pages.last_updated_by_user.id = features.last_updated_by_user.id
track_types	pages.group.id = track_types.group.id pages.created_by_user.id = track_types.created_by_user.id pages.group.created_by_user.id = track_types.created_by_user.id pages.group.last_updated_by_user.id = track_types.created_by_user.id pages.last_updated_by_user.id = track_types.created_by_user.id pages.created_by_user.id = track_types.last_updated_by_user.id pages.group.created_by_user.id = track_types.last_updated_by_user.id pages.group.last_updated_by_user.id = track_types.last_updated_by_user.id pages.last_updated_by_user.id = track_types.last_updated_by_user.id
events	pages.id = events.page_id
guides	pages.id = guides.steps.page_id pages.created_by_user.id = guides.created_by_user.id pages.group.created_by_user.id = guides.created_by_user.id pages.group.last_updated_by_user.id = guides.created_by_user.id pages.last_updated_by_user.id = guides.created_by_user.id pages.created_by_user.id = guides.last_updated_by_user.id pages.group.created_by_user.id = guides.last_updated_by_user.id pages.group.last_updated_by_user.id = guides.last_updated_by_user.id pages.last_updated_by_user.id = guides.last_updated_by_user.id
page_events	pages.id = page_events.page_id
visitor_history	pages.id = visitor_history.page_id

app_id

NUMBER

color

STRING

created_at

DATE-TIME

created_by_user

OBJECT

This is a nested data structure:

first: STRING
id: STRING
last: STRING
role: INTEGER
username: INTEGER

dirty

BOOLEAN

group

OBJECT

This is a nested data structure:

color: STRING
created_at: DATE-TIME
created_by_user: OBJECT, which is also a nested data structure:
- first: STRING
- id: STRING
- last: STRING
- role: INTEGER
- username: STRING
description: STRING
id: STRING
last_updated_at: DATE-TIME
last_updated_by_user: OBJECT, which is also a nested data structure:
- first: STRING
- id: STRING
- last: STRING
- role: INTEGER
- username: STRING
length: INTEGER
name: STRING

STRING

kind

STRING

last_updated_at

DATE-TIME

last_updated_by_user

OBJECT

This is a nested data structure:

first: STRING
id: STRING
last: STRING
role: INTEGER
username: STRING

name

STRING

root_version_id

STRING

rules

ARRAY

This is a nested data structure:

designer_hint: STRING
parsed_rule: STRING
rule: STRING

stable_version_id

STRING

poll_events

The poll_events table contains info about poll events recorded in your Pendo account.

Note: The Period setting you define during setup determine how this table is replicated, including the field used as a Replication Key. Refer to the Replication section for more info.

Replication Method	CDC
Primary Keys	account_id remote_ip visitor_id browser_time poll_id
Replication Key	browser_time
Useful links	Pendo documentation Pendo API method

Join poll_events with	on
accounts	poll_events.account_id = accounts.account_id poll_events.account_ids = accounts.account_id
events	poll_events.account_id = events.account_id poll_events.account_ids = events.account_id poll_events.visitor_id = events.visitor_id
feature_events	poll_events.account_id = feature_events.account_id poll_events.account_ids = feature_events.account_id poll_events.visitor_id = feature_events.visitor_id
guide_events	poll_events.account_id = guide_events.account_id poll_events.account_ids = guide_events.account_id poll_events.account_id = guide_events.account_ids poll_events.account_ids = guide_events.account_ids poll_events.guide_id = guide_events.guide_id poll_events.poll_id = guide_events.poll_id poll_events.visitor_id = guide_events.visitor_id
page_events	poll_events.account_id = page_events.account_id poll_events.account_ids = page_events.account_id poll_events.visitor_id = page_events.visitor_id
track_events	poll_events.account_id = track_events.account_id poll_events.account_ids = track_events.account_id poll_events.visitor_id = track_events.visitor_id
visitors	poll_events.account_id = visitors.metadata_auto.accountid poll_events.account_ids = visitors.metadata_auto.accountid poll_events.account_id = visitors.metadata_auto.accountids poll_events.account_ids = visitors.metadata_auto.accountids poll_events.visitor_id = visitors.visitor_id
guides	poll_events.guide_id = guides.id poll_events.guide_id = guides.steps.guide_id poll_events.visitor_id = guides.audience.select.visitor_id
visitor_history	poll_events.guide_id = visitor_history.guide_id poll_events.visitor_id = visitor_history.visitor_id

account_id

STRING

account_ids

ARRAY

app_id

NUMBER

browser_time

DATE-TIME

country

STRING

guide_id

STRING

latitude

NUMBER

load_time

INTEGER

longitude

NUMBER

poll_id

STRING

poll_response

STRING

region

STRING

remote_ip

STRING

server_name

STRING

type

STRING

user_agent

STRING

visitor_id

STRING

track_events

The track_events table contains info about the track events recorded in your Pendo account.

Note: The Period setting you define during setup determine how this table is replicated, including the field used as a Replication Key. Refer to the Replication section for more info.

Replication Method

CDC

Primary Keys

account_id

remote_ip

server

visitor_id

day

track_type_id

user_agent

Useful links

Pendo documentation

Pendo API method

Join track_events with	on
accounts	track_events.account_id = accounts.account_id
events	track_events.account_id = events.account_id track_events.app_id = events.app_id track_events.visitor_id = events.visitor_id
feature_events	track_events.account_id = feature_events.account_id track_events.app_id = feature_events.app_id track_events.visitor_id = feature_events.visitor_id
guide_events	track_events.account_id = guide_events.account_id track_events.account_id = guide_events.account_ids track_events.app_id = guide_events.app_id track_events.visitor_id = guide_events.visitor_id
page_events	track_events.account_id = page_events.account_id track_events.app_id = page_events.app_id track_events.visitor_id = page_events.visitor_id
poll_events	track_events.account_id = poll_events.account_id track_events.account_id = poll_events.account_ids track_events.visitor_id = poll_events.visitor_id
visitors	track_events.account_id = visitors.metadata_auto.accountid track_events.account_id = visitors.metadata_auto.accountids track_events.visitor_id = visitors.visitor_id
features	track_events.app_id = features.created_by_user.app_id
visitor_history	track_events.app_id = visitor_history.app_id track_events.visitor_id = visitor_history.visitor_id
track_types	track_events.track_type_id = track_types.id
guides	track_events.visitor_id = guides.audience.select.visitor_id

account_id

STRING

app_id

NUMBER

day

DATE-TIME

hour

DATE-TIME

num_events

INTEGER

num_minutes

INTEGER

properties

OBJECT

This is a nested data structure:

android: BOOLEAN
any: BOOLEAN
apple: BOOLEAN
phone: BOOLEAN
table: BOOLEAN

remote_ip

STRING

server

STRING

track_type_id

STRING

user_agent

STRING

visitor_id

STRING

track_types

The track_types table contains info about

Replication Method

CDC

Primary Key

Useful links

Pendo API method

Join track_types with	on
features	track_types.group.id = features.group.id track_types.created_by_user.id = features.created_by_user.id track_types.last_updated_by_user.id = features.created_by_user.id track_types.created_by_user.id = features.group.created_by_user.id track_types.last_updated_by_user.id = features.group.created_by_user.id track_types.created_by_user.id = features.group.last_updated_by_user.id track_types.last_updated_by_user.id = features.group.last_updated_by_user.id track_types.created_by_user.id = features.last_updated_by_user.id track_types.last_updated_by_user.id = features.last_updated_by_user.id
pages	track_types.group.id = pages.group.id track_types.created_by_user.id = pages.created_by_user.id track_types.last_updated_by_user.id = pages.created_by_user.id track_types.created_by_user.id = pages.group.created_by_user.id track_types.last_updated_by_user.id = pages.group.created_by_user.id track_types.created_by_user.id = pages.group.last_updated_by_user.id track_types.last_updated_by_user.id = pages.group.last_updated_by_user.id track_types.created_by_user.id = pages.last_updated_by_user.id track_types.last_updated_by_user.id = pages.last_updated_by_user.id
track_events	track_types.id = track_events.track_type_id
guides	track_types.created_by_user.id = guides.created_by_user.id track_types.last_updated_by_user.id = guides.created_by_user.id track_types.created_by_user.id = guides.last_updated_by_user.id track_types.last_updated_by_user.id = guides.last_updated_by_user.id

app_id

NUMBER

color

STRING

created_at

DATE-TIME

created_by_user

OBJECT

This is a nested data structure:

first: STRING
id: STRING
last: STRING
role: INTEGER
username: STRING

dirty

BOOLEAN

group

OBJECT

This is a nested data structure:

color: STRING
description: STRING
id: STRING
length: INTEGER
name: STRING

STRING

kind

STRING

last_updated_at

DATE-TIME

last_updated_by_user

OBJECT

This is a nested data structure:

color: STRING
description: STRING
id: STRING
length: INTEGER
name: STRING

name

STRING

root_version_id

STRING

stable_version_id

STRING

track_type_name

BOOLEAN

track_type_rules

ARRAY

visitor_history

The visitor_history table contains info about visitor activity.

Replication Method	CDC
Primary Key	visitor_id
Replication Key	modified_ts
Useful links	Pendo documentation Pendo API method

Join visitor_history with	on
events	visitor_history.app_id = events.app_id visitor_history.feature_id = events.feature_id visitor_history.page_id = events.page_id visitor_history.visitor_id = events.visitor_id
feature_events	visitor_history.app_id = feature_events.app_id visitor_history.feature_id = feature_events.feature_id visitor_history.visitor_id = feature_events.visitor_id
features	visitor_history.app_id = features.created_by_user.app_id visitor_history.feature_id = features.id visitor_history.page_id = features.page_id
guide_events	visitor_history.app_id = guide_events.app_id visitor_history.guide_id = guide_events.guide_id visitor_history.visitor_id = guide_events.visitor_id
page_events	visitor_history.app_id = page_events.app_id visitor_history.page_id = page_events.page_id visitor_history.visitor_id = page_events.visitor_id
track_events	visitor_history.app_id = track_events.app_id visitor_history.visitor_id = track_events.visitor_id
guides	visitor_history.guide_id = guides.id visitor_history.guide_id = guides.steps.guide_id visitor_history.guide_id = guides.steps.id visitor_history.page_id = guides.steps.page_id visitor_history.visitor_id = guides.audience.select.visitor_id
poll_events	visitor_history.guide_id = poll_events.guide_id visitor_history.visitor_id = poll_events.visitor_id
pages	visitor_history.page_id = pages.id
visitors	visitor_history.visitor_id = visitors.visitor_id

app_id

NUMBER

duration

INTEGER

feature_id

STRING

guide_id

STRING

guide_step_id

STRING

last_ts

DATE-TIME

modified_ts

DATE-TIME

page_id

STRING

parsed_user_agent

OBJECT

This is a nested data structure:

name: STRING
os: STRING
version: STRING

DATE-TIME

type

STRING

untagged_url

STRING

uri

STRING

visitor_id

STRING

visitors

The visitors table contains info about the visitors recorded in your Pendo account.

Replication Method	CDC
Primary Key	visitor_id
Replication Key	lastupdated
Useful links	Pendo documentation Pendo API method

Join visitors with	on
accounts	visitors.metadata_auto.accountid = accounts.account_id visitors.metadata_auto.accountids = accounts.account_id
events	visitors.metadata_auto.accountid = events.account_id visitors.metadata_auto.accountids = events.account_id visitors.visitor_id = events.visitor_id
feature_events	visitors.metadata_auto.accountid = feature_events.account_id visitors.metadata_auto.accountids = feature_events.account_id visitors.visitor_id = feature_events.visitor_id
guide_events	visitors.metadata_auto.accountid = guide_events.account_id visitors.metadata_auto.accountids = guide_events.account_id visitors.metadata_auto.accountid = guide_events.account_ids visitors.metadata_auto.accountids = guide_events.account_ids visitors.visitor_id = guide_events.visitor_id
page_events	visitors.metadata_auto.accountid = page_events.account_id visitors.metadata_auto.accountids = page_events.account_id visitors.visitor_id = page_events.visitor_id
poll_events	visitors.metadata_auto.accountid = poll_events.account_id visitors.metadata_auto.accountids = poll_events.account_id visitors.metadata_auto.accountid = poll_events.account_ids visitors.metadata_auto.accountids = poll_events.account_ids visitors.visitor_id = poll_events.visitor_id
track_events	visitors.metadata_auto.accountid = track_events.account_id visitors.metadata_auto.accountids = track_events.account_id visitors.visitor_id = track_events.visitor_id
guides	visitors.visitor_id = guides.audience.select.visitor_id
visitor_history	visitors.visitor_id = visitor_history.visitor_id

lastupdated

DATE-TIME

metadata_agent

OBJECT

This is a nested data structure:

email: STRING
ipaddress: STRING
language: STRING

metadata_auto

OBJECT

This is a nested data structure:

accountid: STRING
accountids: ARRAY, which is also a nested data structure:
- firstvisit: DATE-TIME
- id: STRING
- idhash: INTEGER
- lastbrowsername: STRING
- lastbrowserversion: STRING
- lastoperatingsystem: STRING
- lastservername: STRING
- lastupdated: DATE-TIME
- lastuseragent: STRING
- lastvisit: DATE-TIME
- nid: INTEGER

metadata_custom

OBJECT

visitor_id

STRING

Cette page vous a-t-elle aidé ?

Si vous rencontrez des problèmes sur cette page ou dans son contenu – une faute de frappe, une étape manquante ou une erreur technique – faites-le-nous savoir.

Laissez vos commentaires ici