Marketo MA drush commands
All commands in marketo_ma: (marketo_ma)
This module adds Marketo tracking capability to your Drupal site.
The Marketo MA configuration page can be found under Configuration > Search and metadata > Marketo MA. The direct path is admin/config/search/marketo_ma.
API Configuration
Field Definition
Page Visibility
Role Visibility
User Integration
Webform Integration
At a minimum, you need to provide your Marketo Account ID and Munchkin API Private Key. The Munchkin API Private key can be set/retrieved on your Marketo admin site under Admin > Integration > Munchkin > API Configuration.
Account ID: Your Marketo account ID.
Munchkin Javascript Library: Path to munchkin.js. Defaults to //munchkin.marketo.net/munchkin.js and highly likely that you want to leave it set to the default.
Default Lead Source: If you would like all lead updates to include a default Lead Source you can set it here. If a LeadSource field is defined elsewhere in your lead data, perhaps as a webform component, it will take precedence over this setting.
Verbose Logging: If checked, additional data will be added to watchdog.
Tracking Method: Multiple options are available for how captured data is submitted to Marketo.
Munchkin Javascript API - API Private Key: Your Munchkin API Private key. This can be set/retrieved on your Marketo admin site under Admin > Integration > Munchkin > API Configuration. Additional information can be found in the Marketo article Enable Munchkin API Use.
Munchkin Javascript API - Partition: This currently does nothing and is ignored.
SOAP API: Values for these fields can be set/retrieved on your Marketo admin site under Admin > Integration > SOAP API. Additional information can be found in the Marketo article Configuring Your SOAP API Settings.
SOAP configuration will be validated upon save.
SOAP API - SoapClient Proxy Settings: Proxy settings can be set if your server needs to use a proxy for external requests.
The fields configured here will be available for mapping to User and Webform fields. They should match those that are defined in your Marketo admin under Admin > Field Management. Additional information regarding Marketo fields can be found in the Marketo articles Field Management and Export a List of All Marketo API Field Names.
Marketo Fields: This section should contain a pipe "|" delimited list of the fields in the format "[Field API Name]|[Friendly Label]". The default setting is:
FirstName|First Name
LastName|Last Name
Email|Email Address
Configure options for which pages should be tracked or excluded from tracking.
Add tracking to specific pages: This option defines the default rule for tracking pages.
Specify pages by entering their paths, one path per line, and optionally using a * as a wildcard. The default setting is:
admin
admin/*
batch
node/add*
node/*/*
user/*/*
Configure options for which roles should be tracked or excluded from tracking.
Add tracking to specific roles: This option defines the default rule for tracking user roles.
Roles defined on the site will be available for selection.
The Marketo MA User module allows you to capture and update lead data as users login and change their profiles. These steps assume you have already configured additional account fields admin/config/people/accounts/fields.
Management of all integration options are handled on the main Marketo MA configuration page found at admin/config/search/marketo_ma.
It is not necessary to define a mapping for email address as this field is automatically mapped to the Marketo "Email" field.
Note that the module creates three rules that are disabled by default. These three rules allow you to customize the way user data is sent to Marketo beyond the vanilla defaults above. So if you wanted to send some other data that isn't available on the reg field, you can enable the "Update Marketo lead on user creation" rule, add the various fields and data you want to send upon registration into the rule (by default this rule only sends the email) and then save and activate the rule. This rule will then override the default behavior. For more info you can read instructions from @jyokum on this ticket: https://www.drupal.org/node/2507733
Marketo settings for a given webform are managed on each individual node. This section displays a table of all content on the site that may have a webform attached to it and provides an overview of each item's current state.
These steps assume you already have a webform and components defined. Instructions for creating a webform can be found here http://drupal.org/documentation/modules/webform.
All commands in marketo_ma: (marketo_ma)