ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
Connecting to Marketo (REST API): Credentials & Fields
3
4
5
Use this template to help you collect the details within your Marketo instance needed to connect to and post leads from PeerSpot
6
Filling in all required ** info is necessary to integrate Marketo with PeerSpot
7
8
Customizing the template
9
Depending on how you wish to route leads within Marketo, values may be static or could vary (eg. by region/team, Campaign/Source, asset downloaded).
10
If multiple values will be used, we recommend listing them out in a format that makes them easy to view.
11
For example: You might add a column to your media plan for each variable value and list the corresponding values in line with each Source's set-up details.
12
13
My Marketo Credentials** Indicates a required value
14
Client ID **Client Secret **REST API Endpoint URL **REST API Identity URL **programName **programStatussourcereason
15
Corresponds to a Launchpoint service with an API Only User assigned within Marketo.Corresponds to a Launchpoint service with an API Only User assigned within Marketo.Static values unique to your Marketo instance. Located in Admin > Web Services > REST API.Static values unique to your Marketo instance. Located in Admin > Web Services > REST API.Required to use this feature. Must be the exact name of Program in Marketo.Optional, but if used this must be the exact value of Program Status in Marketo. If left blank, Marketo will assign default status for the program.OptionalOptional
16
[Paste your Client ID here][Paste your Client Secret here][Paste your Endpoint URL here][Paste your Identity URL here][Paste your Program Name here][Paste your Program Status here][Paste your Source here][Paste your Reason here]
17
18
19
My Marketo Field Details
20
21
When using the following fields / validations:
22
Email domains - If a blocked / allowed domain list must be used, add this information in the Domain Lists tab.
23
List values - For all list fields, provide the corresponding values in the Picklists tab.
24
LeadID - It’s recommended that this field is used; ensure that Marketo is able to accept alphanumeric characters. This is required if using closed loop reporting.
25
26
REST API Field NamesRequired / OptionalField TypeField validation requirementsExample data
27
List the names of every field in
your Marketo Launchpoint service.		State if the Marketo field is
Required or Optional.		State the type of the Marketo field:
eg. text, list, date, integer, phone, Boolean.		Make a note of any
field validation requirements.		Provide a sample value to illustrate the expected data format.
28
Sample values - delete and populate with your Field Details.
29
firstNameRequiredTextJoe
30
lastNameRequiredTextSmith
31
emailRequiredEmailBlock competitor domainsjsmith@integrate.com
32
phoneOptionalPhone123-456-7890
33
address1OptionalText123 Main Street
34
address2OptionalTextSuite 2
35
cityOptionalTextBoston
36
zipPostalOptionalText98987
37
stateOptionalListRequired for US and CanadaMA
38
countryRequiredListUS
39
companyRequiredTextIntegrate
40
titleRequiredTextDirector of IT
41
levelRequiredListDirector
42
industryOptionalListTechnology
43
numberofemployeesOptionalList100-500
44
assetDownloadedOptionalTextAwesome Asset Title Here
45
mktoPersonNotesOptionalTextMaximum 250 characters, follow example formatDiscussion notes: Some notes would go here - Other notes: More notes would go here
46
optInRequiredBooleanTrue/False values onlyTrue
47
IntegrateLeadIDRequiredText1ab2cdef-3g45-6h78-i90j-1234k5l6m7no
48
mediaPartnerOptionalTextLead2Rev
49
LinkedInLeadIDOptionalText1234567a-8b9c-0d12-e34f-56g789012h34-5
50
LinkedInCampaignIDOptionalText012345678
51
WebinarActivityTypeOptionalListLive
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100