Knowledgebase

Sort by:
Issue Your scheduled send with 'Send Recipient Time Zone' sent early.     Solution When 'Send in Recipient Time Zone' is enabled for a send, our system will start the construction of the emails for the program based on the earliest send time. The remaining emails will be held by our server until the designated time for the intended recipient based on their time zone. This will cause the Send Email activity to be recorded according the time that the email was handed off to the Mail Assembly Server for construction. For the emails that are being held until the appropriate time for the send, our reporting will mark them as Pending until they are either delivered or bounced by the recipient email server.    
View full article
Summary Customers based in our San Jose datacenter experienced a service issue causing an interruption in email sends beginning on Tuesday, September 11, 2018. No customers outside of the San Jose datacenter were impacted. This issue has been mitigated and emails are now sending properly. During the impacted timeframe, some email sends were lost and will not be delivered. This documentation is for customers based in the San Jose datacenter and provides details on how to identify the impacted campaigns. We sincerely apologize for this issue and are committed to helping our customers identify impacted campaigns and ensuring proper safeguards are put in place. Impact During the recovery process, we reinitialized the Active Message Queue (AMQ), which is used to process emails during the sending process. The restarts of the AMQ had the following impact: Emails sent by Trigger campaigns during this timeframe (and those waiting in queue beforehand) could not be processed and were lost. Emails that were sent by Batch campaigns during this time or just prior may show that they were sent, but do not show a delivered activity. There are two ways that these could appear: Some Batch campaigns will show every email as sent, but zero delivered. If there are zero emails showing delivered, these Batch campaigns will not send those emails. Other Batch campaigns will show a mix of some emails sent but not delivered and some that show they were successfully delivered. If there are any deliveries showing in the campaign, the rest of the emails sent should send normally. Timeframe The email sending delays began on the morning (PDT) of Tuesday, September 11, 2018. The AMQ reinitialization caused emails to not be sent during the following timeframes: September 11, 2018, 12:30 PM PDT – 1:00 PM PDT September 12, 2018, 9:15 AM PDT – 9:50 AM PDT The problem was mitigated at approximately 10:30 AM PDT on Wednesday, September 12, 2018. Identifying Impacted Campaigns Smart Lists There are two methods to identify which campaigns had lost emails by using Smart Lists; one for Trigger campaigns, and the other for Batch campaigns. Identifying Trigger Campaigns Emails that were sent by Trigger campaigns while the AMQ was being reinitialized and all emails sent by Trigger campaigns that were waiting in queue to be processed by the AMQ when it was reinitialized were lost. The Smart List below will give you a list of affected leads that had an email sent by a Trigger campaign, but the email was lost before sending. Smart List Filter Rules:   ALL filters Filter #1: Member of Smart Campaign Campaign is "<YOUR_TRIGGERED_CAMPAIGN_NAME>" Filter #2: Was Sent Email Email is "<YOUR_TRIGGERED_CAMPAIGN_EMAIL_NAME>" Date of Activity is 09/12/2018 Filter #3: Not Was Delivered Email Email is "<YOUR_TRIGGERED_CAMPAIGN_EMAIL_NAME>" Date of Activity is 09/12/2018 Filter #4: Not Email Bounced Soft Email is "<YOUR_TRIGGERED_CAMPAIGN_EMAIL_NAME>" Date of Activity is 09/12/2018 Filter #5: Not Email Bounced Email is "<YOUR_TRIGGERED_CAMPAIGN_EMAIL_NAME>" Date of Activity is 09/12/2018 Once complete, your Smart List will look like this: Identifying Batch Campaigns Emails that were sent by Batch campaigns while the AMQ was being reinitialized, or just prior, may show that they were sent, but do not show a delivered activity. There are two ways that these could appear: Some Batch campaigns will show a mix of some emails sent but not delivered, and then some that show they were successfully delivered. If there are any deliveries showing in the campaign, the rest of the emails sent should send as normal and these campaigns were not impacted. Other Batch campaigns will show every email as sent, but zero delivered. If there are zero emails showing delivered, these Batch campaigns will not send those emails. These are the Batch campaigns that were impacted. The Smart List below will show you how to identify whether a specific Batch campaign was impacted. Advanced Smart List Filter Rules: 1 and 2 and (3 or 4 or 5) Filter #1: Member of Smart Campaign Campaign is "<YOUR_BATCH_CAMPAIGN_NAME>" Filter #2: Was Sent Email Email is "<YOUR_BATCH_CAMPAIGN_EMAIL>" Date of Activity is 09/12/2018 Filter #3: Was Delivered Email Email is "<YOUR_BATCH_CAMPAIGN_EMAIL>" Date of Activity is 09/12/2018 Filter #4: Email Bounced Soft Email is "<YOUR_BATCH_CAMPAIGN_EMAIL>" Date of Activity is 09/12/2018 Filter #5: Email Bounced Email is "<YOUR_BATCH_CAMPAIGN_EMAIL>" Date of Activity is 09/12/2018 Once complete, your Smart List will look like this: Campaign Email Results The Summary page in Smart Campaigns has a tab called Email that shows the results of any email sent by that campaign. When trying to identify campaigns that were impacted, you will be looking for campaigns that had emails sent but had zero emails delivered or bounced. All emails will be in Pending. Here’s an example of what to look for: If you see email results showing that all emails that were sent are in pending, this is a Batch campaign that was impacted. No emails from this campaign will be sent. Email Performance Report The Email Performance Report will show you the stats for how your emails have performed. When trying to identify impacted campaigns, check an Email Performance Report for emails on the specific date you need. If you see the same behavior of a large volume of emails sent but all of them in Pending, you’ll be able to track which email sends were impacted. Additional Help If you would like any additional help identifying impacted campaigns, please Contact Marketo Support
View full article
Issue You use the Change Owner or Sync Person to SFDC flow step to assign a record to an owner but when entering the intended owner's name in the flow step to select it from the suggestion dropdown, the user appears twice. Later, when running records through the flow step after selecting either option, you get an error. In SFDC you see that there are two active users with the same name. Solution Sales Owner names should be unique in SFDC for Marketo to be able to run records through this flow properly (e.g. if there are two users named "Marketo Sales", making one "Marketo Sales1" while leaving the other unchanged will correct the issue after the updated users sync over to Marketo.)
View full article
Included in this article Overview Your Premier Support entitlement has been enhanced with a Premier Success Team. Now, your Named Support Engineer is part of a 5-member Premier Success Team whose members work in concert to provide a full range of complementary skills. All your Premier support features remain intact (Mentoring Sessions, Accelerated SLAs, etc), but now your Named Support Engineer will be backed by a focused team of Premier Support Engineers to deliver world-class support tailored to meet the needs of your account. Benefits Each team is led by two Lead Support Engineers, and aided by three Premier Support Engineers. With a larger team, your engineers can specialize in specific knowledge areas, and we can connect you with our most senior engineers for your half-yearly instance reviews and mentor sessions. This will help to increase case resolution speed, decrease escalations, and elevate your overall support experience. Your Team Matthew Smith, Senior Technical Support Engineer Matt is a Certified MCE who has been working with Marketo Support since 2015. He is passionate about his customer's success and takes pride in building the relationships that help them succeed. Matt is an expert in the Core Marketo features as well as focused on CRM integrations and Sales Insight. In his free time Matt likes spend time with his two young boys and play board games and do puzzles with friends and family. Francisco Echavarria, Senior Technical Support Engineer Francisco is MCE certified and has been working with Marketo Support since 2015. He’s working on the frontlines providing triage support, Tier 2 support, and is now co-captain of Team Alpha. Francisco is a subject matter expert in CRM integrations with Microsoft Dynamics and Salesforce, API, and Sales Insight. While away from work Francisco spends most of his free time with his two young kids trying to stop them from burning down his house. Nicholas Wood, Technical Support Engineer Nick has been a member of Team Alpha since Fall 2017, and has been recognized by peers and customers alike for his desire to help our clients succeed.  His patience and resourcefulness are a vital part of what makes him a valuable member of this team.  He is skilled in the Marketo core features, as well as a focus on Email Deliverability. Nick enjoys spending time with his wife and newborn daughter, hiking, and trips to the coast. Tyler Coleman, Technical Support Engineer Tyler has worked in IT and technical support since 2014 and joined Marketo in July 2017. He previously provided technical support for a small business and a university. Tyler has extensive experience with web development, and has worked with a variety of programming languages including HTML/CSS, Javascript/Jquery, C++, python and more. Tyler is a subject matter expert in the REST API, email & landing page templates. During his free time, Tyler enjoys exploring wilderness and learning new skills and hobbies such as Yo-Yoing, juggling, painting, photography, and robotics. Dylan Paris, Associate Technical Support Engineer Dylan has been working in technical support and IT since 2014 and has been a part of Marketo Support since 2018. He brings experience in multiple support fields, with an emphasis on helping customers find quick and accurate solutions to their technical issues. When not on the clock, Dylan spends his time producing music and trying to get good at Super Smash Bros.
View full article
Abuse Report An abuse report is when an email recipient forwards a complaint directly to abuse@marketo.com.  Marketo’s Privacy and Compliance Team processes all complaints to these addresses and will unsubscribe the complainer when possible.   Feedback Loop Complaint A feedback loop complaint is when an ISP forwards the complaints that originate from their users.  For example, when someone clicks the SPAM or JUNK button in their email client. ISPs that offer FBLs expect that subscribers like Marketo will mark the complainer as unsubscribed in the original database.  Marketo does process FBL complaints and marks the email address as unsubscribed.   Additional Information: Feedback Loops (FBL) Abuse Report Deep Dive Finding Leads that are Auto Unsubscribed for Email Spam Complaints / Feedback Loop (FBL)    
View full article
Issue You have a Salesforce Custom Object that has a relationship to multiple objects, which shows up twice in Marketo with the same name. When trying to enable the second object in Marketo, you seeing an error like this: "An object with the same name is currently enabled for sync. Please give the object a unique name and retry."     Solution Marketo requires that each custom object have a unique label. You will see this error when the labels in Marketo are the same for both custom objects. In order to enable it, you'll need to change the label in Marketo for the second custom object that is attempting to be synced. The easiest thing to do is append a letter in parenthesis to denote which object it is for (e.g., "Example Object (A)" for the Account).   This will allow the custom object to sync into Marketo and the API information in the back end will remain unchanged, allowing the records and changes to sync from Salesforce into Marketo.  
View full article
IP Exclusion: did you exclude some IP's in RTP or GA? You'll need to make sure that visitors from these IP are not being tracked in both tools. Exclude internal traffic (GA) Exclude Specific IPs From Being Tracked (RTP) Segmentation: The conditions defined in the RTP segments do not cover all the website traffic. Tag implementation: The RTP or the GA tag is not installed on all the website pages Tag Timing: The data is sent from RTP to GA once both tags are loaded on the page.  In some cases, visitors are leaving the page before the data sent to GA. The recommendation here is to locate both the RTP and the GA tag higher in the code so they will load faster. Web Bot: RTP is treating web bots and crawlers differently than how GA does. There are cases where RTP identifies these "fake" user and doesn't show campaigns / send data to GA while the visit will be recorded in GA as all other sessions. Session Duration: A session in RTP last for 30 minutes from the last click, while in GA this can be customized (see Session and campaign timeout handling). This can cause some gaps in the numbers user sees. Sampling: GA shows sample of the data and not 100% accurate numbers and metrics, see: support.google.com/analytics/answer/2637192?hl=en research.neustar.biz/2013/01/24/hyperloglog-googles-take-on-engineering-hll/
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
Explanation: In RTP the tracking is session-based, similar to most web analytics tools. A session starts with the first page view and ends 30 minutes after the last click on the website. For example: Scenario   RTP Result Visitor views 1 page on the website and leaves 1 visit & 1 page view Visitor views 2 pages on the website within 30 minutes and then leaves 1 visit / 2 page views Visitor views 1 page on the website, leaves, then returns 45 minutes later and views 1 page 2 visits / 2 page views
View full article
Here are a few strategies for finding and handling your competitors if they get to your website or in your lead database. Finding your competitors The best ways to find your competitors are form fill-outs and inferred data.  You can use filters of these fields to find matching leads already in your lead database.  Use the Data Value Changes trigger with these fields to catch these leads as they enter your system. Inferred company This is the best way to spot anonymous competitors visiting your web site.  Try using the Inferred Company field to see if Marketo identified them by their IP address information. Email address There's a chance your competitors use their company email address when filling out your form.  Search for the domains of your competitors using the Email Address filter with the "contains" operator. Company name Like email address, this is a straightforward way to catch your competitors as they enter their information in your forms. Handling competitors You have a few choices for handling your competitors once you find them. Blacklist them Changing these leads' Blacklisted flag to true will ensure that they don't receive any more emails from you.  This is a good way to keep those leads in your database and ensure that they're not part of your email campaigns. This campaign will spot those leads and blacklist them should they appear: Smart List: Trigger on Data Value Changes where Email Address contains [your competitors domains] Flow: Change Data Value -- Blacklisted to true Send an alert You may find it useful to get alerted when your competitors visit your website.  Try this campaign: Smart List: Trigger on "Visit Web Page" Filter on "Inferred Company contains [your competitors]" Flow: Send Alert with an email that includes a Send Alert Info token. Schedule: Change the Qualification Rules to 1 per day But don't delete them Deleting these leads was probably your first reaction, but you probably shouldn't.  Instead, look at their Activity Log to find out what pages and offers they were viewing.  Also if they return to your site, their subsequent activity will be added to that activity log (as opposed to added to a new, anonymous lead).
View full article
Issue Email Performance Report shows different results than same audience as a smart list Solution Create a filter for the report for field Email address is not empty. Root Cause An email performance report includes activities for all people, including those that have been deleted since the email was sent. Sometimes, you want to see activities only for active people. In that case, you need to filter deleted people out of your report. Use the Smart List tab to create a smart list for the report. If you aren't filtering on any specific field, set the Email Address filter to: is not empty.
View full article
Issue What is the typical sync interval timing? Is there a timing difference between updates and inserts? If the change originates in SFDC vs MKTO? Solution By default the sync interval in Marketo is set to 5 minutes. This can be set to be greater than 5 minutes on request. Now this doesn't mean that Marketo will sync updates every 5 minutes, it means that there will be approximately a 5 minute wait after one sync cycle finishes and and the next sync cycle begins. The duration that an individual sync cycle will take depends on how many records for each object need to be updated/created. Remember flow actions in smart campaigns are immediate, so if you ever don't want to wait for the background sync for a specific lead or set of leads then you could always run an intimidate flow action, just bear in mind that flow actions use 1 API call per lead record whereas the background sync is much more efficient and can handle 200 records with just one API call.    
View full article
Issue Description: The Activity Log shows "Fill out a form" without a page visit. How users could fill out a form without visiting the page? Issue Resolution: Google Chrome introduced Incognito. Firefox, Safari, Opera and Internet Explorer implemented Private Browsing. Pages that users visit in Private Browsing/Incognito will not leave traces, like cookies, on users' computers after they close all open windows. A normal visit to any page is not tracked during visits, regardless the navigation path. That includes other pages after the form is filled out. The new Do Not Track feature is a contributing factor for apparently incomplete Activity Logs. When users turn on the Do-not-track feature, the browser tells every website they visit (as well as their advertisers and other content providers) that they do not want their browsing behavior tracked. Honoring this setting is voluntary — individual websites are not required to respect it. Websites that do honor this setting should automatically stop tracking your behavior without any further action from users.
View full article
Issue Does Marketo re-use or recycle old deleted lead IDs?  Root Cause After a lead is fully deleted, it would be very rare for the lead ID to be re-used. The vast majority of the time lead IDs are unique and not re-used. If you have an external database or reporting system that relies on a unique lead ID, the best practice would be to ensure these systems are up-to-date on all lead deletions.
View full article
Included in this article: Overview Missing or Extra Headers Issues with Quotes Invalid Characters Invalid Country or State Names   Overview   The Named Accounts feature is a way to target your RTP Campaigns to specific Accounts in a Segment. It's a powerful tool for targeting specific organizations, but you may encounter errors when uploading the list of Accounts you wish to target. This doc will go over over the most common problems experienced when trying to upload a CSV file to a Named Accounts list. To learn how to upload a Named Accounts list, follow this article.     Missing or Extra Headers   The first line of your CSV file should be, in order: Name, Domain, Country, State. Make sure there are no extra columns or white spaces at the end of the line. See the screenshot below for an example of how to format your headers     Issues with Quotes   Occasionally Excel will use curly quotes, which look like these: “ ”. However, curly quotes are not recognized by the uploader, instead the uploader will recognize straight quotes like these: " ". Any curly quotes will need to be replaced by straight quotes to resolve any uploading issues. To do this:   First, make sure your file is saved as a CSV file (.csv) and not an excel file (.xlsx) Right click on the file to open the CSV file using a text editor (ex. Notepad, TextEdit, etc) Find and replace both opening (“) and closing (”) curly quotes with a regular quote (")   Invalid Characters   This error is caused when there is an invalid character in the CSV file that you are trying to import.  This is particularly common in CSV files using non-English characters.  To rectify this, make sure your CSV file is UTF-8 encoded.  By default, Excel encodes characters in ANSI format, so if your file has non-English characters in it, you will need to convert it to UTF-8.  You can do this in Notepad or similar text editors using the following steps:   Open the CSV file in the text editor and click "Save As" Save as type: All Files (Make sure you include the .csv file extension in the file name) Change the Encoding to UTF-8       Invalid Country or State Names   If the location columns are in use (they are optional), check to verify that the countries and states are input in the correct way:   Country names should be either the full country name, or its two digit country code. Ex: United States or US State names should just be their two digit state code. Ex: CA, NY, OR Make sure that only US states are included in the 'State' column. Named Account lists do not support other countries' states or provinces.
View full article
Please ensure that you have access to an experienced JavaScript developer. Marketo Technical Support is not set up to assist with troubleshooting JavaScript. Summary: Say you want to validate a custom field before someone submits a Marketo form on a Marketo landing page, then let Marketo do it's standard validation.   You can do that by overriding the formSubmit function in Javascript.  You can override it with a Custom HTML element for a single page; you can also add this Javascript to your landing page template so it affects many landing pages.   First, build a Javascript function to execute your custom validation (formIsValid() in the example below).  It should return a value of "true" if the fields validate. If not, return false.   Open the landing page for editing and drag a Custom HTML element onto the web page.  Paste in this Javascript and add your custom validation to the formIsValid() function.   <script type="text/javascript" src="/js/public/jquery-latest.min.js" language="Javascript"></script> <script type="text/javascript">      // set no conflict mode for jquery   var $jQ = jQuery.noConflict();   function myFormIsValid() {     var thisIsValid = true;     // Put your custom validation here.     // If anything goes wrong, set thisIsValid to false.         // for example, show an error message if the email contains "bob"     if ($jQ("#Email[value*=bob]").length > 0) {        Mkto.setError($jQ("#Email ~ span").prev()[0],"No Bobs allowed!");        thisIsValid = false;     } else {        Mkto.clearError($jQ("#Email ~ span").prev()[0] );     }     return thisIsValid;   }   function formSubmit(elt) {     if (!myFormIsValid()) {        return false;     }     return Mkto.formSubmit(elt);   } </script> Here's another example that checks if a required checkbox, such as a terms of service agreement, is filled before submitting: <script type="text/javascript" src="/js/public/jquery-latest.min.js" language="Javascript"></script> <script type="text/javascript">      // set no conflict mode for jquery var $jQ = jQuery.noConflict(); function myFormIsValid() {     var thisIsValid = true;       // show a message if they fail to check the box     if ($jQ("#TermsOfServiceAgreement").attr('checked') != true) {        Mkto.setError($jQ("#TermsOfServiceAgreement ~ span").prev()[0],"Please agree to the terms above.");        thisIsValid = false;     } else {        Mkto.clearError($jQ("#TermsOfServiceAgreement ~ span").prev()[0]);     }     return thisIsValid; } function formSubmit(elt) {     if (!myFormIsValid()) {        return false;     }     return Mkto.formSubmit(elt); } </script>   Follow these instructions if you want to retrieve the form fields via Javascript: Setting or Getting a Form Field Value via Javascript on a Landing Page The example above also shows you how to set an error field If you want to set or clear an error message on a field, you can use these two functions in your validation function. Note: These only work on form fields from the Marketo form designer. Replace the highlighted yellow bits below: Email -- the ID of the field where you want to show an error error message -- the text you want to display for this error           // error -- highlight the field           Mkto.setError($jQ("#Email ~ span").prev()[0], "error message");             // no error -- clear the field           Mkto.setError($jQ("#Email ~ span").prev()[0]);  
View full article
Issue Issue Description A Smart List with a filter for an integer field with a specified range value, such as 'less than 100', is qualifying records that have a NULL(empty) value for the integer field.      Solution Issue Resolution Marketo will treat NULL/empty as equivalent to 0 in this case, and qualify the lead as having a value less than 100.  However, Marketo does not treat 0 as NULL/empty Adding the filter "[field] is not empty" to block records with NULL values will resolve this  
View full article
Issue Revenue Cycle Explorer Data is not accurate comparing to Smart lists or other areas of Marketo.   Solution The data inside of Revenue Cycle Explorer (RCE) can be different from Marketo and can raise concern. However there is a couple reasons the data may not match 100%!   The data date range is within last 24 hours. Revenue Cycle Explorer utilizes an proccess which replicates the data to a dedicated Database just for running RCE reports. This proccess runs during the middle of the night to replicate the data, so the most recent the data would be is from the night before or early morning!   The data measure is looking at different data type or defining it in a different manner. The name of a measure is only part of the story. While 2 measures may have the same name, the way the data is calculated can be different between the two! You can find a deeper confirmation of what exactly is being measured or detailed by one of two ways. Right click on the Measure or Attribute & choose Properties. The Properties window will give you an additional data under Description. A alternate option is if you already have the Measure or Attribute on the report, you can right clic on it and choose "Tell me about..." and it will provide an explanation of the Measure or Attribute and how we are calculating it. Mouse over the Measure or Attribute, this will show an hover text showing the details of what and how its being measured or analyzed. OR   Revenue Cycle Explorer will see all leads and does not filter out leads by work-space visibility. So leads from other workspaces may show in your analytics if not filtered out!   Deleted leads still can show for up to 24 hours, due to the afformentioned data replication cycle.   There are other reasons data may be different, feel free to reach out to Marketo Support for further details or investigation!  
View full article
Issue An Email Performance Report in Marketo was exported and opened in Microsoft Excel and the email open percentage and average click percentage is calculated using the AVERAGE function in Microsoft Excel. There is a difference in the average total calculated using the AVERAGE function in Microsoft Excel as opposed to the Total calculated in the Marketo Email Performance report.   Solution Marketo's total is a 'Weighted Average' which is different to a normal average calculation in Microsoft Excel "A weighted average differs from an average in that a weighted average returns a number that depends on the variables of both value and weight." support.microsoft.com/en-us/help/214049/how-to-calculate-weighted-averages-in-excel    
View full article
  Before you can enable custom field groups for reporting in the Model Performance Analysis (Leads) Area of Revenue Cycle Explorer, you must categorize standard   or custom fields (only applies to lead and company attributes) into groups for reporting via the Field Organizer in Marketo Lead Management.   Here’s How Custom Grouping of Fields Works   The Field Organizer is accessible from the Lead Database in Marketo Lead Management:    Navigate to Lead Database > New > New Field Organizer.   When you select a standard or custom field from the Field drop-down in the New Field Organizer dialog box, the system maps the Marketo Lead Management data   type associated with the field you want to group with one of three available editors in the Field Organizer: string, integer, or date.    The next three sections describe how to create a custom field group for a string, integer, or date type. Refer to the appropriate section below.   Create Custom Field Group – String Editor    To create a custom field group using the Field Organizer string editor:    1.       From Marketing Activities, click New and select New Field Organizer. The New Field Organizer dialog box displays.    2.       Select a standard or custom field from the Field drop-down with a data type that maps to the string editor (see table in previous section).             “Billing State” will be the field used in this example. 3.       Click Create. The new custom group displays in the Lead Database tree represented as Field Name > Field Name Group           (example: Billing State > Billing State Group).           Since you are creating a custom group for a “string” field, the string editor displays in the Settings tab, which opens by default.           All of the data values for the selected field populate in the canvas. 4.       Double-click the notepad icon next to the new custom group name in the string editor to customize the name.           For example, you might rename Billing State Group to Region. Type the desired new name in the modifiable text field and click away to auto-save. 5.       By default, all data values are placed in the “Other” sub-group. To categorize the data values, click Add Group to create a sub-group           and enter the name of the group in the modifiable text field that displays. You can add up to ten sub-groups to categorize the data values.           Each sub-group that is created is assigned an ID number: 0, 1, 2, etc In this example, we will create Regional groups, such as Western (0), Eastern (1), and Southern (2). To delete a sub-group, simply click the red “X” next to the sub-group name. If there are any data values in the group, the data values will be moved to the default group of “Other.” 6.       You can add data values to a sub-group in one of two ways:           a.       Highlight a data value(s) in the canvas  and drag and drop the data value(s) into the appropriate sub-group, OR           b.      Highlight a data value(s) in the canvas and enter the sub-group ID number on your keypad. This shortcut moves the data value(s)                    into the appropriate sub-group To remove a data value from a sub-group, reassign the data value to the default group of “Other.” 7.       Repeat the above step until all data values are assigned to the desired sub-groups as needed. 8.       Use the filter option in the upper left corner directly above the canvas to select and view the data values in one of more sub-groups. The data values based on              your filter selection display in the canvas. Once the groups are defined, you can Enable the custom field group for reporting in Model Performance Analysis (Leads) via the Revenue Cycle Analytics tab in Marketo Lead Management. Create Custom Field Group – Integer Editor To create a custom field group using the Field Organizer integer editor: 1.       From Marketing Activities, click New and select New Field Organizer. The New Field Organizer dialog box displays. 2.       Select a standard or custom field from the Field drop-down with a data type that maps to the integer editor           (see table in beginning of article). “Annual Revenue” will be the field used in this example. 3.       Click Create. The new custom group displays in the Lead Database tree represented as Field Name > Field Name Group           (example: Annual Revenue > Annual Revenue Group). Since you are creating a custom group for an “integer” field, the integer editor           displays in the Settings tab, which opens by default. 4.       Double-click the default custom group name above the integer editor to customize the name. For example, you might rename           Annual Revenue Group to Annual Revenue by Size. Type the desired new name in the modifiable text field and click Save. The integer editor allows you create multiple sub-groups to define each sub-group by size. In this example, three groups will be created for Small, Medium, and Enterprise businesses. 5.       To add your first group, enter a name in the Group Name field (example: Small) and enter a max value in the Group Range field (example: 200000). 6.       Click Add Group. An empty group entry displays below the group just entered. You can add up to ten sub-groups to categorize the data values.           Note that each Group Range entry builds upon the previous entry. If you leave the last Group Range entry blank for the last custom           sub-group you create, a maximum data value is not set. The example below shows an entry for Small, Medium, and Enterprise businesses. To delete a sub-group, simply click the red X next to the sub-group name. 7.       Once all the sub-groups are defined, return to the summary tab to view a summary of all sub-groups defined for that field. Once the groups are defined, you can Enable the custom field group for reporting in Model Performance Analysis (Leads) via the Revenue Cycle Analytics tab in Marketo Lead Management. Create Custom Field Group – Date Editor To create a custom field group using the Field Organizer date editor: 1.       From Marketing Activities, click New and select New Field Organizer. The New Field Organizer dialog box displays. 2.       Select a standard or custom field from the Field drop-down with a data type that maps to the date editor           (see table in beginning of article). “Acquisition Date” will be the field used in this example. 3.       Click Create. The new custom group displays in the Lead Database tree represented as Field Name > Field Name Group           (example: Acquisition Date > Acquisition Date Group). Since you are creating a custom group for a “date” field, the date editor           displays in the Settings tab, which opens by default. 4.       Double-click the default custom group name above the date editor to customize the name. For example, you might rename           Acquisition Date Group to Acquisition Date Categories. Type the desired new name in the modifiable text field and click Save. The date editor allows you create multiple sub-groups and define each sub-group by date. In this example, two groups will be created: Q1-11 Leads and Q2-11 Leads. 5.       To add your first group, enter a name in the Group Name field (example: Q1-11 Leads) and enter a date in the date field that represents           the date the lead was acquired on or before (example: 3/31/2011 for that last day of Q1-11). 6.       Click Add Group. An empty group entry displays below the group just entered. You can add up to ten sub-groups to categorize the data values.           Note that each Group Range entry builds upon the previous entry. If you leave the last Group Range entry blank for the last custom sub-group you create,           an end date value is not set. The example below shows an entry for Q1-11 Leads and Q2-11 Leads. To delete a sub-group, simply click the red X next to the sub-group name. 7.       Once all the sub-groups are defined, return to the summary tab to view a summary of all sub-groups defined for that field. Once the groups are defined, you can Enable the custom field group for reporting in Model Performance Analysis (Leads) via the Revenue Cycle Analytics tab in Marketo Lead Management.
View full article