Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

Issue When you navigate to Admin>Munchkin, you see option to select Workspace. Why is that? This is a article attached image Solution People generally use workspsce either because of their companies geographical location or Business Unit. In each case, the separation is because the marketing assets are completely different. With that said, If you're using Workspaces in your Marketo account, you probably also have separate web presences that correspond to your workspaces. In that case, you can use the Munchkin tracking Javascript to assign your anonymous people to the correct workspace and partition. This is used to differentiate appropriate leads within workspace with the help of appropriate tracking. If you don't use the special workspace Munchkin code, the people will be assigned to the default partition that was created when your account was set up. It's named "Default" initially, but you might have changed that in your own Marketo account. You can only use one Munchkin tracking script for a single partition and workspace on a page. Do not include tracking scripts for multiple partitions/workspaces on your website. I would also like to mention that Landing pages created in Marketo automatically contain tracking code, so you don’t need to put this code on them.

When a user switches to another language in their preferences not everything in Marketo will get translated. Specifically, any object that has an editable name is not automatically translated. Type of Text Example Translated? Editable Text Programs Seeded Channels Seeded Marketing Activities Folders Progression Statuses Custom Fields No Not Editable Text Standard Fields System Smart Lists General User Interface Yes When a user views content in a workspace that is not the same as their preferred language, the above table describes what would be translated.

Issue You have two SFDC picklist fields mapped to one Marketo field but it isn't showing all picklist values for both SFDC fields. Solution When two SFDC picklist fields are mapped to one field in Marketo, the only values that will show in Marketo will be the values that exist in both picklists. Review the picklist values in Salesforce and add any missing values to the picklists so that they match exactly. This could happen in situations where the field in Marketo is mapped to a SFDC picklist field on leads as well as a SFDC field on contact/account.

Issue You need to locate the Munchkin ID for a specific Marketo instance. Solution What is a Munchkin ID? Marketo's custom JavaScript tracking code, called Munchkin, tracks all individuals who visit your website so you can react to their visits with automated marketing campaigns. Even anonymous visitors are tracked along with their IP addresses and other information. The Munchkin ID is the unique identifier for a specific Marketo instance and insures tracked activity goes to the correct instance. How to find your Munchkin ID 1. Log into the specific Marketo Instance you need the Munchkin ID for. You can verify the instance name by checking the listing in the top left of your browser. This is a article attached image 2. Go to Admin and click Munchkin in the tree on the left in the Integration section. This is a article attached image 3. The Munchkin Account ID will be the first thing listed in the Tracking Code box. This is a article attached image

Issue How do you delete the data in Marketo Custom Object records, or in specific fields on the custom object if the the custom objects have already been created and approved? Solution Marketo Custom Objects are not accessible via the User-Interface. API calls must be utilized in order to delete this record data. You can delete the records via the 'Delete Custom Objects' call Delete Custom Objects If you are interested in extracting any of the existing data, you can use the following GET call. You will need to make a 'Get Custom Objects' call Edit Custom Objects Here is an additional resource that may be useful and relevant List Custom Objects

Syntax Recommendations Common Look Up mechanisms Common Modifiers Too Many Mechanisms Character String Too Long Null Records in the SPF Record Repetitive Records in the SPF Record - Void Lookups Validation Tools Syntax Recommendations Common Look Up mechanisms a: mx: include: ip4: ip6: exists: ptr: all Common Modifiers redirect= exp= An A Record must ALWAYS contain IP address (map host to IP) CNAME (Alias) must contain hostnames. No IPs here NS an MX records must contain host names. No IPs allowed. MX records (for mail servers) should contain hostnames NOT IPs. Too Many Mechanisms Section 10.1, "Processing Limits" of the SPF RFC 4408 specifies the following in regards to DNS lookups: SPF implementations MUST limit the number of mechanisms and modifiers that do DNS lookups to at most 10 per SPF check, including any lookups caused by the use of the "include" mechanism or the "redirect" modifier. If this number is exceeded during a check, a PermError MUST be returned. The "include", "a", "mx", "ptr", and "exists" mechanisms as well as the "redirect" modifier do count against this limit. The "all", "ip4", and "ip6" mechanisms do not require DNS lookups and therefore do not count against this limit. The "exp" modifier does not count against this limit because the DNS lookup to fetch the explanation string occurs after the SPF record has been evaluated. This limit is in place to prevent SPF lookups from being a useful avenue for Denial of Service attacks. Using an example SPF record as an example to illustrate, this record was breaking with 12 look-ups: example.com text = "v=spf1 include:_spf-a.example.com include:_spf-b.example.com include:_spf-c.example.com include:_spf-ssg-a.example.com include:spf-a.anotherexample.com ip4:131.107.115.215 ip4:131.107.115.214 ip4:205.248.106.64 ip4:205.248.106.30 ip4:205.248.106.32 ~all" [ 5 mechanisms] _spf-a.example.com text = "v=spf1 ip4:216.99.5.67 ip4:216.99.5.68 ip4:202.177.148.100 ip4:203.122.32.250 ip4:202.177.148.110 ip4:213.199.128.139 ip4:213.199.128.145 ip4:207.46.50.72 ip4:207.46.50.82 a:mh.example.m0.net ~all" [ +1 = 6 mechanisms] mh.example.m0.net a = 209.11.164.116 _spf-b.example.com text = "v=spf1 include:spf.messaging.example.com ip4:207.46.22.35 ip4:207.46.22.98 ip4:207.46.22.101 ip4:131.107.1.27 ip4:131.107.1.17 ip4:131.107.65.22 ip4:131.107.65.131 ip4:131.107.1.101 ip4:131.107.1.102 ip4:217.77.141.52 ip4:217.77.141.59 ~all" [+1 = 7 mechanisms] spf.messaging.example.com text = "v=spf1 include:spfa.anotherexample.com include:spfb.anotherexaple.com include:spfc.anotherexample.com -all" [+3 = 10 mechanisms] spfa.anotherexample.com text = "v=spf1 ip4:157.55.116.128/26 ip4:157.55.133.0/24 ip4:157.55.158.0/23 ip4:157.55.234.0/24 ip4:157.56.112.0/24 ip4:157.56.116.0/25 ip4:157.56.120.0/25 ip4:207.46.100.0/24 ip4:207.46.108.0/25 ip4:207.46.163.0/24 ip4:134.170.140.0/24 ip4:157.56.110.0/23 -all" [+0 = 10 mechanisms] spfb.anotherexample.com text = "v=spf1 ip4:207.46.51.64/26 ip4:213.199.154.0/24 ip4:213.199.180.128/26 ip4:216.32.180.0/23 ip4:64.4.22.64/26 ip4:65.55.83.128/27 ip4:65.55.169.0/24 ip4:65.55.88.0/24 ip4:94.245.120.64/26 ip4:131.107.0.0/16 ip4:157.56.73.0/24 ip4:134.170.132.0/24 -all" [+0 = 10 mechanisms] spfc.anotherexample.com text = "v=spf1 ip4:207.46.101.128/26 ip6:2a01:111:f400:7c00::/54 ip6:2a01:111:f400:fc00::/54 ip4:157.56.87.192/26 ip4:157.55.40.32/27 ip4:157.56.123.0/27 ip4:157.56.91.0/27 ip4:157.55.206.0/24 ip4:157.55.207.0/24 ip4:157.56.206.0/23 ip4:157.56.208.0/22 -all" [ +0 = 10 mechanisms] _spf-c.example.com text = "v=spf1 ip4:203.32.4.25 ip4:213.199.138.181 ip4:213.199.138.191 ip4:207.46.52.71 ip4:207.46.52.79 ip4:131.107.1.18 ip4:131.107.1.19 ip4:131.107.1.20 ip4:131.107.1.48 ip4:131.107.1.56 ip4:86.61.88.25 ip4:131.107.1.44 ip4:131.107.1.37 ~all" [+0 = 10 mechanisms] _spf-ssg-a.example.com text = "v=spf1 include:_spf-ssg-b.example.com include:_spf-ssg-c.example.com ~all" [+2 = 12 mechanisms] _spf-ssg-b.example.com text = "v=spf1 ip4:207.68.169.173/30 ip4:207.68.176.1/26 ip4:207.46.132.129/27 ip4:207.68.176.97/27 ip4:65.55.238.129/26 ip4:207.46.222.193/26 ip4:207.46.116.135/29 ip4:65.55.178.129/27 ip4:213.199.161.129/27 ip4:65.55.33.70/28 ~all" [+0 = 12 mechanisms] _spf-ssg-c.example.com text = "v=spf1 ip4:65.54.121.123/29 ip4:65.55.81.53/28 ip4:65.55.234.192/26 ip4:207.46.200.0/27 ip4:65.55.52.224/27 ip4:94.245.112.10/31 ip4:94.245.112.0/27 ip4:111.221.26.0/27 ip4:207.46.50.221/26 ip4:207.46.50.224 ~all" [+0 = 12 mechanisms] spf-a.secondexample.com text = "v=spf1 ip4:157.55.0.192/26 ip4:157.55.1.128/26 ip4:157.55.2.0/25 ip4:65.54.190.0/24 ip4:65.54.51.64/26 ip4:65.54.61.64/26 ip4:65.55.111.0/24 ip4:65.55.116.0/25 ip4:65.55.34.0/24 ip4:65.55.90.0/24 ip4:65.54.241.0/24 ip4:207.46.117.0/24 ~all" [+0 = 12 mechanisms] Character String Too Long 255 character limitation in a single string https://kb.isc.org/article/AA-00356/0/Can-I-have-a-TXT-or-SPF-record-longer-than-255-characters.html http://www.string-functions.com/length.aspx You may have more than 255 characters of data in a TXT or SPF record, but not more than 255 characters in a single string. If you attempt to create an SPF or TXT record with a long string (>255 characters) in it, BIND will give an error (e.g. "invalid rdata format: ran out of space".) Strings in SPF and TXT records should be no longer than 255 characters. However to get around this limitation, per RFC 4408 a TXT or SPF record is allowed to contain multiple strings, which should be concatenated together by the reading application. In the case of use for SPF (using either TXT or SPF RRs) the strings are concatenated together without spaces as described below. Reassembly by other applications of multiple strings stored in TXT records might work differently. 3.1.3. Multiple Strings in a Single DNS record As defined in [RFC1035] sections 3.3.14 and 3.3, a single text DNS record (either TXT or SPF RR types) can be composed of more than one string. If a published record contains multiple strings, then the record MUST be treated as if those strings are concatenated together without adding spaces. For example: IN TXT "v=spf1 .... first" "second string..." MUST be treated as equivalent to IN TXT "v=spf1 .... firstsecond string..." SPF or TXT records containing multiple strings are useful in constructing records that would exceed the 255-byte maximum length of a string within a single TXT or SPF RR record. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26 ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all“ text = "v=spf1 ip4:199.15.212.0/22“ " ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24" " ip4:72.32.243.0/24 ip4:94.236.119.0/26" " ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all" Null Records in the SPF Record A record that is NULL or that does not exist will break an SPF record. Syntax within the record is very important, if there are extra spaces between mechanisms it will count as NULL. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22“ <- accurate text = "v=spf1 ip4: 199.15.212.0/22“ <- NULL (NOTE the space between IP4: and the IP) Repetitive Records in the SPF Record - Void Lookups If there are too many repetitive mechanisms in the SPF record, including records that cascade (for example when using "include:") the record will break. There is a MAX of 2 void look ups in an SPF record. More than that and the record will break. This prevents SPF records from being used in Denial of Service style attacks. Validation Tools SPF checker, syntax validator and SPF tester http://www.kitterman.com/spf/validate.html SPF checker http://vamsoft.com/support/tools/spf-policy-tester SPF validator http://vamsoft.com/support/tools/spf-syntax-validator CIDR Calculator http://www.subnet-calculator.com/cidr.php Nslookup http://network-tools.com/nslook/ SPF creation wizard http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/ Common SPF errors http://www.openspf.org/FAQ/Common_mistakes SPF syntax definitions http://www.openspf.org/SPF_Record_Syntax

Issue Changing your primary domain can be a bit of a daunting task if you don't know where to start, this guide will walk you through the steps you will need to take to use a new domain with your Marketo instance. Solution Create your new CNAME and point that to your Marketo instance. If this new CNAME is going to be used as your primary domain, then the Domain Name in Admin > Landing Pages will need to be changed to reflect your new domain and your old domain should be added as a domain alias so any old links will be redirected to your new domain Add Additional Landing Page CNAMEs Adding a new branding domain is recommended when changing your domain. This will allow tracked links in emails add a tracking cookie when being directed to your new domain. A new CNAME will also need to be created for this and will need to point to the original tracking link for your instance. Add an Additional Branding Domain with Workspaces If you plan on signing your emails with your new domain, setting up a new SPF/DKIM record is recommended to help keep your deliverability rates as high as possible. Set up SPF and DKIM for your Email Deliverability Set up a Custom DKIM Signature

Issue Issue Description Unable to limit user access specific to certain programs or assets Solution Customization of user roles for assets (such as landing pages, emails, etc.) or programs is currently unavailable. However, you can control user access by limiting their permissions to specific workspaces, provided that Workspaces are enabled for your Marketo instance. Configure Protocols for Marketo

Summary This article explains why certain Company fields show up on the Person/Lead Object when you do a describe API call to Marketo. Issue When making the Describe call on the Lead object in Marketo (/rest/v1/leads/describe.json), several Company object fields are returned along with the Lead object fields. Environment Marketo REST API Solution This is expected behavior. Users can utilize the Describe Leads call to retrieve a full list of the fields available for interaction via the REST API. Several areas within Marketo treat custom Company fields as though they were on the Person/Lead object. For example if you were doing a Bulk Import, you can target the Company and Person/Lead fields and you have the ability to update Company field values as if you were changing it manually on a Person record in the UI. Root Cause This is expected behavior, due to how the Describe call retrieves all

Summary Building a Smart List or Report for Merge Activities within time frame Issue You're looking to have a Smart List or Report built to gather insights on what merges, if any, took place within your database over a given time frame. Environment Marketo Smart List Reporting/Analytics Database API Solution Marketo doesn't have native capabilities to report on Merge activities that take place within your database, either via Smart List filters or within the Analytics section of Marketo. This is due to the activity type surrounding the merging of leads, Merge Leads, not being an attribute available for filters or reporting. The only way to go about getting a sort of list or report of the various merges that took place is to utilize the self-service Bulk Activity API endpoint and filter/specify the desired timeframe that you're wanting to look at. Please partner/consult with your Developer to go about building the job necessary to accommodate this. Below are two resources available on our Marketo Developer site to assist and offer guidance as needed. Resource(s): Bulk Activity Extract documentation Bulk Activity Extract endpoint reference(s) Root Cause Marketo doesn't offer the ability to filter off the Activity Type of Merge Leads.

Summary If you're using the Bulk Custom Object Import API to push records to a Marketo custom object (and you're importing separate files that have duplicates across the files) -- the records will not be deduped on the custom object if multiple imports are pushed at the same time. Issue If you are using a Bulk Custom Object Import API third party service to push records to a custom object (and multiple files, containing duplicates across those files are being imported to the Marketo custom object in a similar time window) -- the records will not be deduped on the custom object, even if the dedupe field value is matched. This is because two concurrent imports can be processed at the same time if they are pushed close together. More information can be found here. "A maximum of 2 jobs are processed at the same time. A maximum of 10 jobs are allowed in the queue at any given time (including the 2 currently being processed)." Solution In this scenario, the third-party App/API service provider that is making the bulk import calls must be consulted to ensure that separate files containing duplicate records aren't being imported to a Custom Object at the same time (or close together times). Once the calls are spaced out adequately so there aren't concurrent imports running containing duplicate records in separate import files, the custom object will dedupe as expected based on the designated dedupe fields. More on dedupe fields can be found here: "Dedupe fields can be used to retrieve, update, or delete custom objects. Every custom object definition must contain at least one (and no more than three) dedupe fields." In Summary, while Marketo does deduplicate on custom object records at import based on the dedupe field(s), it cannot dedupe when concurrent imports are being processed at the same time with duplicates in the separate files (for example: file 1 has dupe A while file 2 has dupe B). If all the duplicates are in the same file, however, Marketo can dedupe within that file as its imported to the custom object. Root Cause Concurrent Custom Object imports running at the same time: when this occurs, the two files being imported concurrently don't have time to check against each other to dedupe based on the configured dedupe field.

Issue Program member custom fields are not syncing data to Salesforce campaign member fields even though they are mapped. In this setup, the sync for Campaign Members is being performed by 'Add to SFDC Campaign' or 'Change Status in SFDC' flow-steps, but the Program itself is not set to sync with an SFDC Campaign. Environment SFDC Integration Solution This is the expected behavior, as the program member custom fields will only sync data to campaign member fields when the Salesforce Campaign Sync is setup for the Instance/Program in question. Using flow steps to sync SFDC Campaign Members will not carry over data for Program Member Custom Fields. Root Cause SFDC Campaign Sync is not enabled. Enable/Disable Campaign Sync Enable/Disable Campaign Sync | Adobe Marketo Engage Program Member Custom Field Sync Program Member Custom Field Sync | Adobe Marketo Engage

Summary Aggregating/summing two score fields Issue You have two new score fields (for example: 'Implicit score' and 'explicit score') and you're wondering if there's a way to sum/aggregate these scores together for all records within Marketo. Solution To aggregate different score values together within Marketo, you should first create a third 'sum' field meant to capture the aggregate of the two scores. (Example: 'sum score') Now, we have 3 scores: Explicit Score, Implicit Score, and a Sum Score SOLUTION First, setup the scoring smart campaigns for implicit and explicit score as you normally would. Once those scoring programs are setup, add the sum score field to the flow of each respective campaign, increasing that score by the same interval that you increase the implicit or explicit score by. This should allow the scores to aggregate over time. Example 1 "Implicit Scoring campaign: Trigger: Visits web page 'x' Flow: 1. Change Score [Implicit score] Change: +5 2. Change Score [Sum score] Change: +5 Explicit Scoring campaign: Trigger: Fills out form 'y' Flow: 1. Change Score [Explicit score] Change +10 2. Change Score [Sum score] Change +10 Final result if a record runs through both campaigns > Implicit score: 5, Explicit score: 10, Sum score: 15" In the above example, the sum score flow step is simply added to each respective explicit/implicit scoring campaign, with the same change interval applied. Once applied to all relevant scoring programs in the instance, the sum score should continue aggregating the two scores into the sum score field. If you're increasing both explicit and implicit scores within one campaign instead of separating out by score type, you could also accomplish this with the same logic and instead adding the summed score interval within that same flow, for example: Example 2 "Scoring campaign: Trigger: Person is created Flow: 1. Change Score [Implicit score] Change: +3 2. Change Score [Explicit score] Change: +4 3. Change Score [Sum score] Change: +7 Result > Implicit: 3, Explicit: 4, Sum: 7" -------------------------------------------------------------------- Potential Alternative solutions: 1. Have your SFDC/CRM Admin create a workflow within the CRM which sums the two fields as they sync. This requires the score fields in question to be synced to the CRM. 2. Call a webhook, which will keep the aggregate in line with the individuals each time it's called. This would be a custom webhook implementation that Support cannot assist with. Sources for alternative solutions: How to sum Lead Scores in one aggregate score field Add two Scores in Marketo

Summary Mismatch between "Added to [custom object]" and "Has [custom object]" filters for a SFDC Custom object Issue You build a Smart List for "Added to [custom object]" for your SFDC Custom object and you notice the number of records qualifying is lower than expected. The "Has [custom object]" filter pulls more records, however, and matches what you see in SFDC. Environment SFDC/Marketo Solution This is expected behavior if you have records that were already associated to the SFDC Custom object before they were pushed to Marketo. If you have records that were already associated to the SFDC Custom object before they initially synced to Marketo, those records would not have an "Added to [SFDC Custom Object]" activity on their record in Marketo, which means they would not qualify for the "Was added to [SFDC Custom Object] Smart List filter" In this scenario, it is recommended to use the "Has [SFDC Custom Object]" filter to get the accurate numbers, as this should include all Marketo records that are associated to the Custom Object, even if they were added to it prior to being synced and created in Marketo. Root Cause Records already being associated to the SFDC Custom object before they were initially synced to Marketo.

Summary Customers may face errors referencing Segmentations when importing programs between instances. Issue Program import fails giving an error message like the example below: "Marketo encountered an error while importing Nurture Program: EXAMPLE - Acquisition NUR B2B [SMB] FY24 - TEST Why: The Segmentation_Type_1003 field exists in the following objects: Person What to do now: Create a field named Segmentation_Type_1003 in the Person object." Environment Marketing Activities Import Program Solution The simplest solution would be to temporarily remove the Segmentation references from the child assets (Smart Campaigns, Smart Lists, etc.) that currently exist in the importing Program within the source instance. Once the import succeeds, references to the Segmentations can be re-added to the source (as well as the destination, if needed) instance's Program's assets.

Issue When trying to clone a Form or Landing page from Design Studio to a specific Program under Marketing Activities, there is no list of programs that appear. Solution This is expected behavior. When you don't see a program listed, this is because the number of programs in Marketing Activities actually exceeds what we're able to display at one time. If you start typing into the Program field in the pop-up window, you should start to see programs listed in the drop-down. For example, you enter the name of the particular program, you will get a result.

Summary UTM Parameters Not Populating with Known People Form Fill Issue UTM parameter field values are not being captured for some people's form submissions, even though the form is configured to capture the values. Solution When a form is using the "Show Custom HTML Form for Known People", the submission button will generate a Filled out Form activity, but will not write any new field values. When attempting to capture UTM parameters with the feature enabled, those UTM values, as well as the other fields on that form, will not be captured. Show Custom HTML Form for Known People | Adobe Marketo Engage

Issue You receive a notification that the Marketo/SFDC sync has failed due to " Invalid username, password, security token; or user locked out." On the Salesforce side, you see the error "Salesforce setCredential failed with code: {LOGIN_DURING_RESTRICTED_DOMAIN} and message: {cannot log in from current domain}" Solution Take the following steps to troubleshoot this issue: Confirm that the username and password are correct by using them to log into Salesforce. Check to make sure the Marketo IPs are on the Salesforce general whitelist. Check the Marketo sync user's profile in Salesforce and make sure the "Login IPs" include the IPs for your Marketo instance. The complete list of IP ranges is: 199.15.212.0/23 199.15.214.0/23 192.28.144.0/23 192.28.146.0/23 192.28.148.0/23 192.28.150.0/23 192.28.152.0/21 192.28.160.0/19 185.28.196.0/22 103.237.104.0/23 103.237.106.0/23 Who This Solution Applies To Customers integrated with Salesforce using IP restrictions

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Why Do I See Workspace Partition While Selecting Munchkin?

What to Expect if Your Language Preference Differs from the Default

Two SFDC Picklist Fields Mapped to One Marketo Field Aren’t Showing All Picklist Values in Marketo

How to Find Your Munchkin ID for a Marketo Instance

Deleting Marketo Custom Object Record Data

Common SPF Errors and Fixes

Changing Landing Page and Tracking Link Domain

Can We Customize User Roles Specific to Certain Programs or Assets?

Company Fields Appear in Lead Object "Describe" API Call

Reporting on Merge Activities

Bulk Custom Object Import API: records not deduping when being added to a custom object

How to Add an Additional Domain for Predictive Content

Program Member Custom Field Data Not Syncing To SFDC Campaign Members

Aggregating Two Score Fields

Mismatch between "Added to [custom object]" and "Has [custom object]" filters

Error During Program Import

How to Change the Display Name of Your Marketo Instance

Unable to Clone form from Design Studio into Marketing Activities

UTM Parameters Not Populating on Form Submission with Show Custom HTML for Known People Enabled

SFDC Sync Error - Salesforce setCredential failed with code: {LOGIN_DURING_RESTRICTED_DOMAIN}