Knowledgebase

Sort by:
Included in this Article: Overview In the Web Personalization platform, you defined a campaign that included certain pages, but you are seeing the campaign appear on pages that you didn't intend them to appear on. Below, we will describe what might be the issue and how to solve it. Why This Happens When defining a segment using the "Specific Pages" parameter, every visitor that views this page will be matched to that segment. Once this happens, the "sticky" campaign will be triggered and will be displayed on every page that includes this Zone id parameter. After the visitor is matched to the segment and the campaign is triggered, the segment is not taken into consideration anymore, so this visitor will keep seeing the campaign every time the Zone id exists on the page. Two Ways to Fix this Problem Set the campaign as "Not Sticky" This will make the campaign show up only once per session, and only when visitors are viewing the specific pages defined in the segment.     Go to the Campaigns page      Edit the existing campaign      Uncheck the box for "Sticky" Use a dedicated Zone id that exists only on the page(s) to include in the campaign In Zone campaigns are displayed in a particular zone in a website, designated by the Zone id.          Find "Zone id" in the campaign editor Then, give the campaign a Zone id corresponding to a unique div ID tag on the desired site(s). This will ensure that once a visitor matches the segment and visited this page once, they will keep seeing the Call To Action (CTA) on this page.
View full article
Included in this article: Overview Preview is a feature that allows you to see your campaign without having the campaign deployed on your website, but not all web pages allow this.  If it is not working with your website, here are some troubleshooting steps to try. Basic Troubleshooting Verify the RTP tag is loading properly on the target page. If there is no RTP tag, there's no way for the preview to work. Clear your browser cache and cookies. Have someone else test the preview.  Copy and paste the link from the preview window to share the campaign example with others. Copy and paste the link from the preview window into another browser and try it there. If it is an In-Zone campaign, verify the div ID specified in the campaign exists on the page you are trying to preview. Go to the original website and look for jQuery / Javascript errors. Create a new campaign containing only the word "Test" and try to preview it on the same page.  Since the maximum length of a URL for most browsers is 2048 characters, a large campaign may fail in the browser Troubleshooting Web Page Restrictions If you get an error such as the ones below, it may be that your website is blocking proxy or cross-domain requests.  This would be a configuration that was made by the IT team in charge of the webpage, perhaps as some sort of connection timeout or DoS attack prevention measures.  You may need to work with your IT team to have the proxy request enabled. Verify that the preview URL is correct - this message might also show up when trying to preview on non-existing pages. If your site has SSL, make sure the certificate is up to date using a tool such as https://www.sslshopper.com/ssl-checker.html. Testing with a Sandbox Segment In cases where the preview option doesn't work due to website proxy or cross-domain restrictions, and you want to see what you campaign looks like live on your website without customers seeing it, we recommend using a Sandbox segment.  Sandboxing allows you to match a segment and see the campaign live by targeting a specific term added into the URL. Since leads won't randomly guess the value and alter the URL, it's safe to test on a live site. Here's how you do it. Create a new 'Sandbox' segment (i.e "sandbox=1" / "sandbox=2"...) Add the Included Pages filter and enter *sandbox=1* as the value for the URL matches. Click 'Save & Define Campaign' Change the campaign's target segment Select the new 'Sandbox' segment from the dropdown list Click 'Launch' Preview on the website Go to your live web page and add the URL parameter at the end of the URL, i.e: www.marketo.com?sandbox=1         In order to see the campaign again or changes made, you will need to clear browser cookies.
View full article
As you know, Marketo issued a security patch on 4/6/16 in order to strengthen token encryption within email links. At Marketo, security is a top priority and we will continue to invest in changes that make the platform more robust. In reference to this patch, Marketo Support has been answering several common questions that are documented here for your reference. Please find this information below and, as always, contact Marketo Support if you still have any unanswered questions. Are all email links impacted by this patch? No, the vast majority of links within emails are not impacted in any way. By default, Marketo converts all email links to shortened tracking links. These links were not impacted by this patch. These links should continue to function as expected, regardless of when your email was sent. Note: This also applies to any links that contain the “mktNoTrack” or “mktNoTok” class. These links were also not impacted by this patch. Which links were impacted? The only links that were impacted were links that contain pre-generated mkt_tok values. There are three ways these type of links can be present in your email: 1.  You use one of the following system tokens in your email: {{system.viewAsWebpageLink}} {{system.unsubscribeLink}} {{system.forwardToFriendLink}} 2.  You use the “Include View as Web Page” option in the Email Editor and your Admin > Email defaults for “View as Web Page Text” explicitly includes an mkt_tok value like this:  mkt_tok=##MKT_TOK## 3.  You use Marketo’s default functionality to auto-insert “Unsubscribe” footers at the bottom your emails and your Admin > Email defaults for “Unsubscribe Text” explicitly includes an mkt_tok value like this:  mkt_tok=##MKT_TOK## How will behavior change for these links? 1.  System Tokens For emails sent out prior to 4/6/16: {{system.viewAsWebpageLink}} - Any pre-patch emails that contain {{system.viewAsWebpageLink}} links will now direct users to a page indicating that the lead-specific email cannot be rendered. Users will, however, have the option to instead see a generic view of the email (no lead tokens, dynamic content, etc.). {{system.forwardToFriendLink}} - Any pre-patch emails that contain the {{system.forwardToFriendLink}} link will no longer function. Currently, users will see an error message on click. {{system.unsubscribeLink}} – Any pre-patch emails that contain the {{system.unsubscribeLink}} link will continue to function and point users to your unsubscribe page. However, the unsubscribe form will not support prefill for this visit. Note: For all of the above system tokens, any emails sent out post-patch are not impacted. 2.  “View as Webpage” - If you implement a “View as Webpage” experience in your emails by using Marketo defaults, selecting “Include View as Web Page” from the Email Editor, then you will see the following behavior: “View as Webpage" links inserted into the HTML side of emails are not impacted. These links should continue to function as expected, regardless of when your email was sent. “View as Webpage" links inserted into TEXT side will behave similarly to {{system.viewAsWebpageLink}}. For emails that were sent prior to 4/6/16, these links will direct users to a page indicating that the lead-specific email cannot be rendered. Users will have the option to instead see a generic view of the email (no lead tokens, dynamic content, etc.). Note: any emails sent out post-patch are not impacted. 3.  “Unsubscribe” - If you implement an “Unsubscribe” experience in your emails by using Marketo’s defaults, then you still see the following behavior: “Unsubscribe" links inserted into the HTML side of emails are not impacted. These links should continue to function as expected, regardless of when your email was sent. “Unsubscribe" links inserted into TEXT side will behave similarly to {{system.unsubscribeLink}}. For emails that were sent prior to 4/6/16, these links will continue to function and point users to your unsubscribe page. However, the unsubscribe form will not support prefill for this visit. Note: any emails sent out post-patch are not impact
View full article
Included in this article Overview Stopping Send Alerts for Anonymous leads Excluding Anonymous Leads entirely (use with caution) Deleting Lead Partitions Revised 2/19/2016 Added caution on "Lead Was Created" work around Added "Stopping Send Alerts" work around Added "Deleting Lead Partitions" Known issue Revised 2/17/2016 Marked "Lead Was Created" work around as under review 1. Overview The upgrade to anonymous leads is a two—step process. The first part removes the “Is Anonymous” filter and performs all other changes to the Marketo UI as outlined in the Changes Inside Marketo UI documentation here. The second part is the introduction of Munchkin V2. This piece is where the new lead promotion behavior is introduced as outlined in the Munchkin V2 Behavior documentation here. The changes to the Marketo UI removes access to anonymous leads, but they do still exist inside Marketo until the Munchkin V2 piece rolls out later this year. In the meantime between now and then, your smart campaigns will include these anonymous leads even though you won’t be able to access those leads. This can result in things like blank Send Alert emails going out for leads that can’t be accessed. This document will show you how to exclude those anonymous leads pending the Munchkin V2 release. 2. Stopping Send Alerts for Anonymous Leads The biggest problem Support has seen so far is with blank Send Alert emails being sent for anonymous leads that can’t be accessed. There is a very isolated use case when this occurs. The Send Alert flow step sends the email to the Lead Owner or the Account owner, but anonymous leads can’t be synced to SFDC, so the only time anonymous leads could have an Alert email sent is if the flow step is set to send “To Other Emails”. To stop anonymous leads from having the Alert email sent, add a choice to the flow step with the condition that if the Email Address is empty, do nothing. Since anonymous leads won’t have an email address, they will skip the flow step and the problem is resolved. This solution will not require any changes after the Munchkin V2 roll out later this year. Since the campaign replay process on lead promotion does not execute Send Alert flow steps (described in Anonymous Lead Promotion to Known Lead – Munchkin V2 Behavior and Anonymous Lead Upgrades – Under The Hood), that replay process will not be affected. 3. Excluding Anonymous Leads (use with caution) When a lead becomes a known lead, a Lead Was Created activity is logged. If the lead is still anonymous, it will not have this activity in its activity log. Adding the “Lead Was Created” filter in your Smart Lists and Smart Campaigns will stop all anonymous leads from going through the campaign. Adding the filter Remove the Date of Activity constraint in the filter by clicking the X on the right side. This will make the filter look for the activity for all time. With this filter added like this, all leads that qualify will be known leads, and all anonymous leads that still exist will be ruled out. 4. Deleting Lead Partitions Until Munchkin V2 rolls out, anonymous leads still exist in the lead database even though they can’t be accessed. Lead partitions can’t be deleted if there are leads still in them and you’ll get this error: If you receive this error, the first step is to make sure these aren’t known leads. To do this, navigate to Admin > Workspaces & Partitions > Lead Partitions and click the “Show # of Leads” button. This will open up the column where you can view how many known leads are in the partition. Any leads showing up here will be known leads. Use a “Lead Partition” filter in a smart list to identify these leads, then move the leads to a different partition. Once this is done, if you have zero leads showing in the partition but still get the error saying you can’t delete the partition because it has leads, open a case with Marketo Support. The anonymous leads will need to be deleted on the back end by our Engineering team.
View full article
At Marketo we take security seriously. As a part of an industry-wide initiative, Marketo is upgrading our web authentication and encryption to enhance our security protections.  The rollout is scheduled to occur on December 12, 2015. Who will be affected? Only a small number of users will be affected, only those who have an integration to Marketo from a system that is over ten years old and hasn't been updated recently.  See this list  for more info on what systems and versions are supported.      The following users will not be impacted: End users accessing Marketo.com through modern browsers (see list) Customers using integration partners such as Informatica, Dell Boomi, and Scribe.    Customers using Launchpoint partners. Rollout schedule The following rollout schedule is planned: Service URL SHA-2 Rollout Date API access mktoapi.com Dec 12, 2015 API access mktoresp.com Dec 12, 2015 Part of MLM Application marketodesigner.com Dec 12, 2015 All other Marketo domains already use SHA2 certificates.
View full article
When doing a list import, sometimes the dialog box won’t advance past the Step 2 section where columns are mapped to Marketo fields. If you look closely, you’ll see that there is a Marketo Field selected that has a red squiggly underline underneath it. If any of the fields have this, you won’t be able to click on Next to get to Step 3 and the import dialog box will get “stuck” at this point. This problem is caused by having two columns in your list mapped to the same one Marketo Field. Two pieces of data can’t be pushed into the same one field, so it stops the import in its tracks at this point until you change it to select a different field. If you mouse-over that field, you’ll get the error that shows that the field is already in use. The quickest way to fix this is to simply choose a different Marketo Field to map the list column to. Once there aren’t any more Marketo Fields used twice, the import dialog box will advance to Step 3. Problem solved!
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
Guide for getting 'Email deliverability' set up
View full article
Yes. You can sync down new fields to Marketo as long as the sync user has access to these fields. You can sync down new fields by going to Admin > Microsoft Dynamics > Field Sync Details. Please note that we will only be syncing new values for these fields, we don’t do complete initial sync for this field. For options to do a complete initial sync for a particular field, please contact support.
View full article
Yes. For leads, contacts, and accounts, you can choose which fields from Microsoft Dynamics CRM you’d like to sync down to Marketo.
View full article
No. Marketo only creates new Leads in Microsoft Dynamics CRM. Updates to existing contacts are synced to Microsoft Dynamics CRM but we don’t create new contacts directly from Marketo. Account updates are one way - from Microsoft Dynamics CRM to Marketo.
View full article
When a net new record is created in Marketo through a form fill out, list upload or though our API it can be pushed to Microsoft Dynamics CRM using the “Sync Lead to Microsoft” flow action.
View full article
When the owner of a record is changed in Dynamics, this action will be mirrored in Marketo in the next sync cycle.
View full article
When a deactivated record is reactivated Microsoft Dynamics CRM, the following behavior occurs in Marketo: If the record was initially deactivated because of a merge or a conversion, we will create a new record in Marketo when the record is deactivated. If any other record is reactivated, Marketo will change the “Microsoft is Deleted” flag of the associated record in Marketo is set to false.
View full article
When lead/contact is deactivated in Microsoft Dynamics CRM Marketo treats this as a delete and sets the “Microsoft is Deleted” flag to true. This is when a lead/contact is manually deactivated in Microsoft Dynamics CRM. When a record is set to deactivated because of conversions/merges, please see those sections on detailed behavior.
View full article
Marketo initiates a sync with Microsoft Dynamics CRM approximately 5 -10 minutes after the previous sync cycle finishes. The time needed to complete a sync cycle depends on the number updates on the two sides.
View full article
Marketo syncs all the records the Sync User has access to. The association between a record in Marketo and Microsoft Dynamics CRM is maintained using the native Microsoft Dynamics CRM IDs.
View full article
No, once you sync Marketo to any CRM you cannot change it to a different CRM. Please contact Marketo Services for options here.
View full article