Knowledgebase

Sort by:
  Syntax Recommendations Common Look Up mechanisms Common Modifiers Too Many Mechanisms Character String Too Long Null Records in the SPF Record Repetitive Records in the SPF Record - Void Lookups Validation Tools Syntax Recommendations Common Look Up mechanisms a: mx: include: ip4: ip6: exists: ptr: all Common Modifiers redirect= exp=   An A Record must ALWAYS contain IP address (map host to IP) CNAME (Alias) must contain hostnames. No IPs here NS an MX records must contain host names. No IPs allowed. MX records (for mail servers)  should contain hostnames NOT IPs. Too Many Mechanisms Section 10.1, "Processing Limits" of the SPF RFC 4408 specifies the following in regards to DNS lookups: SPF implementations MUST limit the number of mechanisms and modifiers that do DNS lookups to at most 10 per SPF check, including any lookups caused by the use of the "include" mechanism or the "redirect" modifier.  If this number is exceeded during a check, a PermError MUST be returned.  The "include", "a", "mx", "ptr", and "exists" mechanisms as well as the "redirect" modifier do count against this limit.  The "all", "ip4", and "ip6" mechanisms do not require DNS lookups and therefore do not count against this limit. The "exp" modifier does not count against this limit because the DNS lookup to fetch the explanation string occurs after the SPF record has been evaluated. This limit is in place to prevent SPF lookups from being a useful avenue for Denial of Service attacks. Using an example SPF record as an example to illustrate, this record was breaking with 12 look-ups: example.com text = "v=spf1 include:_spf-a.example.com include:_spf-b.example.com include:_spf-c.example.com include:_spf-ssg-a.example.com include:spf-a.anotherexample.com ip4:131.107.115.215 ip4:131.107.115.214 ip4:205.248.106.64 ip4:205.248.106.30 ip4:205.248.106.32 ~all" [ 5 mechanisms] _spf-a.example.com  text = "v=spf1 ip4:216.99.5.67 ip4:216.99.5.68 ip4:202.177.148.100 ip4:203.122.32.250 ip4:202.177.148.110 ip4:213.199.128.139 ip4:213.199.128.145 ip4:207.46.50.72 ip4:207.46.50.82 a:mh.example.m0.net ~all"  [ +1 = 6 mechanisms] mh.example.m0.net a = 209.11.164.116 _spf-b.example.com text = "v=spf1 include:spf.messaging.example.com ip4:207.46.22.35 ip4:207.46.22.98 ip4:207.46.22.101 ip4:131.107.1.27 ip4:131.107.1.17 ip4:131.107.65.22 ip4:131.107.65.131 ip4:131.107.1.101 ip4:131.107.1.102 ip4:217.77.141.52 ip4:217.77.141.59 ~all" [+1 = 7 mechanisms] spf.messaging.example.com text = "v=spf1 include:spfa.anotherexample.com include:spfb.anotherexaple.com include:spfc.anotherexample.com -all"  [+3 = 10 mechanisms] spfa.anotherexample.com  text = "v=spf1 ip4:157.55.116.128/26 ip4:157.55.133.0/24 ip4:157.55.158.0/23 ip4:157.55.234.0/24 ip4:157.56.112.0/24 ip4:157.56.116.0/25 ip4:157.56.120.0/25 ip4:207.46.100.0/24 ip4:207.46.108.0/25 ip4:207.46.163.0/24 ip4:134.170.140.0/24 ip4:157.56.110.0/23 -all" [+0 = 10 mechanisms] spfb.anotherexample.com  text = "v=spf1 ip4:207.46.51.64/26 ip4:213.199.154.0/24 ip4:213.199.180.128/26 ip4:216.32.180.0/23 ip4:64.4.22.64/26 ip4:65.55.83.128/27 ip4:65.55.169.0/24 ip4:65.55.88.0/24 ip4:94.245.120.64/26 ip4:131.107.0.0/16 ip4:157.56.73.0/24 ip4:134.170.132.0/24 -all" [+0 = 10 mechanisms] spfc.anotherexample.com  text = "v=spf1 ip4:207.46.101.128/26 ip6:2a01:111:f400:7c00::/54 ip6:2a01:111:f400:fc00::/54 ip4:157.56.87.192/26 ip4:157.55.40.32/27 ip4:157.56.123.0/27 ip4:157.56.91.0/27 ip4:157.55.206.0/24 ip4:157.55.207.0/24 ip4:157.56.206.0/23 ip4:157.56.208.0/22 -all" [ +0 = 10 mechanisms] _spf-c.example.com  text = "v=spf1 ip4:203.32.4.25 ip4:213.199.138.181 ip4:213.199.138.191 ip4:207.46.52.71 ip4:207.46.52.79 ip4:131.107.1.18 ip4:131.107.1.19 ip4:131.107.1.20 ip4:131.107.1.48 ip4:131.107.1.56 ip4:86.61.88.25 ip4:131.107.1.44 ip4:131.107.1.37 ~all" [+0 = 10 mechanisms] _spf-ssg-a.example.com  text = "v=spf1 include:_spf-ssg-b.example.com include:_spf-ssg-c.example.com ~all"  [+2 = 12 mechanisms] _spf-ssg-b.example.com  text = "v=spf1 ip4:207.68.169.173/30 ip4:207.68.176.1/26 ip4:207.46.132.129/27 ip4:207.68.176.97/27 ip4:65.55.238.129/26 ip4:207.46.222.193/26 ip4:207.46.116.135/29 ip4:65.55.178.129/27 ip4:213.199.161.129/27 ip4:65.55.33.70/28 ~all"  [+0 = 12 mechanisms] _spf-ssg-c.example.com text = "v=spf1 ip4:65.54.121.123/29 ip4:65.55.81.53/28 ip4:65.55.234.192/26 ip4:207.46.200.0/27 ip4:65.55.52.224/27 ip4:94.245.112.10/31 ip4:94.245.112.0/27 ip4:111.221.26.0/27 ip4:207.46.50.221/26 ip4:207.46.50.224 ~all" [+0 = 12 mechanisms] spf-a.secondexample.com  text = "v=spf1 ip4:157.55.0.192/26 ip4:157.55.1.128/26 ip4:157.55.2.0/25 ip4:65.54.190.0/24 ip4:65.54.51.64/26 ip4:65.54.61.64/26 ip4:65.55.111.0/24 ip4:65.55.116.0/25 ip4:65.55.34.0/24 ip4:65.55.90.0/24 ip4:65.54.241.0/24 ip4:207.46.117.0/24 ~all" [+0 = 12 mechanisms] Character String Too Long 255 character limitation in a single string https://kb.isc.org/article/AA-00356/0/Can-I-have-a-TXT-or-SPF-record-longer-than-255-characters.html http://www.string-functions.com/length.aspx You may have more than 255 characters of data in a TXT or SPF record, but not more than 255 characters in a single string. If you attempt to create an SPF or TXT record with a long string (>255 characters) in it, BIND will give an error (e.g. "invalid rdata format: ran out of space".)  Strings in SPF and TXT records should be no longer than 255 characters.  However to get around this limitation, per RFC 4408 a TXT or SPF record is allowed to contain multiple strings, which should be concatenated together by the reading application.  In the case of use for SPF (using either TXT or SPF RRs) the strings are concatenated together without spaces as described below.  Reassembly by other applications of multiple strings stored in TXT records might work differently. 3.1.3. Multiple Strings in a Single DNS record As defined in [RFC1035] sections 3.3.14 and 3.3, a single text DNS record (either TXT or SPF RR types) can be composed of more than one string. If a published record contains multiple strings, then the record MUST be treated as if those strings are concatenated together without adding spaces. For example: IN TXT "v=spf1 .... first" "second string..." MUST be treated as equivalent to IN TXT "v=spf1 .... firstsecond string..." SPF or TXT records containing multiple strings are useful in constructing records that would exceed the 255-byte maximum length of a string within a single TXT or SPF RR record. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26  ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all“ text = "v=spf1 ip4:199.15.212.0/22“ " ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24" " ip4:72.32.243.0/24 ip4:94.236.119.0/26" " ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all" Null Records in the SPF Record A record that is NULL or that does not exist will break an SPF record.  Syntax within the record is very important, if there are extra spaces between mechanisms it will count as NULL. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22“ <- accurate text = "v=spf1 ip4: 199.15.212.0/22“ <- NULL (NOTE the space between IP4: and the IP) Repetitive Records in the SPF Record - Void Lookups If there are too many repetitive mechanisms in the SPF record, including records that cascade (for example when using "include:") the record will break. There is a MAX of 2 void look ups in an SPF record.  More than that and the record will break.  This prevents SPF records from being used in Denial of Service style attacks. Validation Tools SPF checker, syntax validator and SPF tester http://www.kitterman.com/spf/validate.html SPF checker http://vamsoft.com/support/tools/spf-policy-tester SPF validator http://vamsoft.com/support/tools/spf-syntax-validator CIDR Calculator http://www.subnet-calculator.com/cidr.php Nslookup http://network-tools.com/nslook/ SPF creation wizard http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/ Common SPF errors http://www.openspf.org/FAQ/Common_mistakes SPF syntax definitions http://www.openspf.org/SPF_Record_Syntax
View full article
Marketo has the ability to see and pull data from Salesforce Formula fields, there is however a catch which will be explained in this article.   Everytime the Marketo Sync connects to Salesforce it will scan records and look at the "SytemModStamp" (salesforce system field) for each one of them. It will compare this value with the stored value, which was pulled at the last scheduled sync. If the values match, Marketo will move on to the next record. If the values are different (new value later date than previous value), then Marketo will do a compare and contrast of all fields on that record in both systems and update the information as needed.   When a normal non-formula field is updated and changed on a Lead/Contact record in SFDC, the SytemModStamp value is updated. This is how on next sync Marketo knows to do a compare/contrast check and pull updates. Formula fields do not behave the same way. A formula field is calculated based on data in fields called upon in the formula; this means that the formula field calculation itself will not update the SytemModStamp in Salesforce.   Chances are you already have existing records in SFDC and Marketo. If you were to create a formula field today in your instance of SFDC and have it sync down into Marketo, the data calculated for the formula field in SFDC will not come into Marketo right away. The reason for this is, the formula field has created data based on already existing data, this does not result in a SytemModStamp change.   Typically formula fields will be a calculation of data from fields which are somehow related to the lead/contact record. This means that moving forward, any change in the normal field, will result in a SytemModStamp change as well as a recalculation of the formula field. In this case, Marketo will see the updated SytemModStamp due to the normal field change. Marketo will do the compare/contrast excercise and find that the formula field also needs updating.   If you create a formula field in SFDC and would like to have all the historical data for the formula field to come into Marketo, you can force an update on the records in SFDC to update the SytemModStamp. This way, on next sync, Marketo will see the formula data and pull it in. Alternatively, you can simply allow for natural SytemModStamp updates in SFDC to occur which should result in a slow trickle of historical data from SFDC into Marketo for the newly created formula field.   You can only use data from a formula field in Marketo to segment data and filter. If you try to do a change data value, Marketo will accept the change, tries to sync it to Salesforce and fails to update there. Eventually the Salesforce calculated value will come back into Marketo. Is this article helpful ? YesNo
View full article
Issue: With long options in a select (dropdown) list, Internet Explorer will not expand the values as Firefox, Chrome and other browsers will do. This makes reading the values in the dropdowns impossible.   Solution: Insert the following Javascript/CSS in a Custom HTML box on your landing page. This script will only run if IE is used.   <script src="/js/public/jquery-latest.min.js" type="text/javascript"></script> <script type="text/javascript"> var $ = jQuery.noconflict();     $(document).ready(function() {   if ($.browser.msie) {   $('select.mktFormSelect')   .bind('focus mouseover', function() {   $(this).addClass('expand').removeClass('clicked');   $(this).parents('li').addClass('liexpand'); })   .bind('click', function() { $(this).toggleClass('clicked'); })   .bind('mouseout', function() { if (!$(this).hasClass('clicked')) {   $(this).removeClass('expand');   $(this).parents('li').removeClass('liexpand'); }})   .bind('blur', function() {   $(this).removeClass('expand clicked');   $(this).parents('li').removeClass('liexpand'); });   }   }); </script>     <style type="text/css">   select.expand { width: auto !important; position: absolute; } li.liexpand { padding-bottom: 22px !important; padding-bottom: 9px !important\9; } *+html li.liexpand { padding-bottom: 9px !important; } </style>   Is this article helpful ? YesNo
View full article
Issue There are two filters available (Acquisition Program and Acquisition Program Name), but only Acquisition Program Name appears in the lead record and is available as a column in the lead views.  What is the difference between these? Solution Acquisition Program is a system-managed field. It isn't available in many picklists, nor in certain filters. Acquisition Program Name is a field that allows you to use this data more freely as it is not locked by the system. Acquisition Program = Master naming for programs Acquisition Program Name = Friendly usable name    
View full article
Distributing leads to sales reps is easy.  Marketo, however, only supports random distribution.  This gives a pretty good approximation of the round robin technique.   Prerequisites: Create A New Program Create A Child Campaign      1. Go to the Smart List tab of the campaign you created, find and drag in the Lead is Created trigger. Tip: Use the trigger that logically would come right before you want to assign the lead to a rep. This is a article attached image        2. I've added the constraint "SFDC Type is empty" so that records that already exist in Salesforce do not get re-assigned.          3. Go to the Flow tab, find and drag in the Change Owner flow step.      4. If you have 3 lead owners click on the Add Choice button 2 times.  You always want the number of choices to equal the number of owners in the round robin minus one. This is because the last person goes in the Default slot.      5. Find and select Random Sample.      6. 100% divided by 3 sales reps is 33%, enter "33".      7. Find and select the first sales rep.      8. Repeat steps 4, 5 and 6 for every remaining choice. Be sure to fill out the default choice also. This is a article attached image        9. Activate the campaign and it should now distribute leads randomly to your lead owners.
View full article
Issue Below are the fields in SFDC that are required by Marketo to sync an object.  Fields in () are fields additional fields that are required if you also have Sales Insight configured. Also specified are the fields that can be updated by Marketo.  The rest of the listed fields only need to be "Read-only" for the purposes of the sync. If any of these fields are not visible to the Marketo Sync user, you will see sync failures indicating that a required field is missing.  To fix this, have your SFDC admin update the permissions level for the field(s) for the sync user's profile.   Solution Lead Fields: IsConverted, ConvertedDate, ConvertedAccountId, ConvertedContactId, ConvertedOpportunityId, status, OwnerId, IsDeleted, MasterRecordId, Id, SystemModstamp, CreatedDate, Name, Email, (Company, Owner.Name) Can be updated from Marketo: status, Name (via first/middle/last name), Email.    Contact Fields: AccountId, OwnerId, IsDeleted, MasterRecordId, Id, SystemModstamp, CreatedDate, Name, Email, (Owner.Name, Account.Name) Can be updated from Marketo: Name (via first/middle/last name), Email   Account Fields: OwnerId, IsDeleted, MasterRecordId, Id, SystemModstamp, CreatedDate, ParentId, Name Sync is one-way only by default so Marketo doesn't make changes to your account records. If two-way sync is turned on (e.g. for Person Accounts), Marketo can update Name.   User Fields: AccountId, CreatedDate, Email, Id, ManagerId, SystemModstamp, UserType Sync is one-way only by default so Marketo doesn't make changes to your user records.   Opportunity Fields: Id, IsDeleted, SystemModstamp, AccountId, CampaignId, CreatedDate, IsClosed, IsDeleted, IsPrivate, IsWon, Name, OwnerId, Probability, StageName, SystemModstamp, (LastModifiedDate) Sync is one-way only by default so Marketo doesn't make changes to your opportunities.   Opportunity Contact Role Fields: ContactId, CreatedDate, Id, IsDeleted, IsPrimary, OpportunityId, SystemModstamp Sync is one-way only by default so Marketo doesn't make changes to the contact roles for your opportunities.   Campaign Fields: Id, IsDeleted, SystemModstamp, CampaignMemberRecordTypeId, CreatedDate, IsActive, IsDeleted, Name, OwnerId, ParentId, Status, Type Sync is one-way only by default so Marketo doesn't make changes to your SFDC campaigns.   Campaign Member CampaignId, ContactId, CreatedDate, Id, IsDeleted, LeadId, Status, SystemModstamp Can be updated from Marketo: Status   Campaign Member Status Fields: CampaignId, CreatedDate, Id, IsDefault, IsDeleted, SystemModstamp   Tasks Fields: Status, SystemModstamp, IsDeleted, CreatedDate, WhoId, OwnerId, WhatId, AccountId, IsClosed, IsArchived, IsReminderSet, RecurrenceActivityId, IsRecurrence, Id, SystemModstamp, Subject   Event Fields: CreatedDate, Id, IsDeleted, OwnerId, Subject, SystemModstamp, WhoId     Who This Solution Applies To All instances with a native SFDC integration.
View full article
  Marketo Champions are customers who have demonstrated outstanding leadership in the Marketo Community, are experts in Marketo products, are avid contributors in the social world, and are loyal advocates of the Marketo brand. Benefits and perks our Champions receive include:   Access: Meetings with our product and marketing teams to give exclusive feedback Previews: Given early previews to products, features, and releases when available Publicity: Exclusive speaking opportunities at our annual Marketo Summit and other events Networking: Special networking events with Marketo executives and fellow Champions and semi-annual conference calls Ownership: Ownership of content and exclusive activities at our annual Marketo Summit that showcase your expertise and thought leadership Credibility: Special Champion badge on Marketo Community profiles, and profiled on Marketo's corporate website Sweet Swag: Champion-exclusive swag To find out more information and apply, click here. To view a complete list of current Champions, click here. Join the Marketo Elite Today!  
View full article
Issue Description You have a record in Marketo that is a Contact in SFDC, and the record fails to sync with the error "INSUFFICIENT_ACCESS_OR_READONLY: insufficient access rights on object id." Issue Resolution This error can occur if the Record Type ID field is not updated in Marketo when the SFDC Lead is converted to a Contact.  If the Record Type ID value displayed in Marketo is not valid for Contacts, the sync will fail with the error, "INSUFFICIENT_ACCESS_OR_READONLY: insufficient access rights on object id." To resolve this, you can update the Record Type ID in Marketo with the correct value from Salesforce, or you can delete the value from Marketo and allow the sync to write the correct value from Salesforce.
View full article
Issue Description A lead fails to sync to Salesforce with the following error: Failed: FIELD_INTEGRITY_EXCEPTION: There's a problem with this country, even though it may appear correct. Please select a country/territory from the list of valid countries. This error may also occur for state as well as country fields. Issue Resolution Country/State pick-list is enabled on your SFDC instance. As a consequence, SFDC will reject any record with country/state value does not belong to the list and therefore, you will have to make sure that countries are set correctly everywhere in Marketo, and especially: in forms in data management campaigns in imports For example, if you try to feed "New York", it will not be accepted. It will only accept "NY". The error messages you're seeing are coming from Salesforce because the State fields have been standardized to only accept certain pick-list values. In order to get these records to sync with Salesforce you'll need to update them to have valid values. Contact your SFDC Admin to get the list of accepted values for that field and update the record in Marketo with the appropriate value that is accepted by SFDC. If you feel like pick list is not necessary on SFDC, you could just disable the state or country pick lists in SFDC by following the below document https://help.salesforce.com/articleView?id=admin_state_country_picklist_enable.htm&type=5 Who This Solution Applies To Customers who use SFDC as their CRM
View full article
Issue You are experiencing slow processing of campaigns, smart lists, and reports.     Solution There are three key components that can slow down an instance: Number of trigger campaigns: Trigger campaigns are always on, always listening.  If there are 50 campaigns triggering at the same time, all the 50 triggers will be in queue, slowing down your processing and routing inside Marketo. Solution: Reduce the number of Triggers. Convert some of the triggers to batches: Batches also run all the flow steps for every lead at once, instead of serially, which reduces total processing time.   Complexity of smart lists: The more complex a smart list, the harder it is for the system to figure it out, which increases backend processing and even creates campaign failures from timeouts. Solution: Reduce the number of nested smart lists called in a smart list. Whenever you ask Marketo to call another Smart List, it has to wait until all of the other smart lists finish, before putting together the final counts. Instead of Marketo looking for the list and running it, just put the filters in the trigger itself.   Volume of Leads: With regular cleaning and good systems design, it is fairly easy to keep your system running fast. Reduce the number of leads that can flow through with filters. Clean up the inactive leads at regular intervals.    
View full article
Revenue Cycle Analytics represents the highest pinnacle of using Marketo. You can analyze your programs in depth. However, it is designed for people with some familiarity with business intelligence analytics tools. EASY Create an Opportunity Influence Analyzer Tell the Marketing Story with an Opportunity Influence Analyzer Configure an Opportunity Influence Analyzer Make a Program Without a Period Cost Available in Revenue Explorer and Analyzers Export Opportunity Influence Analyzer Data POWERFUL Subscribe to a Revenue Explorer Report Create a Program Analyzer Compare Channel Effectiveness with the Program Analyzer Compare Program Effectiveness with the Program Analyzer Explore Program & Channel Details with the Program Analyzer Build a Program Membership Analysis Report that Lists Leads Build an Email Analysis Report that Lists Leads Build an Email Analysis Report that Shows Program Information COMPLETE Create a Success Path Analyzer Explore Model Metrics in the Success Path Analyzer Manage Report Subscriptions Sync Custom Fields to the Revenue Explorer Leads by Revenue Stage Report Override Analytics Behavior at the Program Level Find all Leads in a Revenue Cycle Model Share a Model Across Workspaces Report on Your Revenue Model OLD ARTICLES We are working to improve these articles. They will be updated in the coming months. Add Leads to Your Model Build a Revenue Cycle Model Creating a Revenue Cycle Model Revenue Cycle Modeler Overview Intro to Using Custom Field Groups in the Model Performance Analysis (Leads) Area Launching your Revenue Cycle Model Revenue Cycle Modeler Overview Create Custom Field Groups Via the Field Organizer Graphing Results From Revenue Explorer Email - Click Activity Heat Grid (in CST) Email - Click Rate Decay Email - Clicked Time Distribution (in CST) Email - Open Activity Heat Grid (in CST) Email - Open Rate Decay Email - Opened Time Distribution (in CST) Email - Sent Activity Heat Grid (in CST) Filtering Data in Revenue Explorer reports Built-in Revenue Explorer Reports Create a New Revenue Explorer Report How to View Transition Data in RCE Lead Balance Report Understand Revenue Cycle Explorer Analysis Areas Revenue Cycle Explorer Custom Field Overview Advanced Program Reporting Overview Enable Custom Fields for Reporting in Lead, Campaign, Opportunity, and Program Opportunity Analysis Areas RCE - Program Cost Analysis Understand the Campaign Analysis Area Understand the Program Cost Analysis Area Understand the Program Membership Analysis Area Understand the Opportunity Analysis Area Understand the Program Opportunity Analysis Area Understand What Marketing Programs are Influencing Opportunities with the Opportunity Influence Analyzer Using the "Manual Stage Change" trigger in your model Understand the Email Analysis Area
View full article
Issue: I am looking for the ID to one of my campaigns for a SOAP API project I am working on. Solution: The ID can be found in the URL of the campaign. 1.1 Log into Marketo, under Marketing Activities, find and select the campaign in question. This is a article attached image 1.2 The URL to the campaign will look something like: This is a article attached image   The Campaign ID is between "SC" and "A", in the above example it's "1150". This is a article attached image  
View full article
*Updated in September 2024     Leads can be auto unsubscribed due to default Feedback Loop setup with the ISPs listed on this page. You can use the following filters to find leads that have clicked the SPAM button in your emails:       Filter 1: Data Value Changed Attribute: Unsubscribe New Value: True Reason: Contains, complaint   (Optional to Specify what Email Domain)   Filter 2: Email Address Email Address: Contains, @domain.
View full article
Issue Depending on the marketing strategy, Google AdWords can be a significant portion of the marketing mix.  With any significant expense, your marketing team will be asked to display a return on investment.  Additionally, to help manage the spend, marketers want to compare keyword and ad display with success metrics and revenue results.     Solution Keyword Capture Program - Setup Process The Marketo - Google AdWords integration provides deep insights into revenue generated by keyword and can help marketing teams get a much more granular view of revenue results than they would otherwise have without Marketo. Google AdWords spend can be tracked as its own Program Channel and leveraged within the Program Analyzer to make detailed assessments of performance. It provides very granular insight into performance through multiple dimensions and unique reports. Initial setup of Keyword tracking programs is straight-forward and simple to duplicate for each new Keyword. In addition, Marketo automatically connects to Google AdWords to report Customer-specific funnel conversion information by keyword and display ad.   Template Program Setup: Add a field named PPC Source to the Lead Database – set field to write only if empty. Setup a Default AdWords Program in Marketo that contains a Keyword Token – this program will be cloned for future AdWords so that the steps below do not have to be repeated. Create a Program Token for Keyword. Configure the Smart List to Look for PPC Source containing the Keyword Token. Set the default flow to Update the Program Stages based on Activity Clicked AdWord (Default) Visited Site Filled Out Form Has Opportunity Set up a Smart Campaign within the Program to look for Closed/Won Opportunities and Activate the Campaign       Cloning Process: Once the Default AdWords Program is setup it will only take a few minutes to add new PPC AdWords to Marketo. Clone the default AdWords Program. Update the Token to include the new PPC Keyword. Activate the Closed/Won Opportunity Smart Campaign. Capture Monthly Spend by Keyword Program within Marketo. Example Reports Once setup, reporting on Keywords within Marketo is now simple, easy, and more robust than other platforms.  Here are five reports that will help you manage AdWords:   A. Basic Keyword – Program Results Report     B. Basic Keyword - Opportunity Results Report   Fields include:   Total Leads Count w/ No Opportunity Days No Opportunity Has Opportunity Has Opportunity % Days Until Opportunity Total Opportunity Amount Avg. Opportunity Amount Total Opportunity Won % Won Total Won Amount Days to Close Days in Sales Stage         C. Program Analyzer   Program Cost Cost per New Name Cost per Success First-touch Revenue Expected Multi-touch Revenue Expected Members New Names First-touch Pipeline Created Multi-touch Pipeline Created Success (New Names) Success (Total) % New Names     D. RCE - Advanced Reporting on Keywords     E. Funnel Conversion Data in Google AdWords - By Keyword & Display Ad   The information displayed below is passed directly from Marketo into Google AdWords baed on the pre-configured Marketo-to-AdWords connector.  Marketo does not currently pass along any information through the connector beyond what is shown in the screen below (Funnel Conversion Information).    
View full article
Issue Description Can multiple Marketo forms be used on the same page? Issue Resolution Due to the way Marketo forms are embedded on pages, you cannot have two Marketo forms on a single page (landing page or external). Having multiple forms on a single page can prevent the forms from submitting properly.
View full article
These directions show you how to create a profile with access to Sales Insight while removing access for your other profiles.  These instructions assume you've already installed the Sales Insight AppExchange package.   Create a new profile If you have a dedicated profile for your Sales Insight users, you can skip this step.Otherwise, you should create a new one now.  Go to the Setup page and pick Administration Setup -> Manage Users -> Profiles in the menu.  Then click the New button at the top of the page: This is a article attached image   Next, pick a profile to clone and give the new profile a name.  Click Save when you're done: This is a article attached image Edit profile permissions Go back to your Profiles list.  For each profile, you'll need to edit it by clicking its Edit link: This is a article attached image On the edit page, you'll need to change a few settings.  For profiles allowed access Sales Insight: In Custom App Settings check Marketo to make the Marketo app visible In Tab Settings, change the Marketo tabs to Default On In Custom Object Permissions, check Read, Create, Edit, and Delete on Marketo Sales Insight Config if the user should have access to the config settings For those that should not have access to Sales Insight: In Custom App Settings uncheck Marketo to hide the Marketo app In Tab Settings, change the Marketo tabs to Tab Hidden In Custom Object Permissions, uncheck Read, Create, Edit, and Delete on Marketo Sales Insight Config   Click Save when you're done with each one.   Changing views Next, you'll need to create a new view for your Sales Insight profile. These instructions describe how to set up the Lead page; repeat the steps to set up your Contact, Opportunity, and Account page layouts. Go to the Setup page, then pick App Setup -> Customize -> Leads -> Page Layouts and click the New button. This is a article attached image   Clone your layout of choice and give the layout an appropriate name like Sales Insight Layout.  Click Save when you're done.   This is a article attached image Follow the instructions in the Installation guide for configuring the lead detail page.Installing the Marketo Sales Insight AppExchange packageGo back to the Page Layouts section and click the Page Layout Assignment button.   This is a article attached image   Click Edit Assignment This is a article attached image   Select your Sales Insight profile, then select your sales insight layout from the Page Layout to Use pulldown.Click Save when you're done.   This is a article attached image Repeat these steps for your Contacts, Opportunities, and Accounts page layouts.   Other Changes   Here are some other places where Sales Insight items could appear.  You'll have to remove them outright since you can't use Profiles to limit access to them: Remove Sales Insight buttons from Search Layouts for Contacts, Leads, and Accounts Remove Sales Insight columns from Contact and Lead lists
View full article
Issue You receive a DMARC report from an ISP saying that your email failed to pass the SPF alignment check, but when you check your SPF listing in Admin > Email > SPF/DKIM, SPF is verified. Solution The SPF record in Admin > Email > SPF/DKIM  is tied to your FROM domain.  DMARC alignment (using SPF) aligns the domain in the FROM address with the domain in the “return-path” address.  This “return-path” address, usually using a '*.mktomail.com' domain, is generally unseen by recipients and directs email bounces and errors back to Marketo for processing.    Failed DMARC alignment, between these two domains, is what is triggering the failure your DMARC reporting.   DMARC compliance requires EITHER DKIM or SPF compliance, not both in most cases.  This article reviews the two methods available for DMARC alignment - https://nation.marketo.com/docs/DOC-1202-technical-tip-set-up-dmarc-verified-domains-in-a-few-easy-steps Having DKIM DMARC alignment may be enough and you may not need to rely on full SPF DMARC alignment.   In order to set up SPF DMARC alignment, Branded Return-Path will allow you to align the “return-path” domain with your sending FROM address domain.  If you have a dedicated IP on the current pricing plan or are on the Trusted IP range, Marketo can brand your return path at no additional charge.  If you have a legacy Silver Dedicated IP package, or are on the Shared IP range, you can purchase the Branded Return Path as an add-on.   More technical info can be found here: What is DMARC? - https://nation.marketo.com/docs/DOC-1097 https://nation.marketo.com/docs/DOC-5910-branded-envelopefrom-on-shared-or-trusted-ips https://nation.marketo.com/docs/DOC-5951-branded-envelopefrom-on-dedicated-ips
View full article
Issue Best practices for trigger campaigns. Environment This applies to all Marketo users who are utilizing trigger campaigns in their marketing activities. Solution Marketo's trigger campaigns are designed to monitor every relevant activity, even if it doesn't immediately meet certain constraints or filters. For example, if there are 10 active Clicked Email Campaigns and 100 leads engage with an email, each lead will be evaluated 10 times to check if they qualify for a trigger. In this example that would lead to 1000 evaluations total. This happens even if they don't meet the criteria due to certain filters or constraints. To make your trigger evaluation process quicker and more efficient, follow these best practices: 1. Deactivate any trigger campaigns that are no longer needed. This reduces the number of active monitors that could potentially activate trigger event evaluations.    Note: Marketo automatically deactivates smart campaigns that have been dormant (no lead triggers them) for 6 months or more on a quarterly basis. However, you can manually deactivate campaigns whenever necessary. 2. Convert Trigger campaigns to Batch campaigns if immediate responses are not required. This is particularly useful for activities or campaigns that can run overnight. Batch campaigns operate on a separate component of Marketo's processors, meaning they won't impact the speed of Trigger qualifier processes.  
View full article
Issue Your SFDC Campaign is synced to a Marketo Program but leads that are added to the SFDC Campaign are not showing up as members of the Marketo Program. Solution Take the following steps to troubleshoot this issue: Log into Salesforce using the Marketo Sync credentials. Confirm that the SFDC Campaign is visible to the Marketo Sync user. If it is not visible, this will cause the sync to fail. Confirm the members of the SFDC Campaign are visible to the Marketo Sync user. Marketo cannot sync leads it cannot see. Compare the member statuses of the SFDC Campaign to the statuses of the Marketo Program. The sync will only work for statuses that match exactly. For example, if the statuses for your SFDC Campaign are Invited Registered Attended but the statuses for your Marketo Program are Invited Attended then none of the leads in SFDC with a campaign status of "Registered" will be added to the membership of the Marketo Program. To resolve this, make sure that all statuses match between the campaign and the program. You may need to force an update on the leads to re-queue the sync.    
View full article
Included in this article   How many total named accounts can I have within Marketo TAM? How many account lists can be created? How many Named Accounts can be added to the Account List? Is Marketo TAM Workspace specific? Which lead attributes are used for Lead-to-Account Matching? How are strong lead matches to Named Accounts determined? How are weak lead matches to Named Accounts determined? How can you make Marketo TAM automatically associate leads to Named Accounts? Do I see all the CRM accounts in the Discover CRM grid? Does the number of CRM accounts match the number of CRM accounts shown in Discover CRM grid? What does the Discover Marketo Companies grid show? What happens if I delete Named Accounts? Can I merge duplicate companies or CRM accounts manually in Marketo? How is the week-over-week engagement over time chart determined and how frequently it is calculated? How is the week-over-week pipeline chart determined and how frequently it is calculated? How is the week-over-week revenue chart determined and how frequently it is calculated? Does Marketo TAM backfill data for engagement over time charts? How far back can I see engagement over time, pipeline and revenue charts? How far back are email and web activities calculated for? How is pipeline determined? How frequently are account scores calculated? How is Currency calculated? Does Marketo TAM support Account hierarchy? Additional Documentation   How many total named accounts can I have within Marketo TAM? There is no limit from a product perspective.     How many account lists can be created? 1,000     How many Named Accounts can be added to the Account List? 500     Is Marketo TAM Workspace specific? No. Named Accounts are visible to all the Workspaces. But Lead Partition rules are still honored. Which means you can see a named account in multiple Workspaces but depending on the Lead Partition rules, you can only see leads belonging to the corresponding Workspace within that named account.     Which lead attributes are used for Lead-to-Account Matching? It is based on 3 lead attributes: Email Domain, IP Address and Company Name. We convert Email Domain and IP address to the Company Names and match all 3 to identify strong and weak matches.     How are strong lead matches to Named Accounts determined? When the Company Name matches 3 out of 3, or 2 out of 3 times, then we consider this a strong match.     How are weak lead matches to Named Accounts determined? When the Company Name matches only 1 out of 3 times, then we consider this a weak match.     How can you make Marketo TAM automatically associate leads to Named Accounts? When you create a Named Account from any of the Discover grids, Marketo creates rules which then going forward are used to do automatic association of leads from the company to Named Accounts.     Do I see all the CRM accounts in the Discover CRM grid? Yes, all the CRM accounts that are synced in Marketo show up here     Does the number of CRM accounts match the number of CRM accounts shown in Discover CRM grid? Not necessarily. Marketo ABM does light de-duplication by CRM account names. First, we remove company suffixes before matching to company names. (Ex: Co, Corp, Corporation, Gmbh, Inc, Incorporated, LLC, LLP, LP, Ltd, PA, PC, PLC, PLLC). Second, we merge companies or CRM accounts in Marketo with duplicate names (not case sensitive)     What does the Discover Marketo Companies grid show? This grid shows all the CRM accounts as well as Marketo Companies that we found in the Marketo lead database.     What happens if I delete Named Accounts? None of the leads associated with the Named Accounts will be deleted. You can always go back to the Discover Companies grid and re-create the Named Account.     Can I merge duplicate companies or CRM accounts manually in Marketo? Yes. You can use Discover Marketo Companies to do that.     How is the week-over-week engagement over time chart determined and how frequently it is calculated? We take daily account scores and show the maximum account score for that week. This chart is calculated every 8 hours.     How is the week-over-week pipeline chart determined and how frequently it is calculated? We add the total sum for the 'Amount' of all opportunities except closed-won and closed-lost. We show opportunity amount on last day of the week. This chart is calculated every 24 hours.     How is the week-over-week revenue chart determined and how frequently it is calculated? We add the total sum of the 'Amount' of all the closed-won opportunities on a weekly basis. This chart is calculated every 24 hours.     Does Marketo TAM backfill data for engagement over time charts? No. Engagement is tracked from the time Named Accounts are created. We don't backfill.     How far back can I see engagement over time, pipeline and revenue charts? 90 Days.     How far back are email and web activities calculated for? 30 Days.     How is pipeline determined? Pipeline is calculated as a sum total of 'Amount' for all open opportunities except closed-won and closed-lost in CRM accounts.     How frequently are account scores calculated? Every 30 minutes.     How is Currency calculated? Currency is the Subscription currency. Marketo ABM does not covert the currency.     Does Marketo TAM support Account hierarchy? Not in this current version, but it is planned for future versions.       Additional Documentation Here are some links to related Documentation that you may find useful:   Target Account Management (previously ABM) - Troubleshooting Tips Target Account Management Overview - Marketo Docs - Product Docs TAM - Issue a License - Marketo Docs - Product Docs TAM - Permissions - Marketo Docs - Product Docs TAM - Configure CRM Mapping - Marketo Docs - Product Docs TAM - Account Score - Marketo Docs - Product Docs TAM - Account Lists - Marketo Docs - Product Docs TAM - Add People to a Named Account - Marketo Docs - Product Docs TAM - Discover Accounts - Marketo Docs - Product Docs TAM - Lead to Account Matching - Marketo Docs - Product Docs TAM - Named Accounts - Marketo Docs - Product Docs TAM - Account Filters - Marketo Docs - Product Docs TAM - Account Triggers - Marketo Docs - Product Docs TAM Main Dashboard - Marketo Docs - Product Docs TAM - Account List Insights - Marketo Docs - Product Docs TAM - Named Account Dimension in RCA - Marketo Docs - Product Docs TAM - Named Account Insights - Marketo Docs - Product Docs
View full article