Knowledgebase

Sort by:
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: https://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. http://YOUR-COMPANY.COM/post-proxy/ orhttp://post-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 http://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. - www.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: If you have setup a trigger campaign to send you an alert based on lead activity, you may have received a few blank alerts. Solution: Anonymous leads qualify for trigger campaigns, this is by design, you want anonymous leads to be scored if they show desirable behavior, but receiving blank alerts probably does not make sense. Use the Is Anonymous filter in your trigger campaign's smart list in order to stop anonymous leads from entering: Excellent! You should no longer receive blank alerts from your anonymous leads.
View full article
Marketo allows you to edit the unsubscribe text globally in the Admin section. If desired, you can create an email template for a specific language and create your unbsubscribe text manually. 1.   Create new email templates. See Working with Marketo Email Templates for details.   Using this technique will affect your email performance reports. They will no longer include "unsubscribed from email" stats.  Rather they will track "clicks link in email" when the lead clicks on the unsubscribe link. Is this article helpful ? YesNo  
View full article
The reason why the Sales Insight Anonymous Web Activity report differs from the Lead Management Anonymous Web Activity report is because the Sales Insight report does not show anonymous leads whose company name is either blank or is an ISP while the Lead Management report shows everything. The Sales Insight tool is geared towards Sales, and visitors with blank or ISP company names could be misleading to the Sales person. You can see this by looking at the Lead Management report. Notice that the visitors whose company name is bolded are the ones that are displayed in Sales Insight. When the company name is bolded, that means that the visitors company name has been verified using a reverse DNS lookup. Conversely, if the company name for the visitor is not bolded (or is missing), the reverse DNS lookup just shows us the ISP (or nothing if the reverse DNS lookup yields nothing). If you want to remove anonymous leads who do not have company information from your web activity report, follow these instructions: Hide anonymous leads without an inferred company in web activity reports
View full article
As you know, Marketo issued a security patch on 4/6/16 in order to strengthen token encryption within email links. At Marketo, security is a top priority and we will continue to invest in changes that make the platform more robust. In reference to this patch, Marketo Support has been answering several common questions that are documented here for your reference. Please find this information below and, as always, contact Marketo Support if you still have any unanswered questions. Are all email links impacted by this patch? No, the vast majority of links within emails are not impacted in any way. By default, Marketo converts all email links to shortened tracking links. These links were not impacted by this patch. These links should continue to function as expected, regardless of when your email was sent. Note: This also applies to any links that contain the “mktNoTrack” or “mktNoTok” class. These links were also not impacted by this patch. Which links were impacted? The only links that were impacted were links that contain pre-generated mkt_tok values. There are three ways these type of links can be present in your email: 1.  You use one of the following system tokens in your email: {{system.viewAsWebpageLink}} {{system.unsubscribeLink}} {{system.forwardToFriendLink}} 2.  You use the “Include View as Web Page” option in the Email Editor and your Admin > Email defaults for “View as Web Page Text” explicitly includes an mkt_tok value like this:  mkt_tok=##MKT_TOK## 3.  You use Marketo’s default functionality to auto-insert “Unsubscribe” footers at the bottom your emails and your Admin > Email defaults for “Unsubscribe Text” explicitly includes an mkt_tok value like this:  mkt_tok=##MKT_TOK## How will behavior change for these links? 1.  System Tokens For emails sent out prior to 4/6/16: {{system.viewAsWebpageLink}} - Any pre-patch emails that contain {{system.viewAsWebpageLink}} links will now direct users to a page indicating that the lead-specific email cannot be rendered. Users will, however, have the option to instead see a generic view of the email (no lead tokens, dynamic content, etc.). {{system.forwardToFriendLink}} - Any pre-patch emails that contain the {{system.forwardToFriendLink}} link will no longer function. Currently, users will see an error message on click. {{system.unsubscribeLink}} – Any pre-patch emails that contain the {{system.unsubscribeLink}} link will continue to function and point users to your unsubscribe page. However, the unsubscribe form will not support prefill for this visit. Note: For all of the above system tokens, any emails sent out post-patch are not impacted. 2.  “View as Webpage” - If you implement a “View as Webpage” experience in your emails by using Marketo defaults, selecting “Include View as Web Page” from the Email Editor, then you will see the following behavior: “View as Webpage" links inserted into the HTML side of emails are not impacted. These links should continue to function as expected, regardless of when your email was sent. “View as Webpage" links inserted into TEXT side will behave similarly to {{system.viewAsWebpageLink}}. For emails that were sent prior to 4/6/16, these links will direct users to a page indicating that the lead-specific email cannot be rendered. Users will have the option to instead see a generic view of the email (no lead tokens, dynamic content, etc.). Note: any emails sent out post-patch are not impacted. 3.  “Unsubscribe” - If you implement an “Unsubscribe” experience in your emails by using Marketo’s defaults, then you still see the following behavior: “Unsubscribe" links inserted into the HTML side of emails are not impacted. These links should continue to function as expected, regardless of when your email was sent. “Unsubscribe" links inserted into TEXT side will behave similarly to {{system.unsubscribeLink}}. For emails that were sent prior to 4/6/16, these links will continue to function and point users to your unsubscribe page. However, the unsubscribe form will not support prefill for this visit. Note: any emails sent out post-patch are not impact
View full article
Summary Admin unsubscribe HTML is overriding unsubscribe language hard-coded into an email template Issue You are trying to add unique unsubscribe text to a specific email asset template's code (for example: unsubscribe text in another language), but the Admin Unsubscribe HTML found in Admin > Email > Settings is overriding it.    Environment Design Studio/Admin Solution To implement dynamic unsubscribe text by language into an email asset, we recommend using the Segmentations and snippets, placing the {{system.unsubscribeLink}} directly into the email asset via the snippet as the presence of this system token in the email asset should override the Admin unsubscribe HTML. Make Your Unsubscribe Message Dynamic for Languages | Adobe Marketo Engage  
View full article
Summary Learn how to resolve issues with uploading SVG files to Marketo. Issue You are not able to upload Scalable Vector Graphics (SVG) files to Marketo. You are encountering errors during the upload process or facing issues with improper display in browsers after uploading.  Cause: The root cause behind such issues is often Marketo's security checks, which may reject certain properties of SVG files. This can lead to conflicts between what Marketo accepts and what browsers can display.   Solution To address SVG files not being accepted or displayed correctly in Marketo, try the following steps: 1. Change File Extension to .xml: Instead of saving the file with a .svg extension, save it as a .xml file. This will change the server MIME type and allow it to be uploaded to Marketo. Example: If your file is named "example.svg," rename it to "example.xml" before uploading it to Marketo. 2. Remove Unwanted Properties: If the SVG file contains additional properties or namespaces causing rejection by Marketo, removing them can resolve the issue. For instance, the xlink namespace, if present at the top of the SVG file, may lead to rejection by Marketo. Exercise caution not to remove essential properties, as this could result in errors when attempting to display the file in a browser. Example: If your SVG file has the following line: xml xmlns:xlink="http://www.w3.org/1999/xlink"    Remove this line from the SVG file's code using a text editor.   When saving SVG files from applications like Adobe Illustrator, changing the file extension or manually editing the code may be challenging. However, using any file explorer, you can easily change the file extension to .xml. Code editing can be performed using a text editor to manually remove unwanted properties. Always back up the original SVG file before making any changes to prevent permanent data loss. By following these steps, you should be able to successfully upload SVG files to Marketo and ensure proper display in browsers.
View full article
Summary duplicate records with the same email across lead partitions can be affected by uploaded custom object activity Issue System not separating lead partitions for custom object imports Uploading custom object activity affects duplicate records across partitions Custom Object activity import writing to the most recently updated record regardless of partition Solution Use the following workaround:  Run an update on the records that should be affected by the custom object activities import. This will make sure they are the most recently updated records among the duplicates Root Cause Normally when you do a list import, it would import into the one partition, whatever partition the list is located in and only impact the record in that one instance.  But when you import a Custom Object, it's able the see ALL the records across ALL the partitions.  If there are duplicate records, it just looks to see which one was updated most recently and grabs that one for the list import. So if you have lead record in A with Add to Custom Object already completed and you re-import again but the lead record in B has been updated more recently and has NOT had the custom object added to it, you get the duplicate "Add to Custom Object" activity. Environment Multiple lead partitions with duplicate records across them Custom Object activity import
View full article
Summary Result for Smart List using Web Page constraint is greater than the result for the total of conversion on Landing Page Performance Report.  Issue Result for Smart List using Web Page constraint is greater than the result for the total of conversion on Landing Page Performance Report.  Solution Ensure to append version number to the Landing Page when renaming and ensure each Landing Page has a unique name. Root Cause •             Smart List looks at the information written to the lead’s activity log. •             The Web Page constraint looks at the label and not the ID of the Landing Page. If the Landing Page was renamed, it will show a different result depending what is written to the lead’s activity log. >> Example 1: Lead A filled out the Form when the Landing Page was called LP1. Lead B filled out the Form when the Landing Page was called LP2. Smart List: Filter 1: Filled out Form Form is XXX Web Page is LP2 Result: In this scenario, the result will only display Lead B. >> Example 2: Lead A filled out the Form when the Landing Page was called LPX (ID111) Lead B filled out the Form when the Landing Page was called LPX (ID112) Smart List: Filter 1: Filled out Form Form is XXX Web Page is LPX Result: In this scenario, the result will display Lead A and Lead B. •             Landing Page Performance Report look at data specific to the asset ID. •             Landing Page Performance Report only look at active Landing Pages, therefore data for the deleted Landing Page(s) will not be included. •             If the Landing Page is renamed, it will be reflected on the Landing Page Performance Report (i.e. the Landing Page Performance Report will display the new name going forward).   Environment > Landing Page Performance Report conversion  > Smart List constraint Web Page
View full article
  Yes. There is a daily/weekly Recommended Assets email report that can be configured to be sent to users. Recommended Assets Report This email report includes all the pieces of content and count of clicks on the Content Recommendation Bar. To customize which automated email report the user receives, see: Email Reports - Marketo Docs - Marketo User Manual .  
View full article
  Issue User Receives Communication Failure Error / bandaid when creating a new Email from a custom Template due to unapproved snippet. Resolution Email templates can contain code to reference a snippet by ID: <div class="mktoSnippet" id="FooterText" mktoName="Footer Text" mktoDefaultSnippetId="3"></div> If the snippet is not approved then a new email asset cannot be created, and instead a bandaid error occurs.   The snippet should be approved first before the template is used.    If the ID of the snippet in the HTML is 3 and the pod sj27, the URL to the asset would be Login | Marketo  
View full article
Say you want to keep specific Salesforce fields or records from syncing into Marketo. You can use Salesforce Profiles to restrict access to that data.     In short, Marketo will only sync fields and records that are visible to the sync account in Salesforce. If you don't want records or fields brought into Marketo, use the record- and field-level permissions to prevent the sync account from seeing them. A few notes before you begin... Depending on your version of Salesforce, you may not be able to change these settings. For example, field-level security is available only in Enterprise and Unlimited editions. This will require you to make changes in Salesforce on the account you use to sync with Marketo. If this account is also used by anyone else, these changes will impact that person's view in Salesforce too. You need administrator access in Salesforce to make these changes. If you hide a field in Salesforce that has already been synced to Marketo, it will still display in the Marketo user interface until you hide it with the Field Management tool. Even though you'll still see the field in Marketo, changes to that field will not get pushed to Salesforce.      
View full article
Issue Naming conventions of email in email performance report Solution Email reports will use an email's full label including the program it exists in. Although asset names cannot duplicate within Programs, they can be duplicated within the whole Instance and Email Performance Reports have access to emails from an entire instance. For example if you had two newsletter programs, both with an email named "October Newsletter" the full program name can help differentiate between the two. NL-2018-10-Technology Program.October Newsletter NL-2018-10-Industry Program.October Newsletter The email report will always display with the full email name including the program it was created in to avoid this confusion. Even within a specific Program Report, you can access all emails within the Instance.
View full article
Issue You want to push Marketo activities into MS Dynamics.     Solution Marketo has the ability to push activities in SFDC, however, the same feature does not exist for MS Dynamics.  Instead, you can use Interesting Moments in Marketo Sales Insight to pass activities into Microsoft Dynamics.   Who This Solution Applies To Customers using Microsoft Dynamics.
View full article
Issue Can the {{system.unsubscribeLink}} be customized to point to a different page, such as a preference center?     Solution Issue Resolution The system token unsubscribe link will always behave the same way, and it cannot be customized. The {{system.unsubscribeLink}} will always bring you to: sub.domain/UnsubscribePage.html. If your Landing Pages are not branded, this system token will still behave the same way and take the lead to your out-of-the-box Marketo Unsubscribe Page (ending in /UnsubscribePage.html). If you want the link to go to a different page, the easiest workaround is to create a redirect rule that sends visitors to UnsubscribePage.html to your custom page instead.
View full article
Issue You have a CNAME for your Branded Tracking Links in email but want to restore the settings to the system default (example: mkto-ab01234.com).     Solution Once you have set up a Branded Tracking Link domain, it is not possible to restore it to the Marketo default.  You can change it to a different CNAME domain, but it is not possible to revert to the original.
View full article
Issue You are considering archiving or deleting old programs, and you are wondering how that will affect reporting on membership of leads.     Solution If you delete a Marketo Program, the membership data will be lost. Technically, in the Lead record Activity Log, there will not be an activity for "no longer in program," but any and all reporting will not be able to report from deleted programs.  Keep in mind that Marketo Support cannot restore deleted programs. Archiving Programs keeps program membership data. This means that Analytics reporting, including Revenue Explorer, will be able to see archived programs and the related data. However, smart lists will no longer be able to reference the archived program. For example, say the smart list was: "Member of Program, program is [name]". In this situation, the smart list wouldn't be able to locate the program.    
View full article
Issue Marketo Email templates that have been used are showing or appearing within the Salesforce Email Template Picker/Chooser. Solution The templates are created when Marketo syncs lead email activities to Salesforce.  You can disable these activities from syncing in Marketo Admin > Salesforce > Edit Sync Options. Unselect the Email activities or Sales Email activities you have synced.  The templates will no longer be created, but you also won't get these activities pushed from Marketo anymore. This applies to both Sales Insight and normal Marketo sent emails.     If you would like to note an email was sent to a lead without enabling these activities, you can utilize Interesting Moment Flow Steps or Create a Task to sync via the activity log!   Who This Solution Applies To Customer using Sales Insight for Salesforce    
View full article
Issue How to pull out the stats on which devices emails are being opened on.     Solution In a Smart List, you can use the filter "Opened Email" and you have the constraints of "Is Mobile", "Device", "Platform", and "Browser" to choose from. You can build a Smart List for each device you are interested in reporting on.
View full article
Issue Email Program Audience count is different than delivered/bounced email count. Solution The Audience number doesn't refresh or update once the Smart List is created, so the number of qualified people can change between then and sending the email. That is normal. If you want to double check the people, you can click the refresh button on the Audience pane of the email program just before sending, or create a separate Smart List with the same filters just before you send the email.  Also be aware that the Audience may include duplicate leads, or leads that have reached their communication limit. These leads will not show as blocked, but will not be sent the email
View full article