Your Achievements

0% to

Next /

to gain points, level up, and earn exciting badges like the new !

View All Badges

Open Alert Bar

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

Featured article

(Article Updated - August 2024) Overview A blocklist is a database of IP addresses or domains that have been associated with the sending of unsolicited commercial email or spam. Internet Service Providers (ISPs) and business email networks use information from blocklists to filter out unwanted email. As a result there can be a drop to inbox delivery rates if the IPs or domains involved with sending email are listed on a blocklist. Marketo’s Email Delivery and Compliance team monitors blocklist activity on our IPs and domains daily. When an impactful listing occurs, we reach out to the blocklist, attempt to identify the sender that triggered it, and work with the blocklist organization to get the listing resolved. There are thousands of blocklists, most will not have a significant impact on your delivery rates. Below, we have compiled a list of the blocklists that commonly appear across our sender ecosystem. Each blocklist has been grouped into a top tier (Tier I) by most impactful, to the bottom least impactful tier (Tier III). These may have little to no impact across our sender network. Tier I Blocklist Spamhaus (SBL) Impact: Spamhaus is the only blocklist that we categorize as a Tier I for a reason: it has by far the greatest impact on delivery. It is the most well-respected and widely used blocklist in the world. A listing at Spamhaus will have a negative effect on your ability to deliver emails to your customer’s inbox and can cause bounce rates of over 50%. Evidence suggests that most of the top North American ISPs use Spamhaus to inform blocking decisions. How it works: Unlike many blocklists, Spamhaus lists senders manually. This means they are proactively watching sender activity, collecting data, and base listings on a number of variables. Most commonly senders are listed for mailing to spam trap addresses that Spamhaus owns. Sometimes Spamhaus will list senders based on recipient feedback as well. Next Steps: Please note that every Spamhaus email can be quite different depending on the information provided and the nature of the listing . Because Spamhaus has multiple types of listings, the remediation steps are based on which type of blocklisting has occurred. We have listed the most common types to affect Marketo customers, from most to least impactful. Impact can range from a full block of top severity, to a partial block that is less severe (CSS Data, DBL). If remediation isn’t performed and the problem not addressed, these listings can increase in severity and turn into a full blocklisting. Spamhaus Blocklistings Types SBL (full blocklisting) Considered the most impactful. Remediation steps: Our team monitors closely for Spamhaus listings. Once alerted to the listing, we send an email notifying the customer, and reach out to the Spamhaus contact to start the remediation process. Only a Marketo delivery team member should be in direct correspondence with the Spamhaus contact, to speak on behalf of the customer, and to relay their questions and instructions, ensuring quick resolution and reduced impact. Senders that trigger this listing on a shared IP range will be moved to a more isolated, penalty range (IPB), so as not to impact the other shared senders. Those affected on a Dedicated IP, only impact their own sending and will not be moved. However, depending on the severity of the issue, our team may need to revoke a customer’s ability to send any emails until full resolution. The listing will last until Spamhaus is satisfied that the offending sender has taken the appropriate steps to mitigate the problem. SBL CSS Customers are alerted of the listing with an email containing all the information needed to immediately begin the remediation process. This is part of an automated trigger listing, that allows for a customer to delist directly on the Spamhaus website, after they’ve completed remediation. Remediation steps: Customers will go to the Spamhaus IP lookup website, at https://check.spamhaus.org, where they can check on the status of their IP and continue to monitor it in real time, until it is no longer listed there. Follow the remediation and delisting instructions provided, and check for specific details in the blocklist notification email. DBL (Domain blocklisting) Customers will receive an email notification alerting of the company domain being listed. The email will contain specific information to help narrow down and identify which email source likely triggered it within Marketo. It’s important to note that any email sent from outside of Marketo, that contained the company domain, is suspect. This means, if the sender uses multiple IPs and/multiple email platforms, then any of those could be the source. Remediation steps: Follow the detailed instructions in the email, which will also provide a link to the Spamhaus Domain reputation checker webpage, to check the real time listing status of the affected domain. Once the email source is identified and cause addressed, this customer will follow the online instructions to request to be delisted. Tier II Blocklist SpamCop Impact: SpamCop is not used by any of the major North American ISPs to inform blocking decisions, but it makes it to the Tier II list because it can have a significant impact on B2B email campaigns. SpamCop is considered a Tier I one blocklist for B2B marketers but a Tier II for B2C marketers. SpamCop is a dynamic IP blocklist, that can affect a single IP or a subset of IPs Typically, the block will automatically lift within one business day, but can take longer for relisted IPs. To have triggered a SpamCop listing likely means the sender has a list management problem that should be addressed. How it works: SpamCop lists IPs for one of two reasons: Either the email hit SpamCop spam trap addresses OR A SpamCop user has reported the email unwanted. Most of SpamCop’s spam traps are previously valid addresses that have not been active for 12 months or longer. Remediation steps: If you are seeing a significant number of bouncing emails caused by a SpamCop blocked IP but aren’t sure if your email activity triggered the listing, first identify whether you are sending on a shared sender network or not. If sending from a shared IP range when this occurs, you or any other customer sending from the same network may have contributed to the IP block. This IP block will automatically get dropped within a business day. For those on a Dedicated IP that trigger a listing, refer to the above remediation steps and resources, to address the list management issue. Tier III Blocklist (Low/ No impact ) These are considered the lowest tier and therefore cause the least impact across the Marketo sender ecosystem. Some of these blocklists were more impactful at one time, while others are only impactful based on the sender region (Manitu). Others still can suddenly flare up (Lashback). There are also many blocklists that are ignored (0spam), and are not taken seriously because they do not provide any means to delist once on the list (NoSolicitado) or that they charge money to have the listing removed ( UCEPROTECT ). The pay-to-delist model is not well respected in the email industry. When using blocklist tool checkers, such as MXToolBox, many blocklists will appear, but very few are relevant. Here is our selection of Blocklists you may come across that are least impactful: Project Honey Pot SpamAssassin URIBL/SURBL DrMX PSBL 0spam HostKarma Ascams ZapBL Barracuda Trendmicro Inc. Cloudmark Proofpoint Invaluement ISP Blocklists Some ISPs use internal blocklists to make blocking decisions. Examples include AOL, Yahoo, Gmail, Outlook and Hotmail. If your IP is being blocked by one of these networks, and those networks have a large presence in your lists, a block of this kind could have a noticeable negative impact on delivery. Marketo monitors for significant ISP blocks. Those experiencing deliverability issues with emails not making it to the Inbox and bulking in the spam folder may benefit from additional services with our Email Delivery Consultants. Remediation Steps: Email Delivery Compliance Team works to resolve any ISP blocks. ISP blocks are are usually resolved or lifted within less than 24 hours of a delisting request. Customers experiencing significant blocks for Microsoft domains (outlook.com, live.com, microsoft.com), can submit a request to the delivery team to seek mitigation on their behalf. Additional Resources: Blocklist Deep Dive Abuse Report Deep Dive What is a spamtrap, or spam trap, and why does it matter? Blocklist remediation Blocklist resolution flowchart Successful lead reconfirmation What is a blocklist?

Issue URLs generated by a Velocity script token are not tracking when a person clicks on the link in an email Solution Velocity scripting enforces strict formatting of links in order for them to be tracked: or must be included in the URL. If using a variable, the or must be output outside of the variable. The URL must be part of a fully formed <a> tag. No other type of link tag will work Links must not be outputted from within a for or foreach loop To ensure links are tracked properly, set the entire path inside a variable and then print the variable. Correct: #set($url = "www.example.com/${object.id}") <a href="http://${url}">Link Text</a> Correct: <a href="http://www.example.com/${object.id}">Link Text</a> Incorrect: <a href="${url}">Link Text</a> (missing http/https) <a href="{{my.link}}">Link Text</a> (missing http/htpps, cannot reference an outside my.token) <page xlink:type="simple" xlink:href="https://www.example.com">Click me</page> (must use an <a> tag)

Issue Issue Description How to Pull Data for Program ID, similarly to Campaign ID. (Example): Pull Individual Program Activity Data, then join Data with Programs via Program ID. Solution Issue Resolution [Note]: You can not get the Program directly from the Activity Endpoint. - After one has obtained the Smart Campaign ID, they can use a seperate API Call to get the Program ID. - Within the Get Activity API Call, there will be a Campaign ID. - Once this has been obtained, one can make a Get Campaign API Call with that Campaign ID and it will return the Program ID. [Get Activity]: > Use this [Get Activity - URL] to Obtain Campaign ID. developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Activities/getLeadActivitiesUsingGET [Get Campaign, with the ID]: > Use this [Get Campaign, with the ID - URL] to Obtain Program ID. developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Campaigns/getCampaignsUsingGET The Program ID is not something that is returned in an Activity Call. The above method is the quickest possible way to obtain that information. Who This Solution Applies To API Users Updated Links Activity API https://developers.marketo.com/rest-api/lead-database/activities/ Swagger: https://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getLeadActivitiesUsingGET Get Campaign By ID https://developers.marketo.com/rest-api/assets/smart-campaigns/#by_id Swagger: https://developers.marketo.com/rest-api/endpoint-reference/asset-endpoint-reference/#!/Smart_Campaigns/getSmartCampaignByIdUsingGET

Issue Issue Description Person appears to have changed Segment, but there is no activity for that 'Change Segment' recorded in the Activity Log. Segmentation was not recently re-approved, so this would not account for the behavior we are seeing in other circumstances. Segmentations Not Writing Change Activities However, the record was recently converted from a Lead to a Contact in the CRM. Solution Issue Resolution Upon Lead conversion to Contact in Salesforce, an "initial" segmentation process for that Contact is computed. During these "initial" segmentation computations, in a manner similar to when a person is initially created in Marketo, no activity is recorded in the record's Activity Log.

Issue Issue Description When linking Google AdWords account to a Marketo Revenue Model and adding the Google Adwords conversion in the Revenue Model, Set AdWords Conversion button is missing from the Stage Actions drop down. Solution Issue Resolution You need to add Google AdWords as a Launchpoint service with a manager account Add Google AdWords as a Launchpoint Service with a Manager Account - Marketo Docs - Product Documentation

Issue Issue Description Under Web Services > IP Restrictions, you would like to add a lot of IP addresses to whitelist for IP-based API access. The steps are described here: docs.marketo.com/display/public/DOCS/Create+a+Whitelist+for+IP-Based+API+Access Solution Issue Resolution Even though this is not mentioned in the doc, there is a character limit for the string value. The limit is 2,000. However, the way it is stored in the backend is a bit different from UI. Therefore, it is possible that you have exceeded the limit even though it doesn't look like so.

Summary When submitting a file for bulk import via the REST API, the uploads appears to stall with no response. Issue Occasionally Bulk Import API calls will "hang" or "stall" never returning a response. This may appear to be a blank or missing response when the API is actually still waiting for the end of the file to be transferred. Solution You can add the following header: 'Transfer-Encoding: chunked' to your API calls and it will fix this issue. Please note that adding this header on the client side will cause cURL to send data in chunks. For more information on chunked file transfer, see Wikipedia: Chunked Transfer Encoding Environment REST API Bulk Import

Issue: When building 'Program Membership Analysis' reports in RCE, the Program Status is not sorted according to the step values in the Program Channel. For example in the below screenshot: The value of the steps are clearly showing the progression of statuses from start to finish. However when building a 'Program Membership Analysis' report, it is showing that the order of the status is not correct. 'New Member (Influenced)' should be appearing after 'Subscribed by Form - Non Member.' Troubleshooting: Make sure that you do not have any other Programs Channels with the same Status, as this will cause issues. There is a deduplication that occurs in the backend which causes an issue when a 'Program Membership Analysis' report is created, if there is more than one Program Channel that has the same Program Status it will deduplicate and the one displayed might be due to the lower step. Another issue that might happen also due to having more than one occurance of Program Status in other Program Channels is that other Program Statuses might appear in the report due to this. Resolution: We currently do not support having more than one Program Status appear in the Program Channels, each Program Status has to be unqiue or issues with displaying Program Statuses will appear.

Issue Issue Description \Zoom connector registrants who register directly in Zoom are not being passed to the connected Event Program in Marketo Solution Issue Resolution The Zoom integration does allow for registrants that registered directly from Zoom to be passed to Marketo. The following document shows the process of setting the registrant push from Zoom to Marketo. The documentation is showing the setting at the account level, however this also needs to be done at the Webinar level. support.zoom.us/hc/en-us/articles/207267346-Setting-Up-Zoom-for-Marketo

Issue Issue Description You would like to update My Token values from the Request Trigger Campaigns endpoint, but are unsure of why My Token types can be updated. Solution Issue Resolution The following My Token types can be updated from the Request Trigger Campaigns endpoint: Date Image Number Rich Text Score Text An example of a JSON body in the POST request may look like: { "input": { "leads" : [ { "id" : 1 } ], "tokens" : [ { "name": "{{my.DateToken}}", "value": "10/16/2020" }, { "name": "{{my.EmailScriptToken}}", "value": "{$lead.country}" }, { "name": "{{my.ImageToken}}", "value": "https://www.marketo.com/" }, { "name": "{{my.NumberToken}}", "value": 222 }, { "name": "{{my.RichTextToken}}", "value": "<strong>Hello World!</strong>" }, { "name": "{{my.ScoreToken}}", "value": -10 }, { "name": "{{my.TextToken}}", "value": "Hello World!" } ] } }

Issue Issue Description You are unable to log into multiple instances at one time so you spend time switching between instances frequently. Solution Issue Resolution Chrome profiles can be used to log into multiple instances at the same time on the same computer in different chrome windows. Rather than logging out then logging into additional instances, you can simply switch between windows. Setup: Here is a 1 minute video that walks through the setup process: embed.vidyard.com/share/kpx65nDnwivFuRPyktmJgW? If you have not logged into google chrome: Click the main menu in the upper right corner Click Settings (or navigate to chrome://settings/) Under the people section click Add person Choose an avatar and give your profile a name If you have already logged into Google Chrome: Click your profile icon in the upper right corner of google chrome (next to the main menu button) Click Manage People Click Add Person Choose an avatar and give your profile a name. To access the profiles when you open chrome you can click your profile icon in the upper right corner of chrome then click the name of the profile you wish to access, this should open a new window you can use to log into Marketo.

Issue Issue Description After submitting a form on a landing page, the Thank-you page fails to load, or it loads the wrong page. Solution Issue Resolution The Thank-you page used by the form can be defined in two places, at the Form level and at the Landing Page level. If these two are in conflict, the setting on the Landing Page wins. To troubleshoot this issue, compare the two Thank-you options and make sure the Landing Page is either set to the correct page, or that it allows the Thank-you to be form-defined.

Issue Issue Description User has 'Import List' permission in Marketing Activities and Database but is unable to import a list. The Limited Access message below is being returned: "You do not have sufficient privileges to perform this action" Solution Issue Resolution In order for a user to have permission to import a list in Marketing Activities and Database, the user would need to also have the 'Edit Person' permission. see article for list of permissions: docs.marketo.com/display/public/DOCS/Descriptions+of+Role+Permissions

Issue Issue Description An email with inserted bold/italic font in email subject line is not approving, with an error of "Cannot Update Stale Object," or does approve but the special font text disappears upon approval. Solution Issue Resolution The subject line in an email is intended to be plain text. Some have found success inserting basic symbols, or even emoji with specific encoding, though the rendering of these characters is dependent on the receiving server. Related: Using Emojis in Marketo Emails

Issue Issue Description You want to invite one user to your two (or more) Marketo instances. Solution Issue Resolution All Marketo subscriptions come with the optional Universal ID feature. To setup users with the same "login" in both production and sandbox subscriptions (or Prod and Prod, or Sandbox and Sandbox) we will want to take these steps: 1. Create a new user in the "1st instance" (first is arbitrary, it is whichever instance you want to start with, and if a user already exists in this instance you can jump to step 3) 2. User is created: lets say for example the user "login" is: demouser@adobe.com with "email": user@adobe.com and password: 12345GoodPassword 3. We will then want to go into the second instance and invite a user with the same "login": demouser@adobe.com (you can use a different email or the same) 4. When that user receives the second invite they will want to set their password to be exactly the same as the password in the first instance: 12345GoodPassword Please note: If after following these steps you want to reset your password, you can do so and would want to do so for both instances. To do so, you would want to input your "Login" after selecting the forgot password option. That will initiate the sending of an email to the email address you specified as your "email". Who This Solution Applies To Marketo Users with Universal ID active

Issue Issue Description Marketo Secured Landing Page using domain aliases give an invalid SSL certificate error on load. Solution Issue Resolution Confirm that the domain alias is a CNAME and not another type of record such as an A RECORD. Within Marketo's Documentation for setting up landing pages and tracking links, it only specifies a CNAME configuration. This is the only configuration that is supported. If another configuration happens to work, it does not mean it will continue to do so and will throw an error once SSL is enabled. Below is a diagram showing the configuration that is supported by Marketo. The Top Level Domain is owned and hosted by the Customer. Separate sub-domains, or CNAMEs, are created, one for each Landing Pages and Tracking Links. These CNAMEs then reference Marketo. Other ways of configuring this are not supported due to not being reliable. An A RECORD for example, can point a Domain directly to an IP Address. This can be unreliable because an IP Address can easily and frequently change. As a Domain name is usually synonymous with a Company name, any change is infrequent and usually manual. *Tracking Links only require a sub-domain and SSL if you wish to have them branded. If instance reflects the 'mkto.aa######.com' for tracking links, they are covered under Marketos SSL certificate. Who This Solution Applies To Customers with Secured Landing Pages who also use domain aliases

Issue Issue Description Certain fields that are in your Facebook Lead Ad forms are not populating on the lead when it is created in Marketo. Solution Issue Resolution 1.) Check the Activity Details of the “Fill Out Facebook Lead Ad” activities to see if there are any unmapped form fields included with the standard Lead Ad data fields. Unmapped form fields will show up with the field name on the left, and value on the right. Note that the other Lead Ad standard fields are not actually on the form. This is because these are default metadata fields created by the integration. 2. )Navigate to Admin > LaunchPoint and update your Facebook Lead Ad service to map that field to a Marketo field, so the data can populate over. Instructions for doing so can be found here: Map Custom Fields to Marketo - Marketo Docs - Product Documentation Who This Solution Applies To Customers with a Facebook Lead Ad integration

Issue Issue Description Not receiving device authorization email when attempting to login from a new device or from a new location the system. Solution Issue Resolution The main reason that this can happen is due to a typo in the email address that communication is sent to for your login. If you are not receiving the device authorization email, reach out to Marketo support by emailing support@marketo.com and we can manually authorize your device or location. To prevent this behavior from continuing to take place we recommend you do the following: After you've gained entry into the Marketo instance, we recommend you visit Admin > Users & Roles and confirm that the email address listed is spelled correctly. Validate with your IT team to ensure that Marketo is whitelisted using these IP addresses: Whitelist Marketo IPs

Issue Leads were sent the email and clicked on a web page link on the email. However, the web page activities were not associated to these leads. Solution Issue Resolution Check that the link clicked in the email has tracked link enabled If the web page activities are associated to other records (e.g. duplicates), then: Check who was 'cookied' on the web browser before the visit web page activity was recorded for the other records. This can be checked by looking at the web page activities recorded in the activity log. Check the User Agent details of the Click Link activity of the lead that was sent the email and compare it with the User Agent details of the Web Page Visit activity of the other record. The following tool can be used to help interpret the device details from the User Agent details: developers.whatismybrowser.com/useragents/parse/#parse-useragent In case of a non marketo landing page , check whether the munchkin is enabled correctly over the page without any customization. Reference Doc :- Munchkin Tracking

Issue Why does the record in Marketo have an Opportunity when its matching synced Contact in Salesforce does not have an Opportunity? Solution The Contact in Salesforce has an Opportunity Contact Role associated with an Opportunity that belongs to other Contacts. Since "Marketo associates Opportunities and contacts using Opportunity Contact Roles.", Marketo syncs down the Opportunity for the record has it has an Opportunity Contact Role associated with it.experienceleague.adobe.com/docs/marketo/using/product-docs/crm-sync/salesforce-sync/sfdc-sync-details/sfdc-sync-opportunity-sync.html?lang=en If the Opportunity is needed to be removed from the record in Marketo, then: The Opportunity will first need to be deleted in SFDC. The visibility of the role value that is not the primary owner of the Opportunities will need to be removed from the Marketo Sync User. Re-create the Opportunity so that it can be associated to the primary owner. Who This Solution Applies To Customers who has Salesforce integrated to Marketo

Issue You may want to know which Salesforce fields a specific Marketo field is tied to as shown in this document. You will be able to see that the mappings are either not update or a few fields are missing that were created recently. Solution The Field Mapping that you are seeing under Admin -> Salesforce, as well as the mappings included on that export, are a historical log of how the mappings were set when the SFDC integration was originally implemented. Unfortunately, that page does not refresh when new fields are added, or when mappings are changed. We don't have any other tool that would allow us to export all of the field mappings in your instance as they are currently set either, so the best workaround for this is to check each of your fields within Admin -> Field Management. There is an idea in the Marketo Community specifically asking for this feature to be added and we would recommend that you add your vote to that so our product team sees that there is interest in getting this functionality added to Marketo in a future release.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

URLs in Email Script Token Not Tracking

How to Use Campaign ID to obtain Program ID with API Calls

Change Segment Activity Missing For Recently Converted Contact

Set AdWords Conversion button is missing from Stage Actions drop down

The max number of the IP addresses to add to API whitelist

Bulk Import API Calls Returning Blank Responses

Program Status in RCE not sorted the same way as setup in Program Channel

Zoom Webinar Registrants not passing to Marketo

Using REST API Request Trigger Campaigns endpoint to update My Token values

Log into Multiple Instances with Chrome Profiles

Correct Thank-You Page Does Not Load After Form Submission

User Unable to Import a List in Marketing Activities and Database

Bold/Italic Font in Email Subject Line Gives Error or Does Not Render

Inviting Marketo Users to Two Instances with Universal ID (UID)

Secured Landing Page Aliases Giving SSL Certificate Invalid Error

Custom Facebook Lead Ad Fields are not Populating in Marketo

Not Receiving Device Authorization Emails

Web Page Activities Not Associated to Leads after Clicking Link in Email

Record has Opportunity in Marketo but not in Salesforce

Fields missing from the field mapping section of the instance