Configure destination for Adobe Marketo

Note

This topic contains information about configuring a destination that sends query results to Adobe Marketo using orchestrations. To configure a destination that sends audiences to Adobe Marketo using campaigns see this topic .

Adobe Marketo is marketing automation software that streamlines, automates, and measures marketing tasks and workflows. An email address must be sent to Adobe Marketo. You may also send first names, last names, company names, and phone numbers.

Note

Amperity uses the Adobe Marketo API to update the membership of audience lists in Adobe Marketo to match the membership of audience lists sent from Amperity. The membership updates to match the membership of the audience list sent from Amperity. Amperity adds a user when they do not exist in Adobe Marketo.

Amperity does not keep smart lists and does not remove users from the Adobe Marketo database.

Get details

Review the following details before configuring credentials for Adobe Marketo and before configuring Amperity to send static audience lists to Adobe Marketo.

Credential settings Client ID and client secret Required A client ID is a unique identifier. A client secret is a unique string. Together they generate an access token that authorizes access to the Adobe Marketo REST API. Custom services within Adobe Marketo give the client ID and secret . Subdomain Required The subdomain in Adobe Marketo in which Amperity manages audiences.

Configure credentials

Configure credentials for Adobe Marketo before adding a destination.

An individual with access to Adobe Marketo should use SnapPass to securely share “client ID”, “client secret”, and “subdomain” details with the individual who configures Amperity.

To configure credentials for Adobe Marketo

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Adobe Marketo. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential vary by credential type. For the “marketo” credential type, configure settings, and then click Save. Client ID and client secret Required A client ID is a unique identifier. A client secret is a unique string. Together they generate an access token that authorizes access to the Adobe Marketo REST API. Custom services within Adobe Marketo give the client ID and secret . Subdomain Required The subdomain in Adobe Marketo in which Amperity manages audiences.

Add destination

Use a sandbox to configure a destination for Adobe Marketo. Before promoting your changes, send a test audience, and then verify the results in Adobe Marketo. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for Adobe Marketo

	Open the Destinations page, and then click the Add destination button. To configure a destination for Adobe Marketo, do one of the following: Click the row in which Adobe Marketo is located. Destinations list alphabetically and you can scroll up and down the list. Search for Adobe Marketo. Start typing “adobe”. The list filters to show only matching destinations. Select “Marketo”.
	Select the credential for Adobe Marketo from the Credential dropdown, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Adobe Marketo.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.
	Configure the following settings, and then click “Save”. Folder name Required. The name of the folder in Adobe Marketo in which a program that has the audience list is located. Program name The name of the program in which the audience list managed by Amperity is located. List name (Required at orchestration) Required. The name of the audience list managed by Amperity. It is possible for Adobe Marketo to contain many audience lists with the same name. If the Adobe Marketo API returns more than one audience list, Amperity updates the first audience in that list.
	After configuring this destination users may use: Orchestrations to send query results Orchestrations and campaigns to send audiences Orchestrations and campaigns to send offline events