Knowledgebase

Sort by:
Issue You receive an error in ToutApp - "IMAP access is disabled for your domain. Please contact your domain administrator for questions about this feature. (Failure)" Solution This due to an invalid Gmail connection For this error message to be resolved, we recommend looping in with your Gmail Administrator regarding the IMAP access of your domain and whether or not it can be enabled. See the link below for additional reference on this for your Gmail Administrator: https://support.google.com/a/answer/105694?hl=en    
View full article
Issue Leads are stuck in a smart campaign's Wait Step and have not moved onto next steps, even though the Wait Step has been updated/shortened and the lead should move onto the next step. Solution When a lead enters a Wait Step, it remains in the Wait Step as defined at the moment they entered it. For example, if the lead enters a 1 week Wait Step, it will remain in the step for 1 week. If the Wait Step is updated to be longer or shorter (for example, shortened to 3 days or extended to 2 weeks), the lead that already entered the Wait Step (when it was 1 week) will remain in the Wait Step for the original duration. New leads entering the Wait Step will abide by the new duration.
View full article
Issue Issue Description When filling out a form in preview, an external Thank You Page is not working. Marketo is not redirecting to the Thank You Page.  Solution Issue Resolution This is expected. A workaround is to create a test Marketo Landing Page and place the form for testing. 
View full article
Summary Mismatch between "Added to [custom object]" and "Has [custom object]" filters for a SFDC Custom object Issue You build a Smart List for "Added to [custom object]" for your SFDC Custom object and you notice the number of records qualifying is lower than expected. The "Has [custom object]" filter pulls more records, however, and matches what you see in SFDC. Environment SFDC/Marketo Solution This is expected behavior if you have records that were already associated to the SFDC Custom object before they were pushed to Marketo. If you have records that were already associated to the SFDC Custom object before they initially synced to Marketo, those records would not have an "Added to [SFDC Custom Object]" activity on their record in Marketo, which means they would not qualify for the "Was added to [SFDC Custom Object] Smart List filter" In this scenario, it is recommended to use the "Has [SFDC Custom Object]" filter to get the accurate numbers, as this should include all Marketo records that are associated to the Custom Object, even if they were added to it prior to being synced and created in Marketo. Root Cause Records already being associated to the SFDC Custom object before they were initially synced to Marketo.
View full article
Issue Description You may notice that there may be a block in SFDC that stop syncing unsubscribes from Marketo to SFDC. After fixing the block in SFDC the new unsubscribes will sync as expected. How to get all the unsubscribes that happened before this fix to sync into SFDC?   Issue Resolution You would need to set up a campaign to reset the field value. Smart list: Unsubscribed = true Flow: Change data value  "unsubscribed" -> False Change data value  "unsubscribed" -> True   That would take everyone who is currently unsubscribed, switch to false and then back to true. That should cause the true value to sync up to SFDC for all of those records. However, make sure you do this at a time when you are absolutely positive there are no email campaigns going out.   Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo
View full article
Issue You receive the following error: "Ouch! 500 Error Something went wrong. We monitor this sort of thing, but if you are an authorized support contact, you should create a support ticket."       Solution This can happen because of temporary network issues. Try out the following troubleshooting steps. 1. Clear Browser Cache 2. Try a different browser 3. Try a different device 4. Try a different internet connect (Hotspot/Tether from mobile) If you still have any issue after trying all these steps, please contact Marketo Support for further assistance.
View full article
Issue You would like to have a new lead created in SFDC after every form submission regardless of whether the contact/lead already exists. Solution When you use the "sync lead", assign the person to lead queue explicitly, that will create a new lead since contacts cannot be assigned to queues. However, this is going to create a lot of duplicates in your database unless your salespeople are converting/merging these leads correctly. Furthermore, these new leads will have no campaign history, no interesting moments, no score. It's better to use an "Inbound sales rep campaign" in SFDC and attach the person to it using an "add to SFDC campaign" flow step. Campaigns can contain leads and contacts and can have workflows assigned to them.      
View full article
Issue When using the Merge Lead(s) REST API end-point and merging multiple leads, which field values would be copied to the winning record? In the below example, the winning lead record has a blank value for Job Title. When merging all 4 leads, which field value will get copied to the winning record from the list of losing records?  This is a article attached image Solution The field values that will be injected to the winning lead record are directly impacted by the order of leadID's in the Lead array parameter of the call, where the FIRST leadID listed in the parameter array will be the winning value IF the field on the winning Lead record is blank.  URL Example {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=2232,1323,1455 RESULT  Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = 'electrician'. URL Example #2 {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=1323,1455,2232 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = blank/empty.   Root Cause This is the expected behavior when merging multiple leads via the REST API Merge Leads end-point.  
View full article
Issue Description How to edit the schedule email in ToutApp.   Issue Resolution The way to change the time of a scheduled email: Go into your on the conversations page. Click the Edit button next to the scheduled email. From here you will be able to change the time of the delivery of the email.  Is this article helpful ? YesNo
View full article
Issue Description Getting error "Salesforce 551 unauthorized bounce" in ToutApp   Issue Resolution - Head on over to your Salesforce instance and login.  - Once you're logged in, head over to "Setup" > "Email" > "My Email to Salesforce"      - In the "My Email to Salesforce" page, head over to the "My Acceptable Email Addresses" section and ensure the all the addresses you use are listed in here:     - Just below "My Acceptable Email Addresses" you can set your email logging settings to how you would like them to enter your SFDC.    - Save your settings.           Who This Solution Applies To ToutApp customers Is this article helpful ? YesNo
View full article
Issue Tokens in form-triggered emails are not populating values when a new lead comes in through form fill out.     Solution For the token to populate, the associated Marketo field shouldn't be empty and it must hold a value that will be passed to the token. It takes a small amount of time for the form to write the value to the lead record and it my not write all the info before the triggered email is sent. In case of new leads, using a wait step as the first flow step (before send email flow step) will be helpful. This will leave some time for the fields get their value filled from the form fillout. Once the fields have the value, the associated token will populate correctly during the email send.  
View full article
Issue Description How is syndication ID set up while setting up a referral offer Issue Resolution For a referrer to be given credit they must have a Marketo Syndication ID assigned. This can be done manually (directly on the lead record) or via the social campaigns' Offer Details > Fulfillment Goal > should be set to Referred Sign-Ups. Once you set that up, the referrer will get issued a "syndication id" and be part of that social campaign's participant's list.
View full article
If the user makes changes to the my tokens, snippets, etc during the processing of the an email that is using head start, will those changes be reflected—No If someone unsubscribes during the processing of the an email that is using head start, will they receive the email—Yes Can you cancel a head start program once the processing of the an email that is using head start has begun—Yes What happens to the processing data when someone cancels a program during the processing of the an email that is using head start—It is deleted (I.e. Program membership, etc.)  
View full article
Issue What happens when you enable "Send all Tout emails in my team through this server connection" within the SMTP Server settings on ToutApp.com. Solution When you select "Send all Tout emails in my team through this server connection" within the Tout admin panel, this will provide the option to all standard users to either choose to use the ToutApp Email Servers or your company's own Email servers. If you decide to share the SMTP Settings with the team, t is recommended that you have your IT team setup a dedicated STMP/Email account to use as the Custom SMTP Credentials. Note: Each user can choose to either use the Tout servers or the configured & shared SMTP server. It is not applied automatically to all users.
View full article
Summary If you're using the Bulk Custom Object Import API to push records to a Marketo custom object (and you're importing separate files that have duplicates across the files) -- the records will not be deduped on the custom object if multiple imports are pushed at the same time. Issue If you are using a Bulk Custom Object Import API third party service to push records to a custom object (and multiple files, containing duplicates across those files are being imported to the Marketo custom object in a similar time window) -- the records will not be deduped on the custom object, even if the dedupe field value is matched. This is because two concurrent imports can be processed at the same time if they are pushed close together. More information can be found here. "A maximum of 2 jobs are processed at the same time.  A maximum of 10 jobs are allowed in the queue at any given time (including the 2 currently being processed)." Solution In this scenario, the third-party App/API service provider that is making the bulk import calls must be consulted to ensure that separate files containing duplicate records aren't being imported to a Custom Object at the same time (or close together times). Once the calls are spaced out adequately so there aren't concurrent imports running containing duplicate records in separate import files, the custom object will dedupe as expected based on the designated dedupe fields. More on dedupe fields can be found here: "Dedupe fields can be used to retrieve, update, or delete custom objects. Every custom object definition must contain at least one (and no more than three) dedupe fields." In Summary, while Marketo does deduplicate on custom object records at import based on the dedupe field(s), it cannot dedupe when concurrent imports are being processed at the same time with duplicates in the separate files (for example: file 1 has dupe A while file 2 has dupe B).  If all the duplicates are in the same file, however, Marketo can dedupe within that file as its imported to the custom object.    Root Cause Concurrent Custom Object imports running at the same time: when this occurs, the two files being imported concurrently don't have time to check against each other to dedupe based on the configured dedupe field.
View full article
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.
View full article
Issue Change Lead Owner reason shows "Synched from salesforce.com - fixup Lead Owner." Solution The "synched from salesforce.com fixup lead owner" activity means the lead owner was switched within SFDC, often times through auto-assignment rules. The phrase "fixup Lead Owner" is what Marketo records when it is taking the Owner ID being passed from Salesforce and translating it into the Lead Owner values (First Name, Last Name, Email Address, etc) to populate into Marketo.
View full article
Issue "Currency" type fields are rounding off their value. For example, if you enter the value as 8092384905, Marketo is automatically rounding it to 809239000.     Solution This is an expected behavior. TThe currency field type in MySQL is considered to be a Float field and MySQL will automatically round the values in our current database structure. As a work around for this, change the field type to "string" . Since standard fields type cannot be changed, we suggest that you create a new custom field of type "String" to use instead of the standard field..        
View full article
Issue How to use a script token to calculate and populate the number of years since a given date.   Solution This can be achieved by using a velocity (email script) token:   #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/New_York") )  #set( $defaultLocale = $date.getLocale() )  #set( $calNow = $date.getCalendar() )  #set( $ret = $calNow.setTimeZone($defaultTimeZone) )  #set( $calConst = $field.in($calNow) )  #set( $ISO8601 = "yyyy-MM-dd'T'HH:mm:ss" )  #set( $ISO8601DateOnly = "yyyy-MM-dd" )  #set( $calJoinDate = $convert.toCalendar(  $convert.parseDate(      $lead.JoinDate,       $ISO8601DateOnly,       $defaultLocale,       $defaultTimeZone     )  ) )  #set( $differenceInYears = $date.difference($calJoinDate,$calNow ).getYears() )  #set( $friendlyLabel = $display.plural($convert.toInteger($differenceInYears),"year") )  You joined us ${differenceInYears} ${friendlyLabel} ago!  Where $lead.JoinDate is the joining date. More at http://blog.teknkl.com/velocity-days-and-weeks/    
View full article
Article Text Included in this article   Overview Troubleshooting Steps Verify Global Settings Check for CRE Excluded URLs Verify Content Being Recommended Make Sure the Page Has the RTP Tag Running Clear Your Browser's Cache and Cookies Overview The Content Recommendation Engine allows content assets to be promoted to visitors on your website. But what happens if it stops working? This doc will show you the common things to check and troubleshooting steps to try to get it working again.     Troubleshooting Steps   Verify Global Settings The CRE can be switched on or off for your entire RTP instance whenever you want. It's possible that another user may have switched it off and not turned it back on again (it happens more often than you'd think). To enable or disable the CRE globally, go to the Account Settings page and look for the Recommendation toggle switch. Full directions can be found here.     Check for CRE Excluded URLs You have the ability to prevent the CRE from being added onto specific pages. If you have URLs excluded from allowing the CRE to be displayed, that would cause the CRE to no longer display on those pages. Many times the exclusion can be set and then forgotten, or set by a different user on accident. Directions on how to set up the exclusions can be found here Web Personalization (RTP) - How To Exclude or Include the CRE on Specific Pages     Verify Content Being Recommended Content assets can be switched on or off to designate whether that content should be included in the CRE recommendations or not. Each piece of content can be enabled or disabled individually, but if you don't have any enabled at all, there's nothing for the CRE bar to recommend, so it won't even show up on the page.     To check whether content is enabled, from the menu, select Recommendations     In the Content Recommendations page, look for the Recommendations column. This will list out all pieces of content you have in RTP and display whether they are enabled or disabled. The Red box means it is turned Off and is disabled. The Green circle means it is turned On and is enabled.     Make Sure the Page Has the RTP Tag Running The CRE is a feature of RTP, so if the RTP script tag isn't running on the page, there's no way for the CRE to work. The RTP tag can be implemented in many different ways besides by having it directly in the page's HTML, like having it in a tag manager. These other implementation methods can cause problems so be sure to follow the directions in the documentation here when setting it up: RTP Tag Implementation - Marketo Docs - Product Docs   If you know for sure that the RTP tag is on the page, here's documentation on how to troubleshoot what could be keeping it from loading properly: Troubleshooting Web Personalization (RTP) - RTP Tag   Clear Your Browser's Cache and Cookies Web browsers store cached data from websites, which can frequently cause old versions of webpages to continue showing even if a different newer version of the page should be loading instead. Try clearing both cache and cookies in your browser and then testing the page again. You can also test using a different browser.  
View full article