Knowledgebase

If you tried to sync a lead, company, or opportunity field to to the Revenue Explorer and see this error -- "This field cannot sync with Revenue Explorer" The most common reason is because this field is already synced to Revenue Explorer. Check the Revenue Explorer Sync status of that field to check if it's enabled: Otherwise, please contact Marketo support to help. Is this article helpful ? YesNo

Issue When you click on ‘Forward to Friend’ link on an email template, it redirects you to the below 404 error page.       Solution The ‘Forward to Friend’ link will work only in a sent email and not on an email template. To test this functionality, you need to create an email using the template which contains "Forward to Friend’ link and then send the email to your test lead using a run action.  It will not work properly with a send sample. Open the email and click on the "Forward to Friend" link. Once clicked the email will open on a webpage and then the below "Forward to Friend" box will be visible.   This is a article attached imageThis is a article attached imageThis is a article attached image   To know more about "Forward to Friend", refer the below document.   http://docs.marketo.com/display/public/DOCS/%27Forward+to+a+Friend+Link%27+in+Emails    

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    

Issue You want to find the day that a piece of predictive content was discovered.     Solution There isn't a direct way to see the exact date a piece of content was discovered. What you can do is filter the results to content discovered during a specific time frame. Go to the "All Content" tab. Select the Calendar on the upper right side Choose the time frame and click Apply. Result: You will see only the content that was discovered during that time frame.   Who This Solution Applies To Customers with Real-Time Personalization (RTP) or Predictive Content.    

Article Text Included in this Article: Overview Email Reports not Being Sent Check Report Preferences Fewer Leads than Expected Check Personal Regions Settings Cross-Domain Tracking Data Includes Own Company   Overview   All RTP users should be receiving a monthly and quarterly Summary Report.     This email evaluates the performance of campaigns and recommended content and compares it to that of the previous month or quarter. Performance is based on click count and number of visitors converted to known leads, whether direct or assisted. Direct leads are visitors that clicked on a campaign or a piece of recommended content and filled out a form in the same visit. Assisted leads are visitors that clicked on a campaign or a piece of recommended content and filled out a form in a separate visit, up to 6 months in the future.   If you would like to unsubscribe from the Summary Reports, see this article. Otherwise, several potential issues with Summary Reports are outlined below along with their potential solutions.   Email Reports not Being Sent   Check Spam Folder As a first step, try checking your spam folder. It's certainly possible that the email reports did not make it past your email client's spam filters.   Check Report Preferences In your RTP settings, you will be able to enable or disable email reports. If you are expecting reports but not receiving them, it is possible the reports were disabled in your preferences. To check:        Go to User Settings          Check the Email Report settings at the bottom of the page     Make sure to check the box for Summary Report and whether you would like a monthly or quarterly (or both) report. This page is also where you will be able to manage any other RTP email reports you wish to be subscribed to.     Fewer Leads than Expected   Check Personal Regions Settings Another page to check is the Personal Regions page. This page will allow you to display data in the Web Personalization platform and send email reports only related to the specified regions.          In User Settings, click the Edit Regions button         This should take you to the Set Personal Regions page:         On this page, you will want to verify that any region you may have leads in is checked (marked as included in your Personal Regions). If regions that you have leads in are not included, the Web Personalization platform will not display data from that region or include it in the email reports. This means that if you have leads that are not included in your Personal Regions, their activity will not be included in Summary Reports.   Cross-Domain Tracking If the visitor is shown a recommendation on one domain, but the recommended content is hosted on a different domain, two different sessions will be recorded. This divides the visit into two sessions: The click on the link to the recommended content, on the first domain The content itself and the form fill-out, on the second domain   Because the click and the form fill are in two different sessions, the lead will be recorded as an Assisted Lead rather than a Direct Lead. This applies for both top-level domains (firstdomain.com and www.seconddomain.com) and sub-domains (pages.domain.com and www.domain.com/new_page). Cross-domain tracking will ultimately skew your metrics towards more Assisted Leads. To reduce the impact of this limitation, keep content recommendation and the content itself within the same domain when possible.     Data Includes Own Company   Clicks and visits from your own company can significantly skew your summary data, as your own employees may be visiting the company website on a daily basis. Because of this, it is important to exclude your own company from the organizations contributing to your Web Personalization data. To do this:        Go to your Account Settings          Scroll to the bottom of the page to find the Exclude IPs field     In order to exclude your company's traffic from your data and reports, you will need to know the outbound IP address of your company's network. You should be able to obtain this information from your company's IT department. Once you have your company's outbound IP address, enter it into the Exclude IPs field and press

Article Text Included in this article: Navigate to the Clickstream module How is Visit Duration Caluclated 00:00 Visit Duration Single page viewed Session timed out   Navigate to the Clickstream module        Go to the Visitors page        Click on a visitor to find the Clickstream module in the bottom right     How is Visit Duration Caluclated When a visitor visits a website being tracked by an RTP campaign, it records clicks in the Clickstream module in the RTP platform. Clicking on a visitor allows you to view their viewing information in the Customer Journey section, including: Links clicked Time stamp of each link click Total visit duration     Visit duration is calculated by subtracting the first time stamp from the last time stamp. In other words: visit duration = last time stamp - first time stamp. See the image above for an example of this calculation.   00:00 Visit Duration Single page viewed Both RTP and Google Analytics rely on clicks to determine visit duration. This means that if a visitor only views a single page, neither RTP or GA can track when the visitor leaves the page, since there is only the initial time stamp without a time stamp to mark the exit from the page. The visit duration for viewers that didn't view more than one page during the session is recorded at 00:00 since it cannot be calculated.   Session timed out Another way that a visit duration can be recorded as 00:00 is if a visitor's session times out. By default, a session will end after 15 minutes of inactivity. For example, if a visitor stays on a page without making any clicks for 25 minutes (perhaps they are reading an article or watching a long video), that session will time out and be recorded with a duration of 00:00. If the visitor finally makes a click after the 25 minutes of inactivity, a new session will begin. In Google Analytics, the session timeout can be customized to be longer or shorter than the default 15 minutes.

Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools.   Solution Our system is specific about how you need to access the Support Portal before we can authorize you to use it. The proper steps to take for us to authorize, and for you to submit cases, are as follows:   Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info   Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 Step 2   Step 3 Step 4   If you experience issues, please email marketocares@marketo.com

Article Text Included in this article   Overview The Issue The Explanation   Overview Sometimes you'll see an organization show up as "ISP - Anonymous - Proxy" in your visitors list in RTP.   The Issue RTP is a powerful product with an immense database, but not every ISP can be found.  When we receive a visit from an ISP we can't identify, instead of omitting them from our results, we use the name "ISP - Anonymous - Proxy" and set the location to "United States.     The Explanation Pretty much any free Wifi signal you find like at a library or coffee shop will be listed as an Internet Service Provider (ISP). The admins for that ISP service can configure their network in any way they would like, including whether they allow for identification of their network. If there is no data provided, there's nothing for RTP or any other service to gather. In that case, that's when you'd see the "ISP - Anonymous - Proxy" listing for a visitor in RTP.

Article Text So you’ve now used the previous document (Getting Started With Guided Landing Pages:) to download a template from our library and set it up in your Marketo instance, you have even used it to make a landing page or two and you’ve customized those landing pages, AND you’ve even gone the extra mile and customized your template and modified some elements! (Editing Marketo Guided Landing Page Templates, Pt. 1 - Elements:) All of which is fantastic news! Good job!   But if you recall from the article that showed you how to edit Elements on the template, I skipped right over the section on Variables. This is the piece that this document is designed to tackle.   So what is a variable? If you edit a Guided Landing Page you will see a panel on the right hand side that displays both Elements and Variables. In this instance, the variables do everything from assigning a gradient color, to deciding if you want to display or hide different sections of the landing page. Modifying a variable in the landing page editor is designed to be really simple, just click the variable you want to change and give it a new value. Here I changed the Primary Gradient 1 and 2 from 1DA083 and 0F3450 to A00E35 and F2F2F2 respectively and the landing page changes: At its easiest to understand, a variable works a lot like a token in an email. It’s a placeholder for actual code to be used later. So if I create an email that starts with “Hello, {{lead.firstname:default=Friend}}!” you can tell right away what that’s going to do. Pull the first name from the lead record, if none exists use the word “Friend”.   Think of a Variable as a token that you get to define as well as use. The first step is to define it and the second step is to actually call back to the variable you defined.   While it’s easy for a non-technical user to use a variable (as it should be!), setting one up in the template does require a fair amount of HTML knowledge. As stated before, if you are not comfortable editing HTML and do not have a resource available to you, please reach out to services@marketo.com, they are able to assist with any sort of coding needs.   So as before, let’s dive into the template, this time we’re going straight for the Variable code.       <!-- Marketo Variable Definitions -->     <meta class="mktoColor" id="gradient1" mktoName="Primary Gradient 1" default="#1da083">     <meta class="mktoColor" id="gradient2" mktoName="Primary Gradient 2" default="#0f3450">   So right at the start of the template, we’re off to the races defining variables. As you can see with the Gradient 1 and Gradient 2, these are both marked with a class of “mktoColor”.   As with the Elements, the full list of Variable types can be found here: docs.marketo.com/display/public/DOCS/Create+a+Guided+Landing+Page+Template        class : "mktoString"      class : "mktoColor"      class : "mktoBoolean"   A string is a variable that contains a value, Color should be obvious what that does and Boolean is a yes or no choice.   In addition to the class, each variable has to have a unique ID. This is critical and used when the variable is called later on down the page. When you call a variable it’s always with the syntax of ${id name}. So in this case ${gradient1} and ${gradient2}. As you can see it looks a LOT like a token but it’s a token you can name whatever you want.   The mktoName is how it displays the variable in the Landing Page editor.   The default value is what it starts out with.   So let’s take a look and see how these Gradients are applied now that they’re defined at the top of the template.   Color is typically used in the CSS portion of the header. As defined in the previous document, CSS stands for “Cascading Style Sheets” and is a way of formatting the same thing over and over again, kind of like setting a font in a word processor.       /* Header Gradient */     #is {         top: 0;         width: 100%;         min-height: 620px;         position: relative;         z-index: 1;         color: #fff; padding-top: 10%;                 background-image: linear-gradient(${gradient1},${gradient2});     }   Now normally in CSS, the linear-gradient option would have two colors listed, the top color and the bottom color and it provides a gradual transition from one to the other.   We could just as easily change this in the template to        background-image: linear-gradient(red,white);   But the problem doing that is that an end user, who is only using the Landing Page Editor, would not be able to change it. The gradient would be defined in the template and inaccessible to the Editor.   Changing these values to the variables defined before allows the user to change the first and second colors in the Landing Page editor interface.   In Summary:   The Meta Tags define what the variables mean:     <meta class="mktoColor" id="gradient1" mktoName="Primary Gradient 1" default="#1da083">     <meta class="mktoColor" id="gradient2" mktoName="Primary Gradient 2" default="#0f3450">   The ID= is then used to call the variable and put it into action:       background-image: linear-gradient(${gradient1},${gradient2});   The other benefit to doing it this way is you can re-use the same variable over and over again. Look at this piece of CSS:   body {                 background: ${gradient2};         margin: 0;         color: #696E74;     }   That’s the same ID as the gradient we used before, only applied to a different section. This ensures that the bottom color of the gradient and the background of this section will always be the same color.   Any item in the CSS that contains a text value, a color value or a yes/no choice can be converted to a Variable.   Here’s another common usage:   You’re using a form on your landing page, but you want the end user to be able to change the text on the submit button.   As before you define the variable:        <meta class="mktoString" id="section4ButtonLabel" mktoName="Sec. 4 Button Label" default="More Questions?">   Then farther down the page where the button appears you call the variable you defined before:        <div class="centered mtb">           <a href="${section4ButtonLink}"><button class="btn btn-lg btn-green mt">           ${section4ButtonLabel}</button></a>      </div>   The <a href= is pulling a http link that the user can define in the editor, the button class is setting up a green button as defined in the CSS, and there is our Variable to display the label which reads “More Questions?” Here’s what it looks like in the editor: So this is great, and it makes sense because you can see this was all set up and defined by a professional. What if you wanted to add your own? Is that even possible?   Naturally it is!   First, figure out what you want to convert to a Variable. Is it a piece of text like a button name or a link? Is it a color? Is it a yes/no choice?   Let’s say we want to add a variable that controls the color of the buttons. We have two, both using the same color green, and we want whoever is running the landing page editor to change that without having to go to the template:   Step 1: Define your variable:        <meta class="mktoColor" id="ButtonColor" mktoName="Button Color" default="#1DA083">   We’re talking about colors so the class will be “mktoColor”. The ID can be anything we want it to be as can be the mktoName. The default is the same lovely green shade as was used before.   Now we need to call this color.  Looking at the CSS, we can see the .btn-green is defined as this:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: #1da083;           -webkit-transition: none;           -moz-transition: none;           transition: none;      }   The background is the color we want to change to a Variable so it can be edited without having to access the template.   Change the code to this:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: ${ButtonColor};           -webkit-transition: none;           -moz-transition: none;           transition: none;      }     Approve the template and check out the landing page in the editor: Well that’s fantastic, but there’s a separate color for the border, we could just as easily add a variable for it as well:        border: 4px solid #1da083;   We don’t want to HAVE to add another new variable for just the border. We could change the border at the same time as the button. By changing #1da083; to ${ButtonColor};   The trick now becomes what if you change your mind? What if you have a variable in the template that is no longer desired? How do you get rid of it?   Remember each variable is two pieces, the definition and the call. You have to remove BOTH pieces. Technically removing the call would be enough to prevent the change from being made on the page, but the definition is what makes the variable appear in the Landing Page Editor, if you only removed the call then there would be a non-functional Variable in the landing page editor.   So in the case of our button color:   Step 1 would be to strip out the meta tag containing the definition:   Step 2 would be changing the variable name where it’s being used to some fixed value:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: ${ButtonColor}; -> change this to some other fixed color. #00FF33; or the original #1da083;.           -webkit-transition: none;           -moz-transition: none;           transition: none;      }   Doing both pieces will prevent the Variable from being listed in the Landing Page Editor and prevent it from having any effect on the page.

To ensure all your activities show up under the Activity History (as opposed to Open Activities) make sure you have a "Completed" values in the Task Status list and that it's a "Closed" state. Here is how to check it:   In SFDC, go to Setup > App Setup > Customize > Activities > Task Field.  Click on Status In the Task Status Picklist Values list, check if you have a "Completed" value.  If you do have it, skip to step 5. You need to create the "Completed" value.  Click on the New button Type in Completed and click on Save Click the Edit link next to the Completed value Check the box next to Closed and click on Save. Once the steps above are completed, you should now Completed in the list with "Closed" checked like this:    

Included in this Article:     Overview Why This Happens Two Ways to Fix this Problem Set the campaign as "Not Sticky" Use a dedicated Zone id that exists only on the page(s) to include in the campaign   Overview In the Web Personalization platform, you defined a campaign that included certain pages, but you are seeing the campaign appear on pages that you didn't intend them to appear on. Below, we will describe what might be the issue and how to solve it.     Why This Happens   When defining a segment using the "Specific Pages" parameter, every visitor that views this page will be matched to that segment. Once this happens, the "sticky" campaign will be triggered and will be displayed on every page that includes this Zone id parameter. After the visitor is matched to the segment and the campaign is triggered, the segment is not taken into consideration anymore, so this visitor will keep seeing the campaign every time the Zone id exists on the page.   Two Ways to Fix this Problem   Set the campaign as "Not Sticky"     This will make the campaign show up only once per session, and only when visitors are viewing the specific pages defined in the segment.       Go to the Campaigns page          Edit the existing campaign          Uncheck the box for "Sticky"       Use a dedicated Zone id that exists only on the page(s) to include in the campaign   In Zone campaigns are displayed in a particular zone in a website, designated by the Zone id.          Find "Zone id" in the campaign editor     Then, give the campaign a Zone id corresponding to a unique div ID tag on the desired site(s). This will ensure that once a visitor matches the segment and visited this page once, they will keep seeing the Call To Action (CTA) on this page.

My Salesforce activities are not showing up in Marketo and when I go to the Admin section I see the following sync error:   soqlBatchQuery failed - INVALID_FIELD: CreatedDate, Description, Id, IsAllDayEvent, IsDeleted, OwnerId ^ ERROR at Row:1:Column:70 No such column 'IsAllDayEvent' on entity 'Event'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names. This is due to lack of permissions for the Marketo Sync User on the Salesforce side. Please have your Salesforce Administrator log into your instance of Salesforce and carry out the following steps:   Log into Salesforce with Admin rights Click on your name drop-down and click on Setup In the left hand column, under App Setup, click on Customize Then click on Activities and then Event Fields Click on the All Day Event Field Label then "Set Field-Level Security" Here make sure to check the box under the Visible column for the Profile that the Marketo Sync User is associated to Click Save Once the above changes have been made on next sync we will begin pulling your Salesforce activities and once the next sync is over, the error message in the Marketo Admin section should go away.