Adobe Marketo Measure (formerly known as Bizible)

1. You are here:
2. Handbook
3. Marketing
4. Marketing Operations
5. Adobe Marketo Measure (formerly known as Bizible)

Maintained by:

On this page

• About Adobe Marketo Measure (formerly known as Bizible)
  • How Adobe Marketo Mesure Tracks Attribution
• Adobe Marketo Mesure Components
  • Touchpoints
  • Buyer Touchpoints (BT)
  • Buyer Attribution Touchpoint (BAT)
  • Channel and Subchannel
  • Touchpoint Position
  • Attribution Models
  • Online vs. Offline Touchpoints
    • Online
    • Offline
  • Page View Tracking
• Touchpoint Generation & Mapping
• AMM Channel and Subchannel Mapping
  • Online Channel Mapping
  • Bucket Channel Mapping
• AMM Attribution with Pathfactory
• AMM in SFDC
  • [AMM] SFDC Campaigns
  • Bizible Reports in SFDC
    • Use case: Track registration by source for GitLab owned gated landing pages
• AMM Review Process
  • Online Channel Mapping
  • Offline Channel Mapping
  • AMM data updates

About Adobe Marketo Measure (formerly known as Bizible)

Adobe Marketo Measure (AMM) unifies behavioral and ad data with sales outcomes and machine learning so you can make the right marketing decisions.

How Adobe Marketo Mesure Tracks Attribution

Marketing attribution is the process of assigning revenue credit to marketing activities. AMM tracks a prospect's entire customer journey, from their first interaction with GitLab to purchase. The revenue generated from the deal gets attributed back to the marketing Touchpoints that drove the sale (see below for details on Touchpoints). The amount of revenue credit given to a touchpoint depends on how much that Touchpoint influenced the customer's purchasing decision.

This process allows Marketing to understand the value of each marketing activity.

Adobe Marketo Mesure Components

Touchpoints

AMM defines a touchpoint as: Touchpoints refer to a prospect/lead's interactions with your online or offline marketing efforts.

Touchpoints capture a multitude of information, such as UTM parameters, the date and time of the interaction, and the type of interaction (form submission, campaign response, etc.). AMM stores Touchpoint records on the lead or contact record in SFDC.

Buyer Touchpoints (BT)

Buyer Touchpoints are created on lead or contact objects directly. They do not relate to an opportunity and do not have a NET ARR value.

Buyer Attribution Touchpoint (BAT)

AMM creates Buyer Attribution Touchpoints when Sales accepts an opportunity created on an account with Buyer Touchpoints. AMM only creates Buyer Attribution Touchpoints on Contact objects, and they must relate to an opportunity. BATs have a NET ARR value.

Channel and Subchannel

AMM maps Touchpoints in channels and subchannels.

• Channels - Are the broadest level of Touchpoint groupings and contain many subchannels. Examples of channels include Events, Organic Search, Paid Search, Digital, etc.
• Subchannels - Give more specific information about the source. Examples include Google (for Paid Search channel, LinkedIn (for Paid Social channel), Executive Roundtable (for events)

AMM presents channels and subchannels in dot notation. Where Paid Search.Google has a channel of Paid Search and subchannel of Google.

Touchpoint Position

AMM tracks the position of a touchpoint based on its timing to other touchpoints per person. The abbreviations below are shown in the Touchpoint Position field in SFDC.

• FT - First Touch, a prospect's first-ever interaction
• LC - Lead Created, prospect submits information
• OC - Opportunity Creation, prospect intentionally moves toward a purchase decision
• Closed - Customer Close, prospect makes a purchase
• Pending - The Pending touchpoint position is stamped only on BATs (Buyer Attribution Touchpoints), not on BTs (Buyer Touchpoints). This touchpoint position is shown only when the opportunity is still open, providing a temporary value to allow the opportunity credit to sum to 100%.

Attribution Models

GitLab uses AMM's Custom Attribution model based on a unique machine learning algorithm from AMM. The Custom model uses our touchpoint data to calculate attribution weights for each stage based on how much each opportunity stage drove the deal to close.

Adobe Marketo Mesure supports other attribution methods not used by GitLab.

How is the Machine Learning model Calculated?

AMM calculates the importance of each custom stage by using all of GitLab's touchpoint data. The criteria used to determine the importance of each stage are:

• Model Accuracy: If we build a predictive model with the touchpoint data to predict whether we will win a deal eventually, how accurate will the model be? Higher predictive accuracy means that the details of this stage correlates more with whether a deal will close
• Conversion Rate: If Leads or Opportunities at this certain stage convert to the next stage at a high rate, this suggests that the marketing activities that occurred at this stage didn't matter very much. Conversely, if a certain stage converts to the next stage at a low rate, this can suggest that the marketing activities that occurred at this stage were influential in driving the conversion.
• Touchpoint Uniqueness Weight: If a stage occurs as a standalone transition, meaning there weren't any other stage transitions that occurred at the same time, this stage could receive a higher attribution weight. Conversely, if a touchpoint for a stage is shared with other stages (e.g. the touchpoint shares the First Touch, Lead Conversion, and Opportunity Conversion stages) this stage could receive a lower attribution weighting. The final weight for a custom stage is calculated as such:

Model Percentage = Model Accuracy x Conversion Rate x Touchpoint Uniqueness Weight

The Custom Attribution Model's machine learning algorithm improves as it collects more data but does not automatically adjust stage weights. To ensure GitLab is using the best model, during the first month of the fiscal year, the Marketing Operations team updates the weight of each stage. The previous weights can be seen on this Google Sheet.

Currently the Custom Model has the following weights for each stage (updated April 24th, 2023):

• First Touch - 18.8%
• Lead Creation - 18.3%
• Opportunity Creation - 18.6%
• SAO - 11.5%
• Closed (Lost, Won) - 22.8%
• Middle Touches - 10.0%

Online vs. Offline Touchpoints

AMM generates Touchpoints as either online or offline based on how they were created.

Online

Online Touchpoints are created when users submit a form on a GitLab web property. They are sourced from traditional online marketing channels, including display advertising, paid search, paid social, organic search, organic social, email, chatbots, etc.

While offline Touchpoints need an SFDC campaign created beforehand to create touchpoints, online Touchpoints do not.

Important: Users must have allowed or not rejected cookies for AMM to create online Touchpoints. GitLab uses OneTrust to manage user consent on our web properties, depending on the user's location they may have to allow cookies for the AMM script to load. If the user rejects or opts out of OneTrust consent, AMM will not create online Touchpoints.

Offline

Offline Touchpoints are created from interactions outside the web, including visiting a trade show booth, attending a hospitality event, and being sent a direct mailer. These interactions are for channels where a person's engagement cannot be tracked digitally or where they physically attended an event. A quick rule of thumb: if there is a list uploaded and the person took action, they are offline buyer touchpoints.

Offline buyer touchpoints are created either by:

1. Adjusting the Enable Bizible Touchpoints field on the Salesforce Campaign object to either Include only "Responded" Campaign Members or Include All Campaign Members
2. Through campaign sync rules, which generate TPs for based on well defined criteria. To learn how these rules work please see this Custom Campaign Sync Adobe Marketo Measure documentation.

As of January 2023, we are creating offline Touchpoints through the campaign sync rules. This switch decreases manual setup work for the Marketing Operations Team.

The current campaign sync rules and are largely based on the Campaign Type, Campaign Member Status, Campaign Name, and Campaign Member Created Date fields in SFDC.

See progression statuses for the standard Campaign Types that will have offline buyer touchpoints enabled

Page View Tracking

We have disabled page view tracking in AMM. We found that recording page views into our attribution data skews the data considerably.

Touchpoint Generation & Mapping

Touchpoints are generated one of three ways, on GitLab's Websites, Offline, or through Sales activity. The table below gives examples of how each are sourced.

Once a Touchpoint is created, AMM uses a set of predefined mapping rules to assign a channel and subchannel to each Touchpoint based on how the Touchpoint was generated.

AMM has more extensive documentation on how Touchpoints are generated and mapped.

AMM Channel and Subchannel Mapping

Abode Marketo Measure stores a customizable set of rules for online and offline touchpoints separately. They can be edited through either the Online Channels page or Offline Channels page in AMM.

Important: AMM rule changes can only be made once every 7 days. AMM uses this time to re-process all touchpoint data with the new rules.

Online Channel Mapping

The channels and subchannels are mapped based on 5 attributes:

1. Campaign - taken from the utm_campaign value on the session landing page or form URL where form submission occurs.
2. Medium - taken from the utm_medium value on the session landing page or form URL where form submission occurs.
3. Source - taken from the utm_source value on the session landing page or form URL where form submission occurs.
4. Landing Page - this is the landing page URL that the form submission occurs on.
5. Referring Website - this is the website that referred the submitter to the form submission page.

These rules are hierarchical and will operate top-down, so the first rule is checked, then the second, and so on.

Note: Some Online Touchpoints do not fall into a specific rule with a well-defined source. For example, these Touchpoints could be missing a UTM parameter or have no tracking information. These Touchpoints are mapped to either Direct or Other:

• Other - Touchpoints with tracking information (utm_source, utm_medium, etc.) that does not match any rule.
• Direct - Touchpoints that do not have tracking information, e.g. visitors who may have manually typed in a URL or came from another site with no referring URL.

Bucket Channel Mapping

These channels and subchannels are pulled into Salesforce and can be further filtered by using medium for those channels with overlap or with Ad Campaign name to search for specific UTMs or campaigns. The Bucket Mapping is a high-level grouping of each subchannel set to allow for additional reporting.:

AMM Attribution with Pathfactory

Asset Viewed

A buyer touchpoint will be created, based on the Content Engagement Time Threshold. If the known user spends the required amount of time on a PathFactory asset, a script in the backend will be executed, pushing the event to AMM.

A touchpoint will only be generated if the user has accepted the Cookie Policy and is identified by PathFactory via the lb_email parameter.

AMM parses the referral URL it receives for: utm_medium, utm_campaign, utm_source.

Form Fill

Similarly to asset views, upon a successfull form submission on a PathFactory asset, a buyer touchpoint will be created.

Downloaded Asset When an asset is downloaded on a PathFactory track, a buyer touchpoint is being generated by the backend script. <!– This diagram is to be used internally and with Pathfactory to understand the attribution touchpoints created through our setup of Pathfactory listening campaigns and how the tracks are used in integrated campaigns and other tactics that drive straight to pathfactory.

See figjam flow chart

AMM in SFDC

[AMM] SFDC Campaigns

These are part of AMM's native and automatic functionality. AMM will for every channel and subchannel, create a generic [Bizible] campaign within SFDC in order to attribute touchpoints.

But these are not official campaigns, that is why there are no members, but the touchpoints will reference these campaigns for use in reporting and analytics.

Example: Web Direct [Bizible]

Bizible Reports in SFDC

Below are some frequently used bizible reports in SFDC and their use cases.

Use case: Track registration by source for GitLab owned gated landing pages

Bizible report type used: Bizible person with Bizible touchpoints (Custom)

Below are step-by-step instructions on how to track registration by driving channel for zoom webcasts, where the registration is set up on about.gitlab or Marketo pages.

• Step 1: Click SFDC report tab.
• Step 2: Create new report. In the search bar, type and select report type:Bizible person with Bizible touchpoints (Custom) and click create.
• Step 3: Within the SFDC report, make sure at the top the filters as set as Show All bizible persons and Date Field Range is set to All Time.
• Step 4: Add filter: Form url contains [insert webcast landing page unique identifier] (e.g: Form url contains automate-security-ci)
• Step 5: Select summary format and group by Marketing Channel - Path.

Training Video:

AMM Review Process

Online Channel Mapping

The review of online touchpoints and of the rules governing the creation of touchpoints based on online activities takes place once per month and includes the following checks:

• Pull a Marketo Measure Touchpoint SFDC report, grouped by channel and monitor for touchpoints associated to “Other” as the channel;
• Review the Landing Page Raw field data for the “Other” touchpoints and identify if there are new or rogue utm parameters that need to be added to our online rule sheet;
• Additionally review the UTM Generator spreadsheet which contains the urls that are used in our various online campaigns and make sure any newly added utm parameters are included in the online rules sheet;
• Finalize all updates to the online touchpoint rules sheet and re-upload it back into Marketo Measure > Online Channels section;
• Lastly, if the rule changes require any additions/substractions to our Channel/Sub-Channel mapping, make sure to have those included in the Marketo Measure > Create Channels section.

Offline Channel Mapping

The review of the campaign sync rules, the rules that govern the creation of touchpoints for offline activities takes place once per month and is based on the Adobe Marketo Measure Best Practices for Maintenance. It includes the following checks:

• Pull a Marketo Measure touchpoint grouped by channel, report and monitor if we're seeing many touchpoints associated to NULL as the channel;
• Review the Campaign Ad Name data field for the NULL touchpoints and identify if the Campaign Type is selected. If so, then ensure that Campaign Type is visible in Marketo Measure under Offline Channels, and it is mapped to the correct Channel;
• Under CRM > Offline Channels ensure all offline campaign types are mapped to the proper Marketo Measure channel/Sub-Channel.
• Under CRM > Campaigns ensure the rules setup are still up-to-date and accurate. Run a test on any campaigns that are not tracking properly.
• Publish any changes we make to retroactively update the touchpoints.

AMM data updates

To view all AMM data related updates please visit the marketing changelog spreadsheet. All updates are documented there along with additional information like the date of the update, level of impact and the type of the change.