Knowledgebase

Issue You receive the "Subject is empty" error when attempting to approve an email which contains an emoji character in the subject line, and elsewhere in the email, emojis may fail to render. Solution Marketo can render any Unicode character up to 5.2 and any ASCII character, but this does not encompass emojis. The Marketo email editor will strip out any unsupported symbols. This is because we cannot guarantee the consistency of their appearance across platforms, as not all clients can render all emoji. Marketo only supports the text symbols that are generally then converted into emoji's by the recipient client or operating system. The basic symbols in a list such as https://www.copypastecharacter.com/symbols should work, as they are ASCII characters and not reliant on extra encoding. These are a set of accepted text symbols that will universally work on all clients and many will convert them to emoji. Just highlight the symbol from  https://www.copypastecharacter.com/symbols, copy and paste it into your email. Alternately, you can work around this by q-encoding the emoji in UTF-8 format, which will render a string of code to add to your subject line. This code tells the email client to render the desired emoji. All you need to do is copy your desired emoji and run it through a Unicode to UTF-8 translation tool, such as https://onlinetools.com/unicode/convert-unicode-to-utf8. As an example, say you want to send a Happy Birthday email to a lead. You could copy the  (birthday cake) emoji and run it through a translator to yield the code "=?utf-8?Q?=F0=9F=8E=82?=" Entering this code in your subject line without the quotation marks will render the emoji on the client's end, and render it in the design most compatible with their device/browser. With any email design, it's always important to test before a live send to confirm it appears the way that you expect it to.

Issue Description Issue in delivering Marketo Email (especially for mimecast users). Email get bounced with Error: 550 Rejected by header based Anti-Spoofing policy Issue Resolution This error can happen if: You have not properly white listed the Marketo IPs You have an ssue with DKIM/SPF set up and configuration Please whitelist the set of Marketo IPs found in the doc below and make sure SPF and DKIM are set up correctly for your email domain https://docs.marketo.com/display/public/DOCS/Configure+Protocols+for+Marketo

Here it is: Your guide to understanding merges in Marketo, in Salesforce, and how the two interact. Merging Two Leads We begin with two records in Marketo which have been synced to Salesforce. Both are leads in Salesforce, not contacts. Lead A, Marky Marky, has a Marketo ID of 1001446 and an SFDC ID of 00Qi000000vJ0hK. Lead B, Markee Marquee, has a Marketo ID of 1001447 and an SFDC ID of 00Qi000000vJ0hU. We wish to merge these leads in Marketo. In this example, I first select Lead B, and then hold SHIFT to select Lead A as well. Then right-click in the highlighted area to bring up the Lead Actions drop-down (or click Lead Actions at the top of the screen), and select Merge Leads from the choices. Now I see the Merge Leads dialog box, where we decide which conflicting field values we want to win. We could click the box next to "Lead 1" if I want all of Markee Marquee's values to win. Instead we check the box next to "Marky" because we want that to be their first name, rather than "Markee". Then we click merge. Note: whichever record was most recently updated will be pre-checked to win field conflicts. Here's the result. Note how the remaining single lead has the ID 1001447, that of Lead B, the first one we selected. The first record you select is the target record - this records remains while the other record is deleted, it's field values, activities, and program memberships merged into this winning record. The leads are also merged in Salesforce, and the remaining record there has the ID 00Qi000000vJ0hU (Lead B) as we would expect. Merging Leads and Contacts Here we begin with a lead and a contact. We have a lead, Marky Marquee (Marketo ID1001447, SFDC ID 00Qi000000vJ0hU), and a contact, Joe Hill (Marketo ID 1001448, SFDC ID 003i000002KAFGa). We first select Marky Marquee (the lead) and then select Joe Hill (the contact), and conduct the merge as we did above. This time, however, the second record we clicked, Joe Hill, shows up as "Lead 1". This seems to contradict what we said earlier, but it's happening because the second record is the contact, and the contact is always going to be the target record. I want Marky's name to win out, so I check their First and Last Name and then click Merge. Note: this will cause an error if the Marketo sync user in SFDC doesn't have the Convert Leads permission. Note that the remaining record has the ID 1001448, the ID of the contact, even though that wasn't the first record we selected in Marketo. The contact is always the one which remains. Program Memberships Here we have two leads: Dexter Science (ID 1001451) and James Frankough (ID 1001452). We add James to two programs, Program Example 1 and Program Example 2. We can see this in their activity log: Now we merge the records, selecting Dexter first (so they'll be the winning record), but we check James's values for the First and Last Name. Below is their activity log after the merge. Notice that there are new Change Program Status activities - because the target record in the merge was 1001451, but the programs were associated with 1001452, the system has to copy their program statuses over during the merge. If you double-click one of those activities, it gives "Lead merge transferring program membership (transfer)" as the activity's Reason. Activities caused by merges can trigger campaigns. For example, suppose there is a smart campaign with the trigger Program Status Changes, for an old program with no activity in months. Activities caused by a merge like this could trigger such a campaign. To prevent this from triggering campaigns, we can add Reason as a constraint: Campaign Memberships Next, we have two leads: John Doe (ID 247) and Johnathon Doe (ID 248). We've associated John Doe with two SFDC Campaigns: Campaign Example 1 and Campaign Example 2. When we merge John Doe into Johnathon Doe, since the target lead is ID 248 and the campaigns are associated with ID 247, it has to copy them over - just like it did with campaign memberships. However, unlike with program memberships, it does not provide a Reason in the Add to SFDC Campaign activity following the merge, meaning there's no easy way to prevent this from triggering campaigns which use the Added to SFDC Campaign trigger.

FAQs Included in this Article: Overview Are RTP campaign designs responsive Can you see how your RTP campaigns will be displayed on multiple devices Can campaigns be displayed only on one page Can I insert JavaScript to RTP campaigns Can RTP campaigns be blocked by ad blockers or JavaScript blockers Does marketo RTP support animated GIF files Does RTP impact SEO Does RTP support HTML5 How does Any Page in the Target URL field work How does RTP A/B testing work How accurate is RTP's reverse IP geolocation targeting How to use the User Context API segmentation What are the recommended sizes for RTP campaigns What is a conversion in RTP What is the limit of organizations you can target for an RTP campaign What is the limit of names allowed in the 'Organizations' criteria What is the limit of rows exported in an Excel export What is the limit of Zip Codes allowed What is the limit of segments allowed   Overview Segments and campaigns are powerful tools in the Web Personalization platform for targeting groups of potential leads and pushing them relevant content. Segments allow you to target your audience based on demographic fields like organization, location, and lead status, or based on behavioral fields like number of visits, mobile device used, or search terms used. Campaigns use segments to personalize your marketing efforts, allowing you to deliver relevant content to specific segments of your audience. This doc will answer some of the most frequently asked questions about segments and campaigns in RTP. If you would like to first learn the basics of using segments and campaigns, read through this collection of documents that will get you started: Getting Started (RTP)     Are RTP campaign designs responsive Yes. This means that RTP campaigns will work on mobile devices and will adapt to the sizing of mobile websites. Only Dialog and Widget campaigns are affected by screen sizes, as In Zone campaigns behave as embedded parts of the website. There are RTP Mobile Templates for fitting dialog campaigns to all mobile screen sizes.   Furthermore, in the segment editor, you can segment by mobile device type and manually create campaigns that appear differently on different devices.     Can you see how your RTP campaigns will be displayed on multiple devices In the campaign editor, you can use the preview tool to view how an RTP campaign will look. This tool will allow you to change the view settings to preview your campaign on all different kinds of devices with different screen sizes.     Can campaigns be displayed only on one page Yes, this can be done by using the "Include Pages" field in the segment editor        Go to the Segments page and hit the Edit button on the segment associated with your campaign        Use the Include Pages field to enter the specific page that you wish to have the campaign display on        You can also use this field to include any page with a specific keyword in the URL. To do this, use wildcard characters (*) which will match any sequence of characters. For example, "*product*" will match any URL that contains the keyword "product".     Can I insert JavaScript to RTP campaigns The RTP's campaign editor supports any standard and valid HTML, JavaScript, or CSS codes. Invalid codes will be stripped off the campaign's HTML   While using valid HTML, JavaScript, or CSS will work as expected, the use of jQuery can be problematic. Campaigns generally load very fast, especially In Zone campaigns, and they will often load before jQuery even exists on the web page. This can cause error messages in the developer's console or issues loading the campaign. If you need to use jQuery on your page, contact Marketo Support and we can try to come up with a simple workaround. Advanced solutions will need to be developed by a third party developer or the PS (product services?) team.     Can RTP campaigns be blocked by ad blockers or JavaScript blockers Basically, no. For a more in depth answer, please see Web Personalization (RTP) - Can RTP Campaigns Be Blocked by Ad Blockers or JavaScript Blockers     Does marketo RTP support animated GIF files Yes, we do support both static and animated GIF files in RTP campaigns. We do still recommend you preview and test the campaign to assure that the GIF appears as you hoped it would.     Does RTP impact SEO RTP does not affect any SEO performance and in some cases it can even improve SEO ranks due to longer website engagement. Search engines use robots to crawl through the content of web sites, which happens before RTP runs campaigns and personalizes content. This means that content from RTP does not get picked up by the search engines' robots, and will not contribute to a web page's rank. In many cases, RTP will actually improve a web page's SEO rank. Since RTP can increase engagement among a page's visitors, it can improve behavioral metrics like average time on a site, pages per visit, etc.     Does RTP support HTML5 Yes, all campaign types in RTP support HTML5.     How does Any Page in the Target URL field work The "Any Page" option in the target URL means that once the visitor matches the target segment, the campaign will be shown regardless of which page they are on within your web site.     How does RTP A/B testing work A/B testing a campaign consists of deploying slightly different versions of a campaign to test which version performs the best. To learn how to A/B test a campaign, see AB Test Your Web Campaign   The test works by randomly selecting a certain percentage of users to see one version of the campaign, and the rest see the second version. If the campaign is set to be Sticky (you can find this option in the campaign editor, shown below), the visitor will see one version of the campaign for their entire session on your web site. This means if the user is first shown campaign B, they will keep seeing campaign B until the end of their session. In that visitor's next session, they may see either campaign A or B.   If the campaign is not Sticky, the visitor will only be shown the campaign once during their session, whether that be campaign A or B. In their next session, they will again only be shown the campaign once, and again it could be either campaign A or B.     How can RTP recognize the search term When you visit a web page, your browser will keep track of the URL of web page that you were on directly before getting to that page. This is known as the "referral" URL. With the referrer URL, it is relatively simple to extract the search terms.   RTP uses this ability to extract search terms from the referral URL to determine the search terms used and record them in Marketo.   Unfortunately, Google has recently begun to withhold and encrypt much of this data, making it impossible for RTP to extract the search terms in some cases. For now though, you will still be able to get all search terms from other search engines like Yahoo and Bing.     How the RTP industries and organization groups are defined Industries In the segment editor there is an option to target visitors that come from specific industries, including: Agriculture & Mining Business Services Computers & Electronics Consumer Services Defense Education Energy & Utilities Financial Services Government Healthcare, Pharmaceuticals, & Biotech Manufacturing Media & Entertainment Non-Profit Other Read Estate & Construction Retial Software & Internet Telecommunications Transportation & Storage Travel Recreation and Leisure Wholesale & Distribution   Marketo uses advanced machine learning algorithms to determine the industry based on data from _____. Marketo also uses keywords in the organization's name to get a better match for its industry. For example, an organization named "UCSF Medical Center" probably belongs to healthcare just based on the name itself, and "Stanford University" probably belongs in Education.   Organization Groups You can also target visitors in companies of various sizes, or Organization Groups, including: Fortune 500 Fortune 1000 Global 2000 Enterprise SMB   Marketo uses Forbes' annually updated lists to determine companies in the Fortune 500, Fortune 1000, and Global 2000 groups. Enterprise companies are defined as those with more than 1,000 employees and revenue greater than $250 million. SMB companies are all (non-ISP) organizations that are not defined as any of the above.   For more information on segment categories, visit: https://docs.marketo.com/display/public/DOCS/Using+Web+Segments     How accurate is RTP's reverse IP geolocation targeting IP based geo-location targeting has a 95% accuracy rates for country level and around 85% for states. For ISPs (Internet Service Providers) it is less accurate, because they often use different physical proxies and change their routing more often. Over time we follow the changes and update our database continuously.     Is it possible to redirect target visitors to specific pages Please see Web Personalization (RTP) - Redirect Targeted Visitors to Specific Pages     Is it possible to use segmentations from the Lead Database in RTP Currently this is not a feature that RTP supports. However, see this document if you wish to implement a work-around.     Is there a way to restore a deleted campaign There is no way to restore a deleted campaign in RTP. However, if you need to restore a deleted campaign, contact Marketo Support and it can be done if it was recently deleted. Unfortunately even restoring the campaign through Marketo Support will not restore the campaign's performance statistics.     RTP or CMS campaigns - which will win CMS campaigns are generally injected to the web page, meaning it runs before the page loads. RTP, on the other hand, runs as the page is loading. Since RTP campaigns run after CMS campaigns, they will override the CMS campaign and the page will only show the RTP campaign.     How to use the User Context API segmentation The User Context API is a very advanced and technical functionality. All of its documentation can be found here, on the Marketo Developers database.     What are the recommended sizes for RTP campaigns Of course the size of your RTP campaigns is up to your discretion, but here are our recommendations for various types of campaigns: Dialog (Square Pop-up): 250 x 250 pixels Widget (Medium Rectangle): 300 x 250 pixels For more standard sizes: https://en.wikipedia.org/wiki/Web_banner#/media/File:Standard_web_banner_ad_sizes.svg     What does the "Marketo Email Campaign" option mean When creating a segment with the filter "Marketo Email Campaign", the segment will only match visitors that visit your website after clicking an email in the specified campaign.       What happens when a visitor qualifies for more than one campaign When a visitor qualifies to see more than one campaign, depending on the types, you may see multiple campaigns on the page or only one. Below is a table explaining what happens when a visitor qualifies for two campaigns:     When only one campaign is to be shown, the campaign that is displayed is chosen randomly between the two. When a visitor qualifies for two In Zone campaigns with the same Zone ID, the campaign that is displayed is also chosen randomly.     What is a conversion in RTP A direct conversion is a visitor that became a lead after clicking on an RTP campaign. In a summary report, you will see the Direct Lead Conversion Rate, which is simply the percentage of clicks on the ampaign that lead to direct conversions.     What is the limit of organizations you can target for an RTP campaign There are no constraints on the number of organizations included in a campaign.     What is the limit of names allowed in the 'Organizations' criteria The limit is 100 names. It is a best practice to use dynamic lists instead. Dynamic lists will generally perform better because they are designed to index and handle larger lists.   What is the limit of rows exported in an Excel export By default, RTP limits the number of rows in an Excel (CSV) export to 100.  If you need more rows than that, you can increase it by going to User Settings and changing the value for 'Number of Rows in Excel Export.'  The maximum allowed is 10,000 rows     What is the limit of Zip Codes allowed You can enter up to 6,500 zip codes. They must be separated by semicolons (01234;12345; etc.)     What is the limit of segments allowed The segment limit varies: it can be 30, 60, or unlimited depending on your Marketo subscription type. If you have reached your subscription's limit, you will want to clear out segments that are not being used.   If you get an error message saying you've reached your limit, yet you believe your subscription makes you eligible for more segments, contact Marketo Support.

Issue Description REST API call, Get Lead Activities, is returning 603 error   Issue Resolution Error 603 refers to 'access denied' where authentication is successful but the user doesn’t have sufficient permission to call this API. Additional permissions may need to be assigned to the user role. http://developers.marketo.com/rest-api/error-codes/   Go to Admin > Users and Roles Select API User and identify what role it is assigned to (e.g. API role) Go to Roles and check the permissions assigned to the API role Check to see if the API role does not have 'Read-Only Activity' or 'Read-Write Activity' permission In order to make a Get Lead Activities REST API call with the API user, the API role of the user must be modified to have permissions to  'Read-Only Activity' or 'Read-Write Activity'. If you use Workspaces and Partitions, make sure the API User has the necessary access. Is this article helpful ? YesNo

Issue A webhook that looks to be structured the same as other functioning webhooks is failing with HTTP Error 400: Bad URL request. Solution A 400 error message usually means that the request was malformed. In other words, the data stream sent by the client to the server wasn't formatted in the exact way required by the receiving service.  You will need to work with the service you are trying to reach to figure out the exact cause of the error with the webhook.

Included in this article Questions What is the architectural change Marketo is making? Today, we have two packages in the Salesforce AppExchange: The Marketo Lead Management (MLM) Package The Marketo Sales Insight (MSI) Package When installed, the MLM package auto creates a set of fields in Salesforce. Marketo populates these fields with data as a part of our regular sync. The MLM package is not currently required for syncing. However, it has been a prerequisite to install before you install the MSI package. The MLM package has reached the end of life and is going to be retired. The MSI package will no longer be dependent on the MLM package and our customers will be able to directly install the MSI package. As a result, Marketo will stop updating the fields created by the MLM package. The configuration change will begin on August 15th and will be staggered out over the next 6 months. If some or all of the fields created by the MLM package are important to your organization, you can recreate them by following the instructions here: Adding Marketo Fields to Salesforce How will the primary Salesforce integration affected? It won't be. Marketo continues to invest in and create value for customers through our strategic partnership with Salesforce.com.  Because of this, we’re excited to share some news with you on our continued commitment to our partnership. Please see the documentation here for more information: Marketo Continues Best-In-Class Integration with Salesforce for Customers We never installed the MLM package. Does this change affect us? No, it does not. Do I need to uninstall the MLM package from my Salesforce instance? No. Marketo will simply not update the fields created by this package. If you prefer to uninstall the MLM package, that’s fine too. There will be no impact to the data in those fields. If I do uninstall the MLM package, should I do that before or after recreating the new fields? It's best to recreate the new fields prior to uninstalling the MLM package. What should I be aware of before making these changes? We've prepared lots of documentation (found at the bottom of the doc here) that should be reviewed prior to making the configuration changes here. Some customers may have other dependencies on the affected fields, (such as Workflows, ApexTriggers, other AppExchange packages, Formula Fields, or Reports), so these should be evaluated before making the changes. Check out our documentation here for more detailed information: Changes to Marketo Salesforce Sync – Preventative Troubleshooting Is there any data loss? No, the fields in the MLM package consist of marketing data that will continue to exist in your Marketo instance. If you would still like to have them in Salesforce, you can create new fields, and Marketo will sync the data to Salesforce. Instructions to create these new fields are documented here: Adding Marketo Fields to Salesforce  What if I do nothing? Both MSI and your sync will continue to work. However, once the sync of data is shut down on January 31st, 2017, Marketo will no longer be able to update the fields that were created by the MLM package. This can result in stale data in Salesforce, as data for these fields will continue to change in Marketo, but will not be pushed to Salesforce. Do we need to create all the fields? We only care about Lead Score. Since we are sun setting the MLM package, there is no longer an “all or nothing” proposition. You can create just the fields you want in Salesforce. Can we create a few fields now, and a few later? Yes, you can create some of the fields now, and some later when/if you need it. What happens once we create these new fields? Once you create these new fields, Marketo will automatically recognize these fields in the next sync cycle and map them to the appropriate Marketo fields. Marketo then starts a background process independent of the regular sync to update Salesforce with values from Marketo. For example: You create a new field in Salesforce for Lead Score on the lead and the contact. The API name for this field per our instructions is mkto71_Lead_Score__c In the next sync cycle, Marketo detects that this field has been created and automatically maps it to the Lead Score field in Marketo. A background process is kicked off automatically to start populating these new fields in Salesforce with the appropriate Lead Score from Marketo. Once the “backfill” is done, a notification is sent to the Notification Center letting you know that this process is complete.  Think of the backfill process as an initial sync where we push data for these fields into Salesforce.    How long will it take for Marketo to complete this “backfill”? It is tough to give an exact timeframe. To a large extent it depends on the number of records Marketo needs to update in Salesforce. As a rule of thumb we expect to update at roughly the rate of 10K records per hour. Will this affect my Salesforce sync backlog? The backfill process is separate from our regular sync queues and will not be affected by any backlog there may be in your instance. However, when Salesforce is updated with data during the backfill, it will change the SysModStamp of the records updated. This in turn will require our regular sync to check if any of the other fields have changed on these records. This check is done as a part of the regular sync and could have an impact on your backlog for a short period of time.  For a particular field eg: Lead Score, do we need to create it both on the Lead and the Contact? While not absolutely required, it is highly recommended that for any field that you need, it is created on both the Lead and the Contact. Don’t forget to setup the conversion mapping in Salesforce too. Is there any change to MSI? Your MSI package has already been patched to remove the dependencies it has on the MLM package. This will allow you to uninstall the MLM package if you want to. Additionally, if you currently use the “Debug Mode” setting in Sales Insight Config (very rare), the mouse over on Stars in the Best Bets sections will no longer show the Lead Score. I have some other questions not covered here. How do I get them answered? Discussion thread We've created this discussion thread in the community to address any questions you may have. This discussion thread will be monitored by the Marketo team to ensure you get answers to your questions: Changes to Marketo Salesforce Sync – Questions and Discussion Recap Summary Now that the changes have been completed, and the deprecation date has passed, this doc will give you the overview of what has happened: Changes to Marketo Salesforce Sync - Recap Summary Overview Documentation This doc will give you a high level overview of what the configuration changes are and what to expect moving forward: Changes to Marketo Salesforce Sync - Overview  Release Schedule The release is being staggered over the course of 6 months. This doc will give you exact details so you can know precisely when your Marketo instance will be updated: Changes to Marketo Salesforce Sync – Release Schedule Under the Hood Documentation This doc will give you all of the nitty gritty details of exactly what is happening. If you're looking for in depth technical details, this is the go-to doc to check out! Changes to Marketo Salesforce Sync – Under The Hood Recreating Affected Fields There are different versions of Salesforce, but don't worry, all of the details on how to recreate the affected fields as well as a video tutorial can all be found in the documentation here: Adding Marketo Fields to Salesforce Preventing Problems In Salesforce Recreating the new fields in Salesforce can cause your Workflows, Apex Triggers, Reports and AppExchange apps behave differently. They'll need to be updated and this doc will show you what to watch out for: Changes to Marketo Salesforce Sync – Preventative Troubleshooting Contact Marketo Support If you would prefer to talk to someone live, please contact Marketo Support over any of the channel listed here: Contact Marketo Support

Included in this article Overview Marketo's Live Chat offers a great way to get the help you need. Chat live with Marketo experts and we’ll answer your questions, point you to detailed support resources, or open a support case. Our Live Chat Support feature is a convenient way to connect with us. Live Chat Availability Marketo Live Chat is available around the clock during the week on a 24x5 schedule, excluding regional holidays. Access to Live Chat depends on your support level as shown below: Online Business Premier Elite Support Portal X X X X Live Chat X X X X Phone X X X Starting a Live Chat Session Your Authorized Support Contacts can start a Live Chat session by visiting the Support Portal at support.marketo.com. Locate and click the Live Chat link or button to initiate a chat session. If you do not see this panel in the Support Portal, you may not be an Authorized Support Contact. Please contact your Marketo admin to manage your authorized contacts. Where to Locate the Live Chat Button The live chat option will appear on the Support page in the Community and will also show up in the Case Connector when logging a case online. Support Additional Questions Have additional questions about Live Chat or other support features?  Please feel free to contact us at marketocares@marketo.comsupport@marketo.com Want to upgrade your Service level? Please contact your Marketo Account Manager.

What is Marketo’s Marketing Calendar? What are its benefits? What features does Marketing Calendar include? Is it free or do I need to pay for it? How do I get or buy Marketing Calendar? As of our August release: 1 week after our August release How do I know if Marketing Calendar has been turned on? What is the Program Schedule View? Will I need a services package to implement Marketing Calendar? Is this article helpful ? YesNo

  What’s changing? Previously, customers could choose whether they wanted to secure their pages and tracking links via SSL. The responsibility of procuring, maintaining, renewing, and securely sending the certificates to Marketo lie entirely with the customer – Marketo just hosted them. In 2017, Chrome and Firefox announced they would begin flagging any unsecured pages with clear ‘NOT SECURE’ warnings in their 2018 releases to encourage the use of SSL, and even distrusted certificates from certain providers. This essentially designated the certificate as a foundational security necessity to prevent customers fleeing from unsecured sites.   This change reinforced the increasing need for companies to protect their data and mitigate against online security threats. Recent studies have shown that ~45% of organizations are targets of Distributed Denial of Service (DDoS) attacks, typically lasting a few hours, and potentially costing companies not only lost revenue, but also customer data and overall trust. [1]   Simply put, an SSL certificate just isn't enough anymore, which is why Marketo updated how we manage SSL certificates and the overall security of our customers' landing pages with the introduction of Secured Domains, a comprehensive managed service, in early 2018.   How is Secured Domains different than an SSL certificate? In contrast to our previous solution, Secured Domains is less focused on the SSL certificate itself, and rather the security and performance benefits gained from our partnership with Cloudflare, an industry leader in secure solutions. Secured Domains not only includes the necessary SSL certificates, but, more importantly, provides robust security protection thanks to the investment made to secure our servers, which host Marketo landing pages, behind Cloudflare’s trusted security infrastructure.   With Cloudflare’s enterprise-grade tools securing our servers, we protect against security vulnerabilities and attacks on your Marketo pages. Once Secured Domains is implemented for your instance, your domains will be protected via the following:   Managed Web Application Firewall (WAF): keeps your pages secure by filtering and deflecting malicious attacks DDoS Protection:  keeps your pages live by absorbing attacks and preventing the pages (and Marketo's infrastructure) from crashing Content Delivery Network (CDN): a load balancer to distribute page views based on geolocation, which allows landing pages to load more quickly   Secured Domains also shifts the ownership of SSL certificates onto Marketo, which eliminates the hassle of Marketing & IT teams having to manage them and, because they renew automatically, you no longer need to worry about your landing pages crashing due to an expired certificate. The certificates are provisioned by Cloudflare and authored by DigiCert at an enterprise-level offering. For more information, please see our Overview & FAQ: Secured Domains for Landing Pages.   How do I learn more about Secured Domains? If you’re an existing customer, please contact your Marketo Customer Success Manager to add Secured Domains to your subscription. As of September 2019, a base Secured Domains package, which secures your first landing page domain and first tracking link domain, is now included automatically upon your next Marketo renewal. If you are unsure how to get in touch with your Customer Success Manager, please contact CustomerCare@marketo.com.   If you’re considering Marketo for your marketing automation solution and would like more information on Secured Domains and how it can improve your site security and performance, please contact GRP-Marketo-Sales@adobe.com.     Note Due to the security and risk mitigation enhancements we've made to protect Marketo servers, all customer domains are now hosted on Cloudflare. Marketo customers will be required to use the auto-renewing SSL certificate included with Secured Domains unless an exception is granted (more information on exceptions can be found in the FAQ). If you use more than the 1 landing page domain and 1 tracking link domain covered under the base offering, additional domains may simply be added on a la carte - talk to your CSM or Sales contact for pricing details.   [1] Tim Matthews, Imperva, DDoS Impact Survey Reveals the Actual Cost of DDoS Attacks, 12 Nov. 2014  

Included in this article   Overview Sync Filters for Existing SFDC Integrations Sync Filters for New SFDC Integrations Overview It is often necessary to prevent specific leads from syncing between Marketo and SFDC. There are a few different ways this can be done, such as sharing rules on the SFDC side, but the most effective way is through a Marketo Custom Sync Filter.   A Custom Sync Filter uses a custom field to mark each lead record to indicate whether that lead is allowed to sync between Marketo and SFDC. Here’s how to get it set up!     Sync Filters for Existing SFDC Integrations   If you already have an SFDC integration in place but want to stop some already-synced leads from continuing to sync, this section will show you how to make that change.   1. Create a new custom field in Salesforce. The Marketo bi-directional sync will automatically identify the new custom field and map it between Marketo and Salesforce. The best field type to use is a Checkbox field within Salesforce and the field will need to be created on the Salesforce Object that needs to be filtered (i.e. Lead, Contact, or both). Once the field has been created in Marketo by the bi-directional sync, it will be listed under Admin > Field Management.   Note: A Custom Sync Filter field can also be created on the Account object to dictate whether an account is allowed to sync. This sync filter will be applied independently from the Lead/Contact sync filter.   2. Update the records in Salesforce with the corresponding value you need to indicate whether the record should sync or not. Sync filters can be set up in two ways—a True/Checked value can indicate that a record is allowed to sync, or a True/Checked value could indicate that a record is not allowed to sync. This choice is up to you.   3. The Custom Sync Filter can now be implemented. Contact Marketo Support and request a Custom Sync Filter be activated. Be sure you include the custom field name, which configuration you need (checked=sync vs checked=don’t sync), and all records have been populated with the correct values. Once it has been applied, you’re all done!     Sync Filters for New SFDC Integrations   If you are setting up a new SFDC integration with Marketo, you can set up the sync filter as part of the integration process. This will let you designate which leads and contacts are ever allowed to sync, but this must be done in the middle of the initial SFDC sync process.   1. Create a new custom field in SFDC. The best field type to use is a Checkbox field, and you’ll need to set it up with the same name on both the Lead and Contact objects. Note: A Custom Sync Filter field can also be created on the Account before the initial sync, and it will be applied in the same way.   2. Update the records in Salesforce with the corresponding value you need to indicate whether the record should sync or not. Sync filters can be set up in two ways—a True/Checked value can indicate that a record is allowed to sync, or a True/Checked value could indicate that a record is not allowed to sync. This choice is up to you.   3. Begin your Salesforce Sync Setup but do not finish it. There are two sets of Salesforce Sync installations, one for Enterprise/Unlimited Edition and the other for Professional Edition. For both Enterprise/Unlimited and Professional Edition versions, three documents correspond to the three different steps: “Step 1 of 3”, “Step 2 of 3,” and “Step 3 of 3”. For both versions, complete all steps of “Step 1 of 3” and “Step 2 of 3”. When you get to “Step 3 of 3”, you will only do the first half of the steps and then stop. Complete the sections “Retrieve Sync User Security Token” and “Set Sync User Credentials,” and then stop there. Do not proceed to start the sync.   4. This is when the sync filter needs to be implemented. Contact Marketo Support and request a Custom Sync Filter be activated. Be sure to include the custom field name, which configuration you need (checked=sync vs checked=don’t sync), and note that all records have been populated with the correct values. Once it has been applied and the Marketo Support case is resolved, you’re done and can start your initial SDFC sync!