Knowledgebase

Sort by:
Included in this article Overview Do you need to create fields in Salesforce and have them connect to specific fields in Marketo like for Lead Score or Acquisition Program? If so, this document will take you right to the instructions on how to get that done! Step by Step Directions for all Salesforce Editions Adding Custom Marketo Fields to Salesforce Video Overview Here's a video tutorial of the entire process that should make it easy to follow along: Salesforce Connector Setup​ Enjoy!
View full article
System Uptime and Reliability   Month Uptime May 2021 99.932% April 2021 99.942% March 2021 99.900% February 2021 99.980% January 2021 99.974% December 2020 99.988% November 2020 99.935% October 2020 99.536% September 2020 99.870% August 2020 99.947% July 2020 99.933% June 2020 98.296%     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 May 2021 Good 98 Good 97 April 2021 Good 98 Good 96 March 2021 Good 96 Good 97 February 2021 Good 99 Good 98 January 2021 Good 98 Good 98 December 2020 Good 98 Good 98 November 2020 Good 98 Good 98 October 2020 Good 98 Good 98 September 2020 Good 98 Good 98 August 2020 Good 99 Good 98 July 2020 Good 98 Good 98 June 2020 Good 97 Good 98
View full article
Included in this article Overview Stopping Send Alerts for Anonymous leads Excluding Anonymous Leads entirely (use with caution) Deleting Lead Partitions Revised 2/19/2016 Added caution on "Lead Was Created" work around Added "Stopping Send Alerts" work around Added "Deleting Lead Partitions" Known issue Revised 2/17/2016 Marked "Lead Was Created" work around as under review 1. Overview The upgrade to anonymous leads is a two—step process. The first part removes the “Is Anonymous” filter and performs all other changes to the Marketo UI as outlined in the Changes Inside Marketo UI documentation here. The second part is the introduction of Munchkin V2. This piece is where the new lead promotion behavior is introduced as outlined in the Munchkin V2 Behavior documentation here. The changes to the Marketo UI removes access to anonymous leads, but they do still exist inside Marketo until the Munchkin V2 piece rolls out later this year. In the meantime between now and then, your smart campaigns will include these anonymous leads even though you won’t be able to access those leads. This can result in things like blank Send Alert emails going out for leads that can’t be accessed. This document will show you how to exclude those anonymous leads pending the Munchkin V2 release. 2. Stopping Send Alerts for Anonymous Leads The biggest problem Support has seen so far is with blank Send Alert emails being sent for anonymous leads that can’t be accessed. There is a very isolated use case when this occurs. The Send Alert flow step sends the email to the Lead Owner or the Account owner, but anonymous leads can’t be synced to SFDC, so the only time anonymous leads could have an Alert email sent is if the flow step is set to send “To Other Emails”. To stop anonymous leads from having the Alert email sent, add a choice to the flow step with the condition that if the Email Address is empty, do nothing. Since anonymous leads won’t have an email address, they will skip the flow step and the problem is resolved. This solution will not require any changes after the Munchkin V2 roll out later this year. Since the campaign replay process on lead promotion does not execute Send Alert flow steps (described in Anonymous Lead Promotion to Known Lead – Munchkin V2 Behavior and Anonymous Lead Upgrades – Under The Hood ), that replay process will not be affected. 3. Excluding Anonymous Leads (use with caution) When a lead becomes a known lead, a Lead Was Created activity is logged. If the lead is still anonymous, it will not have this activity in its activity log. Adding the “Lead Was Created” filter in your Smart Lists and Smart Campaigns will stop all anonymous leads from going through the campaign. Adding the filter Remove the Date of Activity constraint in the filter by clicking the X on the right side. This will make the filter look for the activity for all time. With this filter added like this, all leads that qualify will be known leads, and all anonymous leads that still exist will be ruled out. 4. Deleting Lead Partitions Until Munchkin V2 rolls out, anonymous leads still exist in the lead database even though they can’t be accessed. Lead partitions can’t be deleted if there are leads still in them and you’ll get this error: If you receive this error, the first step is to make sure these aren’t known leads. To do this, navigate to Admin > Workspaces & Partitions > Lead Partitions and click the “Show # of Leads” button. This will open up the column where you can view how many known leads are in the partition. Any leads showing up here will be known leads. Use a “Lead Partition” filter in a smart list to identify these leads, then move the leads to a different partition. Once this is done, if you have zero leads showing in the partition but still get the error saying you can’t delete the partition because it has leads, open a case with Marketo Support. The anonymous leads will need to be deleted on the back end by our Engineering team.
View full article
Issue Email get delivered initially but after a while, the email bounces stating 550 error. Solution This is a behavior of a particular type of Bounce called an Out of Band bounce ( OOB). The Send, Delivered and then Bounced sequence tells us that the email was initially accepted, but then due to a variety of reasons (or categories) it was rejected. This type of bounce is not uncommon, but are relatively rare. If you look at the lead record , you'll see that there will be an "Email Delivered" activity right before this bounce message which is what makes it "Out Of Band" . There isn't really any way Marketo can control it--it's entirely up to the recipient mail server. Many times this happens when a recipient mail server takes in emails in through a main server, then dumps them over to a secondary server. The first one that takes in the email gives back the "Email Delivered" message. Then the secondary server evaluates each email based on the spam filters and against known email addresses in their system. If the secondary server gets invalid email addresses or filtered out as spam, they'll then be bounced, causing the bounced message after the delivered message. 
View full article
If you ever need to change your CNAME there are a few things you should consider. Old Links In order to ensure that old links sent out via email are not broken, you should: Remove the old CNAME Setup your new primary CNAME Add the old one back in as a domain alias. You can use Add Additional Landing Page CNAMEs for detailed instructions on adding a secondary CNAME. This will allow all old links to still be functional. Cookies Our recommendation is to change the sub-domain so that cookies can be shared. If you change the top level domain itself, the cookies cannot be shared and every lead would have to re-introduce itself to the new domain by either clicking on a link in an email or filling out a form. Same top level domain go.mycompany.com > info.mycompany.com Good! Cookies are shared. Different top level domains go.mycompany.com > go.mynewcompany.com Bad! Cookies are not shared.
View full article
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
View full article
This article explains how to enable tracking if your Google AdWords ad is configured to link to any landing page on your website, which may or may not have a Marketo form on it. The destination landing page converts the URL parameters into cookies. The page with the form has embedded JavaScript code to read the cookies and insert the values to the appropriate hidden form fields. High-level Requirements Create custom PPC fields to capture the PPC information Add those fields as hidden fields to the Marketo form(s); configure the hidden fields to get their value from the URL Parameters Add parameters to your destination links in Google AdWords ads using static values or ValueTrack parameters; you can use the Marketo or Google URL builder to simplify this Decide on an 'original' or 'most recent' PPC source strategy[REQUIRES CODING] Add JavaScript code to convert URL parameters into cookies, on all landing pages you plan on linking the Google Ad to. If your PPC strategy is to capture original PPC source, then the custom PPC fields need to be configured to block field updates. If your PPC strategy is to capture the most recent PPC source, then you can use the default configuration (i.e. fields not blocked from updates). [REQUIRES CODING] Add JavaScript code to convert URL parameters into cookies, on all landing pages you plan on linking the Google Ad to. [REQUIRES CODING] On the form pages, JavaScript code needs to be added to read the cookie and then pass the information to the appropriate PPC hidden field on form submission. Enter PPC program period (monthly) cost information Instructions Create the custom fields in Salesforce.com on both the lead and contact object, making sure they map from lead to contact. The custom fields will sync over to Marketo mapped 2 Salesforce.com fields to 1 Marketo field. For instructions to create Salesforce.com custom fields, please reference Salesforce.com knowledgebase or work with your Salesforce.com Administrator. The custom fields to be created Campaign Source (utm_source) Required. Use utm_source to identify a search engine, newsletter name, or other source. Example: utm_source=google Campaign Medium (utm_medium) Required. Use utm_medium to identify a medium such as email or cost-per-click. Example: utm_medium=cpc Campaign Term (utm_term) Used for paid search. Use utm_term to note the keywords for this ad. Example: utm_term=running+shoes CampaignID (utm_campaign) Used for keyword analysis. Use utm_campaign to identify a specific product promotion or strategic campaign. This can be used to capture the Adwords CampaignID Example: utm_campaign=spring_sale Create a Marketo program (i.e. Google Adwords Program) and use a program channel (i.e. custom 'Google Adwords' channel) with 'convert' as the success progression status.Create a Marketo form with all the above custom fields on the forms as 'hidden fields' and call this 'PPC Form' Make sure you assign the associated period costs for this program on the setup tab. You will need to do this on a monthly basis; this is required if you want to get a 'cost per' anaylsis. Create a Marketo landing page and include the PPC Form on this landing page. Include code to get parameters from cookies Capturing Search Engine and PPC info on Landing Pages https://nation.marketo.com/docs/DOC-1101 For all landing pages you plan on linking your Google Adword to as the 'destination link', you need to include code to convert URL parameters value to cookies Add the key values and parameter tokens to the URL. In the example below, the first URL is the destination URL you want to use, and the second URL includes the URL parameters and associated values/tokens. URL: http://www.mycompany.com/GreatProducts.html Tagged URL:http://www.mycompany.com/GreatProducts.html?utm_source=AdWords&utm_medium=PPC&utm_term={keyword}&utm_content={creative} When configuring your Google Ad, use the tagged URL as the destination link which takes the lead who clicks on the Google Ad to the landing page. The keyword and CampaignID will be passed automatically when the lead clicks through the Google Adwords ad. The Source (Adwords) & medium (PPC) will be passed as the values in the tagged URL Learn more: Google Adwords and Marketo Overview Linking a Google Adwords Ad to a Marketo Landing Page with a Form Google Adwords and Marketo FAQs
View full article
Using the Marketo SOAP API, you can check whether or not your website visitors have filled out a form and present them content accordingly. The following code below is unsupported and is intended to help you develop your own solution. In the resources section of the Marketo website, we use this method for our premium content. For leads who have already registered, their links go directly to the resource. Leads who haven't registered are given links to a landing page. In both cases, the link appears the same. Behind the scenes, a cookie is used to store whether or not this lead has registered: If the user has the premium registration cookie, the premium links are shown. If the user does not have that cookie, the lead's record is retrieved via the SOAP API. Based on the lead's record: If the lead has a valid email address, the premium content links are shown and the premium registration cookie is set. If not, the premium content links are not shown. Instead, they take leads to a landing page to fill out a form. First, you'll need to develop a SOAP API connection to Marketo. The attached ZIP file has a sample connection PHP file. You'll need to make the following changes in this file: ... $this->access_key = 'Your API Access Key Goes Here'; $this->secret_key = 'Your Secret API Key Goes Here'; // // The endpoint is in the "SOAP API Setup" page in the Marketo Admin section // ex. $soap_end_point = 'https://xx-1.marketo.com/soap/mktows/'; // $soap_end_point = 'Your SOAP API End Point URL Goes Here'; // // Errors are sent to this email address. Your web server // must be configured to send email for this to work correctly. // // ex. $this->error_email_address = 'example@example.com'; // $this->error_email_address = 'Put your debug email address here'; ... After creating your SOAP API connection, the next step is to implement the logic that determines which content to show if the user is logged in or not. The get_premium_url_status() function returns true if the lead has the premium cookie or if they've filled out a form. Otherwise, it returns false. You can use that result to determine what content the lead should see. The attached ZIP file has a PHP file that contains an example of this check.
View full article
If you sent an email from the Lead Database (as a Single Flow Action), as part of a campaign, or as a test email but didn't receive it, here are some tips. Check the "From:" address When sending a test message, make sure to check the "From:" address setting on your message. To do this, go to the Email Settings tab of the email editor. In the "From:" field, make sure that you either have a single valid email address, or a valid email address as the default. Many people want to send their messages from the lead owner. When you use the send test feature, the email address you are sending to doesn't have a full lead record, and so it doesn't have a lead owner. Since Marketo cannot send an email with no "From:" address, test messages without a valid email address in the "From:" field will not send. Send as a Lead If you have verified that the email had a valid From: address and you still aren't getting it, make sure to create yourself as a lead and send using a flow action. See if the mail was sent If you sent the email as part of a campaign or Single Flow Action, check the campaign's Results tab or your lead detail page to see if that mail was already sent to you. If it hasn't been sent yet, try waiting a little while longer. Check your Junk Mail In your email client, check your Junk Mail or Spam folder to see if the mail landed there. If it did, you should change the content of your email. Check your corporate spam filter Your corporate mail server may have blocked emails from Marketo; you should contact your IT department to see if this is the case. Please see our instructions for whitelisting Marketo's email servers: Add Marketo to Your Corporate Email Whitelist​ Try sending to a different recipient If you sent the original mail to your corporate account, try sending to a personal account on Yahoo or Gmail. If you sent it to a personal account, try your corporate mail account.  Use Marketo's Email Deliverability product The Email Deliverability PowerPack , with Design Informant and Inbox Informant, can warn you when your mail is being rejected because of its content and help you identify junk mail pitfalls. Also, using Domain Keys and SPF improve the chances of your email landing in your leads' inboxes. Contact Marketo If you still can't figure out what happened contact Marketo to see if we can help.
View full article
Included in this article   Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details   Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen .   Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces.   Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist.   Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL).   Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes   Building the Directory   1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo   2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program   3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List   4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign     Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails.   Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason.   Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads.   Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}}   Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}}   Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}}   Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1   Flow Step 5: Add to List List Name: “Active Bounce List”   Smart Campaign Two - Remove Leads From the List After Successful Deliveries   Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards.     Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List".   Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}}   Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1   Flow Step 3: Remove from List List Name: Operational.Active Bounce List   5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here  
View full article
Issue Description Integration is not able to see a webinar that has been set up as a "Simulated Live" record type in GoToWebinar Issue Resolution This is not currently possible as the Launchpoint integration between GoToWebinar and Marketo does not utilize version 2 of the GoToWebinar API and v2 is required for "simulated live"  (recorded) webinars. Who This Solution Applies To Customers integrated with GoToWebinar
View full article
Issue You receive an error "Salesforce Sync Error: Daily API Limit Reached" or " TotalRequests Limit Exceeded" Solution The API limit for Salesforce is determined by your Salesforce agreement.  The Marketo sync bundles updates to minimize API calls, but depending on the amount of data you need to sync and your Salesforce API limit, you may encounter this error.  To minimize the number of API calls made to Salesforce by your Marketo instance, try the following: Avoid "Sync to SFDC" flow steps.  These require one API call per lead. Use the Marketo Program to SFDC Campaign sync to add people to SFDC Campaigns Use Salesforce assignment rules to route leads and contacts rather than using Marketo to update lead ownership   To see your Salesforce API limit (per 24 hour period) and your current usage (for past 24 hours) in SFDC, Navigate to: Setup > Administration Setup > Company Profile > Company Information Look for the field called "API Requests, Last 24 Hours" This will display API usage for the past 24-hour period as well as your current 24-hour limit (in parenthesis).   Who This Solution Applies To Customers integrated with Salesforce    
View full article
Issue You want to edit a campaign flow after initiating the run, but there are already members running through the flow in the wait steps. Solution Generally speaking, it is best to not edit the flow of a campaign after activating/initiating. Example: Let's say that a particular campaign has 3 flow steps: Change program status Wait 2 days Send email And you would like to add a new step in between 1&2, so the new flow would be Change program status Change score Wait 2 days Send email If you add a new Flow step above a wait step, the wait step shifts down. However, currently there are leads waiting the designated 2 days (Flow step #2). ( It's helpful to think about wait steps like buckets. Once a lead enters the flow step, the wait duration is calculated, and the lead waits there in that flow step bucket for that amount of time.)   If the campaign was initiated, and a lead entered Flow step #2 and began waiting 2 days, and then you add an additional step above, the Wait 2 days becomes Flow step #3. Now when the leads are done waiting 2 days in Flow Step #2 bucket, then they exit and progress to #3. Even though the actual wait step shifts from #2 to #3, the lead records are still in Step #2 bucket, and they do not shift from #2 to #3, meaning they are now waiting an additional 2 days.   Solution: The solution here is to create a new campaign with the desired flow steps for the same membership (same Smart List), and then run a "Remove from Flow" single action by clicking the following in the old campaign (the one you wanted to edit):   View Campaign Members > Select All > Person Actions > Special > Remove from Flow. In the Run Action dialog box, click on "is" and change to "this campaign". Click "Run Now". After removing these members, they will not progress further into the old campaign flow, and now the new campaign is ready to be activated/initiated.    
View full article
Issue Description You wish to use all features of Revenue Explorer reporting and need to set up your instance to pass the necessary information to RCE Issue Resolution In order to use all the features of Revenue Explorer, the following tasks should be completed. Each one notes the report type it applies to. 1.) Set relevant Channel Tags Analytics Behavior as 'Inclusive (regardless of Period Cost)' (all RCE analysis areas) 2.) Review and establish appropriate statuses and successes for relevant Channel Tags (Opportunity Analysis; Program Membership Analysis; Program Opportunity Analysis; Program Cost Analysis) 3.) Ensure that the appropriate statuses are being set within the Marketing Programs' smart campaign flow. In other words, based on certain actions, changing the assigned program statuses to leads in some unified manner to ensure Success statuses are set for programs of the same Program Tag/Channel Tag. (Opportunity Analysis; Program Membership Analysis; Program Opportunity Analysis; Program Cost Analysis) 4.) Assign Program Tags to programs to ensure accurate data in reporting. You can even assign past programs with current Tags, and the data will be made available to Revenue Explorer (bearing in mind the 24 hour sync delay of data) (Email Analysis; Program Membership Analysis; Program Cost Analysis; Program Opportunity Analysis; Program Revenue Stage Analysis) 5.)Assign Period Costs to Marketing Programs based on the cost it takes to run the program. (Program Cost Analysis; Program Revenue Stage Analysis; Program Opportunity Analysis) 6.) Build a Revenue Cycle Model that reflects the flow of your business - http://docs.marketo.com/display/public/DOCS/Revenue+Cycle+Models (Model Performance Analysis (Companies); Model Performance Analysis (Leads); Program Revenue Stage Analysis) Complete the steps that apply to the types of reporting you are interested in. For example, if you would be interested in using Program Cost Analysis, then you would want to complete steps:1, 2, 3, 4, and 5 to get the full capabilities from the tool. If you were interested in Program Membership Analysis, you would complete steps: 1, 2, 3, and 4. Who This Solution Applies To Customers with Revenue Explorer Is this article helpful ? YesNo
View full article
Issue If your Smart Lists are processing slowly, you may be able to speed them up using Segmentations for exclusion lists.     Solution Many companies maintain email exclusion lists based on a number of criteria. In Marketo, these are often set up using Smart Lists that are then referenced in "Member of Smart List" filters. However, Smart Lists that reference other Smart Lists can be slow to resolve. Using a Segmentation for your exclusion lists instead of Smart Lists can help your campaigns and programs run more efficiently. Instructions for setting up Segmentations can be found here: http://docs.marketo.com/display/public/DOCS/Create+a+Segmentation .  You can then use the Segmentation filters in your Smart List rather than the "Member of Smart List" filters: http://docs.marketo.com/display/public/DOCS/Use+Segment+Filters+in+a+Smart+List .
View full article
Image: Step Flow for Predictive Content for Web and Email What is Auto Content Discovery? This post explains the first part of the flow image above: discovering, mapping and tracking your content assets. Content Discovery is used in the Predictive Content app to auto-discover all the content assets (videos, pdf, blog posts, press releases, white papers, etc.) on a website/domain. Once discovered, you have the ability to see how your content is performing and to decide which pieces of content should be prepared, approved and enabled for the Predictive Content outcomes on web (either in the recommendation bar or rich media) and email.   Setting up Predictive Content and Content Discovery See Set Up Docs: http://docs.marketo.com/display/public/DOCS/Getting+Started+with+Predictive+Content Steps RTP Javascript tag is installed on all your web pages (Note: RTP is now called Web Personalization) Set Asset Discovery to On Asset Discovery auto-discovers extensions (PDFs, PPT, MP4, OFF, WEBM) and a click/view on embedded videos (Youtube, Vimeo, Wistia) Create URL Patterns Setting URL patterns auto-discovers content when a web visitor clicks on the HTML web page relevant to the content pattern The URL syntax pattern determines your ability to optimally use this feature (e.g., to create a pattern for press releases, your press releases should all be stored on a page identified as www.yoursite.com/press-releases/*). How is content auto-discovered? The content discovery technology uses an event listener that runs on every web page (where the RTP Javascript tag is installed) and waits for a web visitor to click on a URL link or arrive directly on that web page in a browser. If that link includes an extension (PDF, ppt, embedded video) or matches the URL pattern defined, then it will be discovered and added to the All Content page in the Predictive Content app.   Only content pieces that a web visitor interacted with (clicked on or viewed) once the RTP Javascript tag has been installed are discovered via Content Discovery. If the content is already discovered, then it will add to the tracking and views of those discovered content pieces. You can also manually add new content to be listed and tracked in the All Content page.   Image: All Content Page in the Predictive Content app displaying and tracking all discovered content What data is discovered? Visitor Data (Used for Analytics + Predictive Algorithm) Pages Viewed  - number of page views by the user in the session Visit Count for Web Visitor Last Content URL Seen Last 5 Content Assets clicked via Predictive Content that have been seen by this visitor in last 90 days Last Web Campaigns Seen - 10 last campaigns per session (within the last 5 sessions) Inferred Organization Inferred, Industry, Size, Revenue Inferred Country, State, City Search Term   Content Data   Extensions Video (Youtube, Vimeo, Wistia) Video Name Video URL Video Image URL PDF PDF Name PDF URL   URL Patterns (HTML pages) Found via metadata of the HTML page Content Name Content URL Content Image URL Content Description What data is auto-populated during the auto-discovery phase? Based on the content data we discover, the aim is to populate as much of the Predictive Content as possible, making it quicker, easier and involving less prep work for you. However, you do still need to review the discovered content, then approve and enable it for the Predictive Source (Email, Rich Media, Recommendation Bar). Assuming we discover an HTML page defined in URL patterns, this HTML content piece will be populated in the following fields in Predictive Content:   Predictive Content Fields Auto-Populated Value Notes Content Name (Content Name) Unique Value Content URL (Content URL) The URL is consistent for all sources (email, bar, rich media) Categories Video OR Category Name from URL Pattern If Video discovered, the category is populated as Video. Category populated from defined URL Pattern. e.g. Marketo.com/blog = Blog all discovered content based on this URL will receive Blog as a category Category is consistent for all sources (email, bar, rich media) Content Title (Content Name)   Email Title (Content Name)   Email URL (Content URL)   Email Image URL (Content Image URL)   Email Button Label Read More Not Auto-populated. Default is "Read More". Rich Media Title (Content Name)   Rich Media URL (Content URL)   Rich Media Image URL (Content Image URL)   Rich Media Description (Content Description)   Bar Title (Content Name)   Bar URL (Content URL)       Image: Example of Populating Metadata for HTML content into Predictive Content
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
Question: Will the munchkin tracking code work on different sites? For example, my company has 2 domains DomainA.com DomainB.com. DomainB.com is a separate site for our blog. Will the munchkin code work on the 2nd site? I want to incorporate the 2nd site into my lead scoring measures. Answer: Munchkin CAN pass domains, however what it can not do is bring across information. Thus, if you have a domain of A, when a known lead passes out of domain A and into domain B, its activity will be tracked, however, it will be tracked anonymously. In addition, there will be no way to link the activity of a known lead in Domain A to the anonymous lead in Domain B, even though they're the same lead. The next step to tie the activity to one lead would be to do one or more of the following: Manually merge the separate anonymous leads Nurture the lead under each domain, send emails with tracked links to each domain, the activity will be tied together under that lead and automatically merged.  
View full article
Wait steps allow you to “pause” a lead’s progression through a campaign’s flow.  This article will explain how this is accomplished, and help guide you around some common pitfalls when using wait steps.   When a lead encounters a wait step in your campaign’s flow it is “stamped” with the information contained in that step.  Think of it like a rubber stamp marking each lead with the time it should resume its movement through the flow.  The stamp also marks the lead with the next step in the flow, so it knows what to look for when its wait time is up. In the example below, leads will be sent an email from Step #1 then stamped by Flow Step #2 with “Resume on January 30 th at 10 AM.  Look for Step #3” which will then set aside these leads.  They don’t leave the flow, but they’re no longer still in Flow Step #2 either. Next, we’ll look at some situations you might run into when using Wait Steps.  It’s best to think through your flow and make any changes before you initiate your campaign, but here’s what to do if you need to make changes to an active flow.   Keep in mind that in a batch campaign all leads will move through the flow together, so they would all reach the wait step together and would all be stamped with the same information.  In a trigger campaign though, leads are more likely to have triggered the campaign at different times, and will be in different places along the flow. Is this article helpful ? YesNo
View full article
Included in this article Overview Marketo uses a set of fields to capture certain kinds of marketing related information. If you would like this data in Salesforce, please follow the instructions below. Create three custom fields in Salesforce on the lead and contact objects: Lead Score, Acquisition Program, and Acquisition Date. Map these custom fields between leads and contacts so that on conversion in Salesforce, the values carry over. You can create other additional fields, if necessary (see the table below). All of these custom fields are optional and are not required to sync Marketo and Salesforce. As a best practice, we recommend that you do create fields for Lead Score, Acquisition Program, and Acquisition Date. Add Marketo Fields to Salesforce Add three custom fields on the lead and contact objects in Salesforce listed above. If you want to add more, see the table of available fields at the end of this section. Perform the following steps for each of the three custom fields to add them. Start with Lead Score. 1. Log into Salesforce and click Setup . 2. In the Build menu on the left, click Customize and select Leads . Click Fields . 3. Click New in the Custom Fields & Relationships section at the bottom of the page. 4. Choose the appropriate field type (for Lead Score — number ; Acquisition Program — text ; Acquisition Date — Date/Time ). 5. Click Next . 6. Enter the Field Label, Length, and Field Name for the field, as shown in the table below. Field Label Field Name Data Type Field Attributes Lead Score mkto71_Lead_Score Number Length 10 Decimal Places 0 Acquisition Date mkto71_Acquisition_Date Date/Time Acquisition Program mkto71_Acquisition_Program Text Length 255 7. Click Next . 8. Specify the access settings and click Next : Set all profiles to Visible and "Read-Only". Uncheck "Read Only" for the profile of your sync user. Often customers have a user with the profile of a System Administrator as the sync user. If that's the case with you, then uncheck “Read Only” for the System Administrator profile as shown in the picture below. If you have created a custom profile for the sync user, then uncheck "Read-Only" for that custom profile 9. Choose the page layouts that should display the field. 10. Click Save & New to go back and create each of the other two custom fields. Click Save when you're done with all three. 11. In the Build menu on the left, click Customize and select Contacts. Click Fields . 12. Perform steps 3 through 10 for the Lead Score, Acquisition Date, and Acquisition Program fields on the contact object, just as you did for the lead object. 13. Optionally, use the above procedure for any additional custom fields from this table.      NOTE: These fields are additional optional fields you may choose to add as well. The Lead Score, Acquisition Date and Acquisition Program fields      are detailed above Field Label Field Name Data Type Field Attributes Acquisition Program Id mkto71_Acquisition_Program_Id Number Length 18 Decimal Places 0 Original Referrer mkto71_Original_Referrer Text Length 255 Original Search Engine mkto71_Original_Search_Engine Text Length 255 Original Search Phrase mkto71_Original_Search_Phrase Text Length 255 Original Source Info mkto71_Original_Source_Info Text Length 255 Original Source Type mkto71_Original_Source_Type Text Length 255 Inferred City mkto71_Inferred_City Text Length 255 Inferred Company mkto71_Inferred_Company Text Length 255 Inferred Country mkto71_Inferred_Country Text Length 255 Inferred Metropolitan Area mkto71_Inferred_Metropolitan_Area Text Length 255 Inferred Phone Area Code mkto71_Inferred_Phone_Area_Code Text Length 255 Inferred Postal Code mkto71_Inferred_Postal_Code Text Length 255 Inferred State Region mkto71_Inferred_State_Region Text Length 255 Map Custom Fields for Conversions A custom field on the lead object in Salesforce should be mapped to a contact field on the contact object so that data is carried over when a conversion occurs.  1. In the top right corner, click Setup . 2. Type "Fields" into the Nav Search without pressing Enter. Fields appears under different objects; Click Fields under Leads. 3. Go to the Lead Custom Fields & Relationships section and click Map Lead Fields . 4. Click the drop-down next to the field you want to map. 5. Select the corresponding contact custom field. 6. Repeat the above steps for any other fields you've created. 7. Click Save when you're done. Here's a video of the entire process that should make it easy to follow along: Salesforce Connector Setup
View full article