Currency Conversion Data Requirements

Default Currency: In Marketo Measure, all revenue and cost are converted to a default currency at reporting time. There must be one record with the same date coverage for the target currency itself (e.g., USD to USD) with a conversion rate of 1.

Conversion Rates: Each (source currency, target currency) pair can have multiple conversion rates for different date periods. The rates must cover the entire time span from 0001-01-01 to 9999-12-31, as per the Salesforce DatedConversionRate object.

Date Range:

  • No overlapping date ranges within a (source currency, target currency) rate set (e.g., 2023-01-01 to 2023-02-01 and 2023-01-01 to 2024-01-01).
  • No gaps between date ranges. The start date is inclusive, and the end date is exclusive.

ExperienceEvent

XDM ClassXDM Field GroupXDM PathXDM TypeData Source FieldRequired?Notes
Activity
XDM ExperienceEvent_idstringIDYesYes
eventTypestringActivityTypeYesYes
timestampdate-timeActivity DateYesYes
Person IdentifierpersonKey.sourceKeystringYesE.g. - 333@999-abc-888.Marketo
personKey.sourceIDstringLead ID or Contact IDYes

E.g. - 333, depending on the data source table, this is either Lead ID or Contact ID.

Foreign key to Lead or Contact

personKey.sourceInstanceIDstringYesE.g. - 999-abc-888
personKey.sourceTypestringYesE.g. - Marketo
Add To CampaignleadOperation.addToCampaign.campaignKey.sourceKeystringYes for leadOperation.addToCampaign type onlyE.g. - 55555@999-abc-888.Marketo
leadOperation.addToCampaign.campaignKey.sourceIdstringCampaign IDYes for leadOperation.addToCampaign type only

E.g. - 55555.

Foreign key to Campaign

leadOperation.addToCampaign.campaignKey.sourceInstanceIdstringYes for leadOperation.addToCampaign type onlyE.g. - 999-abc-888
leadOperation.addToCampaign.campaignKey.sourceTypestringYes for leadOperation.addToCampaign type onlyE.g. - Marketo
Status in Campaign Progression ChangedleadOperation.campaignProgression.campaignKey.sourceKeystringYes for leadOperation.campaignProgression type onlyE.g. - 55555@999-abc-888.Marketo
leadOperation.campaignProgression.campaignKey.sourceIdstringCampaign IDYes for leadOperation.campaignProgression type only

E.g. - 55555.

Foreign key to Campaign

leadOperation.campaignProgression.campaignKey.sourceInstanceIdstringYes for leadOperation.campaignProgression type onlyE.g. - 999-abc-888
leadOperation.campaignProgression.campaignKey.sourceTypestringYes for leadOperation.campaignProgression type onlyE.g. - Marketo

ExperienceEvent Type Supported

Event TypeXDM Event TypeDescription
New LeadleadOperation.newLeadUse to record the creation and details of a new marketing lead
Convert LeadleadOperation.convertLeadUse when a marketing lead is converted into a sales-qualified contact that is assigned to a sales user
Interesting MomentleadOperation.interestingMomentUse for tracking high value activities by potential customers
Fill Out Formweb.formFilledOutUse to capture details when a person fills out a form on a web page
Unsubscribe EmaildirectMarketing.emailUnsubscribedUse to capture details when a person unsubscribes from an email
Open EmaildirectMarketing.emailOpenedUse to capture details when a person opens a marketing email
Click EmaildirectMarketing.emailClickedUse to capture details when a person clicks a link in a marketing email
Change Status in ProgressionleadOperation.statusInCampaignProgressionChangedUse to capture details when a lead's status in a campaign changes
Add to Engagement Program (Add to Nurture)leadOperation.addToCampaignUse to add a person to the specific campaign.

Use the “Interesting Moment” event type for event types not supported in the table above. Add a custom field to indicate the subtype “Interesting Moment”.

Query Examples for Data Inspection

The following is a list of query examples for inspecting ingested datasets in AEP data lake. To use them against your datasets, replace the table name in the query examples below with your actual dataset table name.

We expect all counts to be 0.

For personType field, we expect there are only “Lead” or “Contact” values, and there is no null value.

For all “Contact” person records, we expect there is an Account foreign key.

For “Lead” person records, an Account foreign key does not exist and is not required. If you choose to ingest “Lead” person records as “Contact” person records (which is recommended), an Account foreign key on such person records is not required.