Knowledgebase

Sort by:
Issue Description You want to use Slack with webhooks to be able to customize the integration a bit more than using it as a Launchpoint service. Issue Resolution We will assume you have already created your App within the Slack API page  we will cover everything after that here. 1) Make sure you are logged in so you can access your App through the Slack API page. 2) Select your App: 3) From here you will want to select the "Incoming Webhooks" from underneath "Features": 4) Use the on/off toggle to the right of the title "Activate Incoming Webhooks" 5) Select the "Add New Webhook to Workspace" button to create a new URL that we will use for our webhook within Marketo: 6) Select where you want to post, either at a specific user or channel: 7) Now we are directed back to the page we were one, hit the copy button next to the Webhook URL to copy the URL as we will need it for a later step. 😎 Login to your Marketo instance and navigate to the Admin section. 9) Select Webhooks 10) Select Create Webhook. For the following fields assign the appropriate values: Webhook Name*        =        What ever you want to name Description                 =        A description of what the webhook is used for URL*                           =        Here is where we paste the URL we copied before Request Type*            =        POST Template                     =       This is the information you want to send to your slack channel/user It should in the following format:                                              payload={"text": "DEVELOPER SITE ALERT: {{lead.First Name:default=edit me}} {{lead.Company:default=edit me}},                                                            {{lead.Email Address:default=no email address}}" } Request Encoding Token     =  None (You can change this if you want) Response Type                    =  None 11) Click create and now we are ready to call our webhook and send necessary data to our users in Slack! Who This Solution Applies To Slack Users
View full article
Issue Description After switching to Salesforce Lightning, you receive the following error when trying to open a copy of a Marketo email: "You can't preview or edit Classic templates on the Email Templates home page. Go to Classic Email Templates in Setup." Issue Resolution Currently the email templates are saved under the "Classic Email Templates" and are not compatible with Salesforce Lighting.   If you are trying to view the emails in Salesforce that are sent by Marketo, you will need to view the emails in Classic Mode. Who This Solution Applies To Customers using Salesforce Lightning
View full article
In order to manager authorized support contacts you must be set up as a Support Administrator on your Support Entitlement with Marketo.   1. Log into the Marketo Community and click Support.     2. Click Manage Authorized Contacts to approve or disapprove authorized contacts.   3. The top of the Manage Authorized Contacts page provides information about contact totals.  If the Allow Marketo Support to Add Authorized Contacts is checked, it means that the customer has granted permission to Marketo Support to add authorized contacts. 4. To authorize a contact, check the Is Authorized checkbox next to the contact's name.  In order to appear on the list of available contacts, the user must have clicked Community (while logged into Marketo) at least  once. 5. To un-authorize a contact, click the Authorized checkbox next to a contact name to clear the checkmark. Click OK in the popup. If a contact on the list is no longer an employee at your company or that person does not need to manage cases, you can remove a contact from the listing entirely, by deslecting the Authorized box, and selecting the No Longer checkbox. Click OK in the popup. Great! You can now manage Authorized Contacts for your account.
View full article
Issue Description Using the Web Page, Referrer URL, or Query String constraints to specify web page when using one form on multiple pages. Issue Resolution Use the appropriate constraint to specify which page the form is on when using a "Fills Out Form" trigger or "Filled Out Form" filter in a Smart List. There are three options: Web Page Referrer URL Query String Web Page This constraint is designed for Marketo Landing Pages. If you have one form on multiple pages, and were attempting to specify a Marketo Landing Page, then you would use Web Page.  If you use Web Page, your value is the Landing Page asset name, such as "Global Contact Form Page". Or if the page is local to a program, the name format would be [program name].[landing page name] Referrer URL This constraint is designed for external, non-Marketo pages. If the form you have is embedded on an external page, the value you would enter would be the URL of the page. This constraint is very picky about the values entered. Say the form is on http://www.pages.domain.com/contact-us.html . Only the following 2 options would function: Referrer URL - is - http://www.pages.domain.com/contact-us.html Referrer URL - contains - www.pages.domain.com/contact-us By using "is", the exact value must match. When using "contains" a smaller portion of the whole can be used. Even "contains" /contact-us would have worked successfully, but the less specific the value is the more other pages could qualify depending on the use case. Generally, "contains" is advised with a unique portion of the URL because there can often be querystrings on URLs that would then not satisfy the "is" constraint. Querystrings If the form is on a page, and the page has a querystring, such as: http://www.pages.domain.com/contact-us.html?product=new-stuff , then the form submission activity on the Marketo record would have a new field in the Detail called Query Parameters. ( Querystring, Query String, Query Parameters are all the same thing.) If you set up direct links to the Page with unique querystrings, then you would be able to use the Querystring constraint and use values from the querystring in the trigger/filter form fillout campaign.
View full article
NEW WebAPI (REST) integration now available for Microsoft Dynamics   NOTE: This is currently ONLY available for Dynamics online & on-prem versions 9.x using ADFS 2016 and above. Pre-ADFS 2016 (on-prem v8.x and older with ADFS versions earlier than 2016) authentication is done using client credentials only – clientid/secret is not possible. Since o ur existing WebAPI integration mandates a clientid and secret, it is only supported for Dynamics 365 Online and Dynamics on-prem instances v9.x in conjunction with ADFS 2016 and above. If you do not use these supported Dynamics/ADFS configurations, the native SOAP integration will continue to work for the foreseeable future; however, we are no longer developing SOAP enhancements.   As part of the continued investment in our Microsoft partnership, the native Marketo Engage / Dynamics SOAP integration is being upgraded to a more robust and stable connection using WebAPI (REST) that will better support future upgrades and releases.    The Marketo Engage and Microsoft Dynamics teams are encouraging all customers to proactively adopt WebAPI in preparation for the forthcoming scenario where SOAP API is no longer supported. The upgrade should only take 5-10 minutes by your Dynamics admin and present no loss of data with your existing sync. This is a critical step to ensure your WebAPI connector activation can be completed.   We encourage all Dynamics customers with the supported version/ADFS configurations to upgrade before May 2020, our target time frame to begin releasing new features via WebAPI.   The attached Customer Setup document only applies to Dynamics Online (365) and on-prem v9.x with ADFS 2016 and above. If you have questions or need help with your specific configuration, please open a support case for assistance.
View full article
Issue Description You would like to pull a report of all the non marketable records that you have in Marketo. Issue Resolution You can do this via a Smart list: Use the Any filter in the smart list. Filters: Black Listed = true Unsubscribed = true Marketing Suspended = true Email Invalid = true Email Address is empty This smart list will pull all the people that fall into the blocked leads list.
View full article
Issue Description An Email with only emoji in the subject line is displaying "Subject is empty" error and is not approving, or emoji fail to render elsewhere in the email. Issue Resolution If the subject line only consists of emoji, consider adding text. The Email Editor was not designed to insert emoji. However some have been able to insert emoji from outside sources. Those with the most success are inserting UTF-8 encoded emoticons. This specific encoded emoticon can be inserted (copy/paste) through a 3rd party website, located with a general web search: "UTF-8 emoticons/emoji". If the inserted emoji has a different encoding, it may fail to render in the Email Editor, and it may fail to render upon delivery as well. Rendering upon delivery will be reliant on the recipient server. If the emoji is considered invalid, then the 'diamond with question mark' character may remain. Alternatively, b asic symbols could be used instead of emoji, as they are ASCII characters and not reliant on extra encoding. 3rd party sites, identified with a websearch: "ASCII symbols", can be a resource. Another option can be q-encoding the emoji in UTF-8 format to render a string of code that can be used. This code tells the email client to render the desired emoji. To q-encode, copy and paste the desired emoji through a Unicode to UTF-8 translation tool, such as https://tools.bluestatedigital.com/kb/subject-line-assistant ​and then insert the translated code.
View full article
System Uptime and Reliability   Month Uptime January 2020 99.925% December 2019 99.893% November 2019 99.942% October 2019 99.945% September 2019 99.963% August 2019 99.489% July 2019 99.980% June 2019 99.750% May 2019 99.800% April 2019 99.980% March 2019 99.680% February 2019 99.800%       Email Deliverability Score     Trusted IPs All IPs Month Cisco SenderBase Good/Neutral/Poor ReturnPath Sender Score 0 to 100 Cisco SenderBase Good/Neutral/Poor ReturnPath Sender Score 0 to 100 January 2020 Good 98 Good 98 December 2019 Good 98 Good 98 November 2019 Good 98 Good 98 October 2019 Good 97 Good 98 September 2019 Good 99 Good 98 August 2019 Good 98 Good 97 July 2019 Good 98 Good 97 June 2019 Good 98 Good 97 May 2019 Good 98 Good 97 April 2019 Good 97 Good 98 March 2019 Good 98 Good 98 February 2019 Good 96 Good 97
View full article
What’s changing? On February 21, 2019, Webkit announced the new release of Safari’s Intelligent Tracking Prevention (ITP), known as ITP 2.1 and ITP 2.2 shortly thereafter. With ITP 2.x, all persistent client-side cookies, i.e., non-session cookies created via JavaScript through document.cookie, are capped to a seven-day or one-day expiry.  Mozilla Firefox and Google Chrome have also announced their intent to conform to these new policies, though no details or dates have been released.   How does this impact Marketo? As a result of these changes to cookie policy, 7 days after their initial tracked visit to your domain, the Munchkin cookies of visitors using Safari (or future affected browser versions) created with the existing versions of Munchkin JavaScript will expire, and on subsequent visits they will be tracked as a new visitor.   How does Munchkin operate? On a person’s first visit to a page on your domain, a new anonymous person record is created in Marketo. The primary key for this record is the Munchkin cookie (_mkto_trk) which is created in the user’s browser.  All subsequent web activity on that browser is recorded against this anonymous record.  In order to be associated with a known record in Marketo, one of the following methods should be used: The person may visit a Munchkin-tracked page with a mkt_tok parameter in the query string from a tracked Marketo email link. The person may fill out a Marketo Form. REST Associate Lead call must be sent.   Once one of these actions is completed, the cookie and all its associated web activity will be associated with the known record.   How is Marketo planning to address ITP concerns? Marketo will implement a new web service to allow Munchkin cookies to be set with a Set-Cookie header via HTTP response, so that they may bypass the 7-day expiry cap imposed when setting cookies via JavaScript.   Do I need to do anything to take advantage of these updates? In order to leverage the new behavior and take advantage of the greater expiry period and tracking capabilities, ensure that you have configured the following: A Landing Page CNAME Secured Landing Pages (i.e. HTTPS) For external pages, you must have configured a Landing Page Domain or Domain Alias with a Top-Level Domain (TLD) matching the external domains which you wish to track For example, if you have pages on the domain www.example.com which are tracked, you must have configured an LP Domain or Alias which is a subdomain of example.com, like munchkin.example.com   What happens if I do nothing? Munchkin’s ability to track users across sessions on the same domain will remain limited by ITP to either 1 or 7 days based on the browser and browser version used by the visitor. As of this posting, this only affects visitors using the Safari browser, although Chrome & Firefox may follow suit with their own versions.   When will the solution be launched? These changes will begin as a staggered roll-out to customers who have opted into the Munchkin Beta channel in conjunction with the January 2020 Marketo release. Once the solution has been released to all beta customers, the roll-out to our entire customer base will begin in mid-to-late February. All customers should expect to have the solution by end of March 2020.   Google Chrome Update (Feb. 2020): Google recently announced that the Chrome browser will block all third-party cookies within two years; however, s ince Marketo uses 1st party cookies, this update regarding 3rd party cookies will NOT affect your Marketo tracking efforts. For further context about 3rd party cookies in general, and the industry shift away from using them, please see the following article for Adobe's stance across the Experience Cloud Solutions: https://medium.com/adobetech/an-adobe-perspective-google-chromes-announcement-on-the-future-limits-of-3rd-party-cookies-bbb7bb257fdb
View full article
Issue Description When there is a notification in Marketo for "Microsoft Dynamics Sync Change", sometimes it may also include "localizedMsg" as one of the fields, despite that field not existing in the Marketo instance. Issue Resolution The "localizedMsg" is an extra bit of wording that shows up in these error messages sometimes, but it is not relevant to the rest of the notification. Focus on the other field(s) listed there, as that's what the notification message is really talking about. You can ignore the "localizedMsg" bit since that's not an actual field.  Who This Solution Applies To Dynamics Users
View full article
NOTE: Securing any Marketo domains requires the "Secured Domains" product first be added to your subscription. A base offering will be automatically added to all customer subscriptions at next renewal, but to make any SSL or domain changes, or purchase coverage for additional domains, please contact your Marketo Customer Success Manager (CSM) for more information.   Marketo’s Secured Domains for Landing Pages secures any and all landing page domains defined in your instance to be served via HTTPS. Serving your pages securely assures that you’re providing critical security and data integrity for both your pages and your visitors’ personal information.   Below you’ll find the 5-step process to secure your Marketo landing pages with Marketo’s Secure Domains for Landing Pages. Please note, there is an automated support case that gets created on your behalf when the purchase of Secured Domains for Landing Pages is completed.     Step 1. Verify your Landing Page Domain, CNAMEs and any Domain Aliases are setup Before you can secure your landing page domains and any domain aliases (subdomains), you must first set these up in Marketo. If you are a new Marketo customer working through your implementation, please work with your implementation consultant on the landing page domain(s) setup and timing to cut over to HTTPS. If you’re securing your landing page domains for a previously implemented instance, please verify that your domains and domain aliases (subdomains) are set up in your instance. Below are some links to help: Edit Landing Page Settings – to set you Landing Page Domain Customize Your Landing Page URLs with a CNAME – to understand and set up CNAMEs (subdomains) Add Additional Landing Page CNAMEs – to set up multiple CNAMEs in your instance (subdomains) Be sure your redirect rules and domain aliases are updated to use https:// instead of http:// .   Step 2. Edit and update the HTML code of your existing landing page templates to HTTPS Next, you'll need to review and update your Marketo landing pages to ready them to be served securely. Please complete the following two actions in order before moving on to Step 3: If you purchased Marketo before January 2016, please un-approve and immediately re-approve all landing pages last updated before January 2016. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages for un-approve/re-approve via the “Landing Page Actions” menu. We recommend completing this step in batches of a maximum of 10-20 pages at a time. Instructions for doing so can be found here: Approve Multiple Landing Pages at Once - Marketo Docs - Product Documentation. You can see the "Last Updated" timestamp in the Landing Pages section of Design Studio. Open the HTML code for each landing page template. C hange all URLs listed in the HTML currently formatted as "http ://" to instead read "https://" TIP: Ctrl+F "http" to automatically highlight all URLs that must be updated: Simply add "s" after each http reference until ALL have been updated to https Missing even one URL's http reference will cause the "Mixed Content" browser warning:   vs.  SAVE THE PAGE AS A DRAFT Do  not approve the draft. You will approve the drafts after Support activates SSL in Step 4. NOTE: Once you secure your Marketo landing pages to be served over HTTPS, you should not link to HTTP (unsecured) assets or pages from your secured landing pages.   For more detailed guidance, please see our recorded instructions below   Video Link : 2237     Step 3. Respond to the TSE via the existing support case The TSE will then begin the process on our end to generate certificates to cover all the domains and subdomains configured in your instance. Once notified, please allow 3 business days for Marketo to create your secure server endpoint. Marketo's Support team will contact you when this is complete. We appreciate your patience during this 3-day setup process.   Step 4. Marketo Support Will Activate Your Secured Domains for Landing Pages Once we've generated and issued the necessary SSL certificates for your domains, we'll notify you that it is done and activate SSL for your Landing Pages. NOTE: There will be a brief "cut-over" period between when HTTPS is enabled by the TSE and when you are able to complete Step 5 below. During this time, landing pages may show up to customers with a mixed-content warning; however, all links and emails will continue to work properly without disruption, and your customers are not at any risk. Be ready to complete Step 5 quickly once instructed to minimize this period.   Step 5. Re-approve your landing pages and verify success Once your Support Engineer has activated the switch to HTTPS for your instance, y ou must immediately take the following actions: Approve all draft pages that you edited from Step 2 above. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages to approve via the “Landing Page Actions” menu. If you include a Marketo landing page on a secure website using an iframe, you will need update the HTML to load the secure version of the landing page, otherwise the end user will get a security warning. Verify your pages are loading and rendering as expected. Contact Marketo Support with any issues you may encounter.     Questions & More Information For more information, including and FAQ, please see the Marketo Secured Domains for Landing Pages Overview & FAQ.     Is this article helpful ? YesNo
View full article
Issue Description Updates made to an embedded Form are not immediately reflected on the web after the Form is approved.   Issue Resolution To improve page load times, Marketo Forms are served from a cache. It may take up to 4 minutes for newly approved changes to forms to display on the web. This only applies to embedded forms on non-Marketo pages; forms on Marketo Landing Pages will continue to update immediately after approval.   To preview changes immediately, you can use the Preview functionality.  https://docs.marketo.com/display/public/DOCS/Preview+a+Form
View full article
Issue Description General recommendations for managing and improving deliverability to China Issue Resolution If you are looking for general recommendations around delivering to China, here are some resources both from our Community and external sources. Navigating email delivery into China Golden Shield Project overview Sampi China Email Marketing and Chinese Anti-Spam Laws Summary English language version of the Measures for Administration of Email Service on Internet​ Lehman, Lee & Xu English language version of the Measures for the Administration of Internet E-mail Services 2006​
View full article
Issue Description Even though the Success Path Analyzer and the RCE report may be looking at the same thing (e.g the conversions from one stage to another), the numbers in Success Path Analyzer and RCE Conversion Ratio will not match. Issue Resolution Success Path Analyzer is telling you that records are flowing from one stage to another, for example a record moving from Cold List to MQL, the conversion rate will display the rate from this stage to the next stage. If you look at the RCE Conversion Ratio, this is not tracking just the conversion from the first stage on the Success Path Analyzer to the second but instead this tracks all the conversions from this stage to another (eg. Cold List to MQL, Cold List to Attempting). Thus resulting in a much higher conversion percentage as the RCE is not bound to the green path from the Success Path Analyzer. Who This Solution Applies To Customers using RCE, Customers using Success Path Analyzer
View full article
Issue Description An email appears to have been sent twice to the same lead. Issue Resolution It appears that the record was sent the email twice because the record was merged with another record after the email was sent. So when the email was sent, the record was two separate records that was sent the email individually. This can be identified by looking at the record's activity log for a 'Merge People' activity
View full article
Issue Description Marketo allows you to upload any file type to your instance (100MB or less) but these files don't always download automatically or open in a new browser tab or window consistently between users. Issue Resolution Marketo's servers are not configured to force a download, so any desired effect is up to the user and/or utilizing custom code to achieve that effect. How a file is handled or displayed is largely up to the browser and you will need to test whether your specific desired outcome is possible. Keep in mind, this may vary by file type and file size and may not be feasible. Who This Solution Applies To Anyone providing links to files hosted in Marketo via email or on a landing page.
View full article
Issue Description You are using choices within flow steps with parameters such as "Member of Program" and the lead is qualifying for the choice when they are not part of the program Issue Resolution When using a flow step for a campaign, you have the option of adding "choices" to the flow step so different leads can have different interactions. When using a choice parameter such as "Member of Engagement Program" or "Program Status". If the lead has been part of ANY engagement program, or has EVER had a program status equal to the parameter (i.e program status is email > sent), then the lead will qualify for that step. There is not a way around this unfortunatly, but you could use the "Member of Program" filter in your campaign smart list to make sure content is delivered to your intended audience.
View full article
Issue Description When trying to create a new engagement program, you get an error stating that your instance has reached maximum number of active engagement programs. Issue Resolution Due to engineering constraints and as well as to have better user experience, we have limited the total number of active Engagement Programs to 100. So you can create as many Engagement Programs as you want, but when you try to activate more than 100, you will get an error message that says “You have reached 100 Active Engagement Programs. Please deactivate some of your existing Engagement Programs to activate this program." The easiest way to see all your Engagement Programs is to use the filter on the navigation tree.  Click the filter icon and select Engagement Programs from the list. This will allow you to see which Engagement Programs are no longer needed so that you can deactivate them to make room for more.
View full article
Issue Description Attempting to push a custom audience results onto a Facebook Authorization Error visible in Notifications. Some custom audiences can be pushed and it appears to be only affecting a certain Ad account. Issue Resolution 1.) Check if the Custom Audience Terms (https://www.facebook.com/legal/terms/customaudienc) have been accepted 2.) Check in Audience manager logged in as the user used in the Facebook Custom Audience service in Marketo, to see if there are any custom audiences that have the "Accept Terms" button pop-up similar to this screenshot 3.) As per our recent release notes at https://docs.marketo.com/display/public/DOCS/Release+Notes%3A+Winter+%2719: "Facebook now requires a Business Manager account in order to leverage your Custom Audience integration. Your Facebook LaunchPoint service must be associated with a Business Manager account or your integration will no longer work after January 14, 2019. To set up a Business Manager account, please refer to Facebook Help." 4.) Check if the user used in the Facebook Custom Audience service in Marketo is a Business Manager account 5.) After completing the checks above, try to push a custom audience again to the affected ad account. If unsuccessful, recreate the Facebook service and test to push a custom audience from there.
View full article
Issue Description You would like to know the list of leads who will get blocked from receiving emails when you send email via campaign or program. Your Communication Limit setup can be found in the Admin Panel and looks something like this.     Issue Resolution You can create a smart list with the below setup and this list will show you the list of the people who will hit communication limit when you try to send an email.       To learn more about Communication Limits and how they work, you can review this article. Is this article helpful ? YesNo
View full article