CET-3062 add marketo engage person sync documentation #398
Conversation
|
|
||
| ## Overview {#overview} | ||
|
|
||
| The Marketo Engage Person Sync Connector enables Marketers to stream updates from an AEP person audiences to the corresponding records in your Marketo Engage instance. |
There was a problem hiding this comment.
AEP is not a public-facing term, and let's please revise the wording slightly, like:
Use the Marketo Engage Person Sync connector to stream updates from person audiences to the corresponding records in your Marketo Engage instance.
|
|
||
| The Marketo Engage Person Sync Connector enables Marketers to stream updates from an AEP person audiences to the corresponding records in your Marketo Engage instance. | ||
|
|
||
| ## Supported Identities and Attributes {#support-identities-and-attributes} |
There was a problem hiding this comment.
before going into this part, let's talk about:
- any prerequisites that need to be met in Marketo?
- how this destination is different to the existing Marketo destination
- any callouts from this internal Slack thread: https://adobedx.slack.com/archives/C5RMQUHB9/p1730396494873629
| @@ -0,0 +1,120 @@ | |||
| --- | |||
| title: Marketo Engage Person Sync | |||
| description: Use the Marketo Engage Person Sync connector to stream updates from a person audience to the corresponding records in your Marketo Engage. | |||
There was a problem hiding this comment.
let's add this to the metadata:
badgeBeta: label="Beta" type="Informative"
this will display a beta badge on the page
| --- | ||
|
|
||
| # Marketo Engage Person Sync connection {#marketo-engage-person-sync} | ||
|
|
There was a problem hiding this comment.
I understand that this is an alpha or beta destination at first, so please add a top-of-page note to call that out.
Maybe something like:
>[!IMPORTANT]
>
>This destination connector is in beta and only available to select customers. To request access, contact your Adobe representative.
| > | ||
| >* To connect to the destination, you need the **[!UICONTROL View Destinations]** and **[!UICONTROL Manage Destinations]** [access control permissions](/help/access-control/home.md#permissions). | ||
|
|
||
| To configure a Marketo Engage instance as a destination, that instance must be in the same IMS org as your CDP instance. If you have already configured a destination, you may select an existing Marketo account to use with your new configuration. If not, click the Connector to Destination prompt, which will allow you to set the name, description, and Marketo Munchkin ID of the desired destination. Your Marketo Instance's Munchkin ID can be found in the Admin->Munchkin menu. |
There was a problem hiding this comment.
To configure a Marketo Engage instance as a destination, that instance must be in the same IMS org as your CDP instance.
Hmm, not 100% sure what we are saying here, can you perhaps make this clearer? Also, let's use organization instead of IMS org and Real-Time CDP instead of CDP.
| When sending updates to Marketo engage, records are selected based on the selected partition and one or two user-selected fields. If your destination is configured with the North America partition, and has Email Address and Company Name configured as deduplication fields, then all three fields must match to apply changes to an existing record. For example: | ||
|
|
||
| - Destination is configured with the North America partition | ||
| - Person with Email <[email protected]> and Company name Example Inc. In AEP matches the destination audience |
There was a problem hiding this comment.
Experience Platform instead of AEP
| >[!IMPORTANT] | ||
| > | ||
| >* To activate data, you need the **[!UICONTROL View Destinations]**, **[!UICONTROL Activate Destinations]**, **[!UICONTROL View Profiles]**, and **[!UICONTROL View Segments]** [access control permissions](/help/access-control/home.md#permissions). Read the [access control overview](/help/access-control/ui/overview.md) or contact your product administrator to obtain the required permissions. | ||
| In the Activate Audiences step, you will be able to select from any person audiences which are visible to you. |
There was a problem hiding this comment.
please add a blank line between the note and this line
also, let's link out to the generic activate audiences doc like in the template
https://experienceleague.adobe.com/en/docs/experience-platform/destinations/destination-sdk/document-destination/self-service-template#activate
btw, the template can be downloaded at the top of page here if you haven't done so already
https://experienceleague.adobe.com/en/docs/experience-platform/destinations/destination-sdk/document-destination/self-service-template
|
|
||
| ## Field Mapping {#field-mapping} | ||
|
|
||
| For changes to a particular person attribute to be sent to Marketo Engage, the field must be mapped from a CDP field to Marketo Field. |
There was a problem hiding this comment.
minor, but please use Real-Time CDP
|
|
||
|  | ||
|
|
||
| AEP datatypes and Marketo datatypes can be mapped in the following ways: |
There was a problem hiding this comment.
Experience Platform instead of AEP
|
|
||
| {style="table-layout:auto"} | ||
|
|
||
| In some cases it is desirable to allow integrations to set the value of a field if there is none, while preventing integrations from making updates to fields which already have a value. If you need to prevent the destination connector from overwriting existing values in your Marketo Engage instance, you can configure fields to block updates in the Admin->Field Management section of your Marketo instance and toggling the Adobe Experience Platform source type. |
There was a problem hiding this comment.
Let's also add a section about validating data export, similar to the template. How do I tell if the data export has made it through successfully to Marketo?
Added:
marketo-engage-person-sync.mdthat provides the documentation for our destination connector