Marketing Operations

Charter

Marketing Operations (MktgOps) supports the marketing organization to streamline processes and manage related tools. We work closely with multiple teams to ensure information between systems is seamless, data is as accurate as possible, and terminology is consistent in respective systems. Our team’s primary functions are:

• Project management of marketing technology stack
• Streamline and standardize processes related to tools
• Data cleanliness and accuracy
• Best practices and strategy on marketing technology
• Continuous improvement of marketing systems
• System integrations and data flow
• Evaluate new marketing technology
• Support procurement of new marketing technology

Meet the Team

How to Get Help

Important: Before submitting an issue that may contain Personally Identifable Information (PII) data (including screenshots), please ensure the issue is marked confidential. You can use quick actions to accomplish this in the issue description priort to submitting.

Teams We Work Closely With

Working with Channel Partner Marketing

Channel Partner Marketing Expectation

• To open issues for any new request using the problem statement.
• Channel Partner Team to respond to mktgops queries on the issue
• To provide full problem statement on the issue with as much context as possible.
• Optional - suggested solution for this issue.

Marketing Ops Expectation

• To use labels to denote where the issue is
• To use Milestones to denote when the work will be done
• To provide solution options for the problem statement with clear outline of timeline/ potential blockers.
• To verify possibility of the suggested solution(if there is one).

Bi-weekly Meeting

New issues will be prioritized within the bi-weekly meeting where Salina can understand if/what work should be deprioritised to complete the new work.

Salina to

• Add Priority label
• Add Stage Label
• Add milestone to the issue of when she thinks the work will be started

If no new issues- can either discuss issues or skip a week.

Handbook Updates

When making an update to a handbook page for ABM, FMM, MOps, or SDR handbook pages (or sub-pages), we have a Zapier workflow set up that will push the MR (upon merge) to the related Slack channel to ensure our teams are aware of any change that is made to the page. In order for the merged MR to show up in the respective Slack channel, you must add one of the following corresponding labels on the MR. Slack updates will also trigger for MktgOps MRs when created.

Milestone MRs

The marketing operations team uses collective merge requests, known as our milestone MRs, to make multiple updates across our handbook, see high-level updates in 1 MR, and avoid conflicts with each other. Here is an example. We list all major changes with our Denomas username in the description after a commit and link any relevant issues that the commit closes out. If you have an update for the marketing operations handbook, please feel free to use our milestone MR to make a commit and tag us for review to avoid conflicts.

Working with Sales Systems for New Fields and/or Permission Set Updates

The MktgOps team frequently works with the Sales Systems team to make changes in Salesforce.com (SFDC). See the below information regarding the process for working with Sales Systems for these changes and SLAs we adhere to.

Video: Marketing Salesforce.com Sandbox Training - Creating Changesets

If a field needs to be created in Marketo AND SFDC, it must be created in SFDC first and then added to the Marketo User Permission set within SFDC. From there, the field will sync down to Marketo. If you miss this order of operations and the field is created in Marketo first, you will need to still follow the directions above and then open a support to re-map the fields. **Use documentation for Marketo for field types.

If you need assistance with Sales Systems follow the next steps:

1. Open an Sales System issue in their project and assign the label EntAppsCustomer::MOPS. Then, add to the corresponding Epic as a related issue, or in the description (FY23Q4 Example.
2. If Mops member can create a changeset, please do so shortly after creating the issue to decrease time to deploy,
3. Add prioritization label of MktgOpsPrio::00: Requested
4. Business process owner (Amy or Christine) will review, and if they approve of the request from a business standpoint, they will check the appropriate box and add the MktgOpsPrio::01: Approved label. If not, the request will stay in MktgOpsPrio::00: Requested status until blockers or outstanding questions are resolved.
5. Once approved, requests will be added to the prioritization queue by the business proess owner to review with with Sales Systems or the PMO and labeled MktgOpsPrio::02: In Queue - Mops
6. Once Systems or PMO has agreed to take on work, the request will be added to a Temp holding milestone for further prioritization, and labeled MktgOpsPrio::03: In Queue - Systems
7. Once a milestone is added and the issue is discussed, the label will be updated to MktgOpsPrio::04: Actioned by the MktgOps representative that is in the prioritization call.
   • Once the label has been updated to MktgOpsPrio::04: Actioned, follow along with the Sales Systems labels for next steps.
8. Systems will work on the issue and push any updates to the Staging environment first
9. It is the responsibility of the Business Owner to test and accept. The Business Owner must show proof (such as a testing plan, or screenshot) that the solution is working correctly in the staging environment. This is an important step that represents acceptance of the solution, its testing, and the authority to change the related process.
10. Once ready to deploy, Systems manager will add SFDCReleaseHelp to flag to release managers it is ready for production release. Marketing Ops label should be updated to MktgOpsPrio::05: Pending Release
11. Once in production, MktgOps should confirm again that the field/update in SFDC and corresponding/impacted systems is working as anticipated. Label updated to MktgOpsPrio::06: Completed
12. Issue is closed and completed.

Other helpful links:

• Steps to getting help from Sales Systems
• Sales Systems Charter

Working with the Integrations team on Workato related issues

Workato is a low-code/no-code tool used to for automations and integrations across different teams at Denomas. We frequently work with the Integrations team to build, test and deploy some of the processes in Marketing Operations. The best way to work with the Integrations team is by opening an issue, depending on the scenario, there are two ways to go about that:

1. Request the creation of a new automation/integration

   • For types of request that involve building something from scratch and you require assistence from the Integrations team
     1. Open an issue in the Integrations Work and follow the instructions in the issue template.
     2. If the issue relates to marketing operations, make sure to tag @mihaiConteanu or @amy.waller

2. Bug fixing or deploying recipes developed in the testing environment

   • For fixing issues with currently working recipes or to test and review an independently built recipe before moving it into production. Due to SOX compliance, any change to a recipe in production needs to be acompanied by a change management issue.
     1. Open an issue in the Integrations Work Project and depending on your specific need, choose a template for Bug, Change, or Default and follow the instructions in the issue template.
     2. Open an issue in the Change Management Project and copy and paste this template in the issue description
     3. Follow the instructions in the template, it contains all labels and tags necessary to notify the Integrations Team
     4. Set a meeting with Durgesh Thakkar and Karuna Singh to go over and review your changes/recipe/issue.

Helpful links

• How Integrations Team works
• Workato Playbook

How to Communicate with Us

Slack channels

We do not use or create tool-specific Slack channels (e.g. #marketo).

• #hbupdate-mktgops - This channel is used to automatically post new handbook updates that have been merged.
• #mktgops - We use this channel for general marketing operations support, weekly marketing operations team standup updates, and key system status updates. We attempt to avoid direct messages where possible as it discourages collaboration.
  • In order to efficiently triage common requests, we utilize auto-responses in this channel. Anyone can help triage requests in the #mktgops slack channel by using the slack emoji reactions in the table below.

Salesforce

The Marketing Operations team has created the ‘@mktgops-support’ Chatter in Salesforce to help you make changes or manage Lead objects in Salesforce. Please note, the more information you can provide in your support request, the faster the request can be resolved. Use the ‘@mktgops-support’ Chatter for support with:

• Assigning leads to a new owner
• Merging duplicate leads in different ownership
• Investigating routing logic if you think a lead was routed improperly
• Requesting additional lead support from the Marketing Operations team
• The Marketing Ops team does not manage requests related to Contact, Account, or Opportunity objects.
• Please refrain from mentioning individual Marketing Ops team members and use this Chatter instead. Thank you!

Emergency Comms

If an emergency communication needs to be send out, Marketing Ops will need to assist. Follow directions on this page to initiate the emergency response and view the coverage matrix. You can also follow the security incident communication plan for security related issues.

How We Work

Issue Boards

1. MktgOps Team (issues by team member)
2. MktgOps-Support - FM/Event Marketo set-up (issues by milestone)

Issues

The MktgOps team works from issues and issue boards. If you are needing our assistance with any project, please open an issue or for small checks and questions, use the ~MktgOps::00: Triage label anywhere within the Denomas repo.

If you have a bug, error or discrepancy you’d like the team to help and investigate, please use the bug-request template.

With Agile Delivery being one of the solutions that Denomas (as a product) addresses, the Marketing Operations team aims to follow many of the agile methodologies.

Please do not reopen issues that have been closed in a previous milestone. If you find that you have additional questions about a closed issue, comment in the issue and ping the marketing ops DRI who worked the issue. The DRI within our team will determine whether an issue needs to be reopened and pulled into a current milestone.

OKRs

To track progress on and provide visibility to team OKRs each quarter, Marketing Operations uses the OKR feature in Denomas to organize our team-wide work. Current Marketing Operations OKRs can be found here.

Check out our quarterly highlights trackers to learn more about the key results we’ve accomplished.

Epics

If an issue includes a weight of 21 or more, that issue may be promoted to an epic in order to properly scope the work across multiple issues. Epics will also be used by our team if it relates to an OKR and requires multiple issues in scope to complete the work. Tool implementations also often are tracked within epics.

Labeling

We use labels for three purposes:

1. Categorize the tool or area that is affected
2. Show priority
3. Identify the stage they are in

Milestones

The MktgOps team works in two week iterations which are tracked as milestones at the Denomas.com level. Each individual contributor (IC) is responsible for adding issues to the milestone that will be completed in the two-week time frame. If needed, the IC will separate the main issue into smaller pieces that are workable segments of the larger request.

At the end of every milestone, we will post a thread in the #mktgops Slack channel with links to the Issues that we are moving to the next milestone. Context as to why an Issue is moving to a new milestone will be posted in the Issue (not in the Slack thread). The goal of this is to proactively and transparently communicate to our business partners and to empower marketing operations team members to intentionally and thoughtfully manage their work in each milestone.

A milestone cannot be closed nor marked complete until the milestone’s accompanying merge request has been merged. Within every milestone there is a WIP merge request with all commits being changes to our handbook. All team members contribute their changes to the milestone merge request. The merge request should be tagged with marketing operations labels and the current milestone.

Marketing Ops Calendar

Our team google calendar is available to Denomas team members here. It shows upcoming team PTO and holidays.

Focus Fridays

The Marketing Operations team had started an experiment on 2020-04-20 to commit to no internal meetings one day of the week. Now the entire Marketing team has moved to Focus Fridays. Please try not to schedule meetings for team members on Fridays, so they can devote time for deep work in milestone-related issues.

Marketing Changelog

Periodically Marketing Operations and other teams through the marketing org make significant changes to our system and processes that affect overall tools, data and reporting or uncovers significant changes that affected reporting. As such we have a shared changelog. The MktgOps and Strategy/Perf teams update this document as needed as changes are made. If you are working on an issue or epic that will have a significant impact across marketing, add the label MktgOps - changelog so marketing oeprations can track changes across Denomas.

Important Resources

• Marketing Metrics
• Marketing Owned Provisioning Instructions

List Imports

Marketing Technology Stack

Marketing Technology Tiering System

The Marketing Operations team maintains the Marketing technology tiering system in order to prioritize requests, provide support, and optimize processes.

Tools in the Stack

The SSoT for all tools at Denomas is the Tech Stack Applications page.

As a compliment to the Tech Stack, we created a visual of the Tier 1 and 2 tools in Marketing Technology stack, aligned to our customer journey.

Below are tools in the Marketing Technology stack, organized by tier.

Business Critical Technology - Tier 1

• 6sense
• Bizible / Marketo Measure
• Cognism
• Iterable
• Marketo
• On24
• Outreach.io
• PathFactory
• Qualified
• Traction
• ZoomInfo
• Vartopia - Lead Sharing Module

Operational Technology - Tier 2

• Allocadia
• Base
• Hopin
• Hightouch
• LinkedIn Sales Navigator
• MailJet
• OneTrust
• RingLead

Management Technology - Tier 3

• Litmus
• Reachdesk
• Google Analytics (Search Discovery)
• Survey Monkey
• Terminus Email Experiences
• Typeform

Functional Technology - Tier 4

• Bitergia
• Canva
• Cision
• Common Room
• ContentKing
• Frame.io
• Figma
• Launch Darkly
• MeetUp
• Quantum Metric
• SEMRush
• SheerID
• Sprout Social + Bambu
• Vimeo
• Zendesk Community

Requesting access to an existing tool

To request access to an existing tool in the stack, please follow the access request process as outlined in the business operations handbook.

If you are working with a contractor or consultant that requires access to a tool in our stack, please follow the professional services access request process as outlined in the procurement handbook.

Tool User Management

Technical owners should perform quarterly, bi-quaterly and, for some tools, monthly user audits. If a team member has not been actively taking advantage of a tool for 45 days (30 days for Zoominfo) or more, they will have access to that tool revoked with 5 business days of notification via email or slack (for Zoominfo). Activity will be determined by user reports pulled by the tools’ technical owner. These reports can be found by viewing issues from the Marketing Ops project with the issue label Mktg Tool Audit. The reports will utilize the audit issue template from the Marketing Ops project. To regain access to revoked tools, the team member will need to submit a new access request and follow standard access request procedures. However, user seats will be on a first-come-first-serve basis unless it is determined additional seats should be purchased.

Tech Stack Status Pages

Below is a collection of links leading to status pages of several listed MktgOps DRI tools. Unclickable links did not offer official status pages during the 2023 review of available webpages, but there are several unofficial and unaffiliated websites that offer webpage uptime checking as a service, e.g. www.isitdownrightnow.com, www.downdetector.com and www.downforeveryoneorjustme.com. Feel free to search on these sites during a perceived downtime, but keep in mind it may not be as accurate as an official source.

Renewal process for marketing technology budget owners

• Renewal discussion timing is determined by tier.
• For new software that has been approved create a business case to attach to the Zip Request (example).
• With Procurement submit an RFP every 2 years or for tools over $50K+.
• POC for any new tools or new features before signing a contract.
• No auto-renewals

Align with Procurement and Finance:

• Work with Procurement to structure and negotiate the contract. As well, look to do an RFP with multiple vendors for competitive pricing.
• Align with Finance to confirm budget is accounted for in FY24.

Marketing Operations role:

• Marketing Operations will help to define requirements and be a trusted advisor.
• Submit an issue (example) for new software evaluations.

MarTech Change Management

New Tool Purchase Process

If you are interested in or would like to request a new tool be added to the tech stack, please submit an issue using the tools eval issue template in the Marketing Operations repository. Marketing Operations should be included in new tool evaluations to account for system integrations, budget, etc. Any new tools desired after the budget is set will be handled by transferring budget from the other department to Marketing Operations. Once an issue is submitted, Marketing Operations will evaluate the request and assign the tool a tier.

The process for requesting a new tool is:

1. Tool Eval issue is submited
2. A Marketing Operations member is assigned to review the request. This person scores the requested tool in order to determine its tier. The business and technical owners of the tool are identified.
3. Once the request has been reviewed, the Marketing Operations manager will:
   • Create a new evaluation Epic, capturing relevant details from the intake issue.
   • Assign the new Epic to the business and technical owners
   • Update the intake issue description with a link to the new Epic.

Once the evaluation Epic is created, the following evaluation steps should be followed:

1. Discovery - understand the request/problem we’re trying to solve
2. Stakeholder identification - build the evaluation team based on the roles and responsibilities outlined below
3. Requirements gathering - document user stories, requirements, impacted processes, and features using this requirements gathering template
4. Evaluation - attend demos and compare features
5. Stakeholder alignment - align stakeholders to select vendor of choice
6. Privacy and security reviews - ensure that the selected tool is compliant
7. Negotiations and procurement
8. Implementation
9. Post-Implementation Review & Retro

Roles and Responsibilities

Resources

1. Requirements Gathering Template
2. Weekly Implementation Update Template

Lead Scoring, Lead Lifecycle, and MQL Criteria

For more information about lead lifecycle, visit this handbook page

A Marketing Qualified Lead (MQL) is a lead that has reached a certain threshold, we have determined to be 100 points accumulated, based on demographic/firmographic and/or behavioral information. The Person Score is comprised of various actions and/or profile data that are weighted with positive or negative point values. You can find more details about the scoring model on the Marketo Page

Campaigns and Programs

Campaigns are used to track efforts of marketing tactics - field events, webcasts, content downloads. The campaign types align with how marketing tracks spend and align the way records are tracked across three of our core systems (Marketo, Salesforce and Bizible) for consistent tracking. Leveraging campaigns aligns our efforts across Marketing, Sales and Finance.

Go to the Campaigns and Programs Page to view all of the campaign types, their progression statuses and cost tracking. That page also includes directions for set up in Marketo and Salesforce.

Marketing Ops partners with the Field Marketing and Corporate Events teams to provide Marketo program set-up and configuration, providing these teams with an internal partner to provide advise on the best technical set-up to reach their goals and streamlining more complex program requirements. Visit the Marketo Program/Campaign Support page for additional details.

Email Management

Marketing Ops is responsible for maintaining the email marketing database. Go to the Email Management Page for policies and more detailed information.

Initial Source

Initial Source is the first “known” touch attribution or when a website visitor becomes a known name in our database, once set it should never be changed or overwritten. For this reason Salesforce is set up so that you are unable to update the Initial Source field. If merging records, keep the Initial Source that is oldest (or set first). When creating Lead/Contact records and you are unsure what Initial Source should be used, ask in the #mktgops Slack channel. Initial Source in Marketo is named Person Source, and should only update when empty.

We use Source Buckets to group Sources into acquisition channels. These groups are: core, inbound, outbound, paid demand gen, purchased list, referral, virtual event, and web direct. When using the TD - Marketing Metrics dashboard reports can be filterd by these source buckets.

The values listed below are the only values currently supported. If you attempt to upload or import leads or contacts into Salesforce without one of these initial sources you will encounter a validation rule error. If you think that there needs to be a new Initial Source added to this list and into Salesforce please open an issue with the marketing ops team. When a new initial source is added, the bucket must also be updated in a SFDC workflow to properly show in Sisense.

Status in the table below means:

• Active = can be selected from picklist
• Inactive = cannot be selected from picklist, but a record may exist with this source

Lead and Contact Statuses

The Lead & Contact objects in Salesforce have unified statuses with the following definitions. Also reference Re-MQL workflows for how to move from status to status. To learn more on how we manage our lifecycle including lead/contact status and Lifecycle Classifications, please see here.

One of the following must occur to have a lead move from Raw to Inquiry

1. Become a member of a marketing program (except no-action/default statuses, nor email)
2. Fill out a form (social or website)
3. Behavior score > 10 pts.

Lead Address Fields

On the lead object we have three types of address information, the local/personal address information for that lead, which is stored on the Person Address (address type field), the Ultimate Parent Account Company information stored on Company Address: [XXX] text fields, and the Zoominfo enrichment address information for both the Contact (local information) and the Company level information:

• Person Address is partially filled in from Marketo Form Fills and is also completed by ZI enrichment when it is missing;
  • This is the address that Marketo references for email lists. It contains the local address of the record, if known through form fill, list upload, or ZI enrichment.
• UPA Company Address - stored on the Company Adress: Country, Company Adress: State, Company Adress: City, Company Adress: Street, Company Adress: Postal Code text fields. These fields are updated through APEX code through a 3-step waterfall approach.
  1. Account Demographics Fields (i.e: Account Demographics: UPA City) - If the lead matches to an existing account the address is populated through the Account Demographic fields, taken from the account associated with this lead;
  2. Admin Override Fields (i.e: [Admin] Company Address Country) - If a lead doesn’t match to an account, the Company Address fields are either blank or are populated through step 3 in the waterfall (see below). If the address is blank or the address information from step 3 is wrong, SDRs/BDRs can update the address information themselves using these Admin Override fields. You can see more information about this process in the Overriding Incorrect Account Assignments section from Sales Dev Handbook or in this video.
  3. Zoominfo Company Address Fields (i.e: [ZI] Company Country) - If the lead doesn’t match an account, it was not overwritten using the Admin Override Fields mentioned above and the lead matches to Zoominfo’s database, the Company Address fields are populted with Zoominfo Company Address information from the Zoominfo Company Address fields.
• Zoominfo enrichment address information which as can be of two types, personal (local) or company level address;

1. Zoominfo personal (local) address information can be found in the [ZI] Contact Country, [ZI] Contact State, [ZI] Contact City, [ZI] Contact Street, [ZI] Contact Zip Code fields;
2. Zoominfo Company Address Information can be found on the [ZI] Company Country, [ZI] Company State, [ZI] Company City, [ZI] Company Street, [ZI] Company Zip Code fields;

Data Cleanliness and Enrichment Process

Marketing Operations has the responsibility for cleaning and enriching our database of leads/contacts with the most complete and up to date information.

The cleaning part of this process is being done with the Cleanse functionality of the lead/contact deduplication tool, Ringlead.

The enrichment part of the process is done using the data appending/enrichment tool, Zoominfo, our SSOT when it comes to account/lead/contact data. Cognism, is another enrichment tool but only for a smaller subset of our lead data. As of now, only the BDRs and Cognism admins have login access. However, Cognism data, can be found in the Cognism fields on the lead/contact layout.

This cleaning & enrichment process has 5 main priorities:

1. Enrich net new Marketo leads with Marketo Webhook - All leads created through Marketo are instantly enriched with ZI data.
2. Instant Enrich for leads - When new leads are created in SFDC, Instant Enrich functionality kicks in and the record’s [ZI] fields are enriched upon creation.
3. Enriching net new leads with Scheduled Enrich - As a back-up to the Instant Enrich functionality (in case it fails for any reason), all leads created in the last 24h are enriched through scheduled enrichment, to make sure they contain the most updated information.
4. Existing Database Enrichment - All lead records in SFDC are enriched regularly to make sure that the leads who change roles/companies are updated with the lastest information.
5. Assure Data Cleanliness & Accuracy - The Marketing Operations team is following the recommended deduplication order of operations as detailed below:
   • Lead to Lead Deduplication (Paused to fix duplicates being created by different tools)
   • Account Deduplication (This part is currently performed using Openprise by Sales Operations)
   • Converting Leads to New Contacts (This step is skipped in our case since it would impact sales workflow considerably. We will re-evaluate if the sales team is not as heavily focused on leads as we are now.)
   • Contact to Contact Deduplication (Testing unwanted contact merging effects on order processin and open quotes)
   • Lead to Contact Deduplication (This part of the process will start once Contact Deduplication is completed)
   • Deduplication of Custom Objects (Bizible Person IDs - On hold until Contact Deduplication and Lead to Contact Deduplication are completed)

For more information regarding our data deduplication process visit the Ringlead Handbook Page.

Cleaning & Enrichment Frequency: While the enrichment jobs for net new leads, work on a continuous bases, when it comes to enrichment of our existing leads & contacts in SFDC, this is done via scheduled enrichment jobs as follows:

1. All leads are enriched on a weekly basis, last Saturday of the month.
2. All leads created in the last 7 Days are enriched daily to make sure no new leads from list uploads miss enrichment and also to make sure our sales teams have the most up to date information when working them.
3. All contacts in our SFDC instance get enriched weekly, last Saturday of the month.

You can find more details on the enrichment process in our Zoominfo Handbook Page.

Lead List Upload Enrichment

To be able to upload a lead in our SFDC, it is mandator for the lead to have an email address. Sometimes we do run into situations where the email address is not available.

To bypass this challenge and still be able to upload the leads in SFDC, please create an List Upload - Enrichment Request with this issue template, upload the CSV file in the issue and Mops will use the Zoominfo Enhance, Zoominfo ListMatch and Cognism Enhance functionality to enrich these records with the most up to date information (including the email address).

Note: Such records as lead list uploads with no email addres, that sub-sequently are enriched with the email address through Zoominfo/Cognism enrichment, need to be marked as Opt-out as these individuals did not give us the express consent that they can be reached to;

Cleaning Test Leads

Testing processes and automation are critical for quality assurance in our systems.

As a tester, you create test leads to ensure processes work as expected. These test leads are mixed among real records, causing inaccuracies in our reporting. Marketing Operations has created best practices that make it easier to spot and delete test leads.

The next time you test a program, remember set Job Title = Test and they will be removed promptly.

Notice any test leads? Please open an issue with the Marketing Operations team.

Communication Compliance Best Practices

Internal DNC (Do Not Call) Lists

Internal DNC List are maintained using the Do Not Call checkbox on the lead/contact record layouts. The sales development organization has a clear process on how and in what context should the box be checked. Please visit the Sales Development Handbook page - Cold Calling Checklist section to find out more about it.

External DNC (Do Not Call) Lists

To be compliant with international DNC (Do Not Call) regulations and minimize the risk of litigation, a process was implemented for making sure the records that appear on external DNC lists are not contacted via phone (this applies to both Direct Dial Phone Numbers and Mobile Phone Numbers).

This information gets passed to us with the help of Zoominfo, which populates the [ZI] Do Not Call - Direct Phone and [ZI] Do Not Call - Mobile Phone fields with the Yes value whenever a phone number is found to be on an external DNC list.

With Marketo automation we are then using these two fields to hide the phone number information on the following fields: [ZI] Phone Number, Phone (standard field - only if it matches the [ZI] Phone Number value), [ZI] Mobile Phone Number and Mobile Phone (standard field - only if it matches the [ZI] Mobile Phone Number value).

For more information, please visit this figjam flow chart.

Do Not Do Business

In some cases, there are companies we do not do business with. If an account is flagged, Mops should take the following steps to ensure they are not included in any of our communications moving forward.

1. Add the customer account to the DNDB campaign in Marketo. Use the SFDC Account ID and update contains with the email domain, if sepcific to that company. Click Schedule > Run once. (This will also run nightly.) This flow updates the lead/contacts to unsubscribe``, removes them from Security Distro, marks email as invalid, marks as Do Not Call``, updates person status to Ineligible, and marks the reason as ECCN - Do Not do Business
2. No need to check Iterable for the email address. They will be removed via API, as Marketo sends unsubscribes over via webhook to Iterable automatically once unsubscribe = true.

Zoominfo Opt Out Lists

Zoominfo is our SSOT when it comes to data enrichment of our leads/contacts and accounts.

To be compliant with the latest privacy policies and safeguard our database from potential litigation, Zoominfo’s recommendation for contacts that have opted out of their database is to:

If you have downloaded any of these contact records from ZoomInfo or uploaded them to your internal systems, you must remove >them unless you have an independent lawful basis to possess and use such person’s personal data.

Note: This only applies for leads/contacts that do NOT currently have an existing business relationship

After collaborating with Denomas’s privacy department, it was decided to create a process for removing said contacts from our database.

The current process takes place on a weekly basis and is implemented with the help of a Marketo Program. It takes advantage of the Zoominfo Non-Matched Reason field which is populated by Zoominfo. All leads/contacts that have the OPT_OUT value, enter the process and are checked for additional activities that could qualify as independent lawful basis to be kept. If they lack said activities they will be removed from our database.

For more information, please visit this figjam flow chart.

If you have any questions or concerns feel free to open an issue with the Marketing Operations team.

View page source - Edit this page - please contribute.