(Beta) Marketo Engage namespaces and schemas

IMPORTANT

The Marketo Engage source is currently in beta. The feature and documentation are subject change.

This document provides information on the underlying set up for the B2B namespaces and schemas used with Marketo Engage (hereinafter referred to as “Marketo”). This document also provides details around setting up your Postman automation utility required for generating Marketo B2B namespaces and schemas.

Set up the Marketo namespace and schema auto-generation utility

The first step in using the Marketo namespace and schema auto-generation utility is to set up your Platform developer console and Postman environment.

With a Platform developer console and Postman set up, you can now start applying the appropriate environment values to your Postman environment.

The following table contains example values as well as additional information on populating your Postman environment:

Variable Description Example
CLIENT_SECRET A unique identifier used to generate your {ACCESS_TOKEN}. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {CLIENT_SECRET}. {CLIENT_SECRET}
JWT_TOKEN The JSON Web Token (JWT) is an authentication credential used to generate your {ACCESS_TOKEN}. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to generate your {JWT_TOKEN}. {JWT_TOKEN}
API_KEY A unique identifier used to authenticate calls to Experience Platform APIs. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {API_KEY}. c8d9a2f5c1e03789bd22e8efdd1bdc1b
ACCESS_TOKEN The authorization token required to complete calls to Experience Platform APIs. See the tutorial on authenticating and accessing Experience Platform APIs for information on how to retrieve your {ACCESS_TOKEN}. Bearer {ACCESS_TOKEN}
META_SCOPE With regards to Marketo, this value is fixed and is alway set to: ent_dataservices_sdk. ent_dataservices_sdk
CONTAINER_ID The global container holds all standard Adobe and Experience Platform partner provided classes, schema field groups, data types, and schemas. With regards to Marketo, this value is fixed and is always set to global. global
PRIVATE_KEY A credential used to authenticate your Postman instance to Experience Platform APIs. See the tutorial on setting up developer console and setting up developer console and Postman for instructions on how to retrieve your {PRIVATE_KEY}. {PRIVATE_KEY}
TECHNICAL_ACCOUNT_ID A credential used to integrate to Adobe I/O. D42AEVJZTTJC6LZADUBVPA15@techacct.adobe.com
IMS The Identity Management System (IMS) provides the framework for authentication to Adobe services. With regards to Marketo, this value is fixed and is always set to: ims-na1.adobelogin.com. ims-na1.adobelogin.com
IMS_ORG A corporate entity that can own or license products and services and allow access to its members. See the tutorial on setting up developer console and Postman for instructions on how to retrieve your {IMS_ORG} information. ABCEH0D9KX6A7WA7ATQE0TE@adobeOrg
SANDBOX_NAME The name of the virtual sandbox partition that you are using. prod
TENANT_ID An ID used to ensure that the resources you create are namespaced properly and are contained within your IMS Organization. b2bcdpproductiontest
PLATFORM_URL The URL endpoint that you are making API calls to. This value is fixed and is always set to: http://platform.adobe.io/. http://platform.adobe.io/
munchkinId The unique ID for your Marketo account. See the tutorial on authenticating your Marketo instance for information on how to retrieve your munchkinId. 123-ABC-456
sfdc_org_id The organization ID for your Salesforce account. See the following Salesforce guide for more information on acquiring your Salesforce organization ID. 00D4W000000FgYJUA0
msd_org_id The organization ID for your Dynamics account. See the following Microsoft Dynamics guide for more information on acquiring your Dynamics organization ID. f6438fab-67e8-4814-a6b5-8c8dcdf7a98f
has_abm A boolean value that indicates if you are subscribed to Marketo Account-Based Marketing. false
has_msi A boolean value that indicates if you are subcscribed to Marketo Sales Insight. false

Running the scripts

With your Postman collection and environment set up, you can now run the script through the Postman interface.

In the Postman interface, select the root folder of the auto-generator utility and then select Run from the top header.

root-folder

The Runner interface appears. From here, ensure that all the checkboxes are selected and then select Run Adobe I/O Access Token Generation + Automate Namespace creation.

run-generator

A successful request creates the B2B namespaces and schemas according to beta specifications.

Marketo namespaces

Identity namespaces are a component of Identity Service that serve as indicators of the context to which an identity relates.

A fully qualified identity includes an ID value and a namespace. A new custom namespace is required for every new Marketo instance and dataset combination. For example, a Marketo source connector ingesting the programs dataset requires its own custom namespace, and another Marketo source connector ingesting the same dataset also requires its own new custom namespace. See the namespaces overview for more information.

The Marketo namespace is used in the primary identity of the entity.

The following table contains information on the underlying set up for Marketo namespaces.

NOTE

Please scroll left/right to view the full contents of the table.

Display name Identity symbol Identity type Issuer type Issuer entity type Munchkin ID example
marketo_person_{MUNCHKIN_ID} auto-generated CROSS_DEVICE Marketo person 123-ABC-789
marketo_company_{MUNCHKIN_ID} auto-generated B2B_ACCOUNT Marketo company 123-ABC-789
marketo_opportunity_{MUNCHKIN_ID} auto-generated B2B_OPPORTUNITY Marketo opportunity 123-ABC-789
marketo_opportunity_contact_role_{MUNCHKIN_ID} auto-generated B2B_OPPORTUNITY_PERSON Marketo opportunity contact role 123-ABC-789
marketo_program_{MUNCHKIN_ID} auto-generated B2B_CAMPAIGN Marketo program 123-ABC-789
marketo_program_member_{MUNCHKIN_ID} auto-generated B2B_CAMPAIGN_MEMBER Marketo program member 123-ABC-789
marketo_static_list_{MUNCHKIN_ID} auto-generated B2B_MARKETING_LIST Marketo static list 123-ABC-789
marketo_static_list_member_{MUNCHKIN_ID} auto-generated B2B_MARKETING_LIST_MEMBER Marketo static list member 123-ABC-789
marketo_named_account_{MUNCHKIN_ID} auto-generated B2B_ACCOUNT Marketo named account 123-ABC-789

Salesforce namespaces

If you are subscribed to the Salesforce integration, the Salesforce namespace is used in the secondary identity of the entity.

The following table contains information on the underlying set up for Salesforce namespaces.

NOTE

Please scroll left/right to view the full contents of the table.

Display name Identity symbol Identity type Issuer type Issuer entity type Salesforce subscription organization ID example
salesforce_lead_{SALESFORCE_ORGANIZATION_ID} auto-generated CROSS_DEVICE Salesforce lead 00DA0000000Hz79
salesforce_account_{SALESFORCE_ORGANIZATION_ID} auto-generated B2B_ACCOUNT Salesforce account 00DA0000000Hz79
salesforce_opportunity_{SALESFORCE_ORGANIZATION_ID} auto-generated B2B_OPPORTUNITY Salesforce opportunity 00DA0000000Hz79
salesforce_opportunity_contact_role_{SALESFORCE_ORGANIZATION_ID} auto-generated B2B_OPPORTUNITY_PERSON Salesforce opportunity contact role 00DA0000000Hz79
salesforce_campaign_{SALESFORCE_ORGANIZATION_ID} auto-generated B2B_CAMPAIGN Salesforce campaign 00DA0000000Hz79
salesforce_campaign_member_{SALESFORCE_ORGANIZATION_ID} auto-generated B2B_CAMPAIGN_MEMBER Salesforce campaign member 00DA0000000Hz79

Microsoft Dynamics namespaces

If you are subscribed to the Dynamics integration, the Dynamics namespace is used as secondary identity of the entity.

The following table contains information on the underlying set up for Dynamics namespaces.

NOTE

Please scroll left/right to view the full contents of the table.

Display name Identity symbol Identity type Issuer type Issuer entity type Dynamics subscription organization ID example
microsoft_person_{DYNAMICS_ID} auto-generated CROSS_DEVICE Microsoft person 94cahe38-e51h-3d57-a9c6-2edklb7184mh
microsoft_account_{DYNAMICS_ID} auto-generated B2B_ACCOUNT Microsoft account 94cahe38-e51h-3d57-a9c6-2edklb7184mh
microsoft_opportunity_{DYNAMICS_ID} auto-generated B2B_OPPORTUNITY Microsoft opportunity 94cahe38-e51h-3d57-a9c6-2edklb7184mh
microsoft_opportunity_contact_connection_{DYNAMICS_ID} auto-generated B2B_OPPORTUNITY_PERSON Microsoft opportunity relationship 94cahe38-e51h-3d57-a9c6-2edklb7184mh
microsoft_campaign_{DYNAMICS_ID} auto-generated B2B_CAMPAIGN Microsoft campaign 94cahe38-e51h-3d57-a9c6-2edklb7184mh
microsoft_campaign_member_{DYNAMICS_ID} auto-generated B2B_CAMPAIGN_MEMBER Microsoft campaign member 94cahe38-e51h-3d57-a9c6-2edklb7184mh

Marketo schemas

Experience Platform uses schemas to describe the structure of data in a consistent and reusable way. By defining data consistently across systems, it becomes easier to retain meaning and therefore gain value from data.

Before data can be ingested into Platform, a schema must be composed to describe the data’s structure and provide constraints to the type of data that can be contained within each field. Schemas consist of a base class and zero or more schema field groups.

For more information on the schema composition model, including design principles and best practices, see the basics of schema composition.

The following table contains information on the underlying setup of Marketo schemas.

NOTE

Please scroll left/right to view the full contents of the table.

Schema name Base class Field groups Profile in Schema Primary identity Primary identity namespace Secondary identity Secondary identity namespace Relationship Notes
Marketo Company {MUNCHKIN_ID} XDM Business Account XDM Business Account Details Enabled accountID in the base class marketo_company_{MUNCHKIN_ID} extSourceSystemAudit.externalID in the base class salesforce_account_{SALESFORCE_ORGANIZATION_ID}
  • accountParentID in XDM Business Account Details field group
  • Type: one-to-one
  • Reference schema: Marketo Company {MUNCHKIN_ID}
  • Namespace: marketo_company_{MUNCHKIN_ID}
Marketo Person {MUNCHKIN_ID} XDM Individual Profile
  • XDM Business Person Details
  • XDM Business Person Components
  • IdentityMap
Enabled personID in the base class marketo_person_{MUNCHKIN_ID}
  1. extSourceSystemAudit.externalID of XDM Business Person Details field group
  2. workEmail.address of XDM Business Person Details field group
  3. identityMap of Identity Map field group
  1. salesforce_lead_{SALESFORCE_ORGANIZATION_ID}
  2. Email
  3. ECID
  • personComponents.sourceAccountID of XDM Business Person Components field group
  • Type: Many-to-one
  • Reference Schema: Marketo Company {MUNCHKIN_ID}
  • Namespace: marketo_company_{MUNCHKIN_ID}
  • Destination property: accountID
  • Relationship name from current schema: Account
  • Relationship name from reference schema: People
Marketo Opportunity {MUNCHKIN_ID} XDM Business Opportunity XDM Business Opportunity Details Enabled opportunityID in the base class marketo_opportunity_{MUNCHKIN_ID} extSourceSystemAudit.externalID in the base class salesforce_opportunity_{SALESFORCE_ORGANIZATION_ID}
  • accountID in the base class
  • Type: Many-to-one
  • Reference Schema: Marketo Company {MUNCHKIN_ID}
  • Namespace: marketo_company_{MUNCHKIN_ID}
  • Destination property: accountID
  • Relationship name from current schema: Account
  • Relationship name from reference schema: Opportunities
Marketo Opportunity Contact Role {MUNCHKIN_ID} XDM Business Opportunity Person Relation None Enabled opportunityPersonID in the base class marketo_opportunity_contact_role_{MUNCHKIN_ID} extSourceSystemAudit.externalID in the base class salesforce_opportunity_contact_role_{SALESFORCE_ORGANIZATION_ID} First relationship
  • personID in the base class
  • Type: Many-to-one
  • Reference Schema: Marketo Person {MUNCHKIN_ID}
  • Namespace: marketo_person_{MUNCHKIN_ID}
  • Destination property: personID
  • Relationship name from current schema: Person
  • Relationship name from reference schema: Opportunities
Second relationship
  • opportunityID in the base class
  • Type: Many-to-one
  • Reference Schema: Marketo Opportunity {MUNCHKIN_ID}
  • Namespace: marketo_opportunity_{MUNCHKIN_ID}
  • Destination property: opportunityID
  • Relationship name from current schema: Opportunity
  • Relationship name from reference schema: People
Marketo Program {MUNCHKIN_ID} XDM Business Campaign XDM Business Campaign Details Enabled campaignID in the base class marketo_program_{MUNCHKIN_ID} extSourceSystemAudit.externalID in the base class salesforce_campaign_{SALESFORCE_ORGANIZATION_ID}
Marketo Program Member {MUNCHKIN_ID} XDM Business Campaign Member XDM Business Campaign Member Details Enabled campaignMemberID in the base class marketo_program_member_{MUNCHKIN_ID} None None First relationship
  • personID in the base class
  • Type: Many-to-one
  • Reference Schema: Marketo Person {MUNCHKIN_ID}
  • Namespace: marketo_person_{MUNCHKIN_ID}
  • Destination property: personID
  • Relationship name from current schema: Person
  • Relationship name from reference schema: Programs
Second relationship
  • campaignID in the base class
  • Type: Many-to-one
  • Reference Schema: Marketo Program {MUNCHKIN_ID}
  • Namespace: marketo_program_{MUNCHKIN_ID}
  • Destination property: campaignID
  • Relationship name from current schema: Program
  • Relationship name from reference schema: People
Marketo Static List {MUNCHKIN_ID} XDM Business Marketing List None Enabled marketingListID in the base class marketo_static_list_{MUNCHKIN_ID} None None None Static List is not synced from Salesforce and therefore does not have a secondary identity.
Marketo Static List Member {MUNCHKIN_ID} XDM Business Marketing List Members None Enabled marketingListMemberID in the base class marketo_static_list_member_{MUNCHKIN_ID} None None First relationship
  • personID in the base class
  • Type: Many-to-one
  • Reference Schema: Marketo Person {MUNCHKIN_ID}
  • Namespace: marketo_person_{MUNCHKIN_ID}
  • Destination property: personID
  • Relationship name from current schema: Person
  • Relationship name from reference schema: Lists
Second relationship
  • marketingListID in the base class
  • Type: Many-to-one
  • Reference Schema: Marketo Static List {MUNCHKIN_ID}
  • Namespace: marketo_static_list_{MUNCHKIN_ID}
  • Destination property: marketingListID
  • Relationship name from current schema: List
  • Relationship name from reference schema: People
Static list member is not synced from Salesforce and therefore does not have a secondary identity.
Marketo Named Account {MUNCHKIN_ID} XDM Business Account XDM Business Account Details Enabled accountID in the base class marketo_named_account_{MUNCHKIN_ID} extSourceSystemAudit.externalID in the base class salesforce_account_{SALESFORCE_ORGANIZATION_ID}
  • accountParentID in XDM Business Account Details field group
  • Type: one-to-one
  • Reference Schema: Marketo Named Account {MUNCHKIN_ID}
  • Namespace: marketo_named_account_{MUNCHKIN_ID}
Marketo Activity {MUNCHKIN ID} XDM ExperienceEvent
  • Visit WebPage
  • New Lead
  • Convert Lead
  • Add To List
  • Remove From List
  • Add To Opportunity
  • Remove From Opportunity
  • Form Filled Out
  • Link Clicks
  • Email Delivered
  • Email Opened
  • Email Clicked
  • Email Bounced
  • Email Bounced Soft
  • Email Unsubscribed
  • Score Changed
  • Opportunity Updated
  • Status in Campaign Progression Changed
  • Person Identifier
  • Marketo Web URL
Enabled personID of Person Identifier field group marketo_person_{MUNCHKIN_ID} None None First relationship
  • listOperations.listID field
  • Type: one-to-one
  • Reference Schema: Marketo Static List {MUNCHKIN_ID}
  • Namespace: marketo_static_list_{MUNCHKIN_ID}
Second relationship
  • opportunityEvent.opportunityID field
  • Type: one-to-one
  • Reference Schema: Marketo Opportunity {MUNCHKIN_ID}
  • Namespace: marketo_opportunity_{MUNCHKIN_ID}
Third relationship
  • leadOperation.campaignProgression.campaignID field
  • Type: one-to-one
  • Reference Schema: Marketo Program {MUNCHKIN_ID}
  • Namespace: marketo_program_{MUNCHKIN_ID}
The primary identity of Marketo Activity {MUNCHKIN_ID} schema is personID, which is the same as the primary identity of [!DNL Marketo] Person {MUNCHKIN_ID} schema.

Next steps

To learn how to connect your Marketo data to Platform, see the tutorial on creating a Marketo source connector in the UI.

On this page