Knowledgebase

Sort by:
Issue When forwarding email that was received via Marketo to other people, the email does not render the same in the recipient's email client. Solution This can happen when forwarding emails, as the email rendering capabilities depend upon the email client that recipient uses. HTML and CSS can be interpreted differently by different email clients. As noted in the comment below Some clients' HTML parsers don't understand all types of markup, for example an HTML4-level client will not recognize HTML5 elements. Some HTML elements and CSS rules are deliberately ignored, even if the underlying parser and (in the case of webmail) browser supports them completely The HTML markup is can be changed, sometimes drastically, from the original markup before being displayed for security reasons   With that said, you can code against some of these anomalies by adding extra code in CSS to account for the differences. Marketo Support is not set up to assist with troubleshooting custom code as we are not web developers. We would suggest that you consult with an HTML/CSS designer to make these changes. To ensure that the existing email templates are coded to comply with different email clients, it is advisable to consult with a web developer/designer to review the code. Here is a guide that you may find helpful: https://www.campaignmonitor.com/css Furthermore, even if the clients are the same, the act of forwarding an email can itself change the HTML of the email.  However, Marketo does have a workaround for this. You would just need to put the ‘Forward to Friend' link directly into an email and when the person forwards the email using this link, there is a reduced possibility of the rendering issue occurring.  It also adds the forwarded email address to your Lead Database as an unsubscribed lead. The below article covers adding the ‘Forward to Friend’ link to your emails https://docs.marketo.com/display/DOCS/'Forward+to+a+Friend+Link'+in+Emails    
View full article
Overview These instructions will show you how to add a filter to Segments that will prevent a visitor from seeing the same campaign twice. When done this way, each visitor will only see the associated Campaign once and won't see it again.   This is a article attached image   1. Locate and select the User Context API filter (in the API category). This is a article attached image     2. Select "Campaigns - Viewed" from the "Select field to add" drop down. This is a article attached image   3. Select "is not" and insert the Campaign ID. This is a article attached image     Where to find the Campaign ID The Campaign ID is the identifier used by RTP to specify which Campaign you are referencing. It can be found in the URL for the campaign once you've navigated to it. Look for the number in the end of the URL, just after "reactionId=".            This is a article attached image   4. Click the plus sign to add a second field to the filter. Choose "Campaigns - Viewed" as the second field, same as the first.   5. Select OR from the AND/OR field. 6. Select "is empty" for the second Campaigns Viewed filter option. S This is a article attached image     Finally please make sure that the campaign is not marked as "Sticky", as this will make it appear every time.   You're all set! This segment will now only match visitors who have not seen the campaign yet.
View full article
Note: Please ensure that you have access to an experienced Web developer.  Marketo Technical Support is not set up to assist with troubleshooting code. Marketo Form Proxy enables forms to be submitted to Marketo while removing any tracking information. The most common example where this can be used is a customer referral landing page. For an example (available at this writing), see www.marketo.com/referral. Server Requirements PHP CURL Server Installation To begin: Download this project, if you haven't already, here: github.com/Marketo/Form-Proxy/downloads. Edit the variables in mkto_proxy_config.template.php as necessary. Rename mkto_proxy_config.template.php to mkto_proxy_config.php. Drop the entire directory onto your website (or subdomain), e.g. YOUR-COMPANY.COM/post-proxy/ orpost-proxy.YOUR-COMPANY.COM/. Visit the directory you just created. If it redirects to the default URL you set in mkto_proxy_config.php, it works. Otherwise, you must've skipped a step. Now, on each landing page: Copy the text from Custom-HEAD.html.txt into the Custom HEAD HTML field in Marketo Design Studio (click Landing Page Actions, then Edit Page Meta Tags). Update that code. Replace YOUR-COMPANY.COM/post-proxy/ with the URL to the directory you created in the 3rd server installation step. Save your landing page and test thoroughly. Contributions This script is open sourced under a modified BSD license (more on that below). It does not require you to send contributions, but if you have any you'd like to share, please submit a PULL request through GitHub. License Copyright (c) 2012 Marketo, Inc. - marketo.com All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Marketo, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
View full article
Issue Issue Description You are unable to check any emails to select in the Email Filter section in the Setup tab of your report (http://docs.marketo.com/display/public/DOCS/Filter+Assets+in+an+Email+Report) when Global Reporting is enabled (http://docs.marketo.com/display/public/DOCS/Report+Email%2C+Campaign+Performance+Across+Workspaces).   Solution Issue Resolution When using the Global Reporting feature in a report, you can only view a report for all emails across workspaces. You cannot filter the report to include only certain emails.  
View full article
Issue Leads were uploaded into Marketo with the wrong opt-in date and time, which also synced with Microsoft Dynamics 365.   Solution To correct the opt-in date and time, do the following. Update information in Marketo. Prepare and upload a corrected list for the leads. Confirm the opt-in field in Marketo is not blocked from updates. CRM Sync The corrected data in Marketo will auto-sync with Dynamics 365. If auto-sync fails, manually update the opt-in dates in the CRM. Additional Steps Check for any automated actions triggered by the wrong data and rectify them If needed. Confirm data accuracy in both systems after updates. Back up data before mass updates to prevent data loss.  
View full article
Issue If you create a Landing Page Domain Alias within Marketo Admin > Landing Pages > Rules, you are given the option to set up a Default Page for that Alias. What happens if an end-user navigates to an invalid page on the Domain Alias?     Solution Let's say that your Branded Domain Name is pages.domain.com, and the Fallback Page set to domain.com.You have also set up a Domain Alias: pages.otherdomain.com. The Default Page for that Alias is: otherdomain.com. When you navigate to an invalid page on the primary domain (pages.domain.com/invalid-page.html,) you will be redirected to the Fallback Page: www.domain.com. If you were to navigate to an invalid page on the Alias (such as pages.otherdomain.com/invalid-page.html), you will be still be redirected to the Admin Settings Fallback Page: www.domain.com. The Domain Alias Settings are particular in the sense that the exact setting is for the "default page". You will only be redirected to the Domain Alias Default Page if you were to navigate to pages.otherdomain.com.
View full article
Issue You want to know if updated lead/person record data will reflect changes to that data made while the lead was in a wait step. This is important to know, because values could affect the following flow steps. For example, if there is a choice in the send email flow step that is determined by those values. Solution Any information that was updated while the lead was in the wait step will be reflected in the next step.  
View full article
Issue You have developed a Marketo landing page and enabled Personalized URLs (PURLs) for your records but when people visit the PURL, form pre-fill does not take place.   Solution When a person visits a PURL landing page, the form pre-fill checks their Munchkin tracking cookie to identify what values to populate for the form fields. If that person has a Munchkin tracking cookie associated to a known record in the database, it will pull and populate the information from that record. However, if this is the first time this person has visited a Munchkin tracked page or their browser is tied to an anonymous record, the pre-fill will not populate any information into the form. The customer/prospect will need to fill out a form or click on a tracked link in an email sent from Marketo. This will allow future PURLs that people visit going forward will have pre-fill populate as their cookie will be tied to a known record in the database. The web page visit will be associated back to the know record for the PURL. Additionally, you can also use Person related tokens on the landing page and those will resolve. For examples having the token in the text that states {{lead.First Name:default=Default}} within the body of the landing page will populate with the expected persons first name for the PURL they visited. This is because the token generation goes through a different path on the back end for PURLs.    
View full article
With Marketo's newly released Customer Engagement engine, you can now easily nurture and engage your leads. Not only does the Customer Engagement engine automatically and intelligently deliver the right content to the right person, at the right time, but you now no longer have to manually create or maintain complex workflows. View this webinar to If you are looking to convert your “traffic cop” nurture program to the Customer Engagement engine.  Cheryl Chavez, the Director of Product Management at Marketo will cover the best practices and steps for converting your campaigns. View the training here: pages2.marketo.com/cee-training-migration-aug-2013.html Is this article helpful ? YesNo
View full article
Issue After going through a modification of a text field type from 'Text' to 'String', the field is no longer available as a filter for smartlists. Don't worry, the field is not gone - it is just temporarly unavailable. Solution Changing the field type from one type to another is a database intensive operation and in some cases where the field values are widely populated across your database records, this can cause the filter to be unavailable until the operation is completed in full. The time it takes for the field filter to become available may vary and it can take up to ~30 hours sometimes until the field filter is available again after the type of the field has been changed.  
View full article
As Marketo customer and a member of the Marketing Nation, it's important to have something you can reference, a brief guide or checklist.  Here is a collections of articles that we think will be invaluable to you as you move along in your Marketo journey.   Marketing Nation Marketing Nation Glossary   Marketo Marketo Icon Glossary Managing Marketo Users Managing User Roles and Permissions Munchkin   Sales Insight Sales Insight is super easy to use and will give you the visibility needed to prioritize and close business faster.   Issue a Marketo Email License Publish an Email to Sales Insight Using Interesting Moments Sales Insight Email Performance Reports   Email Marketing Add Editable Sections to an Email Template The Engagement Dashboard   Demand Generation Add Editable Sections to a Landing Page Template   Revenue Explorer Revenue Explorer Report Revenue Explorer Report Types Is this article helpful ? YesNo
View full article
Issue When making changes to an email with the 'Edit Code' option, these changes aren't shown in the Audit Trail like other changes made to an email draft. Solution This is an expected behavior of the Audit Trail. Only edits made with the Design Studio interface will be displayed on the Audit Trail.  
View full article
Also see: Enabling Asset Discovery - Marketo Docs - Marketo User Manual Steps to fix: Verify the RTP tag exists on the page Verify there are no any jQuery / Javascript / Other errors in the Developers Console Login to your account and go to the 'Account Settings' panel > make sure the 'Assets' toggle is switched to On In the 'Account Settings', go to the 'Assets' tab and make sure the URL patterns configuration are valid Select an asset in 'Assets' tab and click on link to check if click count increases and capturing you as the visitor. (see note 2) NOTES Don't forget to add wildcards (*) in your URL patterns, otherwise it will only cover the exact page you inserted:  marketo.com/solution  won't match: marketo.com/solution/rtp.pdf This step doesn't work with PDF files, simply because the rtp js tag is not installed on PDFs. In addition, the click event listener doesn't work on the back office, so only if it is an HTML page and you are viewing it (while rtp is running in the background) you should see the counter changes.
View full article
Issue Lead activity log shows "Change segment" or "Add to Segment" for a segmentation (i.e. "Change Title to "Directors") The named segmentation ("Title") does not show up in the segmentation list in Database Environment Marketo instance with the Target Account Management feature Solution Even though the activity log shows a segment activity, the segment is actually a Persona, which is a feature of Target Account Management.
View full article
Issue The "Make Dynamic" button does not appear in the drop down gear menu when an image is clicked in the email editor. Solution 1.Click the image in the editor twice 2.Click the gear Menu next to the image 3.In the menu "Make Dynamic" should appear. This is occurring because the image is located inside of another element such as a <div> which is being used as a module. The first time the image is clicked, the module is being selected, so the Make dynamic option does not appear. The second time the image is clicked, the image within the module is selected so the Make dynamic option can be selected.        
View full article
Issue There is a discrepancy for certain emails between Email Insights and Email Performance Report. The data (e.g. sent, delivered, opened and clicked) are significantly lower in Email Insights for the emails as compared to the Email Performance Report for the same emails. Solution There is most likely a discrepancy because at the time Email Insights was first enabled "you’ll have four weeks of historical Email data in addition to all new email activity". There was no request to Marketo support to upload historic data beyond four weeks which would have included data for the emails above. This request relates to the notes below from the article: "We’ll give you a four-week period before you can request Marketo Support to upload your data" The solution is to request that Marketo Support backfill the report data so you have data for Email Insights beyond the four weeks.    
View full article
Issue How to delete email from ToutApp Live Feed. Solution The way to stop the tracking is to archive the email.  All you need to do is find the email, click the arrow next to Email, and click "Archive". This will stop the tracking and it won't show up in the live feed.   )   Who This Solution Applies To ToutApp customers    
View full article
Issue Description When sending an email through the ToutApp Panel within Salesforce, what email server is used? Issue Resolution The Salesforce plugin will utilize the settings for your ToutApp.com sends. In ToutApp.com you can choose to send via the ToutApp Servers or via your company's outgoing email server.
View full article
Issue New leads created through form submissions in Marketo are not being registered by the "Fills Out Form" trigger in associated campaigns. Solution To address this issue: Verify Referrer Value: You'll see a referrer value in the Fills Out Form. Confirm that the referrer value in the Fill Out Form activity aligns with the campaign trigger criteria. Check Configuration Changes: Inspect any recent changes to URLs that may affect form submissions. Communicate these changes to the Marketing Operations team for proper adjustments. Review Campaign Setup: Ensure the campaign is set up to include the specific form and that no filters exclude new leads. By following these steps, you should be able to resolve the issue and have new leads correctly trigger the Fills Out Form activity in Marketo campaigns.
View full article
Issue Recent Activities are shown in Lead Activity Log for being added to an SFDC Campaign, however this campaign may have occurred a significant time in the past. Solution A common reason for this occurring is a deleted record in SFDC was restored, so the past activities are coming down to Marketo as if they happened recently. The root cause is that the SysModStamp for one of the object records (Campaign, Campaign Member, Campaign Member Status) for the record was updated, so, in the perspective of the Sync User, the newly updated (recent SysModStamp time) record needs to be queued up to be synced. If this is causing some unintended Marketo Trigger Campaign activity, we advise that active Trigger Campaigns be reviewed to make sure that past campaigns are deactivated, and only relevant campaigns are currently active.      
View full article