---
title: "Data Destination - Adobe Marketo Engage"
slug: "data-destination-marketo"
updated: 2024-10-07T05:27:14Z
published: 2024-10-07T05:27:14Z
canonical: "documents.trocco.io/data-destination-marketo"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documents.trocco.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Destination - Adobe Marketo Engage

## summary

Help page for ETL Configuration of Data Settings for adding leads in Adobe Marketo Engage.

## constraints

- none in particular

## important point

The column name on TROCCO must match the field REST API name on the Adobe Marketo Engage side. Check the [official page](https://developers.marketo.com/rest-api/lead-database/fields/list-of-standard-fields/) for the REST API name.

## Setting items

### STEP1 Basic settings

| item name | indispensable | default value | Contents |
| --- | --- | --- | --- |
| Adobe Marketo Engage Connection Configuration | Yes | - | Select the previously registered Connection Configuration that has the necessary permissions for this ETL Configuration. If you do not have a registered Connection Configuration, please **go to Add Connection** Configuration **to** create one. For more information on Connection Configuration, please [click here.](/docs/connection-configuration-marketo) |
| target | Yes | - | Specify the type of object at Data Destination. Currently, the four possible values are lead, opportunity, opportunity_role, and custom_object. |
| custom object name | Yes | - | Must be specified if custom_object is selected as the target. Enter the API name of the custom object whose data you wish to transfer. |
| action | Yes | - | This must be specified when opportunity, opportunity_role, or custom_object is selected as the target. You can choose between creating data (createOnly), updating data (updateOnly), or creating and updating at the same time (createOrUpdate). |
| lookup field | Yes | email (LEAD only) | The column name specified here becomes the primary key. If the target is lead, the default value is email. When the target is an opportunity, opportunity_role, or custom_object, it can be specified only when the action is set to updateOnly. Selecting dedupeFields specifies the externalOpportunityId and selecting idField specifies the marketoGUID. |
| partition name | No | - | If you have set up partitions, specify the partition name here. |
| static list ID | No | - | If you wish to select a static list for Data Destination, specify the static list ID here. |