Knowledgebase

Sort by:
Issue Issue Description When a lead is created through an API call, the Reason and Source attributes say "Web Service API" with no further detail.       Solution Issue Resolution As described in the doc here, https://docs.marketo.com/display/DOCS/Understanding+System+Managed+Fields , "Source" and "Reason" fields are managed by Marketo: Web Service API for Original Source Type means Person was discovered by a web service API. For Registration Source Type, it states that Person was created via SOAP/REST API When a lead is created via API, no additional "Source" or "Reason" is provided to Marketo. A possible workaround is to create a custom field and populate it as needed through the API.    
View full article
Issue You have a field (e.g. Most Recent Website Visit) that you want to see previous values for without needing to look through the activity log. Solution This can be done using a few custom fields, and one trigger campaign. Make duplicates of the field you want to see most recent values of (e.g. Most Recent Website Visit 1, Most Recent Website Visit 2, etc.) while still keeping the original field. Use the original field as you previously have, but set a trigger campaign to look for data value changes to that field. In the flow of that campaign, set the logic like so:   (1) Change Data Value: Most Recent Website Visit 3 new value: {{lead.Most Recent Website Visit 2}} (2) Change Data Value: Most Recent Website Visit 2 new value: {{lead.Most Recent Website Visit 1}} (3) Change Data Value: Most Recent Website Visit 1 new value: {{lead.Most Recent Website Visit}}   Using the above flow, the most recent values for the field can be checked without looking into an activity log. This can be useful in a number of ways, for example this information could be included in an email or alert. Another example, if the primary field (in the above example it is Most Recent Website Visit) is updated to a value that it should not have, then you can setup another campaign to update Most Recent Website Visit using the value in Most Recent Website visit 2 to restore the previous value.   Warning Please Note: The above process can be somewhat resource intensive (particularly if a large number of records trigger the campaign at close to the same time), this should be done with as few fields as possible to assure good instance health overall.
View full article
Issue You would like to know which partition a record that was captured by using "Forward to a friend link" in an email will be created in. Solution The record will be created under the partition which is associated with the work space under which the email asset is present. The record will not be created under the default partition.  For example, if you have a workspace named "Asia" which is connected with the partition named "APAC", then leads created via Forward-to-Friend links in emails stored in the "Asia" will be created in the "APAC" partition.
View full article
Issue You want to know the difference between a field with the type of string and text area.   Solution Both a string and text field will hold information that you can freely write in. The major difference between the two fields is how many characters you can put in these fields. A string field has a limit of 255 characters, whereas a text field has a character limit of 30,000 characters. (This is a general rule.  It may vary by application and platform.) A string field is a good choice if you wanting to store data like address, names, or simple custom data. A text area field is a good choice when you want to store information from something like a comment box on a form or if you are importing a large block of text.  
View full article
Issue You try to approve a segmentation and get the error message of "No possible draft" even when there is a draft in place. Solution This error message can be a little misleading, as there usually is a draft in place. Check to make sure that segments in the draft have Smart List filters in place and that there are no empty values in the smart lists. An example of an empty value would be "First Name is ____" instead of "First Name is Joe."
View full article
Issue You have a lead that is marked as Email Suspended and you are not sure whether they can receive Marketo emails or not. Solution When emails bounce as spam, the lead that bounced is set to "Email Suspended." "Email Suspended" is a historical field.  A more accurate name for this field would probably be "This email was suspended at some point in its history."  The actual suspension only lasts 24 hours. To see if the lead is currently suspended, check the timestamp on the 'Email Suspended' field.  If it is more than 24 hours ago, the lead is not currently suspended and can receive email from your Marketo instance.  However, the "Email Suspended" flag will remain on the lead record for the purposes of future troubleshooting.  It is not possible to set "Email Suspended" to "false" once it has been set to "true."  The "Email Suspended Cause" field will provide the bounce message associated with the most recent spam bounce.    
View full article
Issue List Import shows other lists Pending Import import even though you are only importing one list.     Solution The List Import function can be accessed via API as well as through the Marketo user interface.  By default, the list import function can process two list imports at a time and can queue up to ten more.  If the API has a large number of list imports queued up, this may interfere with your ability to import lists in your Marketo instance.  If this occurs regularly, you may want to work with your IT department to schedule the API calls to run outside of business hours.
View full article
Issue You want to know how long changing a segment takes.     Solution Segment changes are treated like any other activity that is being queued up and processed to be run. Segment changes have an extremely low priority and can sit in the queue waiting for other activities to finish, so you should wait for some time after making the change before you reference the segment elsewhere. Depending on the segmentation rules and the number of leads, it can take quite a while for it to re-process.
View full article
Issue How deleting or archiving programs will affect the Lead field: Acquisition Program.     Solution If you delete a Marketo Program, the field will append a "deleted" at the end of the Program Name. For example, if the Program Name was "July 2016 newsletter" for Acquisition Program, after deleting the Program, the field value would change to: "July 2016 newsletter  -  deleted (####)". The numbers represent an activity ID on the backend. Note: Archiving Programs does not affect the Acquisition Program.    
View full article
Issue You created a picklist field in SFDC and want to know if that field will sync down to Marketo with the field type of picklist.     Solution Marketo has a picklist option in form fields, but not in Lead Database fields. When you sync a field from SFDC that has the type of picklist, this field will show in Marketo with a type of String. However, when you create a form, the field type for your field will show as "select," which is a picklist.  
View full article
Issue You have been sending live emails (non-samples) to yourself or colleagues to test functionality of an upcoming email blast, and even though you may be opening the email, you are not seeing the open email activity on the Lead Activity Log.     Solution Note that there may be a slight delay between opening the email, and the activity displaying on the Log. Marketo considers an "open" to be when the images in the email are downloaded, specifically a single-pixel tracking image. The recipient may be receiving the emails and viewing them, but not downloading the images. This would not count as an "open."  Please note that since text-only emails have no images, so they will never log an Open activity. If the images are being downloaded, and you are still not seeing the activity after about 5 minutes, check to make sure there are no duplicate leads that are logging the activity instead.  If you need further assistance, please contact Marketo Support.    
View full article
Issue "Added to List" trigger is not firing when a lead is imported to a list when the List Import Mode "Skip new people and updates" is selected.     Solution Campaign triggers fire when the triggering activity is written to the lead's activity log. "Skip new people and updates" mode specifically skips activity logging. Since the "Added to List" activity is not written to the lead record when a lead is imported, the campaign will not be triggered.
View full article
Issue Some Marketo records have a discrepancy between the date of the New Lead activity in the Activity Log and the Created datetime in the lead record.     Solution What you have noticed here is the difference between anonymous and known record creation. In Marketo Smart Lists, there are 2 filters: Lead Was Created Created At "Created At" is when the anonymous record was originally created in Marketo. "Lead was created" is when this anonymous record was 'created' as a Known Lead in your database.
View full article
Issue Person/Lead Source is empty. Why isn't it populating?     Solution Marketo does not automatically assign Person Source. We do populate Original Source Type. Assigning credit for a Lead can only be determined by someone with intimate knowledge of a company's marketing strategies.  If someone fills out a form, Marketo doesn't know if they were brought to that form by an email blast, TV commercial, talked to a salesperson, or any number of other reasons. If they came in through a List Import, they could have attended a Tradeshow and signed up there, they could have been exported by a CRM and are being imported, or any number of other ways.  There are many discussions on best practices for handling Lead Source attribution in the Community.  If you need assistance setting up Smart Campaign to update the Lead Source based on your specific business criteria, please contact Marketo Support.    
View full article
Issue You want to create separate lead records with the same email address. Example: "John and Mary share the same email address smithfamily@mail.com . How can they be created as two separate records in Marketo?"   Solution By default, records created in Marketo via the areas listed below are deduplicated against Email Address. This can be configured to include additional deduplication field(s) so that records are deduplicated against Email Address + Additional Field(s) To set up custom deduplication rules, create a support ticket providing the additional fields that you would like to include as part of the deduplication and which areas you would like to apply it to. Deduplication Areas: Web form fillout Munchkin API Web service API List import Web service API - Import to list
View full article
Issue A Change Data Value activity gets recorded on a person record but the Updated At field for the record doesn't get changed to reflect it.   Solution The "Updated At" field in Marketo is a system managed field that gets refreshed any time that there is a data value change to a person field, but not when the field is on the company object instead.  To confirm what object the field in question is on, search for it in Field Management and check what folder it is located in.  The folder Info (or Lead Info) contains person fields while company fields are contained within the Company Info folder.
View full article
Issue The segmented database shows a different total for the segments than the number of leads you get on a Smart List filtering for that segment. Solution The numbers shown when viewing the segmentation is meant to be an approximation. Clicking in to the segments and selecting the people tab will show you the actual number of records in your database who are a member of the segment.  
View full article
Issue In the activity log, you see that a lead has been added to a Marketo Custom Object, but in the Custom Object tab there is no data. Solution The reason why that it appears as the custom object data is missing for a lead is because the custom object data becomes disassociated to the lead and associated to another lead when the custom object data is pushed into Marketo. When the custom object data is pushed to Marketo intended for lead A with the same dedupe field value of an existing custom object record associated to lead B, it disassociates it from the lead B and associates it with lead A. Therefore, when looking at lead B that has had an 'Add to Custom Object' activity, but does not have the Custom Object data visible in the Custom Objects tab, it is because the custom object data was associated to another lead.   For example: On Lead A, custom object data is added on x time with the dedupe field value 'test' --> custom object data is associated to this lead and is visible in the Custom Object tab On Lead B, custom object data is added on y time with the same dedupe field value 'test' --> existing custom object data that was created in previous step is now associated to this lead, becomes visible in the Custom Object tab Since the custom object data is moved to this lead, it is no longer visible in the custom object tab for Lead A.
View full article
Issue Description Why is the number of records shown in the Opportunity Analysis report in Revenue Explorer different from the number of records shown in a smart list with the same filters? (e.g. 100 records in Opportunity Analysis vs. 200 records in smart list) Why are some records in the smart list do not appear in the Opportunity Analysis report? Issue Resolution The attribution settings is set up to report on "Explicit: Only contacts with roles (default)" This means, the records in a smart list that do not appear in the Opportunity Analysis Report in RCA, are contacts without roles. Who This Solution Applies To Customers using Revenue Cycle Analytics
View full article
Issue Description Communication Failure is displayed when trying to swap an image in a section of the email   Issue Resolution This is known to occur when the email contains a significant amount of elements configured with dynamic content . These elements refer to subject, hero-banner, cta-button, etc.   For example, for an email that contains 10 elements with 50 segments (used for dynamic content), there are at least 500 versions (i.e. 10 elements multiplied by 50 segments) of the email that needs to be updated when an element is updated (e.g. swapping an image)   In order to avoid the communication failure or be able to swap an image, it is recommended to reduce the number of elements configured with dynamic content (i.e. make some elements static where possible) Is this article helpful ? YesNo
View full article