Skip to main content

Marketo

Setting up the Marketo connector

NoItemRequiredExampleNotes
1Client IDYesThe Client ID of your Marketo developer application. See the docs for info on how to obtain this.
2Client SecretYesThe Client Secret of your Marketo developer application. See the docs for info on how to obtain this.
3Start DateYes2020-09-25T00:00:00ZUTC date and time in the format 2017-01-25T00:00:00Z. Any data before this date will not be replicated.
4Domain URLYeshttps://000-AAA-000.mktorest.comYour Marketo Base URL. See the docs for info on how to obtain this.

Tables in the Marketo connector

NoTable NameColumnsPrimary KeysRead ModeInc. Sync KeysAPI Info
1campaigns10idFull Refresh, IncrementalcreatedAt
2lists8idFull Refresh, IncrementalcreatedAt
3leads90idFull Refresh, IncrementalupdatedAt
4activity_types5idFull Refresh
5programs12idFull Refresh, IncrementalupdatedAt

Table: campaigns

NoColumn NameTypeNotes
1createdAtVARCHARIncremental sync key
2programNameVARCHAR
3nameVARCHAR
4activeBOOLEAN
5descriptionVARCHAR
6workspaceNameVARCHAR
7idINTEGERPrimary Key
8typeVARCHAR
9programIdINTEGER
10updatedAtVARCHAR

Table: lists

NoColumn NameTypeNotes
1createdAtVARCHARIncremental sync key
2programNameVARCHAR
3nameVARCHAR
4descriptionVARCHAR
5workspaceNameVARCHAR
6idINTEGERPrimary Key
7updatedAtVARCHAR
8workspaceIdINTEGER

Table: leads

NoColumn NameTypeNotes
1contactCompanyVARCHAR
2countryVARCHAR
3leadStatusVARCHAR
4isLeadBOOLEAN
5originalSourceInfoVARCHAR
6mainPhoneVARCHAR
7originalSourceTypeVARCHAR
8mktoIsPartnerBOOLEAN
9postalCodeVARCHAR
10inferredPostalCodeVARCHAR
11ratingVARCHAR
12mktoNameVARCHAR
13mktoPersonNotesVARCHAR
14inferredCompanyVARCHAR
15createdAtVARCHAR
16mktoDoNotCallCauseVARCHAR
17registrationSourceInfoVARCHAR
18registrationSourceTypeVARCHAR
19inferredMetropolitanAreaVARCHAR
20billingCountryVARCHAR
21idINTEGERPrimary Key
22stateVARCHAR
23faxVARCHAR
24anonymousIPVARCHAR
25relativeUrgencyINTEGER
26updatedAtVARCHARIncremental sync key
27inferredStateRegionVARCHAR
28originalSearchEngineVARCHAR
29leadRevenueCycleModelIdVARCHAR
30inferredCityVARCHAR
31originalSearchPhraseVARCHAR
32leadSourceVARCHAR
33mktoIsCustomerBOOLEAN
34mktoAcquisitionDateVARCHAR
35billingStateVARCHAR
36priorityINTEGER
37numberOfEmployeesINTEGER
38firstNameVARCHAR
39externalSalesPersonIdVARCHAR
40isAnonymousBOOLEAN
41externalCompanyIdVARCHAR
42mobilePhoneVARCHAR
43phoneVARCHAR
44doNotCallBOOLEAN
45inferredPhoneAreaCodeVARCHAR
46salutationVARCHAR
47annualRevenueDOUBLE
48marketingSuspendedCauseVARCHAR
49leadScoreINTEGER
50lastNameVARCHAR
51personPrimaryLeadInterestVARCHAR
52cityVARCHAR
53emailInvalidCauseVARCHAR
54industryVARCHAR
55mktoCompanyNotesVARCHAR
56titleVARCHAR
57marketingSuspendedBOOLEAN
58doNotCallReasonVARCHAR
59cookiesVARCHAR
60unsubscribedReasonVARCHAR
61originalReferrerVARCHAR
62personTimeZoneVARCHAR
63blackListedCauseVARCHAR
64leadPersonVARCHAR
65emailSuspendedBOOLEAN
66urgencyDOUBLE
67emailSuspendedAtVARCHAR
68leadRevenueStageIdVARCHAR
69emailInvalidBOOLEAN
70companyVARCHAR
71personTypeVARCHAR
72departmentVARCHAR
73emailVARCHAR
74websiteVARCHAR
75addressVARCHAR
76emailSuspendedCauseVARCHAR
77dateOfBirthVARCHAR
78leadPartitionIdVARCHAR
79blackListedBOOLEAN
80leadRoleVARCHAR
81siteVARCHAR
82unsubscribedBOOLEAN
83relativeScoreINTEGER
84acquisitionProgramIdVARCHAR
85inferredCountryVARCHAR
86billingStreetVARCHAR
87billingPostalCodeVARCHAR
88sicCodeVARCHAR
89middleNameVARCHAR
90billingCityVARCHAR

Table: activity_types

NoColumn NameTypeNotes
1primaryAttributeVARCHAR
2nameVARCHAR
3descriptionVARCHAR
4attributesVARCHAR
5idINTEGERPrimary Key

Table: programs

NoColumn NameTypeNotes
1createdAtVARCHAR
2workspaceVARCHAR
3folderVARCHAR
4nameVARCHAR
5channelVARCHAR
6descriptionVARCHAR
7idINTEGERPrimary Key
8typeVARCHAR
9urlVARCHAR
10headStartBOOLEAN
11updatedAtVARCHARIncremental sync key
12statusVARCHAR

External Resources

Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.