Marketo offers a range of tools to help marketing teams capture more precise data, personalize campaigns, and improve reporting accuracy. Program Member Custom Fields (PMCFs) are one of the more underutilized features in that toolkit. Salesforce’s 2026 Tenth Edition State of Marketing report, based on 4,450 marketing decision makers worldwide, found that 75% of marketers have adopted AI yet still use it to send generic campaigns, with poor data quality and siloed systems cited as the primary barrier. PMCFs directly address one of the most common causes of that problem inside Marketo: program-specific data that has no clean place to live. Adobe’s official Marketo Engage documentation defines PMCFs as program-level fields that store values specific to a person’s membership in a single program, completely separate from their global lead record.
In this post, we’ll cover:
- What Are PMCFs?
- Benefits of Using PMCFs
- How to Implement PMCFs in Marketo
- How PMCFs Fix UTM Tracking
- When to Use PMCFs vs. Global Lead Fields
- Common Mistakes to Avoid
- FAQs
Key Takeaways
- PMCFs store data at the program level: the same lead can have different values for the same PMCF across different programs without overwriting their global record.
- The 20-field limit applies to your entire Marketo subscription, shared across all programs. Hidden fields count against the limit.
- PMCFs cannot be deleted after creation, only hidden, and hidden fields still count against your 20. Plan field types before you build.
- UTM tracking via PMCFs is more accurate than person-level UTM fields because the data ties to the program, not the person, and survives multi-touch journeys without overwriting.
- PMCFs can sync to Salesforce Campaign Member fields, but do not sync natively to lead or contact records.
- PMCFs are available in local program assets only and are not supported in Design Studio.
What are Program Member Custom Fields in Marketo?
Program Member Custom Fields (PMCFs) are program-level data points in Marketo Engage that store information specific to a person’s involvement in a single marketing program, rather than on their global lead or contact record. Unlike standard fields tied to a lead record, PMCFs are unique to the program member. This means you can track and store data relevant to a member’s participation in a particular program (event sessions attended, trial usage details, webinar poll responses) without that data carrying over to or overwriting anything on the lead record.
The supported field types are: boolean, date, datetime, float, integer, string, and URL. These fields are defined globally in your Marketo Admin under Field Management, but the values stored in them are local to each program member record.
The practical result: a lead who attends three of your webinars has three separate sets of PMCF values, one per program, without any of that data touching their lead record or getting overwritten by subsequent events.
What are the benefits of PMCFs over standard lead fields?
PMCFs give you three things standard lead fields cannot: program-level personalization, reliable segmentation, and attribution data that doesn’t overwrite itself across campaigns. Here are the key benefits:
Enhanced Personalization
PMCFs let you capture a program member’s interactions and preferences within a specific program and use that data to tailor follow-up communications. Because the data is tied to the program rather than the lead record, you can reference exactly what session someone attended, what feedback they submitted, or what product version they trialed, without that context getting confused across campaigns.
Improved Segmentation
With PMCFs, you can build smart lists using program-level criteria. A segment like "Leads who attended Session B of our Q2 Summit and rated it 4 or 5 stars" requires program-level data. Standard lead fields cannot support that level of specificity without overwriting concerns. PMCFs make those segments reliable and repeatable.
Better Reporting and Analytics
PMCFs add program-specific data points that can be used for in-depth reporting and analysis. You can track attendance rates, feedback scores, trial usage, and conversion by program, giving your team the granular view needed to evaluate program performance accurately and improve future campaigns.
Streamlined Data Management
Using PMCFs keeps your lead and contact records cleaner and more organized. One-time, program-specific data (the kind that clutters global records and complicates segmentation) stays contained at the program member level. Your lead schema reflects what you know about the person, not the accumulation of every form they’ve ever submitted.
How do you set up Program Member Custom Fields in Marketo?
Step 1: Map your field architecture before creating anything
Start by determining what data you need to capture for your program members. Consider whether the data is program-specific (it belongs in a PMCF) or meaningful across all programs (it belongs on the lead record). Map out the field types you’ll need (string, boolean, date, integer) before creating anything.
The Program Member object supports up to 20 custom fields per subscription, shared across all programs, as confirmed in Adobe’s Marketo Engage documentation. Once a field is created, it cannot be deleted through the UI, only hidden, and hidden fields still count against your 20. Decide on versatile, reusable field names before you build.
Step 2: Create the fields in Admin > Field Management
Navigate to Admin > Field Management > New Custom Field. In the Object dropdown, select Program Member. Name your fields clearly and consistently. A naming convention like [Category]_[Descriptor], for example Event_SessionAttended or UTM_Source, keeps your instance organized as the field list grows.
One constraint to note: Person and Program Member custom fields cannot share the same name. If a lead-level field with that name already exists, Marketo will block the PMCF creation. Check for naming conflicts in Field Management before building.
Step 3: Add PMCFs to local program forms, not Design Studio
PMCFs are available in local program assets only and cannot be added to forms created in Design Studio. Build your registration or data-capture form inside the program, add the PMCF as a form field, and your marketing automation workflows will populate those fields at submission.
Step 4: Use PMCF triggers and filters in smart campaigns
PMCFs are available as triggers and filters in smart campaigns within the program: "Program Member Custom Field Changes" as a trigger, "Program Member Custom Field" as a filter. Use these to send relevant follow-ups based on what the lead submitted or how they engaged during the program.
Step 5: Audit field usage quarterly and manage deletions via Support
Review which fields are actively populated versus empty or hidden. If you need to delete a field to free up a slot, you must contact Marketo Support, as this cannot be done through the UI. Build that constraint into your PMCF governance process from the start.
How do PMCFs fix UTM tracking in Marketo?
UTM tracking at the person level has a well-known problem: lead fields hold one value at a time. When the same lead fills out forms across multiple programs, each new UTM overwrites the previous one. Your attribution model ends up reflecting the last touch, not the full journey.
PMCFs solve this by tying UTM data to the program where the conversion happened. Because the data lives at the program member level, each program preserves its own UTM values independently. The same lead can have different UTM source, medium, and campaign values across three different programs, and none of them overwrites the others.
This makes PMCFs significantly more effective for UTM tracking than person-level fields, and the data can be mapped to Salesforce Campaign Member fields through Adobe’s Program Member Custom Field Sync, giving your CRM accurate campaign-level attribution without polluting lead or contact records.
When should you use PMCFs instead of global lead fields?
If the data is meaningful only within the context of a specific program, it belongs in a PMCF. If it describes the lead across all programs and campaigns, it belongs on the lead record.
Use PMCFs for:
- Event-specific data: session attended, food restrictions, t-shirt size, in-person vs. virtual selection, post-event feedback rating
- Product trial data: trial start and end dates, product version trialed, usage statistics, conversion feedback
- UTM parameters at registration: source, medium, campaign, and content, captured per program rather than per person
- Webinar-specific data: poll responses, Q&A submissions, attendance duration, resource downloads during the session
Keep on the lead record:
- Lifecycle stage and lead score
- Company, title, and industry
- Overall communication preferences and consent
- Persona or ICP classification
- Primary CRM owner
A useful decision rule: if you would need to say "their answer for that event" to make the field value meaningful, it belongs in a PMCF.
What are the common mistakes when setting up PMCFs in Marketo?
Using the field limit on single-use fields.
A boolean PMCF named SummitAnnual2024_Attended serves one program. A string PMCF named Event_SessionSelected serves every event program you run. Teams that create program-specific field names exhaust their 20-field limit before they’ve built a reusable architecture. Design for versatility.
Forgetting that hidden fields count against the 20-field limit.
If you hit the limit and see fewer than 20 fields in your Admin view, check the hidden fields section. Adobe’s Knowledge Base documents this directly: hidden PMCFs still occupy a slot. Deleting a hidden PMCF requires a Marketo Support ticket, so don’t get caught at the limit during an active campaign build.
Building registration forms in Design Studio.
Design Studio forms cannot capture data into PMCFs. If you build your form in Design Studio and then try to add a PMCF field, the option won’t appear. The form must live inside the program. Organizations that centralize all forms in Design Studio will need to adjust that workflow before implementing PMCFs.
Naming conflicts with existing lead fields.
Marketo blocks PMCF creation if the name matches an existing field on another object, but the error isn’t always clear. Before creating any PMCF, search Admin > Field Management to confirm the name is available.
Skipping the Salesforce sync configuration.
If you want PMCF data visible in Salesforce campaign member records, you must configure the mapping manually under Admin > Salesforce > Program Member Custom Field Sync. This does not happen automatically. Teams that skip this step lose program-level data at the CRM layer even when the Marketo data is accurate.
Frequently Asked Questions
How many Program Member Custom Fields can I have in Marketo?
Marketo supports up to 20 Program Member Custom Fields per subscription, per Adobe’s official Marketo Engage documentation. These fields are shared across all programs in the instance; this is not a per-program limit. Hidden fields count against the 20. If you receive an "exceeded limit" error but see fewer than 20 visible fields, check the hidden fields section in Admin > Field Management.
Do PMCFs sync to Salesforce or other CRMs?
PMCFs do not sync natively to Salesforce lead or contact records. They are designed to remain at the Marketo program member level to keep CRM data clean. However, you can map PMCFs to Salesforce Campaign Member fields through Adobe’s Program Member Custom Field Sync, available under Admin > Salesforce. This allows program-level data to appear in Salesforce campaign reporting without affecting lead or contact records.
Are Program Member Custom Fields global or local?
The field definitions are global, created in Admin and available to any program in the instance. The values stored in those fields are local to each program member record. A lead who attended two webinars can have different values in the same PMCF for each program, and neither value affects the other.
Can I delete a PMCF after creating it?
No. Once a Program Member Custom Field is created, it cannot be deleted through the Marketo UI. You can hide it, but hidden fields still count against the 20-field limit. To permanently delete a PMCF, contact Marketo Support. This is why planning field names and types before creation is the most important step in any PMCF implementation.
Can I use PMCFs in Design Studio forms?
No. PMCFs are only available in local program assets. A form must live inside a specific program to capture data into that program’s PMCFs. Forms in Design Studio do not have access to PMCF fields, and a form containing PMCFs cannot be cloned or moved to Design Studio after creation.
GNW Consulting is a certified Adobe partner specializing in Marketo Engage implementation and marketing operations for B2B organizations. For questions about PMCF architecture, UTM attribution setup, or Marketo data management, *contact our team* or explore our *Marketo Engage services*.
