Marketo Measure Fields on Standard Salesforce Objects

Last update: June 28, 2024
NOTE
You may see instructions specifying “Marketo Measure” in the documentation, but still see “Bizible” in your CRM. We are working to have that updated and the rebranding will be reflected in your CRM soon.

Learn about the various Marketo Measure fields that are added to Salesforce standard objects.

Account

Predictive Engagement Score: This field is used with our ABM feature to provide a score related to how engaged the Account is and takes into consideration many factors such as the recency of page views, how many contacts are associated to the account, is there a closed opp, etc.

Campaign

There are only 4 fields added, 1 button, and 1 validation rule.

UniqueID: This field is used internally for us to track the different Campaigns that are synced with Marketo Measure.

Enable Buyer Touchpoints: This field is for the actual syncing of Campaigns for offline attribution inclusion and historical data.

Touchpoint Start Date: This field is used for setting a start date of applying touchpoints to historical campaigns.

Touchpoint End Date: This field is used for setting an end date for applying touchpoints to historical campaigns. A common example would the inclusion of digital campaigns pre-Marketo Measure and then setting the end date as the day the script was applied.

Bulk Update Touchpoint Date (Button): This button is used to manage the touchpoint date of the Campaign members when the Campaign is synced as we will reference either the Campaign Membership date or the first response date out of the box. In the event that those date fields aren’t an accurate representation of the actual touchpoint date, we would use this button to set the touchpoint date.

Update Marketo Measure Attribution (Validation Rule): This rule is deprecated after package version 6.0.

Campaign Member

There are 5 fields and 1 Apex Trigger added with the package.

Touchpoint Status (Lead): This is a diagnostic field related to a feature that is not turned on out of the box. We use this to understand whether a Touchpoint was created against the related Lead record or if not, why.

Touchpoint Status (Contact): This is a diagnostic field related to a feature that is not turned on out of the box. We use this to understand whether a Touchpoint was created against the related Contact record or if not, why.

Touchpoint Status (Opportunity): This is a diagnostic field related to a feature that is not turned on out of the box. We use this to understand whether a Touchpoint was created against the related Opportunity record or if not, why.

Touchpoint Status Date: This is the date the diagnostic fields were populated.

Buyer Touchpoint Date: This is related to the Bulk Update Touchpoint date button from the Campaign object. When that is used, we apply the defined Touchpoint date to the Campaign Member.

OnCampaignMemberDelete: Out of the box, Salesforce doesn’t surface when Campaign Members are deleted which can cause issues with accurate attribution reporting. When a Campaign Member is deleted, this is triggered to inform Marketo Measure to remove Touchpoints related to that non-existent Campaign Member.

Lead

The Bizible Account field is used for our Lead to Account mapping for our ABM feature. We populate this field to create the look-up relationship between the two objects.

Account

This is used for our Lead to Account mapping for our ABM feature. We populate this field to create the look-up relationship between the two objects.

Opportunity

Marketo Measure Opportunity Amount: This field is used in the scenario where a custom amount field is used on the Opportunity. We map that custom field value to Marketo Measure Opportunity Amount using a workflow and then read this field for our Revenue attribution fields on the Buyer Attribution Touchpoint object.

Activity

BizibleID: This is for us to relate a touchpoint to activities for our activity attribution and calltracking metrics integration.

Buyer Touchpoint Date: This is a field that can be populated via a workflow to use as the date for activities attribution and will be populated for our calltrackingmetrics integration to know when the interaction occurred.

Previous pageMarketo Measure Object and Field Taxonomy
Next pagePage Layout Instructions

Marketo Measure