Knowledgebase

Sort by:
Issue: You would like to change the position of the form button. (Typical case: You've just changed the button color of the form and now you want to change the position.) Please ensure that you have access to an experienced Web developer. Marketo Technical Support is not set up to assist with troubleshooting code. Solution: Add css style using adding the margin-left property referencing  the button. The following code snippet can be a positive or negative number to shift the button left or right. Typically if you used the button solution, add the margin-left property as in the screen shot - or add the code below in a custom html block. Code snippet: <style> div.buttonSubmit input, div.buttonSubmit span { margin-left: 50px; } </style> Related Articles How to move the form button up or down using CSS Forms 1.0 - Change the Style of the Submit Button
View full article
Included in this article Overview Due to changes to the SFDC integration architecture, action is required soon to continue syncing a small number of fields to your Salesforce instance. Unlike the hundreds of fields that sync between your Marketo and Salesforce instance every day, these fields are set up by deploying a separate “package” on force.com. Now, we can directly sync these fields just like the others. Most customers are only using a couple of these fields in their Salesforce instance – Lead Score and Acquisition Program. However, if your SFDC users rely on any of the 16 fields affected, you’ll need to make some quick modifications to the integration setup. What’s Happening? Marketo's MLM AppExchange package is being retired. The core Marketo > SFDC sync functionality will remain unchanged. The MLM package itself doesn’t do much, but was responsible for taking 16 fields from Marketo and creating 32 corresponding SFDC fields to sync data into (16 on the Lead object, 16 on the Contact object). The configuration update will shut off the sync of data to the MLM package and these fields, so the data in those fields in SFDC will become stale and won’t update. You can keep syncing the same data to SFDC but it requires creating new custom fields. Once the fields are created, a drip process will be initiated to backfill existing data from Marketo into the new fields in SFDC. The MLM package will be officially deprecated as of January 31st, 2017. The data will stop syncing to the fields created by the MLM package after this date. Fields Affected When the configuration change happens, data will stop syncing from these 16 Marketo fields to their 32 corresponding SFDC fields. Lead Score Acquisition Program Acquisition Program Id Acquisition Date Original Search Phrase Original Source Info Original Source Type Original Referrer Original Search Engine Inferred Company Inferred Metropolitan Area Inferred Phone Area Code Inferred State Region Inferred City Inferred Postal Code Inferred Country Where to Go for More Information 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 Frequently Asked Questions Check out our FAQ for the answers to the most commonly asked questions. Changes to Marketo Salesforce Sync – Frequently Asked Questions 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 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​
View full article
NOTE: Securing any Marketo domains requires the "Secured Domains" product first be added to your subscription. A base offering will be automatically added to all customer subscriptions at next renewal, but to make any SSL or domain changes, or purchase coverage for additional domains, please contact your Marketo Customer Success Manager (CSM) for more information.   Marketo’s Secured Domains for Landing Pages secures any and all landing page domains defined in your instance to be served via HTTPS. Serving your pages securely assures that you’re providing critical security and data integrity for both your pages and your visitors’ personal information.   Below you’ll find the 5-step process to secure your Marketo landing pages with Marketo’s Secure Domains for Landing Pages. Please note, there is an automated support case that gets created on your behalf when the purchase of Secured Domains for Landing Pages is completed.     Step 1. Verify your Landing Page Domain, CNAMEs and any Domain Aliases are setup Before you can secure your landing page domains and any domain aliases (subdomains), you must first set these up in Marketo. If you are a new Marketo customer working through your implementation, please work with your implementation consultant on the landing page domain(s) setup and timing to cut over to HTTPS. If you’re securing your landing page domains for a previously implemented instance, please verify that your domains and domain aliases (subdomains) are set up in your instance. Below are some links to help: Edit Landing Page Settings – to set you Landing Page Domain Customize Your Landing Page URLs with a CNAME – to understand and set up CNAMEs (subdomains) Add Additional Landing Page CNAMEs – to set up multiple CNAMEs in your instance (subdomains) Be sure your redirect rules and domain aliases are updated to use https:// instead of http:// .   Step 2. Edit and update the HTML code of your existing landing page templates to HTTPS Next, you'll need to review and update your Marketo landing pages to ready them to be served securely. Please complete the following two actions in order before moving on to Step 3: If you purchased Marketo before January 2016, please un-approve and immediately re-approve all landing pages last updated before January 2016. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages for un-approve/re-approve via the “Landing Page Actions” menu. We recommend completing this step in batches of a maximum of 10-20 pages at a time. Instructions for doing so can be found here: Approve Multiple Landing Pages at Once - Marketo Docs - Product Documentation. You can see the "Last Updated" timestamp in the Landing Pages section of Design Studio. Open the HTML code for each landing page template. C hange all URLs listed in the HTML currently formatted as "http ://" to instead read "https://" TIP: Ctrl+F "http" to automatically highlight all URLs that must be updated: Simply add "s" after each http reference until ALL have been updated to https Missing even one URL's http reference will cause the "Mixed Content" browser warning:   vs.  SAVE THE PAGE AS A DRAFT Do  not approve the draft. You will approve the drafts after Support activates SSL in Step 4. NOTE: Once you secure your Marketo landing pages to be served over HTTPS, you should not link to HTTP (unsecured) assets or pages from your secured landing pages.   For more detailed guidance, please see our recorded instructions below   Video Link : 2237     Step 3. Respond to the TSE via the existing support case The TSE will then begin the process on our end to generate certificates to cover all the domains and subdomains configured in your instance. Once notified, please allow 3 business days for Marketo to create your secure server endpoint. Marketo's Support team will contact you when this is complete. We appreciate your patience during this 3-day setup process.   Step 4. Marketo Support Will Activate Your Secured Domains for Landing Pages Once we've generated and issued the necessary SSL certificates for your domains, we'll notify you that it is done and activate SSL for your Landing Pages. NOTE: There will be a brief "cut-over" period between when HTTPS is enabled by the TSE and when you are able to complete Step 5 below. During this time, landing pages may show up to customers with a mixed-content warning; however, all links and emails will continue to work properly without disruption, and your customers are not at any risk. Be ready to complete Step 5 quickly once instructed to minimize this period.   Step 5. Re-approve your landing pages and verify success Once your Support Engineer has activated the switch to HTTPS for your instance, y ou must immediately take the following actions: Approve all draft pages that you edited from Step 2 above. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages to approve via the “Landing Page Actions” menu. If you include a Marketo landing page on a secure website using an iframe, you will need update the HTML to load the secure version of the landing page, otherwise the end user will get a security warning. Verify your pages are loading and rendering as expected. Contact Marketo Support with any issues you may encounter.     Questions & More Information For more information, including and FAQ, please see the Marketo Secured Domains for Landing Pages Overview & FAQ.     Is this article helpful ? YesNo
View full article
Full Details of all Marketo Support Offerings:   Support Levels Offered Service Level Response Targets   Global Contact   http://nation.marketo.com : Online Support Portal for Case management and Knowledgebase search support@marketo.com : Email to Case Submission supportescalations@marketo.com : Contact Support management regarding Support services marketocares@marketo.com : Questions regarding Support or Community access   Regional Contact Information     Americas: Hours: M-F, 6am to 6pm Pacific Toll Free US: +1.877.270.6586 Direct: +1.650.376.2302   Languages Supported: English, Spanish Observed Holidays: New Year's Eve New Year's Day Independence Day Thanksgiving Day and the Day After Christmas Eve Christmas Day Europe, Middle East, & Africa: Hours: M-F, 8am to 5pm GMT Europe: +353 (0)1 242 3030 UK: 0800 151 3030   Languages Supported: English, French, German, Portuguese Observed Holidays: New Year's Day Easter Monday Christmas Day St. Stephen's Day Australia Hours: M-F, 9am to 6pm Aus AET ANZ: +61 2 8310 7646   Languages Supported: English Observed Holidays: New Year's Day ANZAC Day Christmas Day Good Friday Easter Monday Boxing Day Japan: Hours: M-F, 9am to 5:30pm JST JP: +81 3 6478 6080   Languages Supported: Japanese Observed Holidays: New Year's Holiday Marine Day Coming of Age Day Respect for Senior Citizens Day National Founding Day National Holiday Spring Equinox Day Autumnal Equinox Day Day of Showa Sports Day Constitution Memorial Day Culture Day Green Day Labor Thanksgiving Day Children's Day Emperor's Birthday Substitute Public Holiday Year End   After-hours Support for Production Down Issues:   Online: Enter a Support Portal Case with Priority=P1 Phone: Call Support Line and follow the P1 prompts   Initial Response SLT We ask that you use the following priority definitions when setting your case priority:   Priority Description P1 Production down: Production system, application or critical feature / function is down P2 Production impaired: A major feature or function is not working correctly and is blocking full use of the Marketo system, but existing production campaigns are working correctly and other features are operational. P3 Minor issue: A minor issue is impacting usability of the system, but a workaround is available and major features/functions are working correctly.
View full article
With the evolving best practices and awareness around data privacy, Marketo will be upgrading how we handle form pre-fill. What change is being made? Starting April 24, 2019, Marketo will only pre-fill form fields if the URL used to navigate to the Marketo landing page contains a valid mkt_tok URL parameter value (which occurs when users click tracked links in Marketo emails). What that means is, any time a person is viewing a Marketo landing page with a form, the URL being used must contain the mkt_tok token in the query string, otherwise the form on that landing page will not be pre-filled. If the URL in the browser window does have a valid mkt_tok tracking token, then the form within the page will pre-fill as expected with data corresponding to the person record associated with that mkt_tok. Also note that if you are embedding Marketo Landing Pages within other web pages using an <iframe>, the mkt_tok would need to be passed from the parent page to the <iframe> URL if you intend for form prefill to work within the <iframe> ​How did it work before? Previously, Marketo landing pages would rely on Munchkin tracking cookies to identify known person records, and forms would pre-fill based on that cookie. Form pre-fill did not require being linked to a Marketo landing page from a tracked email link. Why is this changing? This upgrade is being made to provide a more consistent and more secure experience with Marketo’s forms. We have identified that, in the past, people have experienced scenarios where data pre-filled into a form didn’t always correspond with the actual person viewing the page. For example, people using a shared computer or those who may have been cookied incorrectly by clicking through a forwarded email, could end up viewing incorrect data associated with a different person. To provide a more consistent customer experience, and as a security enhancement, Marketo is upgrading the conditions under which the form pre-fill will display known customer information. In short, pre-fill will only work when users clickthrough links in Marketo emails, demonstrating that they have ownership of the email address associated with the known person record. Below is a list of different scenarios and how form pre-fill will work moving forward. Please note, these changes to form pre-fill will not affect any other functionality of Marketo Forms, including the progressive profiling feature. Scenario Will the form pre-fill? Notes Clicking a tracked link in a Marketo email to a Marketo landing page with a form which has pre-fill enabled Yes The email link must have mkt_tok enabled. Links that are not tracked or that have mkt_tok disabled will not work. Navigating directly to a Marketo landing page with a form which has pre-fill enabled No A direct link to the landing page will not have the mkt_tok present in the HTTP request. Refreshing a Marketo landing page with a form which has pre-fill enabled No The mkt_tok is stripped from the URL after Marketo Landing Pages load so refreshing the page will not include the mkt_tok in the URL. As a result, pre-fill will not work. Clicking a link in a sample email to a Marketo landing page with a form which has pre-fill enabled No The sample email will not have a valid mkt_tok attached to the link and so will not pre-fill the form. If you wish to test form pre-fill you will need to use a real email from a Marketo campaign. Navigating to a non-Marketo page that includes an embedded Marketo form which has pre-fill enabled No This behavior does not change with the upgrade. Pre-fill has never been supported for Marketo forms that are embedded on non-Marketo pages. Navigating to a non-Marketo page that includes an <iframe> pointing to a Marketo Landing Page that includes a form with pre-fill enabled With custom implementation The form within the Marketo Landing Page that is being loaded in the <iframe> will pre-fill if the mkt_tok value from the original HTTP request is passed along to the <iframe> URL Visiting a Marketo page with a mkt_tok that is not associated with the same person record as an existing Marketo Munchkin cookie currently stored on the browser No This will prevent the wrong person’s information from being displayed in cases where a computer is shared, or an email with a mkt_tok tracked link is forwarded to another person that may already be cookied as a known person in your database. Copying a Marketo tracked link from an email and sharing/pasting it externally (email, blog, chat, social media post, etc.) that enables another individual to click the tracked link Yes The tracked link in a Marketo email will redirect to a URL with the mkt_tok included, so anyone clicking this link will reach a page and see pre-fill data associated with the known person record from the “to” line of the email.
View full article
Included in this article Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” When finished, your Flow will look like this: Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List When finished, your Flow will look like this: 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here
View full article
  Identifying Landing Page Domains in Your Instance As of August 2019, Secured Domains will be included as a base offering for all subscriptions, to ensure our customers are set up for digital security best practices when it comes to their marketing efforts. The base offering will secure your first Landing Page domain and first Tracking Link domain - additional domains may be purchased a la carte.   New Subscriptions: If you’re a new Marketo customer with a new subscription, one of the steps in setting up your instance is to set your CNAMES, landing pages domain name, and any domain aliases. For more information see, Customizing Your Landing Pages URL with a CNAME and Adding Additional Landing Page CNAMEs. Once this is done, you’ll be ready to count the unique domains (as described below) and initiate the Secured Domains for Landing Pages process (if purchased or included in your instance).   Established Subscriptions: Have you had your Marketo subscription for a while and want to know how many landing page domains you’ve got setup in your instance? If you’re a Marketo Admin, you can see your landing pages domain name and domain aliases by clicking on Landing Pages in the Integration section of the Admin console:   On the Landing Pages tab, you’ll see your landing pages Domain Name. The first part of the URL (info.) is your CNAME and the second part (gladiatorapps.com) is the domain. Here’s an overview of the pieces that make up a full domain name:   Next, you’ll also need to check the Rules tab and look for Domain Aliases. In the example below, there are two domain aliases. One has the same domain as the landing pages domain (gladiator.com) and the other has a different domain (theappninjas.com).   For the instance in the example above, it has been set up with two unique domains (gladiatorapps.com and theappninjas.com). It’s important to note that when it comes to securing your Marketo landing pages, the Secured Domains for Landing Pages process will secure all of the domains in your instance. It’s an all-or-nothing action, meaning you cannot chose which domains to secure for HTTPS and which to leave HTTP. And don’t worry – we’ll count these up for you so we can scope your subscription correctly.   Adding Additional Secured Domains to Your Marketo Subscription If you need to secure more than the 1 Landing Page domain and 1 Tracking Link domain included in the base Secured Domains package, contact your Marketo Customer Success Manager to add additional domains a la carte to ensure you're covered. This should be discussed/audited at each renewal to ensure you're only paying for what you use.   The Secured Domains for Landing Pages Process If HTTPS in NOT currently enabled in your instance, the process to secure your pages includes steps that must be completed on your end before we can provision and enable HTTPS.  On our side, we’ll provision your Marketo domains on Cloudflare servers and install the necessary SSL certificates to create secure server end points to serve your landing pages over HTTPS.   A summary of the steps linked above are listed below: First, you’ll need to review, update and reapprove your landing pages: Unapprove and re-approve all landing pages. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages for unapprove and re-approve via the “Landing Page Actions” menu. Change all images, JavaScript files and other external links in landing pages to HTTPS. Pages with HTTP links may display an “Insecure Content on Secure Pages” error. You can read more about that here: What Exactly Is a Mixed Content Warning? Note: any images hosted in Marketo will be updated automatically unless you’ve explicitly referenced them as HTTP. If you use Marketo Forms 1.0 on a non-Marketo webpage, you will need to update the post URL to HTTPS (Forms 2.0 does not need to be updated). If you do a server-side post to a Marketo Form and use your CNAME as the Post URL, you also need to change that to HTTPS. Please note that server-side form posts are not supported and you should make a Marketo form submission in the background instead. If you include a Marketo landing page on a secure website using an iframe, you will need update the HTML to load the secure version of the landing page, otherwise the end user will get a security warning. If you use a Marketo Form on a non-Marketo page, you will need to update the follow-up URL to HTTPS if you’ve explicitly referenced a HTTP page.   Once you’ve completed the steps above, it’s time to coordinate the cutover to HTTPS with Marketo. You’ll need let Marketo Support know that you’re ready to initiate the cutover process. To help ensure a smooth transition, we’ll work with you to plan a time when you have few or no upcoming batch campaigns running, and also a time when your team is available, if needed, to make a few updates in your Marketo instance.   RECOMMENDATION: After the cutover, you may notice that images are not displayed in the Marketo email editor or preview mode. Rest assured your emails will send correctly and the images will render for recipients. To see the images in Marketo, you must adjust the image URLs from HTTP to HTTPS in the editor. Again, whether you take this step or not, the images will render properly for your email recipients. In the example below, you would adjust the HTTP to HTTPS.   That’s it! Once our team enables Secured Landing Pages for your instance, your landing pages will be served via HTTPS. Of course, it’s a good idea to do some validation of your pages after the cutover to be sure your pages are loading correctly, images are loading, and that you didn’t miss any hard-coded HTTP links. Moving your pages to HTTPS, you can rest assured that you’re providing critical security and data integrity for both your pages and your visitors’ personal information. Good job, you!   OTHER HELPFUL FAQs What exactly does Secured Domains include or cover? As of August 2019, all NEW customer subscriptions will include 1 unit of Secured Domains for Landing Pages & Tracking Links - existing customers will have the opportunity to update to the new pricing and packaging at renewal, and secure additional domains a la carte. The base offering will secure 1 Landing Page domain and 1 Tracking Link domain per instance. This covers provisioning each domain behind our security net (WAF/CDN/DDoS protection), and  the SSL certificate.   Do I need to provide a TLS/SSL Certificate? No. Secured Domains includes the required SSL certificates, and shifts the responsibility of managing ALL aspects of procuring and renewing the certificate to Marketo. Since the certificates also auto-renew annually, there is no need to continually provide us a new bundle/key every year. You will be updated to the new Secured Domains managed solution at either your next SSL certificate renewal, or Marketo renewal, whichever comes first.   What Certificate Authority issues the certificate(s) for the Marketo’s Secured Domains for Landing Pages product? The certificates are authored by DigiCert.   What type of certificate is provided? We produce a pack of two certificates; The primary certificate uses a P-256 key, is SHA-2/ECDSA signed, and will be presented to browsers that support elliptic curve cryptography (ECC). The secondary or fallback certificate uses an RSA 2048-bit key, is SHA-2/RSA signed, and will be presented to browsers that do not support ECC.   Will my domains be on a shared SSL certificate with other companies? No. Each of your domains will get its OWN certificate. That means you will not be on a shared certificate with other companies.   What Marketo configuration is required to complete the Landing Page SSL Setup? One or more CNAMEs for the Marketo Landing Pages must be configured in the Admin section of the application as described here: Setup Steps - Marketo Docs - Product Docs   How do I see the Landing Page domains in my instance? Marketo Admins can see your landing pages domain name and all domain aliases by clicking on Landing Pages in the Integration section of the Admin console. On the Landing Pages tab, you will see your full Landing Page Domain Name. On the Rules tab, you will find all Domain Aliases set up for your instance. For the Secured Domains for Landing Pages you will need to count the number of domains used in your instance. When counting domains, please provide the number of unique domains – only the orange part below:   If I am using Domain Aliases in my Marketo subscription, do I have to secure each of these? Securing your Marketo landing pages requires you to secure all domains used in your instance, including your Domain Aliases.   Are Domain Aliases for different countries counted separately? When counting domains, you might have: info.mydomain.com, info.mydomain.au, info.mydomain.de. In this case mydomain.com, mydomain.au and mydomain.de are all counted as separate domains (in this example there are 3 unique domains that must be secured).   Can I choose which domains to secure? No. Technically, we provision and secure domains in an all-or-nothing fashion by domain type (Landing Page or Tracking Link). This means whatever is configured in your instance will be provisioned, and you will be charged accordingly for all domains secured; if you have unused domains, please ensure you delete them so you're only charged for what you use.   What counts as a 'unique' domain? (How is this product charged?) Reference the screenshot above that denotes CNAME + domain = full domain. For example, your top-level domain is company.com domains, and your subdomains include go.company.com (your tracking link), info.company.com & help.company.com (two landing pages). Commercially, this would count as 3 total domains (1 TL + 2 LP domains).   If I have a CAA record, can it affect my certificate issuance? Yes. CAA records must be configured to allow DigiCert issuance, or we will not be able to issue a certificate for your domain. Your IT team MUST whitelist DigiCert in your DNS before we can successfully complete provisioning. Further information: https://www.digicert.com/dns-caa-rr-check.htm   Can I provide my own SSL certificate(s) to secure my domains? On a pre-approved exception-basis ONLY. To avoid unnecessary cost, please do NOT renew your own SSL certificate until you have spoken to Support or your CSM and received an exception.  A major time- & stress-saving benefit of Secured Domains is that Marketo fully manages and auto-renews your SSL certificates each year. While we temporarily accepted 3rd party certificates for an interim period of almost two years, we will no longer be accepting customer-provided certificates unless you have a business/industry requirement (e.g. an EV certificate). IMPORTANT: Another reason to use the certificates included with Secured Domains - Apple (Safari browser) announced in Feb. 2020 it will no longer accept SSL certificates valid for greater than 13 months. We expect Chrome and Firefox to follow suit. This means customer-provided certificates must be manually renewed and sent to Marketo each year - an unnecessary cost, risk, and hassle.  If you do qualify for an exception, you will be 100% responsible for renewing your own certificate AND sending us the bundle/key well in advance of it's expiration date (we recommend AT LEAST 10 business days) to ensure it doesn't expire - expired certificate Support cases will only be categorized as P3 priority. Please ensure they are valid for only one year to comply with browser policies.   We require an Extended Validation (EV) certificate. Can Secured Domains accommodate this? Serving Extended Validation (EV) certificates is an example of a business requirement where you WILL need to procure the EV certificate/private key and provide this to Marketo. Secured Domains must be added to your subscription to host any SSL certificate as we now provision all Marketo domains behind Cloudflare protections. The SSL certificate included with Secured Domains is not an EV certificate, and is therefore absolutely an allowed exception.   Will URLs to the existing non-secure (HTTP) Marketo Landing Pages continue to work? Your existing HTTP URLs will continue to work and will automatically be redirected to the secure (HTTPS) pages. There are only few situations where you may have to manually update the URL, specifically when you include a Marketo landing page on a secure website using an iframe. In this case, you will need to load the secure version of the landing page, otherwise the end user will get a security warning.   Does securing my Marketo landing pages also secure my corporate website? No. Marketo Secured Domains for Landing Pages only affects the landing pages served by Marketo. It does not affect any pages on your corporate (non-Marketo) website.   If I don’t use Marketo Landing Pages, do I need Secured Domains? You may if you are embedding Marketo Forms on secured non-Marketo webpages. The default form code snippet that Marketo provides uses //app-aba.marketo.com which is a Marketo domain that can be served securely on a HTTPs parent page (the // indicates the request will use whatever protocol the parent uses). With this, your Marketo form will take on the security level of the page it’s embedded on regardless of whether you’re using our Secured Domains for Landing Pages product. However, if you prefer not to have any reference to “marketo” on your corporate website, you may choose to change this code snippet from //app-aba.marketo.com to //<MY_LP_CNAME> to serve the form. In this case, you would need the Secured Domains for Landing Pages product since the LP CNAME will need a security certificate associated with it to serve securely.   Ultimately, Secured Domains is required EXCEPT if you: Do NOT use Marketo landing pages (including unsubscribe page) DO NOT use view as webpage DO NOT use forward to a friend DO NOT store anything in images and files DO NOT load embedded forms using their landing page domain   Will the Munchkin JavaScript API also be encrypted via SSL? Calls to the Munchkin JavaScript API automatically switch to SSL if the page on which the calls are made is SSL encrypted.   Can I add additional Domains to my instance and secure these too? Once you’ve secured your landing page domains with the Secured Domains for Landing Pages process, you will need to contact Marketo when adding additional domains/domain aliases. Please contact your Marketo Customer Success Manager. Additional domains are charged a la carte, cost is dependent on the number of domains you are adding.   If I previously secured my Marketo Landing Pages with the SSL for Landing Pages Service, do I need to switch to Secured Domains for Landing Pages? Yes. We have discontinued the one-time fee "SSL for Landing Pages" product and process, so you will need to switch. Your Customer Success Manager will work with you to add Secured Domains for Landing Pages at your next SSL certificate renewal or at your subscription renewal, whichever comes first.   Do I need to secure my tracking links as well? You should, per best practices. This is why we've included 1 tracking link domain as a base offering for all Marketo subscriptions. Links formatted as HTTPS will also aid in deliverability as more email clients are starting to 'dock' emails with unsecured links. If your domain enforces a strict HSTS policy on all subdomains you will NEED to secure them for the redirect to your landing page to work properly. For more information on HSTS and Marketo subdomains, please see the following documentation SSL: The HSTS policy and your Marketo subdomains   Is this article helpful ? YesNo
View full article
Overview Beginning August 15, 2018, Marketo will implement a new policy for the retention of marketing activity data. Under this policy, Lead Activity and Campaign Membership data will be stored for a rolling 25 months past the activity date, and certain high-volume activity data will be retained for a rolling period of 90 days past the activity date. Beyond these retention periods, this data will not be available. This change in retention will enable Marketo to continue to meet the performance demands of its customer base while providing clear expectations for data retention across the platform. Customers who wish to export marketing activities that are older than 25 months or high-volume activities that are older than 90 days should do so before August 15, 2018. After this date, Marketo will apply the new retention policy and the older data will no longer be available. Summary of Changes There are two components to the data retention policy: a retention period of 90 days for nine (9) high-volume activities; and a retention period of 25 months for all other activities. Activities with 90-Day Retention Period The high-volume activities listed below will be retained for 90-days. After 90-days, all such activities will be deleted. Activities Retained for 90 Days Add to List Change Score Change Data Value Visit Webpage Click Link on Webpage Sync Lead to SFDC Sync Lead to Microsoft Sync Lead Updates to SFDC Update Opportunity Request Campaign Activities with Minimum 25-Month Retention Period The activities listed below will be retained for 25 months. After 25 months, all such activities will be deleted. The only exception is the New Lead activity, which will always be displayed in the activity log. All other activities will be deleted, but the New Lead activity will not, giving you a permanent record of when the lead was created and how. Category Activities Retained for 25-Months Web Click Predictive Content Click RTP Call to Action Fill Out Form Smart Campaign Add to Engagement Program Call Webhook Change Lead Partition Change Engagement Program Cadence Change Engagement Program Stream Change Program Success Change Revenue Stage Change Revenue Stage Manually Change Program Status Compute Data Value Delete Lead Enrich with Data.com Interesting Moment Merge Leads Remove from List Resolve Ruleset Reward Test Group Variant Schedule Test Variants Send Alert Engagement Program Cast Push Lead to Marketo Social Click Shared Link Share Content Vote in Poll Email Click Email Email Bounced Email Bounced Soft Email Delivered Open Email Received Forward to Friend Email Send Email Sent Forward to Friend Email Unsubscribe Email CRM Salesforce Add to Opportunity Add to SFDC Campaign Change Owner Change Status in SFDC Campaign Click Sales Email Convert Lead Delete Lead from SFDC Lead Assigned New SFDC Opportunity Open Sales Email Receive Sales Email Remove from Opportunity Remove from SFDC Campaign Resolve Conflicts SFDC Activity Sales Email Bounced Send Sales Email SFDC Activity Updated SFDC Merge Leads Add to Case Add to SFDC Custom Object Test (Contact) Microsoft Dynamics Add to Opportunity (Contact) Add to Opportunity (Account) Remove from Opportunity (Contact) Remove from Opportunity (Account) Update Opportunity (Contact) Update Opportunity (Account) Delete Lead from Microsoft Segmentation Add to Segment Change Segment​ Once this data retention policy goes into effect, Marketo will enact the following: Activities will be available via the Marketo UI or for REST API Bulk Extract for 25 months from the activity date. Activity data in reports for campaigns, forms, emails, or website visits will be available for 25 months from the activity date. Activity data from decision rules in Smart Lists will be available for 25 months from the activity date. Smart Lists and Smart Campaigns will be able to access data for 25 months. Engagement programs will still not send the same email to a lead again for at least 25 months after the first email send activity date. Marketo Data Retention Policy You can see the Marketo Data Retention Policy in the Marketo Community here: Marketo Activities Data Retention Policy Frequently Asked Questions What Happens Next? You have until August 15, 2018 to export any of your existing, historical (older than 25 months) marketing activity data. After this date, Marketo will apply the data retention policy to marketing activities on an ongoing basis. What do I need to do? No action is required unless you wish to store activity data that was generated more than 25 months in the past. If you need to retain data that is older than 25 months, you should export it via the REST API Bulk Extract before August 15, 2018. If you would like to store the activity data from the high-volume activities, you should export it within its 90-day retention period. For additional help, you may want to engage a technology partner from the Marketo LaunchPoint Partner ecosystem or contact Marketo Professional Services. What's in it for me? Your individual benefits from this data retention change will depend on your usage. Generally, users of the Marketo platform may see performance-related improvements, such as: Smart Lists can process faster. Filters for activities (such as email opens or website visits) won’t need to query multiple years of historical data, making the search time shorter. Emails will send faster. Since Smart Lists will process faster, campaigns will qualify members faster and email batches will take less time to assemble. Lead scoring will happen faster. Activity that contributes to lead scoring will be processed faster. REST API and campaigns will execute faster. Without a large amount of historical data to process, your campaigns will execute faster and REST API calls will speed up. Will this affect my reports? You'll see changes if you attempt to run a report on lead activity beyond the retention period. Your reports will show up to 25 months’ worth of data, but data beyond the activity retention period will no longer be available. For more detailed information, please see our documentation here: Marketo Activities Data Retention Policy – Impact on Reporting How will this affect my contact data? The new data retention policy will not change the way Marketo stores field values within Lead, Account, or Custom Object records. The retention policy change applies to the activities logged in the activity log. The field values (attributes) in the record won’t be affected. Example: Say a lead has a Change Data Value activity that inputs an address into the Address field. The address itself that is entered into the Address field will not be affected. However, the Change Data Value activity that is logged in the activity log will only be retained for 25 months, after which it will be deleted. Will there be any change to lead scoring? Activities that affect lead scoring (including those from emails, forms, or campaigns) will be available for 25 months. Beyond that period, the activities will not be retained and won’t affect lead scoring. The existing score won’t be changed when the activity is deleted. Example: Say a lead visited your pricing page one time in 2014 and a Smart Campaign changed the score +5 for the activity. Four years later, the lead will still have the score of 5, but the activity that generated the score change will have been deleted. For most, the value of activities that happened over two years ago isn’t as great as the value of more recent activities. The usefulness of activities affecting scores decays over time, so the overall impact should be minimal. How will this affect marketing assets? The new data retention policy will not change the way marketing assets (such as campaigns, forms, emails, etc.) are stored. The data policy change applies only to activities, not the assets within your Marketo instance. Does this include Custom Activities? Yes. Custom activities are included in the new data retention policy. All activities, even custom activities, will be deleted after 25 months. How will this affect global unsubscribe? The new data retention policy will not affect global unsubscribe status. Even after the unsubscribe activity moves beyond the retention period date and is deleted, the lead’s Unsubscribed status is kept as a lead attribute, and is retained in the Durable Unsubscribe. How do I tell when an anonymous lead record was created and when it became known? There are two places in lead records where info is stored for when it was created. In the lead’s activity log, the “New Lead” activity records when a lead became a known lead. This activity is the only one that is not deleted after 25 months. The “New Lead” activity will always be retained in the activity log, even after others are deleted. In the Lead Info tab of the lead record, the first attribute listed is “Created”. This gives you the exact date and time when the lead record itself was first created. If the lead was anonymous first before becoming known, this will give you the date and time of the first anonymous activity. Will there be any change to my CRM sync? Any activity that was synced with your CRM prior to the new data retention policy will remain stored in the CRM and should not be changed. However, some information within Marketo Sales Insight could be affected. See our “Under the Hood” documentation for more details. Marketo Activities Data Retention Policy - Under the Hood How does this impact those in the financial services industry? Due to the very specific data retention requirements for customers in the financial services industry, we highly encourage such customers to implement their own processes to retain and archive data. If needed, you can purchase an Extended Data Retention subscription, which extends data retention to a period of 37 months (please note, the Extended Data Retention subscription does not apply to high-volume activity data which is retained for 90-days). Records can also be exported through REST API Bulk Extract. What if I use the activity data in some of my calculations? Using the raw activity data as a transactional data store is a practice that should be avoided for performance reasons. Instead of this approach, best practices for typical use cases include the following: Purchase History: Historical data such as "Purchases in the last 6 months" are often used as indicators of customer engagement. But querying the amounts from the activities each time will slow your trigger campaign performance. Instead, consider a weekly scheduled batch campaign which calculates the data and stores it as a custom attribute on the Lead. Preference/subscription history: Customer preferences and subscriptions change over time. These are frequently updated via a form, and in some cases, you might want to retain either the modified time stamp or the prior settings. However, using the raw form activities is not advisable. Instead, if you're tracking subscriptions, use either a custom attribute (for one preference) or custom objects (for multiple preferences or subscriptions). You can also use those tools to store the modification time stamp and even the previous value if necessary, though you should consider carefully how far back you really need to retain such information. Relationship marketing: Certain industries, such as Wealth Management or Consulting, have long-term relationship strategies in place. The engagement campaigns might have been set up to depend on the activities to signal that certain events have occurred. For example, an introductory or sign up package might have been sent several years ago. Instead of using the activity, have the date that activity occurred stored as a custom attribute on the Lead. Are there any options to retain my data longer than 25 months? If you need to retain your data longer than 25 months, you have two options: You can purchase the premium Extended Data Retention subscription to retain your activity data for 37 months. Talk to your Customer Success Manager for more information. NOTE: The Extended Data Retention subscription cannot be applied to the high-volume activities. Those activities will still only be retained for 90-days. You can use REST API to bulk export your data and retain it yourself. The REST API documentation containing directions for bulk exporting can be found in our REST API Bulk Extract article. What kind of data can I export using the REST API Bulk Extract? You can use a REST API call to retrieve the list of standard activity types; the call is documented in our REST API Bulk Extract article. Additional information about REST API calls can be found in REST API. Is there a way of opting out of this policy? In order to ensure that our customers continue to receive the best level of performance from the platform, all Marketo customers will be subject to this data retention policy. Where Can I Find More Information? Activities Data Retention Update Webinar In the webinar, you'll get an introduction to the updated Activities Data Retention Policy, affects across Marketo, and options for extending the data retention period and/or exporting activities data. Also includes Q&A from the live session: Marketo Activities Data Retention Policy Update Webinar Overview & FAQ Documentation This doc will give you an overview of what the policy changes and answers to the most commonly asked questions: Data Retention Policy Change - Overview & FAQ Marketo Activities Data Retention Policy The official Marketo Data Retention Policy can be found here: Marketo Activities Data Retention Policy Data Retention Policy - Impact on Reporting See how your Analytics reports will operate after the new policy goes into effect. Marketo Activities Data Retention Policy – Impact on Reporting Under the Hood Documentation This document will give you all of the details of exactly what is happening. If you're looking for in depth technical details, this is the go-to document to check out! Marketo Activities Data Retention Policy - Under the Hood Ways to store activity data beyond the retention policy Here are two docs that give possible work arounds you can try Storing Activity Data Beyond Retention Policy Maintaining a Directory of Leads Bouncing Emails Bulk Extract API Check out the documentation here to find out how to use the Bulk Extract API Contact Marketo Support If you have additional questions, please Contact Marketo Support
View full article
Traditional Bounce Codes When you add the Email Invalid Cause to display as a Column to any of your Deliverability Smartlists, you will see a code value, and potentially a suffix as well, to help you understand the reason for the Bounce. Codes in the 400 range are generally Soft Bounces Codes in the 500 range are generally Hard Bounces Mail server administrators can create custom messages that accompany bounce codes Code Explanation 250 Mail accepted by receiving network 421 <domain> Service not available, closing transmission channel 450 Requested mail action not taken: mailbox unavailable (e.g., mailbox busy) 451 Requested action aborted: error in processing 452 Requested action not taken: insufficient system storage 500 The server could not recognize the command due to a syntax error. 501 A syntax error was encountered in command arguments. 502 This command is not implemented. 503 The server has encountered a bad sequence of commands. 504 A command parameter is not implemented. 550 User’s mailbox was unavailable (such as not found) 551 The recipient is not local to the server. 552 The action was aborted due to exceeded storage allocation. 553 The command was aborted because the mailbox name is invalid. 554 The transaction failed for some unstated reason. Enhanced Bounce Codes If a suffix appears after one of the codes above, it is an enhanced Bounce code Mail server administrators can crate custom messages that accompany bounce codes Code Explanation 5.0.0 Address does not exist 5.1.0 Other address status 5.1.1 Bad destination mailbox address 5.1.2 Bad destination system address 5.1.3 Bad destination mailbox address syntax 5.1.4 Destination mailbox address ambiguous 5.1.5 Destination mailbox address valid 5.1.6 Mailbox has moved 5.1.7 Bad sender’s mailbox address syntax 5.1.8 Bad sender’s system address 5.2.0 Other or undefined mailbox status 5.2.1 Mailbox disabled, not accepting messages 5.2.2 Mailbox full 5.2.3 Message length exceeds administrative limit. 5.2.4 Mailing list expansion problem 5.3.0 Other or undefined mail system status 5.3.1 Mail system full 5.3.2 System not accepting network messages 5.3.3 System not capable of selected features 5.3.4 Message too big for system 5.4.0 Other or undefined network or routing status 5.4.1 No answer from host 5.4.2 Bad connection 5.4.3 Routing server failure 5.4.4 Unable to route 5.4.5 Network congestion 5.4.6 Routing loop detected 5.4.7 Delivery time expired 5.5.0 Other or undefined protocol status 5.5.1 Invalid command 5.5.2 Syntax error 5.5.3 Too many recipients 5.5.4 Invalid command arguments 5.5.5 Wrong protocol version 5.6.0 Other or undefined media error 5.6.1 Media not supported 5.6.2 Conversion required and prohibited 5.6.3 Conversion required but not supported 5.6.4 Conversion with loss performed 5.6.5 Conversion failed 5.7.0 Other or undefined security status 5.7.1 Delivery not authorized, message refused 5.7.2 Mailing list expansion prohibited 5.7.3 Security conversion required but not possible 5.7.4 Security features not supported 5.7.5 Cryptographic failure 5.7.6 Cryptographic algorithm not supported 5.7.7 Message integrity failure Not all mail servers adhere to these standards.
View full article
Just joined the Marketo family? Want to learn more about how to use Marketo? Drop by one of our Office Hours! Group Office Hours are one-hour sessions for you to virtually connect with a marketing automation expert when you need personalized guidance and insightful advice. Office Hours are available weekdays at different hours to meet our customers' needs around the globe. Please note these open sessions are open to Launch Pack customers only. If you have not signed up for the service and would like to, please send an email to services@marketo.com. Prerequisites: You must be within 90 days of your Marketo subscription start date or have signed up for the service You must have taken the Marketo Core Concepts class What to expect: Marketo Expert facilitating the open group session Types of questions: How to/Best Practices/Strategy/On-boarding Upcoming Sessions EMEA Office Hours: Monday, 2 PM GMT North America Office Hours: Monday, 11 AM PT / 2 PM ET APAC Office Hours: Tuesday 1pm AEDT, 3pm NZDT North America Office Hours: Wednesday, 11 AM PT / 2 PM ET APAC Office Hours: Thursday 1pm AEDT, 3pm NZDT North America Office Hours: Friday, 11 AM PT / 2 PM ET
View full article
Issue: You would like to change ths position of the form button up or down. (Typical case: You've just changed the button color of the form and now you want to change the position.) Please ensure that you have access to an experienced Web developer. Marketo Technical Support is not set up to assist with troubleshooting code. Solution: Add css style using adding the margin-top property referencing the button. The following code snippet can be a positive or negative number to shift the button up or down. Typically if you used the button color solution add the margin-top property as in the screen shot or add the code below in an additional custom html block. Code snippet: < style> div.buttonSubmit input, div.buttonSubmit span { margin-top: 50px; } < /style> Related Links: Change Submit Button Style and Color How to move a form button left or right using CSS
View full article
Blacklist Remediation I n offering a premium email delivery platform to our customers we carefully monitor our IPs for listings on significant blacklists . The Marketo Privacy team maintains relationships with the major blacklists to better assist our customers in resolving these issues. When we find that one of our customers was responsible for a blacklisting we contact that customer and request some actions be taken to remediate the issue. In many cases we find that sending an email to a spamtrap address caused the blacklisting.  Spamtraps are email addresses that have either never been used or have not been used for a long time and are now owned by anti-spam organizations. They are considered by these organizations as a sign of poorly maintained or inappropriately acquired addresses. Based on this assessment they conclude that the marketer is sending spam and consequently blacklist the sender. To prevent future blacklistings you'll need to review your recent activity to remove the spamtrap from your mailing. Finding the spam trap address can be difficult; they are closely guarded secrets of the blacklisting organizations and they do not share these addresses. We describe several strategies below. The best approach for you depends on the make-up of your database and the amount of behavioral history in your Marketo system. The goal is to isolate potential spamtrap addresses and remove them. The group of addresses you select should be broad enough to capture those potentially bad addresses but small enough not to suppress a huge portion of your database. Blacklists are not all the same - some provide Marketo with more information, some with less. If at all possible we will provide you with a date and a subject line to help you isolate potential traps.         Step 1         To narrow the list of potential traps you should consider the following: Have you recently added any new leads or new lead sources? What is the source of these leads? Any purchased or appended email addresses should be removed because these data sources are often the source of newly introduced spamtraps. In addition lead sources like this can violate Marketo's Email Use and Anti-Spam Policy​ Have you recently added any older leads from another database that have not received email in the past year?  Some email providers will turn an address into a spamtrap after a year of inactivity.  If you have a list of addresses that had not received email for a year or more before recent email campaigns this list should be removed. Does your system use any custom fields to indicate customer status, event attendance, recent contact with your sales team, or other forms of engagement?  Take advantage of this and isolate the inactive or nonresponsive segments of your database using all activity data you have available. Is there anything different about this specific mailing that makes it different compared to your previous email campaigns? Did you send any other mail on the same day?  You could compare the recipient lists. Step 2 If you were able to identify newly introduced email addresses to your email program that are likely the source of the spamtrap suppress or remove those from your database so they will not receive email in future email campaigns.  If you have not identified a specific data source than you should target the inactive or nonresponsive segments of your database for potential spamtraps.  Because an individual does not manage spamtrap addresses, they are generally part or a larger spamtrap network; they will generally not show any form of activity. If you have behavioral history, the best approach to take is to identify the people who are not interacting with your company - not opening or clicking emails, not visiting the web page, not attending events, etc. Build an inactive Smart List using ALL filters: W as sent email the day of and day before the spam trap hit (please contact support@marketo.com for the date of the trap hit if you do not have this information already.) Lead “was created” date is at least 6 months ago Inactivity Filters Not visited web page is “any”; constraint date of activity “in past 3 months” Not filled out form is “any”, constraint date of activity “in past 6 months” Not clicked link in email is “any”, constraint date of activity “in past 6 months” Not opened email is “any”, constraint date of activity “in past 6 months” If you have custom database fields that would show other forms of activity feel free to add this into your inactive Smart List to exclude active leads. Step 3 Once you have created a smart list to identify these suspect leads you have several options. [Leads Tab > Lead Actions > Flow Actions] Remove leads from database Why waste your time on inactive leads? Set leads to Marketing Suspended = true to suppress from future mailings Marketing suspended is functionally equivalent to unsubscribe. These leads will still be available for other flow actions, tracking, or operational emails. To avoid suppressing an active lead’s email address you can create a daily recurring batch campaign to take any marketing suspended lead who "wakes up" and engages and set them back to marketing suspended is false.  The daily batch campaign would be set to change Marketing Suspended back to false if the lead performed any specific activity in the last 24 hours like if they visit a web page, open or click a link in an email, fills out a form or has a lead status change. Here's how to set up the campaign: Smart List (using the "ANY" filter, not "AND"): "Visits Web Page" "Clicks Link in Email" "Fills Out Form" "Opened Email"           All selectors for these filters should be set to 'any'. Flow: "Change Data Value" flow step Attribute: "Marketing Suspended. New Value: "False" . Opt-In reconfirmation pass Create and release an email to inactive list with the following sample copy: "We have not heard from you in a while. Click this link to continue to receive messages." Anyone who does not click the link within 2 weeks should be set to Marketing Suspended. For recommendations on successful reconfirmation messages search our help articles for reconfirmation . Some mix of the above Many of our customers take a tiered approach to blacklist remediation. If they can identify inactive, low-priority leads they may choose to immediately delete or Marketing Suspend these while reserving a reconfirmation pass for higher priority leads. If your list includes extremely high value sales targets you might consider having your sales team reach out individually. If considering this approach we recommend that you export the list and try various sorting techniques to get a feel for the leads you're looking at before deciding on the best way to segment them for different tiers of attention. Step 4 – You’re Done! Don't forget to fill out the delisting form Is this article helpful ? YesNo
View full article
Included in this article Overview Marketo uses a set of fields to capture certain kinds of marketing related information. If you would like this data in Salesforce, please follow the instructions below. Create three custom fields in Salesforce on the lead and contact objects: Lead Score, Acquisition Program, and Acquisition Date. Map these custom fields between leads and contacts so that on conversion in Salesforce, the values carry over. You can create other additional fields, if necessary (see the table below). All of these custom fields are optional and are not required to sync Marketo and Salesforce. As a best practice, we recommend that you do create fields for Lead Score, Acquisition Program, and Acquisition Date. Add Marketo Fields to Salesforce Add three custom fields on the lead and contact objects in Salesforce listed above. If you want to add more, see the table of available fields at the end of this section. Perform the following steps for each of the three custom fields to add them. Start with Lead Score. 1. Log into Salesforce and click Setup . 2. In the Build menu on the left, click Customize and select Leads . Click Fields . 3. Click New in the Custom Fields & Relationships section at the bottom of the page. 4. Choose the appropriate field type (for Lead Score — number ; Acquisition Program — text ; Acquisition Date — Date/Time ). 5. Click Next . 6. Enter the Field Label, Length, and Field Name for the field, as shown in the table below. Field Label Field Name Data Type Field Attributes Lead Score mkto71_Lead_Score Number Length 10 Decimal Places 0 Acquisition Date mkto71_Acquisition_Date Date/Time Acquisition Program mkto71_Acquisition_Program Text Length 255 7. Click Next . 8. Specify the access settings and click Next : Set all profiles to Visible and "Read-Only". Uncheck "Read Only" for the profile of your sync user. Often customers have a user with the profile of a System Administrator as the sync user. If that's the case with you, then uncheck “Read Only” for the System Administrator profile as shown in the picture below. If you have created a custom profile for the sync user, then uncheck "Read-Only" for that custom profile 9. Choose the page layouts that should display the field. 10. Click Save & New to go back and create each of the other two custom fields. Click Save when you're done with all three. 11. In the Build menu on the left, click Customize and select Contacts. Click Fields . 12. Perform steps 3 through 10 for the Lead Score, Acquisition Date, and Acquisition Program fields on the contact object, just as you did for the lead object. 13. Optionally, use the above procedure for any additional custom fields from this table.      NOTE: These fields are additional optional fields you may choose to add as well. The Lead Score, Acquisition Date and Acquisition Program fields      are detailed above Field Label Field Name Data Type Field Attributes Acquisition Program Id mkto71_Acquisition_Program_Id Number Length 18 Decimal Places 0 Original Referrer mkto71_Original_Referrer Text Length 255 Original Search Engine mkto71_Original_Search_Engine Text Length 255 Original Search Phrase mkto71_Original_Search_Phrase Text Length 255 Original Source Info mkto71_Original_Source_Info Text Length 255 Original Source Type mkto71_Original_Source_Type Text Length 255 Inferred City mkto71_Inferred_City Text Length 255 Inferred Company mkto71_Inferred_Company Text Length 255 Inferred Country mkto71_Inferred_Country Text Length 255 Inferred Metropolitan Area mkto71_Inferred_Metropolitan_Area Text Length 255 Inferred Phone Area Code mkto71_Inferred_Phone_Area_Code Text Length 255 Inferred Postal Code mkto71_Inferred_Postal_Code Text Length 255 Inferred State Region mkto71_Inferred_State_Region Text Length 255 Map Custom Fields for Conversions A custom field on the lead object in Salesforce should be mapped to a contact field on the contact object so that data is carried over when a conversion occurs.  1. In the top right corner, click Setup . 2. Type "Fields" into the Nav Search without pressing Enter. Fields appears under different objects; Click Fields under Leads. 3. Go to the Lead Custom Fields & Relationships section and click Map Lead Fields . 4. Click the drop-down next to the field you want to map. 5. Select the corresponding contact custom field. 6. Repeat the above steps for any other fields you've created. 7. Click Save when you're done. Here's a video of the entire process that should make it easy to follow along: Salesforce Connector Setup
View full article
Note: Please ensure that you have access to an experienced CSS and Jquery developer, because Marketo Technical Support is not set up to assist with troubleshooting custom coding. Advanced solution - requires CSS and jQuery knowledge Issue: Need to set a popup window in Marketo. The rich text editor (hyperlink - popup tab) has this feature but gets overrode by most browsers opening in a new tab. Solution: Use jQuery. Here's a third party site that covers how: http://yensdesign.com/2008/09/how-to-create-a-stunning-and-smooth-popup-using-jquery/ This does work in Marketo landing pages - The header content goes in the custom head HTML Save a copy of the CSS and popup.js to the images and files section of Marketo Update the CSS and .js files to your copies in Marketo I used the same input version in the example here, but you could use a link or content instead. Click here for a sample page in Marketo using the above solution: http://info.dbmayberry.com/popupsolution.html
View full article
‌ Marketo offers a number of ways to contact Marketo Support directly for assistance in our different support regions. Support Portal (https://support.marketo.com) The Marketo Support Portal features a web form submission to submit support cases to Marketo Support.  The form gives authorized support contacts the ability to provide details on the support issue that allows Marketo Support to efficiently and effectively assign your case to the best suited available support engineer. Email to Case Submission Authorized Support Contacts can email their support cases to: support@marketo.com Reminder: Cases submitted by email are all submitted with a P3 Priority Regional Phone Contact Information For customers with Business, Premier, or Elite Support Levels, we offer phone support coverage.  Authorized Support contacts can contact Marketo Support by calling one of the regional phone numbers listed below.  Our phone system will validate your inbound phone number and route you to one of our available Technical Support Engineers Americas: Hours: M-F, 6am to 6pm Pacific Toll Free US: +1.877.270.6586 Direct: +1.650.376.2302   Languages Supported: English, Spanish Observed Holidays: New Year's Day Independence Day Thanksgiving Day and the Day After Christmas Day Europe, Middle East, & Africa: Hours: M-F, 8am to 5pm GMT Europe: +353 (0)1 242 3030 UK: 0800 151 3030   Languages Supported: English, French, German, Portuguese Observed Holiday: New Year's Day Easter Monday Christmas Day St. Stephen's Day Australia Hours: M-F, 9am to 6pm Aus EST ANZ: +61 2 8310 7646   Languages Supported: English Observed Holiday: New Year's Day ANZAC Day Christmas Day Good Friday Easter Monday Boxing Day Japan: Hours: M-F, 9am to 6pm JST JP: +81 3 6478 6080   Languages Supported: Japanese, English Observed Holiday: New Year's Holiday Marine Day Coming of Age Day Respect for Senior Citizens Day National Founding Day National Holiday Spring Equinox Day Autumnal Equinox Day Day of Showa Sports Day Constitution Memorial Day Culture Day Green Day Labor Thanksgiving Day Children's Day Emperor's Birthday Substitute Public Holiday Year End Online Chat (https://support.marketo.com) Marketo Support also offers online chat with our support engineers from our Support Community.  Authorized support contacts who are logged into our Marketing Nation Community can take advantage of chatting with our support engineers online.
View full article
Included in this article Overview Many times it is necessary to prevent certain 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 also that 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, there are three documents that correspond to the three different steps: “Step 1 of 3”, “Step 2 of 3” and “Step 3 of 3”. For both versions, proceed through all steps of “Step 1 of 3” and “Step 2 of 3” completely. 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 you include the custom field name, which configuration you need (checked=sync vs checked=don’t sync) and also 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!
View full article
Overview Starting August 15, 2018, Marketo will be implementing a new policy for the retention of marketing activity data. Under this policy, Activity and Campaign Membership data will be stored for a rolling period of 25 months past the activity date, and high-volume activity data will be retained for a rolling period of 90 days past the activity date. Beyond these retention periods, the data will not be available through the Marketo UI. Activities and Retention Settings There are two components to the data retention policy: a retention period of up to 90 days for nine (9) high-volume activities; and a retention period of up to 25 months for other lead activities. Activities with a 90-Day Retention Period These lead activities have a very high volume and will be retained for 90 days. After 90 days, these activities will be deleted. Activities Retained for 90 Days Add to List Change Score Change Data Value Visit Webpage Click Link on Webpage Sync Lead to SFDC Sync Lead to Microsoft Sync Lead Updates to SFDC Update Opportunity Request Campaign Activities with a 25-Month Retention Period The lead activities listed below will be retained 25 months. After 25 months, all such lead activities will be deleted. The only exception is the New Lead activity, which will always be displayed. Category Activities Retained for 25-Months Web Click Predictive Content Click RTP Call to Action Fill Out Form Smart Campaign Add to Engagement Program Call Webhook Change Lead Partition Change Engagement Program Cadence Change Engagement Program Stream Change Program Success Change Revenue Stage Change Revenue Stage Manually Change Program Status Compute Data Value Delete Lead Enrich with Data.com Interesting Moment Merge Leads Remove from List Resolve Ruleset Reward Test Group Variant Schedule Test Variants Send Alert Engagement Program Cast Push Lead to Marketo Social Click Shared Link Share Content Vote in Poll Email Click Email Email Bounced Email Bounced Soft Email Delivered Open Email Received Forward to Friend Email Send Email Sent Forward to Friend Email Unsubscribe Email CRM Salesforce Add to Opportunity Add to SFDC Campaign Change Owner Change Status in SFDC Campaign Click Sales Email Convert Lead Delete Lead from SFDC Lead Assigned New SFDC Opportunity Open Sales Email Receive Sales Email Remove from Opportunity Remove from SFDC Campaign Resolve Conflicts SFDC Activity Sales Email Bounced Send Sales Email SFDC Activity Updated SFDC Merge Leads Add to Case Add to SFDC Custom Object Test (Contact) Microsoft Dynamics Add to Opportunity (Contact) Add to Opportunity (Account) Remove from Opportunity (Contact) Remove from Opportunity (Account) Update Opportunity (Contact) Update Opportunity (Account) Delete Lead from Microsoft Segmentation Add to Segment Change Segment Data Access Marketo’s data retention policy gives you a rolling 90-day view of certain high-volume lead activities and a rolling 25-month view of other lead activity data. To help prevent any actual data loss, Marketo has developed a Bulk Extract API that enables you to export this data directly if desired. Once exported, you will be able to host this information locally and utilize it in any way you deem necessary. Areas Affected Smart List filters Smart List filters referencing high-volume lead activities beyond their 90-day retention period or other activities beyond their 25-month retention period will not have the activity to reference. Results from any Smart Lists or campaigns that use filters looking for lead activities that occurred past their retention period will not show results from those activities. Flow Steps with Choices Added Flow steps offer the option to add a choice to do different things depending specified conditions. In addition to searching for lead attributes, these choices may include looking for activities that the lead has taken. If the condition selected in the flow step is searching for an activity the lead has taken, that flow step choice will only be able to find activities that happened within the data retention period for that activity. Lead Records Activity Logs Activity log data will be retained for 25 months and will not display any activities older than 25 months. This provides a rolling 25-month view of lead activities. The one exception to this policy is for the “New Lead” activity. That activity will be retained regardless of how long ago the lead was created. Identifying Anonymous Lead Creation vs Known Lead Creation There are two places in lead records where info is stored for when it was created - in the activity log, showing when the lead became known, and in the Lead Info tab, where it shows the first anonymous activity. Known Lead Creation - Activity Log In the lead’s activity log, the “New Lead” activity records when a lead became a known lead. This activity is the only one that is not deleted after 25 months. The “New Lead” activity will always be retained in the activity log, even after others are deleted. Anonymous Lead Record Creation Date - Lead Attribute In the Lead Info tab of the lead record, the first attribute listed is “Created”. This gives you the exact date and time when the lead record itself was first created. If the lead was anonymous first before becoming known, this will give you the date and time of the first anonymous activity. NOTE: If the lead did not first have have anonymous activity, but was instead created through list import or manual lead entry, this date and time will match the New Lead activity. Custom Activities Custom activities are included in the new data retention policy. All activities, even custom activities, will be deleted after 25 months. Programs Program Membership Record of program membership will not be affected. Leads that became members of a program over 25 months ago will still show as members of that program. Engagement Programs Engagement Programs will not send the same email to a lead that has already received it, unless the lead was sent the email more than 25 months ago. Engagement Program Transition Rules Marketo’s Engagement Programs allow you to move leads into different streams based on criteria you set in the stream’s transition rules. The transition rules use triggers to activate the transition from one stream to the next. Filters can be added to the transition rule as well, including activity-based filters. If you add activity-based filters to your engagement stream transition rules, they will only be able to access lead activities within their retention period. For example, if the activity you’re filtering for has a 25-month retention period and it has occurred more than 25 months ago, the transition rule will not be able to reference the activity and the lead will not transition to the new stream. NOTE: This same condition applies to Revenue Cycle Model transitions. See the information in the section below for more details. Recommendation: Review your marketing strategies. Do you really want a lead to be in the same engagement program for over two years? Do you still want the same email in circulation if it was drafted over 2 years ago? Smart Campaigns Records of campaign membership will be stored for up to 25 months. After 25 months, that information will not be available. Smart Lists, campaigns and reports that use the “Member of Smart Campaign” filter will only be able to reference a lead’s membership in the campaign for up to 25 months. While most activity information can be exported through the Bulk Extract REST API, campaign membership activity cannot be exported. Revenue Cycle Model Transition Rules Marketo’s Revenue Cycle Model allows you to advance leads through Revenue Model Phases based on criteria you set in the Revenue Model’s transition rules. The transition rules use triggers to activate the transition from one phase to the next. Filters can also be added to the transition rules, including activity-based filters. If you add activity-based filters into your Revenue Model Transition rules, they will only be able to access lead activities within their retention period. For example, if the activity you are filtering for has a 25-month retention period and it has occurred more than 25 months ago, the transition rule will not be able to reference the activity and the lead will not transition to the next revenue model phase. Reporting Marketo Analytics reports can be affected by the data retention period of lead activities. Reports that directly draw data from lead activity logs will only show data for up to 25 months. Also, reports that do not directly reference lead activity, such as those with filters added to the smart list of the report, could be affected. Filters that look for activities the lead took are only going to be able to access activities for 25 months, so if the activity occurred beyond the 25-month retention period, it will alter the results of the report. Note, filters that reference lead attributes (information in fields in the lead record) will not cause any change to the report. Example: The People by Status report does not draw data from lead activities by default. However, if you add filters to the Smart List of the report, the report results may be affected depending on the type of filter you apply. Adding the filter, “Job Title” would not have any effect on the report results because lead attributes are not affected by the data retention limits. Adding the filter, “Filled Out Form” does potentially affect the report results because its references data in the lead activity log which is retained for up to 25 months only. To help you identify exactly how each report will behave, please see the detailed documentation on Data Retention Policy – Impact on Reporting. Sales Insight Sales Insight is a powerful tool for your sales reps to get information about your leads and contacts. The data in Sales Insight is not actually stored in Salesforce, it’s an up-to-date feed directly from the Marketo database. When Sales Insight is opened, it makes an API call to Marketo to pull data into Salesforce. Since the data shown in Sales Insight is coming directly from the lead records within Marketo, it will only be able to access lead activities within their retention period. Sales Insight on Lead and Contact Page The Sales Insight window in your Lead and Contact pages has four tabs; Interesting Moments, Web Activity, Score and Email. All four of these actively retrieve data from the corresponding lead’s activity logs, so the data displayed in each of those tabs will only display information up to 25 months old. Example - Interesting Moments Example - Email: Marketo Sales Insight Tab Aside from the Sales Insight you see within the Lead and Contact page, there is also the Sales Insight Marketo tab in the toolbar. In this section of Sales Insight, only one area is affected: My Email. The other tabs including Best Bets, My Watch List, Web Activity and Anonymous Web Activity are not affected The activity found within the My Email tab is based on Marketo lead records. Therefore, it will only display records up to 25 months in age. Areas NOT Affected Custom Activity Sync Marketo gives you the ability to customize the sync of specific activities to Salesforce. Sales Insight and Custom Activity Sync tend to go together, even though they’re different features. When you set up Custom Activity Sync, the activity data is sent to Salesforce and stored there inside of SFDC. Since the data exists inside SFDC at this point, this feature will not be affected in any way. To set up Custom Activity Sync, go to Admin > Salesforce > Edit Sync Options. You’ll find a dialog box like this: Once you’ve selected which activities to sync to Salesforce, they will appear in the Activity History of your Lead/Contact inside Salesforce. Since the Activity History of a Salesforce Lead/Contact is contained inside of Salesforce, these activities will not be affected by this policy change. Variations of Current Policy Marketo’s Activity Data Retention Policy is intended to standardize data retention across all Marketo instances. Over time there have been three variations of data retention: Default Retention Setting, Legacy Retention Setting, and Custom Retention Setting. All variations will be replaced by the new policy. Default Retention Setting The Default retention settings are the most current settings and are what most customers currently use. The high-volume activities are displayed in the lead’s activity log for 90 days and can be referenced in filters and reports. After 90 days, these activities are moved into an archive where they are no longer accessible in Smart Lists or reports. These archived activities can still be accessed, but only when searching each individual lead’s activity log directly. No other activities have retention limits applied. Note: Once the new Data Retention Policy goes into effect, the high-volume activities will only be retained for 90-days and the archive tab/feature will be removed. Legacy Retention Settings The Legacy retention setting is an older default setting that was replaced by the newer Default setting listed above. Only a small number of long term customers may have this Legacy retention setting. This setting worked in the exact same way that the current Default retention setting except that the 90-day archive was applied to five activities, not the nine activities that the Default setting above archives. Default High Volume Activities Archived at 90 Days Legacy High Volume Activities Archived at 90 Days Add to List Change Score Change Data Value* Visit Webpage Click Link on Webpage Sync Lead to Microsoft Sync lead to SFDC Sync Lead Updates to SFDC Update Opportunity Request Campaign Add to List Change score Change Data Value* Visit Webpage Click Link on Webpage Note: Once the new Data Retention Policy goes into effect, the high-volume activities will only be retained for 90-days and the archive tab/feature will be removed. All variations will be replaced by the new policy. High Volume Activity Archive Some customers may use the archive view of lead activities. Even though it is being removed, below is a description of where it was to help you better understand the exact changes being made. Archived activities are seen in individual lead records by navigating to the lead’s activity log and changing the filter setting to custom. A dialog box will open where you can select which activities to display. Change the Activity Source to Archive and the only activities that will be displayed in the log will be the high volume ones that were archived at 90 days. All variations will be replaced by the new policy. Custom Retention Settings Some Marketo customers have customized retention settings to extend the duration that high-volume activities are displayed in the activity log. Instances with custom retention settings will not have the archive option available in the custom filter. The Activity Source selector will not show at all. All variations will be replaced by the new policy. Where to go for More Information Activities Data Retention Update Webinar In the webinar, you'll get an introduction to the updated Activities Data Retention Policy, affects across Marketo, and options for extending the data retention period and/or exporting activities data. Also includes Q&A from the live session: Video Link : 2314 Overview & FAQ Documentation This doc will give you an overview of what the policy changes and answers to the most commonly asked questions: Data Retention Policy Change - Overview & FAQ​ Marketo Activities Data Retention Policy The official Marketo Data Retention Policy can be found here: Marketo Activities Data Retention Policy Data Retention Policy - Impact on Reporting See how your Analytics reports will operate after the new policy goes into effect. Marketo Activities Data Retention Policy – Impact on Reporting Ways to store activity data in custom fields Here are two docs that can help you keep activity data inside of custom fields on the lead records Storing Activity Data Beyond Retention Policy Maintaining a Directory of Leads Bouncing Emails Bulk Extract API Check out the documentation here to find out how to use the Bulk Extract API​ Contact Marketo Support If you have additional questions, please Contact Marketo Support
View full article
Issue Description You want to know the difference between a field with the type of string and text area. Issue Resolution Both a string and text field will hold information that you can freely write in. The major difference between the two fields is how many characters you can put in these fields. A string field has a limit of 255 characters, whereas a text field has a character limit of 30,000 characters.   A string field is a good choice if you wanting to store data like address, names, or simple custom data. A text area field is a good choice when you want to store information from something like a comment box on a form or if you are importing a large block of text. Is this article helpful ? YesNo
View full article
Included in this article Overview Do you need to create fields in Salesforce and have them connect to specific fields in Marketo like for Lead Score or Acquisition Program? If so, this document will take you right to the instructions on how to get that done! Step by Step Directions for all Salesforce Editions Adding Custom Marketo Fields to Salesforce Video Overview Here's a video tutorial of the entire process that should make it easy to follow along: Salesforce Connector Setup​ Enjoy!
View full article
To enable Marketo to meet the performance demands of its customers, Marketo has a standardized Data Retention Policy used across the platform. This policy applies to the activities stored in the activity logs of people in your database. Activities and Data Retention There are two components to our data retention policy: a retention period of 90 days for nine (9) high-volume activities; and a retention period of 25 months for other lead activities. Activities with Retention Period of 90 days The high-volume activities listed below will be retained for 90-days. After 90-days, these activities will be deleted. Activities Retained for 90 Days Add to List Change Score Change Data Value Visit Webpage Click Link on Webpage Sync Lead to SFDC Sync Lead to Microsoft Sync Lead Updates to SFDC Update Opportunity Request Campaign Activities with Retention Period of 25 Months The activities listed below will be retained for 25 months. After 25 months, all such lead activities will be deleted. The only exception is the New Lead activity, which will always be displayed in the activity log. All other activities will be deleted, but the New Lead activity will not, giving you a permanent record of when the lead was created and how.   Category Activities Retained for 25-Months   Web Click Predictive Content Click RTP Call to Action Fill Out Form   Smart   Campaign Add to Engagement Program Call Webhook Change Data Value Change Lead Partition Change Engagement Program Cadence Change Engagement Program Stream Change Program Success Change Revenue Stage Change Revenue Stage Manually Change Program Status Compute Data Value Delete Lead Enrich with Data.com Interesting Moment Merge Leads Remove from List Resolve Ruleset Reward Test Group Variant Schedule Test Variants Send Alert Engagement Program Cast Push Lead to Market   Social Click Shared Link Share Content Vote in Poll   Email Click Email Email Bounced Email Bounced Soft Email Delivered Open Email Received Forward to Friend Email Send Email Sent Forward to Friend Email Unsubscribe Email   CRM Salesforce Add to Opportunity Add to SFDC Campaign Change Owner Change Status in SFDC Campaign Click Sales Email Convert Lead Delete Lead from SFDC Lead Assigned New SFDC Opportunity Open Sales Email Receive Sales Email Remove from Opportunity Remove from SFDC Campaign Resolve Conflicts SFDC Activity Sales Email Bounced Send Sales Email SFDC Activity Updated SFDC Merge Leads Add to Case Add to SFDC Custom Object Test (Contact) Microsoft Dynamics Add to Opportunity (Contact) Add to Opportunity (Account) Remove from Opportunity (Contact) Remove from Opportunity (Account) Update Opportunity (Contact) Update Opportunity (Account) Delete Lead from Microsoft Segmentation Add to Segment Change Segment​ Retaining Data Marketo’s data retention policy gives you a rolling 90-day view of certain high-volume activities and a rolling 25-month view of other lead activity data. To help prevent any actual data loss, Marketo has developed a Bulk Extract API that enables you to export this data directly if desired. Once exported, you will be able to host this information locally and utilize it in any way you deem necessary. Premium Data Retention Option Marketo offers a premium Extended Data Retention subscription option that will allow activity data to be stored for 37 months instead of the standard retention period of 25 months. The high-volume activities, however, will only be retained for 90 days even with the premium option. For more information, contact your Customer Success Manager. Is this article helpful ? YesNo
View full article