Mailshake
Mailshake is a sales engagement platform designed to streamline and automate cold outreach efforts.
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 generate the API key:
- Log into your Mailshake account.
- Go to Extensions > API.
- Click Create API Key to create an API key. Your API key is displayed on the page.
If your account already has an API key, it is displayed in the Your Access section of the page.
- Fill in your API key in the Connection settings page.
Creating the connection
자세한 내용은 SaaS 응용 프로그램에 연결을 참조하십시오.
- 필요한 연결 속성을 입력합니다.
연결 이름에 연결 이름을 입력합니다.
연결이 만들어질 때 연결에 대한 메타데이터를 정의하려면 연결 메타데이터 열기를 선택합니다.
만들기를 클릭합니다.
Connection settings| Setting | Description |
|---|
| Data gateway | 사용 사례에 필요한 경우 데이터 이동 게이트웨이를 선택합니다. 정보 메모이 필드는 데이터 이동 게이트웨이를 지원하지 않으므로 Qlik Talend Cloud 시작 구독에서는 사용할 수 없습니다. 다른 구독 계층이 있고 데이터 이동 게이트웨이를 사용하지 않으려면 없음을 선택합니다. 데이터 이동 게이트웨이의 이점과 이를 필요로 하는 사용 사례에 대한 자세한 내용은 Qlik 데이터 게이트웨이 - 데이터 이동를 참조하십시오. |
| Start Date | 데이터를 소스에서 대상으로 복제해야 하는 날짜를 MM/DD/YYYY 형식으로 입력합니다. |
| API Key | API key. |
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 your team’s campaigns.
| Join campaigns with | on |
|---|
| clicks | campaigns.id = clicks.campaign.id campaigns.messages.id = clicks.campaign.id campaigns.messages.id = clicks.parent.message.id |
| leads | campaigns.id = leads.campaign.id campaigns.messages.id = leads.campaign.id |
| opens | campaigns.id = opens.campaign.id campaigns.messages.id = opens.campaign.id campaigns.messages.id = opens.parent.message.id |
| recipients | campaigns.id = recipients.campaignId campaigns.messages.id = recipients.campaignId |
| replies | campaigns.id = replies.campaign.id campaigns.messages.id = replies.campaign.id campaigns.messages.id = replies.parent.message.id |
| sent_messages | campaigns.id = sent_messages.campaign.id campaigns.messages.id = sent_messages.campaign.id campaigns.messages.id = sent_messages.message.id |
| senders | campaigns.sender.id = senders.id |
actionDate
DATE-TIME
|
archived
BOOLEAN
|
created
DATE-TIME
|
endedAt
DATE-TIME
|
id
INTEGER
|
isPaused
BOOLEAN
|
messages
ARRAY
This is a nested data structure: - campaignId: INTEGER
- id: INTEGER
- isPaused: BOOLEAN
- object: STRING
- replyToID: INTEGER
- subject: STRING
- type: STRING
|
object
STRING
|
sender
OBJECT
This is a nested data structure: - created: DATE-TIME
- emailAddress: STRING
- fromName: STRING
- id: STRING
- object: STRING
|
title
STRING
|
url
STRING
|
clicks
The clicks table contains info about recent click activity.
| Join clicks with | on |
|---|
| campaigns | clicks.campaign.id = campaigns.id clicks.campaign.id = campaigns.messages.id clicks.parent.message.id = campaigns.messages.id |
| leads | clicks.campaign.id = leads.campaign.id clicks.recipient.id = leads.recipient.id |
| opens | clicks.campaign.id = opens.campaign.id clicks.parent.message.id = opens.parent.message.id clicks.recipient.id = opens.recipient.id |
| recipients | clicks.campaign.id = recipients.campaignId clicks.recipient.id = recipients.id |
| replies | clicks.campaign.id = replies.campaign.id clicks.parent.message.id = replies.parent.message.id clicks.recipient.id = replies.parent.message.id |
| sent_messages | clicks.campaign.id = sent_messages.campaign.id clicks.parent.message.id = sent_messages.message.id clicks.recipient.id = sent_messages.recipient.id |
actionDate
DATE-TIME
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
id
INTEGER
|
isDuplicate
BOOLEAN
|
link
STRING
|
object
STRING
|
parent
OBJECT
This is a nested data structure: - id: INTEGER
- message: OBJECT, which is also a nested data structure.
- id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
- object: STRING
- type: STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
leads
The leads table contains info about the leads in your Mailshake account.
| Join leads with | on |
|---|
| campaigns | leads.campaign.id = campaigns.id leads.campaign.id = campaigns.messages.id |
| clicks | leads.campaign.id = clicks.campaign.id leads.recipient.id = clicks.recipient.id |
| opens | leads.campaign.id = opens.campaign.id leads.recipient.id = opens.recipient.id |
| recipients | leads.campaign.id = recipients.campaignId leads.recipient.id = recipients.id |
| replies | leads.campaign.id = replies.campaign.id leads.recipient.id = replies.parent.message.id |
| sent_messages | leads.campaign.id = sent_messages.campaign.id leads.recipient.id = sent_messages.recipient.id |
| team_members | leads.assignedTo.id = team_members.id |
assignedTo
OBJECT
This is a nested data structure: - emailAddress: STRING
- first: STRING
- fullName: STRING
- id: INTEGER
- last: STRING
- object: STRING
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
created
DATE-TIME
|
id
INTEGER
|
lastStatusChangeDate
DATE-TIME
|
object
STRING
|
openedDate
DATE-TIME
|
recipient
OBJECT
This is a nested data structure: - created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- last: STRING
- object: STRING
|
status
STRING
|
opens
The opens table contains info about recently opened emails.
| Join opens with | on |
|---|
| campaigns | opens.campaign.id = campaigns.id opens.campaign.id = campaigns.messages.id opens.parent.message.id = campaigns.messages.id |
| clicks | opens.campaign.id = clicks.campaign.id opens.parent.message.id = clicks.parent.message.id opens.recipient.id = clicks.recipient.id |
| leads | opens.campaign.id = leads.campaign.id opens.recipient.id = leads.recipient.id |
| recipients | opens.campaign.id = recipients.campaignId opens.recipient.id = recipients.id |
| replies | opens.campaign.id = replies.campaign.id opens.parent.message.id = replies.parent.message.id opens.recipient.id = replies.parent.message.id |
| sent_messages | opens.campaign.id = sent_messages.campaign.id opens.parent.message.id = sent_messages.message.id opens.recipient.id = sent_messages.recipient.id |
actionDate
DATE-TIME
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
id
INTEGER
|
isDuplicate
BOOLEAN
|
object
STRING
|
parent
OBJECT
This is a nested data structure: - id: INTEGER
- message: OBJECT, which is also a nested data structure.
- id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
- object: STRING
- type: STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
recipients
The recipients table contains info about the recipients in a campaign.
| Join recipients with | on |
|---|
| campaigns | recipients.campaignId = campaigns.id recipients.campaignId = campaigns.messages.id |
| clicks | recipients.campaignId = clicks.campaign.id recipients.id = clicks.recipient.id |
| leads | recipients.campaignId = leads.campaign.id recipients.id = leads.recipient.id |
| opens | recipients.campaignId = opens.campaign.id recipients.id = opens.recipient.id |
| replies | recipients.campaignId = replies.campaign.id recipients.id = replies.parent.message.id |
| sent_messages | recipients.campaignId = sent_messages.campaign.id recipients.id = sent_messages.recipient.id |
action
STRING
|
campaignId
INTEGER
|
created
DATE-TIME
|
emailAddress
STRING
|
fields
OBJECT
This is a nested data structure. |
first
STRING
|
fullName
STRING
|
id
INTEGER
|
last
STRING
|
object
STRING
|
replies
The replies table contains info about recent replies to your emails.
| Join replies with | on |
|---|
| campaigns | replies.campaign.id = campaigns.id replies.campaign.id = campaigns.messages.id replies.parent.message.id = campaigns.messages.id |
| clicks | replies.campaign.id = clicks.campaign.id replies.parent.message.id = clicks.parent.message.id replies.parent.message.id = clicks.recipient.id |
| leads | replies.campaign.id = leads.campaign.id replies.parent.message.id = leads.recipient.id |
| opens | replies.campaign.id = opens.campaign.id replies.parent.message.id = opens.parent.message.id replies.parent.message.id = opens.recipient.id |
| recipients | replies.campaign.id = recipients.campaignId replies.parent.message.id = recipients.id |
| sent_messages | replies.campaign.id = sent_messages.campaign.id replies.parent.message.id = sent_messages.message.id replies.parent.message.id = sent_messages.recipient.id |
actionDate
DATE-TIME
|
body
STRING
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
externalConversationID
STRING
|
externalID
STRING
|
externalRawMessageID
STRING
|
id
INTEGER
|
object
STRING
|
parent
OBJECT
This is a nested data structure: - id: INTEGER
- message: OBJECT, which is also a nested data structure.
- id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
- object: STRING
- type: STRING
|
plainTextBody
STRING
|
rawBody
STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
subject
STRING
|
type
STRING
|
senders
The senders table contains info about your team’s senders.
| Join senders with | on |
|---|
| campaigns | senders.id = campaigns.sender.id |
created
DATE-TIME
|
emailAddress
STRING
|
fromName
STRING
|
id
STRING
|
object
STRING
|
offerType
STRING
|
sent_messages
The sent_messages table contains info about recently sent emails.
| Join sent_messages with | on |
|---|
| campaigns | sent_messages.campaign.id = campaigns.id sent_messages.campaign.id = campaigns.messages.id sent_messages.message.id = campaigns.messages.id |
| clicks | sent_messages.campaign.id = clicks.campaign.id sent_messages.message.id = clicks.parent.message.id sent_messages.recipient.id = clicks.recipient.id |
| leads | sent_messages.campaign.id = leads.campaign.id sent_messages.recipient.id = leads.recipient.id |
| opens | sent_messages.campaign.id = opens.campaign.id sent_messages.message.id = opens.parent.message.id sent_messages.recipient.id = opens.recipient.id |
| recipients | sent_messages.campaign.id = recipients.campaignId sent_messages.recipient.id = recipients.id |
| replies | sent_messages.campaign.id = replies.campaign.id sent_messages.message.id = replies.parent.message.id sent_messages.recipient.id = replies.parent.message.id |
actionDate
DATE-TIME
|
body
STRING
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
externalConversationID
STRING
|
externalID
STRING
|
externalRawMessageID
STRING
|
from
OBJECT
This is a nested data structure: - address: STRING
- first: STRING
- fullName: STRING
- last: STRING
- object: STRING
|
id
INTEGER
|
message
OBJECT
This is a nested data structure: - id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
|
object
STRING
|
plainTextBody
STRING
|
rawBody
STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
subject
STRING
|
to
ARRAY
This is a nested data structure: - address: STRING
- first: STRING
- fullName: STRING
- last: STRING
- object: STRING
|
type
STRING
|
team_members
The team_members table contains info about the individual members of your team.
| Join team_members with | on |
|---|
| leads | team_members.id = leads.assignedTo.id |
emailAddress
STRING
|
first
STRING
|
fullName
STRING
|
id
INTEGER
|
isDisabled
BOOLEAN
|
isTeamAdmin
BOOLEAN
|
last
STRING
|
object
STRING
|
teamBlockedDate
DATE-TIME
|
teamID
INTEGER
|
teamName
BOOLEAN
|