Knowledgebase

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 Data in Email Performance Report does not match with data in Email Insights Solution Email Insights does not update in real time and can take up to 24 hours to reflect data. Check if the email is an Operational email, sent via a batch campaign or Trigger campaign. In Email insights, by default, the email communications only show Batch campaign and not Operational Emails or email sent by Trigger campaign. To show operational email and emails sent by Trigger campaign, Click on the Gear icon on the top right corner Select Personal Check Email communication to include Operational Emails and Trigger. This will display the data as per your Email Performance Report. If there are discrepancies even after changing the settings, create a support ticket as a data back-fill may need to be performed.

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. http://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. http://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 When you go to schedule a Smart Campaign, the Status tab says it is "set to affect about N/A people" instead of showing the actual number of leads that should go through the campaign. Solution There are two probable causes for this There is an error in the Smart List. If the Smart List references another nested Smart List, the error may be in the secondary Smart List, so you may need to drill down when you check this. The Smart Campaign has a Smart List in it with the same name. For example, if the Smart Campaign were named "EMEA Networking" but it also contained a Smart List named "EMEA Networking", it would cause the list processor to give this error. Making one of the names slightly different - "EMEA Networking Smart List" - should resolve this issue. If you have tried both options and are still unable to get the affected leads count to resolve, please contact Marketo Support with the results of the above troubleshooting and we will investigate further.

Once you have the RTP tag installed onto your website, there are several steps that RTP goes through to actually display a Campaign on the web page. Below we describe the process from the tag being loaded to the Campaign being shown on the page. Beware, the details are somewhat technical, so tread with caution! When the page with the RTP tag is loaded, the RTP script (rtp.js) is loaded. This script includes all of your individual tag configurations, and it triggers a sequence of actions: First, information about the visitor is sent to the Marketo servers, including: Referral site Search terms and the visitor's IP address. Using this IP address, several things about the visitor can be deduced relatively accurately: Location (country, state, city, zip code) Organization name (if applicable) Organization group (Enterprise, SMB, Fortune 100, etc.) If the visitor is a known lead in your Marketo lead database, RTP will pull values for all of the default Marketo fields and custom fields. Next, RTP will check if the visitor qualifies for any of your pre-defined Segments based on this information about the visitor. If the visitor does match a Segment that's attached to a Campaign, that Campaign will be loaded on the page being visited. Finally, once the Campaign has loaded on the page, the visitor's browser takes note that the visitor has seen the campaign. This allows for Campaigns that are not sticky to be only loaded once per visitor.

Technically, you cannot move records backwards in a progression status. The only so called “backward” status that you can change the record to is a progression status of “Not In Program”; however, doing this removes them from the membership of the program. If you do this procedure, this will allow you to re-add them with a different status. We mentioned technically this cannot be done but logically, there is another method that allows you to juggle the record’s progression status but in a more lateral movement with what appears to be in a “backward” state. This is all dependent on how you have your channel steps configured. To access your channel steps, please do the following: Choose Admin Choose Tags Click the + next to Channel Locate the channel you wish to configure and highlight it Click the drop-down menu towards the top of Tag Actions, and select Edit You should now see a pop-up window that allows you to configure the status steps for that channel like the following example: This is a article attached image If you configure statuses that have the same step number, this will allow you to move the record in a lateral movement which, in a sense, is somewhat like a backward progression but it really isn't. With the example screen capture, I can do a change in progression status of “Invited” to “Attended Show” and vice-versa because the step is with an identical number. If I wanted to change in progression status of “Invited” to “Engaged” and back, it will not work because the step value is not identical. You can reference more information about this in the Create a Program Channel article.

Your Salesforce sync is not working because the password for your Salesforce sync user expired. You may see an error in Marketo saying: "describeSObject failed - The users password has expired, you must call SetPassword before attempting any other API operations." Similar to this: To resolve this error, you will have to change both your password and security token in Salesforce and then update these credentials in Marketo under Admin -> Salesforce -> Edit Credentials -> update both your password and security token in the 2 boxes illustrated below then press the Save button: To permanently fix this issue, you will need to change the password policies in Salesforce so that your password never expires in Salesforce. To do this, in Salesforce, go to Setup -> Administration Setup -> Security Controls -> Password Policies -> User passwords expire in -> Never expires -> Save for your "your_sync_user@domain.com" user in Salesforce: Please note this is a Salesforce setting and you should consult your Salesforce Admin before implementing this change Whenever the Salesforce user password expires (it periodically expires for security reason), Marketo stops syncing with the Salesforce account. As a result, any of the leads created in Marketo during this down-time won't be synced to Salesforce. Marketo will not automatically re-sync. Once you have reset your password and the API calls work once more, you can create a batch campaign that will sync the new leads that have been created in Marketo to Saleforce.

Issue: You've changed the color of the label for your form to white, but because of the background of the form matches the input color you can no longer see information as the form is filled out. Solution: Change the font color of just the input values. Add the following style to a custom HTML block in the landing editor. Depending on what types of fields you have in your form all or some of the lines will apply. This changes the font on the input fields black , for the case of the labels being set to white(for example) <style> form.lpeRegForm ul select { color: black; } form.lpeRegForm ul textarea { color: black; } form.lpeRegForm ul input[type="text"] { color: black; } </style>

Complete these Marketo Quick Wins from the User Manual (Help Articles) to learn the core features of Marketo! 1. Get Set Up and Add a Lead 2. Send an Email 3. Landing Page with a Form 4. Simple Scoring 5. Email Auto Response 6. Import a List of Leads 7. Drip Drip Nurture 8. Personalize an Email 9. Alert the Sales Rep 10. Update Lead Data To run through some more activity and exercises that are guaranteed to show you more of how to use core functions in Marketo, check out the Learning Exercises from the User Manual for details

Issue Description You are receiving this error from your GoToWebinar Launchpoint Service: API Error: Authentication succeeded, but access to the requested resource is denied. This error can occur either in Launchpoint Tab's Service details in Admin or when trying to Refresh an Event Program and selecting the service in the drop down menu. Issue Resolution This error "API Error: Authentication succeeded, but access to the requested resource is denied." is a response from GoToWebinar when Marketo sends an API Call to retrieve the Webinar Meeting details. What is the main cause of this? This is mainly a licensing issue with the Account Credentials specified in the Launchpoint service. The GoToWebinar account does not have a GoToWebinar License and therefore, the account has successfully "Authenticated" and the Requested resource (GoToWebinar Meeting Details) were denied as it does not have access to GoToWebinar features. How to check if you have a license? Login into the home page of GoToWebinar with the account credentials used in the Launchpoint Service and check if GoToWebinar Product is selectable. (if GTW is not selectable then the account does not have a product license) Speak to your GoToWebinar Account Admin if you are using a corporate account and ensure that it has a GoToWebinar License. Contact the GoToWebinar's Support Team Other Causes Other reasons this may have occurred is that a Trial account for GoToWebinar was used and the trial has expired. You may be using a login under a corporate account that does not have the license or was removed. - Check with your GoToWebinar Admin for more details Who This Solution Applies To GoToWebinar Launchpoint Users Is this article helpful ? YesNo

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 Description The lead's activity log shows that the 'Sync Person to SFDC' flow step failed because of the following message: "Failed: INVALID_CROSS_REFERENCE_KEY: Record Type ID: this ID value isn't valid for the user:" Issue Resolution The issue is the SFDC ID value populated in the "Record Type ID" field is not considered a valid value in Salesforce for the Lead/Contact. You'll want to work with your SFDC Admin to identify a valid value or try deleting the value in Marketo and then updating this value from the Salesforce side. Is this article helpful ? YesNo

Issue Description Person/Lead Source is empty. Why isn't it populating? Issue Resolution Marketo does not automatically assign Person Source. We do populate Original Source Type. Assigning credit for a Lead can only be determined by someone with intimate knowledge of a company's marketing strategies. If someone fills out a form, Marketo doesn't know if they were brought to that form by an email blast, TV commercial, talked to a salesperson, or any number of other reasons. If they came in through a List Import, they could have attended a Tradeshow and signed up there, they could have been exported by a CRM and are being imported, or any number of other ways. There are many discussions on best practices for handling Lead Source attribution in the Community. If you need assistance setting up Smart Campaign to update the Lead Source based on your specific business criteria, please contact Marketo Support. Is this article helpful ? YesNo

Issue You receive the following error: "Ouch! 500 Error Something went wrong. We monitor this sort of thing, but if you are an authorized support contact, you should create a support ticket." Solution This can happen because of temporary network issues. Try out the following troubleshooting steps. 1. Clear Browser Cache 2. Try a different browser 3. Try a different device 4. Try a different internet connect (Hotspot/Tether from mobile) If you still have any issue after trying all these steps, please contact Marketo Support for further assistance.

Issue You are unable to log into Marketo because you need to be authorized on your device. Solution Marketo tracks authorized devices by IP. If you are logging in from a different network, such as a home or hotel network, your IP will be different and you may need to authorize or re-authorize your device. Also, some networks assign IPs dynamically, so even if you are logging in from a location and device you have used before, the IP address may have changed and you would need to re-authorize the device. You should receive an email with a code that allows you to authorize and log in. If for some reason you are not able to do so, please contact support and we can authorize your device for you. Another option would be to disable the IP restrictions in the Admin panel: Admin > Login Settings > Edit IP Restrictions.

Issue What to do if you've exceeded your daily limit of API calls. Solution If you go Admin > Web Services in Marketo, you will see a section called API Call Information. The number next to "Enforced Daily Request Limit" lets you know how many API calls you can make daily. If you need this number to be increased, the best option is to contact your Custom Success Manager; they can help you start the process of increasing your limit.

Summary A service issue has been identified that can potentially cause duplicate leads to be generated in Marketo for customers using Microsoft Dynamics (MSD) CRM. This issue only applies to customers using MSD 2016, and only when upgrading to MSD version 9. Who is Impacted All customers using the native CRM Sync between Marketo and MSD 2016 Already Impacted: Customers using MSD 2016 Version 9 with Marketo Lead Management (MLM) solution version 4.0.0.23 or lower Potentially Impacted: Customers using MSD 2016 version 8 or lower who plan to upgrade to version 9 The issue of duplicate leads being created occurs when the MSD instance is upgraded to version 9 All customers who have already upgraded to MSD v9 are already impacted If you have MSD but have not yet upgraded to v9, you are not yet impacted, but could be by upgrading to MSD v9 Who is Not Impacted Customers using MSD On Premises CRM instances Customers using Dynamics 2011, Dynamics 2013, or Dynamics 2015 Customers with Salesforce CRM When the Service Issue Occurs Qualifying a Lead to a Contact in MSD may not be reflected properly in your Marketo subscription. Expected Behavior: The existing Lead record in Marketo is converted to a Contact record (i.e. the Microsoft Type for the person record should change from Lead to Contact). The existing record in Marketo remains synced to this record in MSD Current Behavior: A new Contact record is created in Marketo to sync with the Contact record in MSD. The existing Lead record in Marketo becomes orphaned (no longer synced with any record in MSD). Additionally, the orphaned Lead record in Marketo contains the activity history while the new Contact record in Marketo contains the contact information Resolution There are two parts to the solution, depending on whether you have already upgraded your MSD 2016 instance to version 9. If you have not yet upgraded your MSD 2016 instance to v9, you will only need the first step. If v9 has already been installed, you will need to perform both. Part One - Install the latest Marketo Lead Management solution A new version of the Marketo Lead Management solution has been released for Dynamics 2016 that prevents duplicate records from being created when upgrading to MSD 2016 v9. This solution must be installed before upgrading to MSD 2016 v9. Installation Process 1. Within your Marketo subscription, you will need to download the latest version of the Marketo Lead Management solution. Documentation on how to download the Marketo Lead Management solution for MSD can be found here: Download the Marketo Lead Management Solution Documentation on how to upgrade the Marketo Lead Management solution for MSD can be found here: Upgrade the Marketo Solution for Microsoft Dynamics NOTE: Microsoft Dynamics has 4 product versions that Marketo supports; Dynamics 2011, Dynamics 2013, Dynamics 2015 and Dynamics 2016. The only product version this applies to is Dynamics 2016. No other product versions are impacted in any way. 2. Install the new Marketo Lead Management solution in your MSD 2016 instance as a normal update. Be sure to install the new solution on top of your existing solution in Microsoft Dynamics as a normal update. Part Two – Correcting Duplicate Records in Marketo This step only applies to customers who have already upgraded to MSD 2016 v9 prior to the new Marketo Lead Management solution being released. This part applies to customers who have had duplicate records created in Marketo. In order to eliminate the duplicate records that were created in error, we must first identify those records. The next step is to merge the two duplicates together. In this scenario, due to both records being synced to MSD, it is a little complicated. Build a Smart List to Identify Duplicates Use the following filters to identify the impacted records: Duplicate Fields > Email Address Microsoft is Deleted > True Microsoft Type > Lead When finished, your Smart List will look like this: This Smart List will identify the duplicate records created by this service issue. When this issue occurs, both of the duplicate records are synced to MSD. It is not possible to merge two records if they are both synced to MSD. However, Marketo Support is able to disconnect the sync of one record on the back end and perform the merge of the two records. Submit a Case with Marketo Support Merging these duplicate records is only possible when done by Marketo’s Engineering team. Contact Marketo Support to open a Support case. Be sure to include all related details, including the link to your Smart List. Marketo Support will evaluate the duplicates and escalate the ticket to our Engineering team. The Engineering team will perform the merge for the records.

To enhance the stability of Marketo’s email assembly infrastructure, we are disabling some Velocity Script functionality on June 14, 2019. What change is being made? The following Velocity Tools will permanently be disabled for use in email script, on June 14, 2019. My Tokens: classTool contextTool resourceTool Some common use examples of these tools include: $class. getClass() $context. When are these changes taking effect? These changes will take effect in the June 2019 Release on June 14, 2019. How did it work before? The way Velocity Tools are used in your email scripts is highly dependent on the structure of your code and varies on a case-by-case basis. To identify how you are currently utilizing Velocity Tools in your email design, please consult directly with your developer. Documentation on each tool can be found on Apache’s website at the links below: classTool : https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ClassTool.html contextTool: https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ContextTool.html resourceTool: https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ResourceTool.html Why is this changing? We regularly review our infrastructure to ensure it meets the highest standards for stability and security. During a recent review, we identified that a small subset of Velocity Tools could potentially impact the health of our message assembly servers, and as a result, we made the decision to disable these permanently. What do I need to do? If you are currently using Velocity Tools in your email scripting, you will need to review and update your script to use alternate methods before June 14, 2019. Documentation on supported Velocity Scripting can be found on our Developers’ site at http://developers.marketo.com/email-scripting/. Any email script tokens still referencing Velocity Tools after the June 14, 2019 deadline could fail to compile, resulting in emails not rendering as expected or complete send failure. We have identified impacted customers using these Velocity Tools and will alert them individually via Marketo Notifications. Considering the customized nature of Velocity Scripting, Marketo Support is not able to assist with the authoring or troubleshooting of custom code. Please reach out to your developer for assistance. If you no longer have access to a technical resource, you may also contact your CSM to coordinate a scoping call with our Professional Services team.

Issue Your SFDC team wants to enable the SFDC feature associating contacts to multiple accounts. Solution If a contact is associated with multiple accounts in SFDC, the Company Name field will contain that primary account name – and Marketo will have no visibility into the fact that the contact is also associated with other accounts. One way to do this in Marketo is actually to create a purposeful duplicate of the contact- one associated with the first account, the other associated with the second account and so on. At this time, there are not any plans to enable people in Marketo to be associated with multiple accounts.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Discrepancies between Email Performance Report and Email Insights

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

Using Tokens in Smart Campaigns

Smart Campaign Status: Set to Affect Around N/A Existing People

RTP - How Does the RTP JavaScript work

Backward Progression Status

Expired Password on Salesforce Sync User

Change the font color of form Field

Marketo Quick Wins

GoToWebinar Launchpoint Service Error: API Error: Authentication succeeded, but access to the requested resource is denied

Changing Landing Page and Tracking Link Domain

Sync Person to SFDC failed

Person/Lead Source is empty

Troubleshooting Ouch! 500 Error

Unable to Log Into Marketo - Device Authorization

SSO Login for CRM Integration User

Raising Your Daily API Limit in Marketo

Microsoft Dynamics 2016 Online Upgrade to Version 9

Unsupported Velocity Tools Disabled in June 2019 Release

Associating Contacts to Multiple Accounts in Salesforce