Knowledgebase

Sort by:
  Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well.   Activities in the activity log are only retained for 25 months, or 37 if you have purchased the premium data retention option. The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done.     Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed.   For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead.   An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list.         Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs.   Example: This approach can work for many different activities, but let’s use form fill outs as an example.   Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter.   Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it:   1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field.   2. Create a new Smart Campaign   3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List     4. Add these two Flow Steps to the Campaign Flow: Flow Step 1: “Change Score” Score Field Name: your score field name Change: +1   Flow Step 2: “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name”  “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing       This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing.       Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.      
View full article
Issue A recent Smart Campaign or Email Program sent Person records in Marketo more emails than should be allowed based on settings in Communication Limit Settings in the Admin area of Marketo. Solution This is commonly caused by one of three things: The emails that sent after the communication limit was hit were Operational. To verify if this is the case, select the email asset from the menu tree on the left and review the summary of the asset in the canvas where you will see if the email is Operational or not. The Block non-operational emails checkbox is not checked in Edit Communication Limit Settings. Setting values the "Per Day" and "Per 7 Days" dropdown menus does not enforce the communication limit. In order for this limit to be enforced, the "Block non-operational emails" checkbox must be checked.  Enable Communication Limits The Email Program or Smart Campaign are not set up to follow Communication Limits. Apply Communication Limits to Smart Campaign Enable/Disable Communication Limits in an Email Program  
View full article
Technically, you cannot move records backwards in a progression status.  The only so called “backward” status that you can change the record to is a progression status of “Not In Program”; however, doing this removes them from the membership of the program.  If you do this procedure, this will allow you to re-add them with a different status.   We mentioned technically this cannot be done but logically, there is another method that allows you to juggle the record’s progression status but in a more lateral movement with what appears to be in a “backward” state.  This is all dependent on how you have your channel steps configured.  To access your channel steps, please do the following:   Choose Admin Choose Tags Click the + next to Channel Locate the channel you wish to configure and highlight it Click the drop-down menu towards the top of Tag Actions, and select Edit   You should now see a pop-up window that allows you to configure the status steps for that channel like the following example:   This is a article attached image     If you configure statuses that have the same step number, this will allow you to move the record in a lateral movement which, in a sense, is somewhat like a backward progression but it really isn't.  With the example screen capture, I can do a change in progression status of “Invited” to “Attended Show” and vice-versa because the step is with an identical number. If I wanted to change in progression status of “Invited” to “Engaged” and back, it will not work because the step value is not identical. You can reference more information about this in the Create a Program Channel article.
View full article
Note: Once you have migrated to Admin Console, you can manage your support cases through the feature provided in the Admin Console Platform. To learn more, visit: https://experienceleague.adobe.com/docs/customer-one/using/home.html. Once you have submitted a case to Marketo support, we provide a simple way of staying connected to your case and the cases submitted from your company through the Marketo Support Portal. You can access the support portal through your Marketo instance by selecting Community in the top right corner: This is a article attached image You can also access the support portal directly at https://support.marketo.com and login with your Marketo credentials (login and password). This will not work for users with SSO.   Once you are in the support portal you can Create a Case for Marketo Support or you can also review any cases that are open and being worked on by support or review your case history. Navigate to My Case management: This is a article attached image From the My Cases navigation you can access the following case views: This is a article attached image My Recent Cases* - Cases that you have opened in the past 30 days All Company Recent Cases* - Cases that any authorized support contact has opened in the past 30 days My Open Cases – Cases created by you that are being triaged by Support and pending Support’s response and are more than 30 days old My Closed Cases – Cases that were created by you and are now closed My Awaiting Fix Cases – Cases that were created by you where Marketo is developing a fix which will be implemented at a later date All Company Closed Cases – Cases that were created by you or your colleagues that are now closed All Company Open Cases - All open cases submitted for the account Company Awaiting Fix Cases – Cases that were created by you or your colleagues where Marketo is developing a fix which will be implemented at a later date Management Escalations - Escalations opened by you or your colleagues  Survey Cases - Surveys that are available for you to fill out after a case is closed *Cases that have been opened for more than 30 days will move from Recent cases to Open cases   To view specific case details, click a case number. This is a article attached image From the Case Details, you can perform the following: Close your Case - Select the "My Case is Resolved" button to close your case Add Comments - Provide additional comments to support or respond to a Support question Add Attachment - Provide any screenshots or documents that will help illustrate the issue you are reporting   If your case has been closed there are two options available to you.   Reopen - You can reopen your case if you are not satisfied with the case resolution by adding a comment in the case. Case Survey - Once your case has closed, please consider offering feedback on the level of Support you received.
View full article
If you have submitted a support case and you feel that the case was improperly handled or that the solution being offered does not meet the communicated Marketo support expectations, then we would welcome the opportunity to look deeper at your specific support engagement and work with you on delivering a better resolution. Caution: If the item you're looking to escalate is related to a Production Down incident, please call the support line for your region to receive immediate assistance. Support Manager escalations are only handled during normal business hours. The phone numbers for each region are listed below, follow the prompts for P1: Americas: +1.877.270.6586, Direct: +1.650.376.2303 Europe, Middle East, & Africa: +353 (0)1 242 3030,  UK: 0800 151 3030 Asia Pacific: +61 2 8310 7646  Japan: +81.03.4233.9014 How to Escalate: Step 1. Navigate to the "Case Management" area of the support portal either by mousing over the Support tab and selecting "Case Management" or clicking the Support tab and click on the “My Case Management” button. NOTE: You will need an open or recently closed case in order to escalate to support leadership. This is a article attached image Step 2. From here you will need to click on either an open or a recently closed* case: This is a article attached image *Support Cases that have been closed for longer than 10 days are no longer eligible to be re-opened and we ask that you open a new support ticket for your current issue prior to escalating to a Support Manager. We ask that you have an open support ticket for a Support Manager to be able to address specific issues. Step 3. After selecting a case, click on the Escalate to Manager button: This is a article attached image Step 4. A pop up will display and you will need to the purpose for the escalation and click on the “Escalate” button. This is a article attached image Once your support escalation case has been submitted a Marketo Support Leader will contact you within 1 business day of your support region's support hours to address the issue.
View full article
    Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well.   Activities in the activity log are only retained for 90 days, 25 months, or 37 if you have purchased the premium data retention option. The official Marketo Data Retention Policy can be found here: Marketo Activities Data Retention Policy   The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done.     Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed.   For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead.   An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list.   Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs.   Example: This approach can work for many different activities, but let’s use form fill outs as an example.   Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter.   Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it:   1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field.   2. Create a new Smart Campaign   3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List 4. Add these two Flow Steps to the Campaign Flow: Flow Step 1: “Change Score” Score Field Name: your score field name Change: +1   Flow Step 2: “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name”  “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing. Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.
View full article
Issue What BCC options are there for email sends? Solution Marketo support can enable BCC on request.  If an email address is to be BCC'd on a batch email send, they'll get 1 BCC for every 1 email Marketo sends. (10k email sends = 10k BCC emails). This can be useful for archiving and compliance purposes, but should not be used for simple campaign confirmation. If you just want to make sure the email went out as scheduled, the easiest way is to create yourself as record in the database, and include yourself in the batch send. Only one BCC address is supported at this time, if multiple BCC recipients are required then it is recommended to create an alias which will forward the messages. This setting is applied to the entire instance, and will affect all emails sends from all Campaigns and Programs while enabled.  Every email sent while this feature is enabled will result in a corresponding BCC email. CAUTION: Dedicated email address setup for the BCC email traffic must be able to handle high volumes of email. Discuss with your IT Team or email service provider to verify their Email Server can handle the estimated volume of incoming email. If the Email Server is not well equipped this feature can cause your Email Server to backlog, become unavailable temporarily, or reject the BCC emails. If the request is for a single email send, we recommend using the following CC process: Email CC | Adobe Marketo Engage  
View full article
  Overview SSO Authentication Updating SSO Credentials Tips SSO Only Login Wait to disable the existing certificate Overview Marketo’s Single Sign On (SSO) feature allows your company to use your own company’s SSO service to authenticate your login into your Marketo instance. Your initial setup of the SSO is covered in the documentation here.   You may need to change your SSO authentication settings after the initial setup. This document will show you the process on how to do so.     SSO Authentication The Identity Provider (IdP) you use will provide you with your SSO authentication credentials and security certificate. Marketo uses this information to validate your login from your IdP, so these credentials come from your IdP.     Updating SSO Credentials Once you have retrieved the new security certificate, you can enter it into Marketo.   1. Under Admin click on Single Sign-On. 2. Select Edit in the SAML Settings 3. Enter your Issuer ID, Entity ID, select the User ID Location and click Browse. 4. Select your Identity Provider Certificate file. 5. Click Save. Tips There are a couple things to watch out for when changing your SSO certificate. Here’s a couple tips to avoid trouble along the way.     SSO Only Login If your company uses SSO for login, you’ll have an optional setting to restrict login access to your Marketo instance to SSO logins only. This prevents users from logging in directly, forcing the use of SSO.   You can check for this setting under Admin > Login Settings   These settings do allow the creation of a special User Role that can bypass the SSO restriction. However, sometimes as people come and go within the company, the users enabled with that User Role could no longer be available.   TIP: Before changing your SSO certificate, create a new user utilizing this User Role that bypasses the SSO requirement. If something goes wrong while setting up the new certificate, you’ll be glad you have a back door into the Marketo instance!   Wait to disable the existing certificate Your IdP will issue a new certificate, but what if something goes wrong while entering the new information into Marketo?   TIP: Get the new certificate and set it up in Marketo before you fully disable the existing certificate within your IdP on their side. If something happens to the new certificate, you’ll be glad you have the do-over available and can switch back to the existing certificate that still works!
View full article
Issue Will custom settings, such as Launchpoint integrations, API configurations and SFDC sync settings, remain in place when doing an instance copy, or will they be overwritten?     Environment Non-Microsoft Dynamics integrated Instance Solution All permanent configuration settings which can be done to a Marketo instance are reset to the default values or settings in the destination instance. Everything is copied except for the below list: Lead Database and activity history are not copied CRM configuration is reset on the destination instance. Users are not copied. CRM Field Mappings are removed in the destination instance except for standard mappings, and must be set during the Field Mapping Stage of CRM sync initialization. RCA information is not copied. Program subscriptions are not copied. Campaign History is not Copied. CNAMES for Email links and LPs are not copied. All Account-string based properties are modified accordingly. Munchkin ID of the destination instance is preserved. Sales Insight Admin Configuration is Reset. Outlook licenses are not copied. All pre-existing data on the destination instance will be destroyed. Asset IDs for emails, landing pages, and programs will match Launchpoint and API integrations are not copied   If data may exist on the destination instance prior to the copy process, this may require that you work with your Success Manager to obtain a replacement instance for the copy to be completed. NOTE* This process is not applicable to customers utilizing the native Microsoft Dynamics integration.
View full article
Issue After going through a modification of a text field type from 'Text' to 'String', the field is no longer available as a filter for smartlists. Don't worry, the field is not gone - it is just temporarly unavailable. Solution Changing the field type from one type to another is a database intensive operation and in some cases where the field values are widely populated across your database records, this can cause the filter to be unavailable until the operation is completed in full. The time it takes for the field filter to become available may vary and it can take up to ~30 hours sometimes until the field filter is available again after the type of the field has been changed.  
View full article
Marketo Support's Mission is: To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success.   Areas of Responsibility: Technical Support Engineers (TSEs) are your initial point of contact for any technical questions or concerns. TSEs are responsible for troubleshooting issues within your Marketo instance and common include:   My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community   Our TSEs are not web developers and as a result they are unable to troubleshoot most types of custom coding (ie. HTML, JavaScript, XML, etc.). Our support team is able to help with the following types of non-custom code:    Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API   Our TSEs are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience.   Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented.   Response Time   Our TSEs are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services.  We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to Service Level Targets.
View full article
Issue Executing a GET API call to retrieve a list of available activity types in the target instance using the '/rest/v1/activities/types.json' endpoint, resolves with an unexpected attribute name for a field with the display name ID in the context of Marketo Custom Objects. An example of that may be a Marketo Custom Object with the following name: '3 to be', as can be shown in the image below: One of the '3 to be' Marketo custom object fields name is 'ID'. (highlighted in red). When performing a GET API call using the '/rest/v1/activities/types.json' endpoint, you will be getting a list of available activity types in the target instance, along with associated metadata of each type, however for a Marketo custom object with an ID field name, you may see it returns back with a slightly different name, in this case, it would be returning the following output for my test Marketo Custom Object activity: { "id": 100019, "name": "Add to 3 to be", "primaryAttribute": { "name": "3 to be ObjRef", "dataType": "integer" }, "attributes": [ { "name": "3 To Be Person Id", "dataType": "integer" }, { "name": "ID (3)", "dataType": "string" }, { "name": "Linkfield4", "dataType": "string" } ] } ], Here's an image of what it may look like when making the call using POSTMAN: In fact, the character in the brackets next to the ID field represents the very first character of your Marketo Custom Object name.    Environment Customers who have Marketo Custom Objects where one of the custom object fields is named 'ID'. Solution If this is interrupting your business, you may want to select a different name for the ID field under your Marketo Custom Object. (ie. ID number, Transaction ID etc.) Root Cause This behavior is expected and is a result of the 'ID' field being a unique field in the context of Marketo custom objects world and while it may be possible to create a Marketo Custom Object field with the name 'ID', it may be better to give it a distinct name that will be better describing what kind of ID field it is.   
View full article
Issue When editing the expiration date for a user in Admin by completely removing the expiration date set to null and clicking save. The change is not saved, and the expiration date remain. Environment Expired Date for user Expiration Date Changing the expire date to never in Admin   Solution There are two options: 1. Change the expiration date to a date in the future.  2. Delete the user in Admin and recreate the user again and set the expiration to never.  *Please note that if option 2 is selected, the history of the user is will be lost and this cannot be retrieved. Root Cause This is a design limitation as it is expected for the user with an expiration date to be deleted from the Marketo Instance after the expiration date has been reached. 
View full article
Issue When changing Program Status in Admin > Tags > Channel for "Event" result in this error, "Failed: no more information".  Environment Changing Program Status  Failed: no more information Solution "System mapping for Registered, Waitlisted, and Attended statuses is required." Therefore, ensure the status is mapped to Registered, Waitlisted, and Attended.   Root Cause One or more of these statuses "Registered, Waitlisted, and/or Attended" were not mapped as required. 
View full article
Issue When adding new IP Address to the IP Restrictions list on Admin > Login Settings > IP Restrictions, you receive this error message: "Your current IP address (XXX.XXX.XXX.XXX) cannot be blocked."   Environment Admin IP Restrictions Login Solution Ensure that you have Admin Access to the Marketo instance and that you have logged into the Marketo instance via one of the IP Addresses listed on the IP Restrictions list.  Root Cause User logging into the instance with an IP Address not on the IP Restrictions list. 
View full article
Issue What type of HTTP Redirect Rules does Marketo use when you setup a redirect rule in Admin > Landing Pages?     Solution Internal Pages such as landing pages hosted on Marketo will use a HTTP 301 Redirect External pages & non landing page URL's (when using "non-Marketo landing page") used in the redirect rule will utilize a HTTP 302 Redirect: Branding links do not use an HTTP Redirect and use a script-based redirect on the Branded links page. Example: Email branding link - http://go.mybranddomain.com/ABCDEFIlB0ETg0X063WLL1 is a Marketo hosted page that utilizes a script to redirect & point to http://www.thetargeturlinanemail.com
View full article
Issue Per our developer page: https://developers.marketo.com/rest-api/assets/programs/#update, it is possible to update tags on your existing program When updating a program tag within an existing program, you may encounter an error below given the tag and its values are correct.  {"code": "709","message": "Required tags are mandatory"}]} Environment Any API clients when performing the Web Service API Solution The workaround is to have the tag updated via the UI. Root Cause "Updating tags is a destructive operation." Any attempt to update the tags of a program must include valid values for all of the required tags for a program. Unless the 'specific' tag type you are working on is the only required tag type in the instance, then that is possible to update it using the API. Otherwise, you'll encounter the error above as it is a system behaviour.
View full article
  Full Details of all Marketo Support Offerings:   Support Levels Offered   Service Level Response Targets   Global Contact   https://support.marketo.com:             Online Support Portal for Case management and Knowledgebase search support@marketo.com:                     Email to Case Submission supportescalations@marketo.com:   Contact Support management regarding Support services marketocares@marketo.com:            Questions regarding Support or Community access   Regional Contact Information Americas: Hours: M-F, 6am to 6pm Pacific Toll Free US: +1 877 270 6586 Direct: +1 650 376 2303   Languages Supported: English, Spanish Observed Holidays: New Year's Day Independence Day Thanksgiving Day and the Day After Christmas Day New Year's Eve Europe, Middle East, & Africa: Hours: M-F, 8am to 5pm GMT Europe: +353 (0)1 511 9556 UK: 0800 151 3030   Languages Supported: English, French, German, Portuguese Observed Holidays: New Year's Day Easter Monday Christmas Day St. Stephen's Day Australia Hours: M-F, 9am to 6pm AET ANZ: +61 2 8031 8188   Languages Supported: English Observed Holidays: New Year's Day                           ANZAC Day Christmas Day                             Good Friday Easter Monday                             Boxing Day Japan: Hours: M-F, 9am to 6pm JST JP: +81.03.4233.9014   Languages Supported: Japanese Observed Holidays: New Year's Holiday                      Marine Day Coming of Age Day                      Respect for Senior Citizens Day National Founding Day                National Holiday Spring Equinox Day                     Autumnal Equinox Day Day of Showa                              Sports Day Constitution Memorial Day          Culture Day Green Day                                   Labor Thanksgiving Day Children's Day                             Emperor's Birthday Substitute Public Holiday             Year End After-hours Support for Production Down Issues: Online: Enter a Support Portal Case with Priority=P1 Phone: Call Support Line and follow the P1 prompts   Initial Response SLT We ask that you use the following priority definitions when setting your case priority: Priority Description P1 Critical Business Impact: ​ Customer's production business functions are down or have significant data loss or service degradation and immediate attention is required to restore functionality and usability. P2 Major Business Impact:​ Customer's business functions have major service degradation or potential data loss, or a major feature is impacted. P3 Minimal Business Impact: ​ Customer's business functions have minor service degradation but there exists a solution/workaround allowing business functions to continue normally.   P4 No business impact:​ General question regarding current product functionality or an enhancement request.
View full article
Issue A smart campaign is configured to clear the field value for a field, however, when the smart campaign ran, it didn't appear to have cleared the field values and the campaign results display no activities. Solution Check to see if people qualified for the smart campaign and became campaign members by clicking on the 'View Campaign Members' button. If there were people that are in the campaign members list, then it means people qualified and the flow step did not process. If people did qualify, then check [Admin > Field Management] to see if there is a block field updates enabled on "Flow change data value" - In this case, temporarily disable the block field updates on "Flow change data value" for the field, run the campaign so that it can clear the values on the field and then re-enable the block field updates. Root Cause The smart campaign did not return any activities in the results if the flow step was only configured to change the data value of a field that has block field updates enabled for "Flow change data value" Environment Smart Campaign Change Data Value Clear Field Values Field Management Block Field Updates
View full article
Summary duplicate records with the same email across lead partitions can be affected by uploaded custom object activity Issue System not separating lead partitions for custom object imports Uploading custom object activity affects duplicate records across partitions Custom Object activity import writing to the most recently updated record regardless of partition Solution Use the following workaround:  Run an update on the records that should be affected by the custom object activities import. This will make sure they are the most recently updated records among the duplicates Root Cause Normally when you do a list import, it would import into the one partition, whatever partition the list is located in and only impact the record in that one instance.  But when you import a Custom Object, it's able the see ALL the records across ALL the partitions.  If there are duplicate records, it just looks to see which one was updated most recently and grabs that one for the list import. So if you have lead record in A with Add to Custom Object already completed and you re-import again but the lead record in B has been updated more recently and has NOT had the custom object added to it, you get the duplicate "Add to Custom Object" activity. Environment Multiple lead partitions with duplicate records across them Custom Object activity import
View full article