Pardot
Pardot is a marketing automation solution that enables marketers to identify prospective customers that are most likely to convert.
Pardot integration replicates data using the Pardot API.
See the
Schema section for a list of objects available for replication.
유용한 링크와 지원되는 기능을 포함하여 이 커넥터에 대한 전반적인 내용을 살펴보겠습니다.
| 특징/기능 | 지원 세부 정보 |
|---|
| 지원되는 Qlik Talend Data Integration 프로젝트 | 복제 프로젝트에만 해당됩니다. 데이터 파이프라인 프로젝트는 지원되지 않습니다. |
대상 업데이트 방법 | 복제 작업: 데이터 레이크 작업에 데이터 랜딩: |
메타데이터 관리 | 수동 메타데이터 생성이 필요하지 않습니다. |
스키마 진화 | 열 데이터 유형 변경 작업만 지원됩니다. |
| LOB 열(NCLOB, CLOB 및 BLOB) 복제 | 지원되지 않음. |
| 예정된 CDC | 필수. 이렇게 하면 소스의 변경 내용이 대상에 최신 상태로 유지됩니다. 복제 작업의 경우 작업 예약 을 참조하십시오. 레이크 랜딩 작업의 경우 레이크 랜딩 작업을 위한 CDC 일정을 참조하십시오. |
| 알림 | 부분적으로 지원됨 작업 변경 알림 설정 |
| 모니터링 중 | CDC에만 해당되며, 이 커넥터의 경우 전체 로드가 적용되지 않습니다. 개별 데이터 작업 모니터링 |
| JSON 열 페이로드의 자동 압축 해제 | 지원되지 않음. 소스 데이터 집합의 JSON 열 페이로드는 대상에서 자동으로 압축 해제되지 않습니다. |
Preparing for authentication
To access your data, you need to authenticate the connection with your account credentials.
정보 메모사용하는 계정에 가져오려는 테이블에 대한 읽기 액세스 권한이 있는지 확인합니다.
To retrieve your business unit ID:
- Log into your Salesforce account.
- Navigate to Setup.
- Search for Pardot in the Quick Find box.
- Copy and paste your business unit ID into a secured file.
To retrieve your consumer key and secret:
- Log into your Salesforce account.
- Navigate to Setup.
- Search for App Manager in the Quick Find box.
- Go to your connected app and select View.
- Copy and paste your consumer key into a secured file.
- Click Click to reveal to show your consumer secret and copy it.
Creating the connection
For more information, see SaaS 응용 프로그램에 연결.
Click Authenticate when you have filled in the required connection settings.
You may be asked to log in to the source application.
A window is displayed with an authentication code.
Copy the code to the clipboard and return to the connection dialog.
Paste the code in Complete authentication with the code provided by the source and click Verify.
팁 메모You may need to scroll down to see this field.
When status is Verified, the authentication is verified.
Provide a name for the connection in Connection name.
Select Open connection metadata to define metadata for the connection when it has been created.
Connection settings| Setting | Description |
|---|
| Data gateway | 사용 사례에 필요한 경우 데이터 이동 게이트웨이를 선택합니다. 정보 메모이 필드는 데이터 이동 게이트웨이를 지원하지 않으므로 Qlik Talend Cloud 시작 구독에서는 사용할 수 없습니다. 다른 구독 계층이 있고 데이터 이동 게이트웨이를 사용하지 않으려면 없음을 선택합니다. 데이터 이동 게이트웨이의 이점과 이를 필요로 하는 사용 사례에 대한 자세한 내용은 Qlik 데이터 게이트웨이 - 데이터 이동를 참조하십시오. |
| Start Date | 데이터를 소스에서 대상으로 복제해야 하는 날짜를 MM/DD/YYYY 형식으로 입력합니다. |
| Pardot Business Unit ID | Business unit ID.
|
| Consumer Key | A unique identifier for the connected app.
|
| Consumer Secret | A password for the connected app.
|
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.
campaigns
The campaigns table contains info about the campaigns in your Pardot account.
| Join campaigns with | on |
|---|
| opportunities | campaigns.id = opportunities.campaign_id |
| prospects | campaigns.id = prospects.campaign_id |
cost
INTEGER
|
id
INTEGER
|
name
STRING
|
email_clicks
The email_clicks table contains info about email click events.
| Join email_clicks with | on |
|---|
| visitor_activities | email_clicks.email_template_id = visitor_activities.email_template_id email_clicks.list_email_id = visitor_activities.list_email_id email_clicks.prospect_id = visitor_activities.prospect_id |
| list_memberships | email_clicks.prospect_id = list_memberships.prospect_id |
| prospects | email_clicks.prospect_id = prospects.id |
| visits | email_clicks.prospect_id = visits.prospect_id |
created_at
DATE-TIME
|
drip_program_action_id
INTEGER
|
email_template_id
INTEGER
|
id
INTEGER
|
list_email_id
INTEGER
|
prospect_id
INTEGER
|
tracker_redirect_id
INTEGER
|
url
STRING
|
list_memberships
The list_memberships table contains info about list memberships.
Note: To replicate this table, the lists table must also be set to replicate.
| Join list_memberships with | on |
|---|
| lists | list_memberships.list_id = lists.id |
| email_clicks | list_memberships.prospect_id = email_clicks.prospect_id |
| prospects | list_memberships.prospect_id = prospects.id |
| visitor_activities | list_memberships.prospect_id = visitor_activities.prospect_id |
| visits | list_memberships.prospect_id = visits.prospect_id |
created_at
DATE-TIME
|
id
INTEGER
|
list_id
INTEGER
|
opted_out
INTEGER
|
prospect_id
INTEGER
|
updated_at
DATE-TIME
|
lists
The lists table contains info about the lists in your Pardot account.
created_at
DATE-TIME
|
description
STRING
|
id
INTEGER
|
is_crm_visible
BOOLEAN
|
is_dynamic
BOOLEAN
|
is_public
BOOLEAN
|
name
STRING
|
title
STRING
|
updated_at
DATE-TIME
|
opportunities
The opportunities table contains info about the opportunities in your Pardot account.
| Join opportunities with | on |
|---|
| campaigns | opportunities.campaign_id = campaigns.id |
| prospects | opportunities.campaign_id = prospects.campaign_id |
campaign_id
INTEGER
|
closed_at
DATE-TIME
|
created_at
DATE-TIME
|
id
INTEGER
|
name
STRING
|
probability
INTEGER
|
stage
STRING
|
status
STRING
|
type
STRING
|
updated_at
DATE-TIME
|
value
NUMBER
|
prospect_accounts
The prospect_accounts table contains info about prospect accounts.
| Join prospect_accounts with | on |
|---|
| users | prospect_accounts.assigned_to.user.id = users.id |
assigned_to
OBJECT
This is a nested data structure: - user: OBJECT, which is also a nested data structure.
- account: INTEGER
- created_at: DATE-TIME
- email: STRING
- first_name: STRING
- id: INTEGER
- job_tile: STRING
- last_name: STRING
- role: STRING
- updated_at: DATE-TIME
|
created_at
DATE-TIME
|
id
INTEGER
|
name
STRING
|
updated_at
DATE-TIME
|
prospects
The prospects table contains info about the prospects in your Pardot account.
address_one
STRING
|
address_two
STRING
|
annual_revenue
STRING
|
campaign_id
INTEGER
|
city
STRING
|
comments
STRING
|
company
STRING
|
country
STRING
|
created_at
DATE-TIME
|
crm_account_fid
STRING
|
crm_contact_fid
STRING
|
crm_last_sync
DATE-TIME
|
crm_lead_fid
STRING
|
crm_owner_fid
STRING
|
crm_url
STRING
|
department
STRING
|
email
STRING
|
employees
STRING
|
fax
STRING
|
first_name
STRING
|
grade
STRING
|
id
INTEGER
|
industry
STRING
|
is_do_not_call
BOOLEAN
|
is_do_not_email
BOOLEAN
|
is_reviewed
BOOLEAN
|
is_starred
BOOLEAN
|
job_title
STRING
|
last_activity_at
DATE-TIME
|
last_name
STRING
|
notes
STRING
|
opted_out
BOOLEAN
|
password
STRING
|
phone
STRING
|
prospect_account_id
INTEGER
|
recent_interaction
STRING
|
salutation
STRING
|
score
INTEGER
|
source
STRING
|
state
STRING
|
territory
STRING
|
updated_at
DATE-TIME
|
website
STRING
|
years_in_business
STRING
|
zip
STRING
|
users
The users table contains info about the users in your Pardot account.
created_at
DATE-TIME
|
email
STRING
|
first_name
STRING
|
id
INTEGER
|
job_title
STRING
|
last_name
STRING
|
role
STRING
|
updated_at
DATE-TIME
|
visitor_activities
The visitor_activities table contains info about visitor activities.
| Join visitor_activities with | on |
|---|
| email_clicks | visitor_activities.email_template_id = email_clicks.email_template_id visitor_activities.list_email_id = email_clicks.list_email_id visitor_activities.prospect_id = email_clicks.prospect_id |
| list_memberships | visitor_activities.prospect_id = list_memberships.prospect_id |
| prospects | visitor_activities.prospect_id = prospects.id |
| visits | visitor_activities.prospect_id = visits.prospect_id visitor_activities.visitor_id = visits.visitor_id |
| visitors | visitor_activities.visitor_id = visitors.id |
campaign
OBJECT
This is a nested data structure. |
campaign_id
INTEGER
|
created_at
DATE-TIME
|
details
STRING
|
email_id
INTEGER
|
email_template_id
INTEGER
|
file_id
INTEGER
|
form_handler_id
INTEGER
|
form_id
INTEGER
|
id
INTEGER
|
landing_page_id
INTEGER
|
list_email_id
INTEGER
|
multivariate_test_variation_id
INTEGER
|
paid_search_id_id
INTEGER
|
prospect_id
INTEGER
|
site_search_query_id
INTEGER
|
type
INTEGER
|
type_name
STRING
|
updated_at
DATE-TIME
|
visitor_id
INTEGER
|
visitor_page_view_id
INTEGER
|
visitors
The visitors table contains info about visitors.
campaign_parameter
STRING
|
content_parameter
STRING
|
created_at
DATE-TIME
|
hostname
STRING
|
id
INTEGER
|
ip_address
STRING
|
medium_parameter
STRING
|
page_view_count
INTEGER
|
source_parameter
STRING
|
term_parameter
STRING
|
updated_at
DATE-TIME
|
visits
The visits table contains info about visits.
Note: To replicate this table, you must also set the visitors table to replicate.
| Join visits with | on |
|---|
| email_clicks | visits.prospect_id = email_clicks.prospect_id |
| list_memberships | visits.prospect_id = list_memberships.prospect_id |
| prospects | visits.prospect_id = prospects.id |
| visitor_activities | visits.prospect_id = visitor_activities.prospect_id visits.visitor_id = visitor_activities.visitor_id |
| visitors | visits.visitor_id = visitors.id |
campaign_parameter
STRING
|
content_parameter
STRING
|
created_at
DATE-TIME
|
duration_in_seconds
INTEGER
|
first_visitor_page_view_at
DATE-TIME
|
id
INTEGER
|
last_visitor_page_view_at
DATE-TIME
|
medium_parameter
STRING
|
prospect_id
INTEGER
|
source_parameter
STRING
|
term_parameter
STRING
|
updated_at
DATE-TIME
|
visitor_id
INTEGER
|
visitor_page_view_count
INTEGER
|
visitor_page_views
OBJECT
This is a nested data structure: - visitor_page_view: ARRAY, which is also a nested data structure.
- created_at: DATE-TIME
- id: INTEGER
- title: STRING
- url: STRING
|
