Knowledgebase

Sort by:
Issue How to subscribe to Marketo service interruption and outage notices.       Solution Issue Resolution   Follow the instructions RE: Subscribe to Status page notifications for the latest information on service issues, degradations, or disruptions that may be impacting your Adobe Marketo Engage subscription.   
View full article
Issue New person records are missing data and only contain Email Address. Environment On24 Event Partner Launchpoint Integration Solution When Marketo pulls the Attendance Report, for On24 Events through the On24 Launchpoint Event Partner integration, as documented here: ON24 Event Registration Updates | Adobe Marketo Engage For any net new records to Marketo (people who registered and attended the event outside of Marketo), Marketo will only sync the Email Address and Attendance Status. This will result in records in Marketo that do not have complete data from On24, such as First and Last Name. To avoid this scenario, it is recommended that all records are properly registered for the Event through Marketo, using Marketo Forms and Registration Campaigns as documented here: Create Child Campaigns and Local Assets | Adobe Marketo Engage
View full article
System Uptime and Reliability   Month Uptime October 2022 99.946% September 2022 *Due to a change in internal tooling, availability calculations for September 2022 reflect only the second half of the month 99.903% August 2022 99.997% July 2022 99.681% June 2022 99.819% May 2022 99.953% April 2022 99.946% March 2022 99.933% February 2022 99.576% January 2022 99.700% December 2021 99.965% November 2021 99.970%     Email Deliverability Score     Trusted IPs All IPs Month Cisco SenderBase Good/Neutral/Poor ReturnPath Sender Score 0 to 100 Cisco SenderBase Good/Neutral/Poor ReturnPath Sender Score 0 to 100 October 2022 Good 99 Good 98 September 2022 Good 99 Good 98 August 2022 Good 99 Good 98 July 2022 Good 99 Good 98 June 2022 Good 99 Good 98 May 2022 Good 99 Good 98 April 2022 Good 98 Good 98 March 2022 Good 98 Good 98 February 2022 Good 98 Good 98 January 2022 Good 98 Good 98 December 2021 Good 98 Good 98 November 2021 Good 99 Good 98
View full article
Summary Estimating the external storage requirements for your Marketo Engage Database Issue I want to extract all of my data from Marketo Engage and store it. How much storage space will I need? Environment Marketo Engage and External Systems Solution Summary There is no repeatable method to accurately estimate the amount of storage you will need to extract and store your Marketo Engage database. Standing in the way of good estimation is data availability, field selection, and storage method. Any accurate estimate will take into account the potential sizes of each type of data and their quantities (known to data scientists as "facts and dimensions"). Determining ranges for these values takes a lot of preparation and may require a high level of skill. IMPORTANT NOTE: Estimating Database size is hard so any estimate used to make business decisions should be made in cooperation with a database or application architect or other qualified professional. Scope Some information won't be extracted. Information about anonymous leads, for example, cannot be extracted. Some of the data that can be extracted may not be needed at all. Selecting the right data for your needs is the best practice as it reduces the required storage and leads to a more efficient extraction process. Field Definitions How the fields are defined in the target system will affect how big the stored data is. Depending on your storage format, padding may play a role in the size of your extracted database. As an example, the "Country" field in Marketo is a string of up to 255 characters. You could chose to store 255 characters for every country value. Or you may choose a format that uses a variable amount of space. You might also know that the longest country name is "the United Kingdom of Great Britain and Northern Ireland" meaning that 199 of those characters will always be extra so you truncate the value from Marketo storing the first 56 characters only. Each choice will have an impact on the size of your extracted database. Estimating 199 unnecessary characters per lead and making similar decisions for other fields will add up to increased storage requirements and slower extraction time. Format Once the desired data is identified, the next step is to extract, transform and load (ETL) the data from Marketo Engage into your storage system. The data returned by Marketo's API is plain old text which is usually formatted as JSON or CSV. For the information to be useful, you will transform it from JSON into the format necessary for your storage system. That format could be an Excel spreadsheet, Microsoft SQL database or a schema-agnostic database like Azure Cosmos DB. How the data is formatted and encoded will make a big difference in the amount of storage needed. Take this simple example: a Microsoft Excel spreadsheet with "Marketo Engage" in cell A1. I saved that same file in four different formats which resulted in files ranging from 1 KB to 25 KB. The format you store you information in may have a bigger impact on your final storage requirement than the data itself. This is a article attached image   To help illustrate the impact of the storage system, take a look at this guide for Microsoft SQL Database size estimation: https://docs.microsoft.com/en-us/sql/relational-databases/databases/estimate-the-size-of-a-database  Functionalization Once you've extracted your data, what are you going to do with it? Archiving your data (simply storing it) is easiest and comes with the fewest contraints. A compressed archive (Zip file) will save dramatically on storage space at the cost of functionality and ease of use. Functionalizing your data (using it in an application) requires more: at least better speed and searchability: typically a relational database. An application will often require additional data and that will need to be accounted for too. Facts and Dimensions: Do the Math It's a lot of work to get to this stage. Once you've determined how your extracted data will be stored, you can set upper and lower bounds on the sizes for each object type extracted (lead, email, activity, etc). These are your facts. Then multiply those values by the number of each type of record. These are your dimensions. Add to that the overhead of your target storage system and its functional requirements to generate your final estimates.    
View full article
This is a article attached image Marketo offers a number of ways to contact Marketo Support directly for assistance from 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. This is a article attached image   Email to Case Submission Authorized Support Contacts can email their cases to: support@marketo.com Reminder: Cases submitted by email are all submitted with a P3 Priority   Regional Phone Contact Information Marketo does feature the tried and true means of contact support, by the phone.  Authorized Support contacts with any support entitlement of Business level or higher can contact Marketo Support by calling one of the regional phone numbers listed below.   Region Contact Details Observed Holidays North America Hours: M-F, 6am to 6pm Pacific Toll Free US: +1 877 270 6586 Languages Supported: English New Year's Eve and Day Independence Day Thanksgiving Day and the Day After Christmas Eve and Day Europe, Middle East, Africa Hours: M-F, 8am to 5pm GMT Europe: +353 (0)1 511 9556   Languages Supported: English New Year's Eve and Day Easter Monday Christmas Eve and Day St. Stephen's Day Asia Pacific Hours: M-F, 9am to 6pm AET ANZ: +61 2 8031 8188 Language Supported: English New Year's Day Good Friday Easter (following Monday) ANZAC Day Christmas Day Boxing Day Japan Hours: M-F, 9am to 6pm JST JPN: +81 3 6478 6080 Language Supported: Japanese New Year's Day Coming of Age Day National Foundation Day Emperor's Birthday Spring Equinox Showa Day Constitution Memorial Day Greenery Day Children's Day Marine Day Health and Sports Day Respect for the Aged day Fall Equinox Labor Thanksgiving Day
View full article
Once you have submitted a case to Marketo support, we provide a simple way of staying connected to your case and the cases submitted from your company through the Marketo Support Portal. You can access the support portal through your Marketo instance by selecting Community in the top right corner: This is a article attached image You can also access the support portal directly at https://support.marketo.com and login with your Marketo credentials (login and password). This will not work for users with SSO.   Once you are in the support portal you can Create a Case for Marketo Support or you can also review any cases that are open and being worked on by support or review your case history. Navigate to My Case management: This is a article attached image From the My Cases navigation you can access the following case views: This is a article attached image My Recent Cases* - Cases that you have opened in the past 30 days All Company Recent Cases* - Cases that any authorized support contact has opened in the past 30 days My Open Cases – Cases created by you that are being triaged by Support and pending Support’s response and are more than 30 days old My Closed Cases – Cases that were created by you and are now closed My Awaiting Fix Cases – Cases that were created by you where Marketo is developing a fix which will be implemented at a later date All Company Closed Cases – Cases that were created by you or your colleagues that are now closed All Company Open Cases - All open cases submitted for the account Company Awaiting Fix Cases – Cases that were created by you or your colleagues where Marketo is developing a fix which will be implemented at a later date Management Escalations - Escalations opened by you or your colleagues  Survey Cases - Surveys that are available for you to fill out after a case is closed *Cases that have been opened for more than 30 days will move from Recent cases to Open cases   To view specific case details, click a case number. This is a article attached image From the Case Details, you can perform the following: Close your Case - Select the "My Case is Resolved" button to close your case Add Comments - Provide additional comments to support or respond to a Support question Add Attachment - Provide any screenshots or documents that will help illustrate the issue you are reporting   If your case has been closed there are two options available to you.   Reopen - You can reopen your case if you are not satisfied with the case resolution by adding a comment in the case. Case Survey - Once your case has closed, please consider offering feedback on the level of Support you received.
View full article
Issue Issue Description There are two email bounce filters, "Email Bounces" and "Email Bounces Soft" and they both appear to function the same.   Solution Issue Resolution There are two email bounce filters: Email Bounces and Email Bounces Soft The Email Bounces filter only references leads that have had hard bounces occur. The bounce codes associated with hard bounces are 1 and 2. The Email Bounces Soft filter only references leads that have had soft bounces occur. The bounce codes associated with hard bounces are 3, 4, and 9. More can be read on bounce codes here.  Maintaining a Directory of Leads Bouncing Emails  
View full article
Questions? Ask Support! Securing your Adobe Marketo Engage Landing Pages By default, Marketo Engage serves domains as HTTP, and historically we’ve given our customers the choice of whether or not to secure their Marketo Engage domains (HTTPS); however, in 2018, browsers enforced new security measures to better protect their users - one of which was to flag all non-secure (HTTP) web pages with a visible "Not Secure" warning (the unlocked pad lock icon in the address bar). This effectively shifted the choice of using secured (HTTPS) domains from a best practice to a requirement. Marketo Engage's Secured Domains solution secures any and all domains defined in your instance so they will be served via HTTPS.  For a full explanation of the benefits Secured Domains provides, in contrast with a basic SSL certificate, please see this Nation Post.   NOTE: As of late 2019, Marketo Engage changed it's pricing/packaging to now automatically include a base Secured Domains package with ALL subscriptions. This base offering secures the first landing page domain and first tracking link domain to provide all of our customers with the basic necessities of digital marketing. Should you use more than these two domains, they may be purchased a la carte, so customers only pay for what they need. Contact your Marketo Engage Customer Success Manager to purchase additional Secured Domains or discuss further.   Identifying Landing Page Domains in Your Instance Please note the below only covers securing your Landing Page domains. For steps on how to secure your Tracking Link domains, please visit this Nation Post.   New Subscriptions: If you’re a new Marketo Engage 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 provisioning process through Support.   Established Subscriptions: Have you had your Marketo Engage subscription for a while and want to know how many landing page domains you have configured in your instance? If you’re a Marketo Engage Admin, you can see your landing pages domain name and domain aliases by navigating to: Admin console > Integration > Landing Pages   On the Landing Pages tab, you’ll see your landing pages Domain Name. In the example www.info.mycompany.com, the first part of the URL (info.) is your CNAME and the second part (mycompany.com) is the top-level domain (TLD). Marketo charges per unique top-level domain - i.e. only the orange part.   Next, you’ll also need to check the Rules tab and look for Domain Aliases.   It’s important to note that when it comes to securing your Marketo Engage 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.   The Secured Domains Provisioning Process The process to secure your landing page domains includes steps that must be completed on Marketo Engage’s side as well as steps that you’ll need to complete in your instance prior to us enabling HTTPS.   First, you'll need to configure your domains, choose a CNAME, and point it to your unique Marketo domain (i.e. prefix.mktoweb.com). These first-time-setup instructions can be found here.   Then, you'll need to contact Marketo Support to complete the process. NOTE: Domains are NOT automatically secured once they're configured in your instance - you MUST contact Support for any domain changes!   On our side, we’ll first provision your prefix.mktoweb.com domain on Cloudflare servers, then complete the secure handshake validation between DigiCert and Cloudflare to provision the necessary SSL certificates to serve your landing pages over HTTPS.   On your side, to ready your instance for the conversion to HTTPS, you’ll need to review, update and re-approve your landing pages: 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? If you include a Marketo Engage 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 Engage Form on a non-Marketo Engage 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 cut-over to HTTPS with Marketo. You’ll need let Marketo Engage Support know that you’re ready to initiate the cut-over process.   NOTE: To help ensure a smooth transition, please confirm with your IT team that they have NOT placed a CAA against DigiCert on your top-level domain (this grants permission to only specific vendors to issue SSL certificates to your domain). 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 cut-over, you may notice that images are not displayed in the Marketo Engage 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 Engage, 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.      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 cut-over 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 Cloudflare has blocked my domain from being secured by Marketo Engage. What does this mean and how do I resolve it? Cloudflare takes security steps on their SSL for SaaS v2 platform used by Adobe Marketo Engage to ensure domains belonging to the internet's most popular brands and websites are not issued SSL certificates without explicit permission from it's owner. Cloudflare pulls from the list of the top 1 million domains on the internet from Tranco to determine which domains it will block from securing without consent.   Adobe does not control the content of this list and cannot make changes to add or remove your domain. If your domain is on this list, Customer Support may report that your domain is unable to be secured without taking extra steps. Your business may either: Request a certificate from LetsEncrypt instead of Digicert. LetsEncrypt offered certificates do not have the same restrictions. Submit a Letter of Authorization with your request to Customer Support. This must be a signed letter on company letterhead confirming that your company authorizes Adobe Marketo Engage to secure your requested subdomains. Do I need to provide a TLS/SSL Certificate? No, in fact, to avoid the unnecessary hassle, risk and fire drills caused by expired certificates, Marketo Engage now only accepts customer-provided certificates on an exception-only basis. The certificates included with Secured Domains auto-renew annually without any human interaction on either side.   What Certificate Authority (CA) issues the certificates for the Marketo Engage’s Secured Domains? 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? Absolutely NOT! That's like sharing the same car lock with other people - avoid dealing with vendors who offer this service. Each of your domains will get its own certificate, meaning you will not be on a shared certificate with other companies.   Will all the subdomains be covered? Marketo Engage defines a subdomain interchangeably with CNAME for billing purposes. As an example, with your company.com domains, the subdomains go.company.com, info.company.com, help.company.com etc. would could as 3 unique subdomains. Please keep in mind that company.com, company.com.uk, company.com.ca are separate top-level domains.   Can I choose which domains/subdomains to secure? Securing your domains is all-or-nothing, meaning the process automatically secures all domains/subdomains you've set up in your instance. If you do not use or need old domains lingering in your instance, be sure to delete them so you're not charged.   If I have a CAA record, can it affect my certificate issuance? Yes, CAA records MUST be configured to allow DigiCert issuance, or else we will be restricted from issuing one. Please check with your IT team to ensure this is not a blocker. Further information: https://www.digicert.com/dns-caa-rr-check.htm   Can I provide my own SSL certificate to secure my domains? Not unless they are the Extended Validation (EV) certificate type. If not, but your IT team has instructed you they must manage them, please reach out to your CSM with the business use case and any details to request an exception. Please note this only causes additional risk, hassle, time, and effort on all parties.   We require an Extended Validation (EV) certificate. Can the Secured Domains for Landing Pages product accommodate this? Since the certificate provided with Secured Domains is not an Extended Validation (EV) type, Marketo Engage absolutely allows customers who require this (typically healthcare, finance, government) to procure the EV certificate/private key and provide this to Marketo Engage Support; however, please note you will then be 100% liable for managing/renewing/sending Marketo Engage the new certificate with ample time to install it to avoid expiration. Expired certificates will not be categorized as a P1.   What Marketo Engage configuration is required to complete the Secured Domains 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 many domains can I secure? Technically, as many as you like. However, please note there is an additional cost associated with secured multiple domains beyond the first two covered by the base offering.   If I am using Domain Aliases in my Marketo Engage subscription, do I have to secure each of these? Securing your Marketo Engage landing pages requires you to secure all domains used in your instance including your Domain Aliases.   How do I see the Landing Page domains in my instance? Marketo Engage 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 top-level domains – only the orange part here: www.info.mycompany.com Are Domain Aliases for different countries counted separately? When counting domains, you might have the same CNAME but unique top-level domains: info.mydomain.com, info.mydomain.au, info.mydomain.de. Even though the CNAME is the same, the top-level domains (mydomain.com, mydomain.au and mydomain.de) are unique and thus counted as such (3 total domains). Vice-versa, unique CNAMEs (info., go., pages.) with the same top-level domain (mycompany.com) are considered subdomains of a single top-level domain.    Will URLs to the existing non-secure (HTTP) Marketo Engage 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 Engage 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 Engage landing pages also secure my corporate website? No. Marketo Engage Secured Domains only affects the landing pages served by Marketo, because the underlying domain is technically a Marketo Engage domain (i.e. your CNAME 'points' to prefix.mktoweb.com). It does not affect any pages on your corporate (non-Marketo) website.   If I don’t use Marketo Engage Landing Pages, do I need Secured Domains for Landing Pages? Most likely, as there are many aspects of Marketo Engage that rely on your domains being secured, such as assets and images. Further, if you are embedding Marketo Forms on secured non-Marketo Engage webpages, the default form code snippet that Marketo provides uses //[munchkinID].mktoweb.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 Engage 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.    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 Engage when adding additional domains/domain aliases. Please contact your Marketo Engage Customer Success Manager. There is an additional a la carte charge depending on the number of domains you are adding.   Do I need to secure my tracking links as well? If your company enforces HSTS (a web directive that denies any redirects from HTTP links), you WILL need to also secure your Tracking Links for your recipients' email->landing page functions correctly. For more information on HSTS and Marketo subdomains, please see the following documentation SSL: The HSTS Policy and Your Marketo Subdomains If not, Marketo still recommends using secured links as a best practice, as it can help with deliverability and avoid spam traps; plus, it looks far more professional to have secured links, and can foster brand confidence when your recipients know their email->web page redirect is fully secure.   For additional questions on anything technical, just ask the Marketo Support team! If it's a pricing or commercial question, please reach out to your Customer Success Manager.
View full article
  Overview SSO Authentication Updating SSO Credentials Tips SSO Only Login Wait to disable the existing certificate Overview Marketo’s Single Sign On (SSO) feature allows your company to use your own company’s SSO service to authenticate your login into your Marketo instance. Your initial setup of the SSO is covered in the documentation here.   You may need to change your SSO authentication settings after the initial setup. This document will show you the process on how to do so.     SSO Authentication The Identity Provider (IdP) you use will provide you with your SSO authentication credentials and security certificate. Marketo uses this information to validate your login from your IdP, so these credentials come from your IdP.     Updating SSO Credentials Once you have retrieved the new security certificate, you can enter it into Marketo.   1. Under Admin click on Single Sign-On. 2. Select Edit in the SAML Settings 3. Enter your Issuer ID, Entity ID, select the User ID Location and click Browse. 4. Select your Identity Provider Certificate file. 5. Click Save. Tips There are a couple things to watch out for when changing your SSO certificate. Here’s a couple tips to avoid trouble along the way.     SSO Only Login If your company uses SSO for login, you’ll have an optional setting to restrict login access to your Marketo instance to SSO logins only. This prevents users from logging in directly, forcing the use of SSO.   You can check for this setting under Admin > Login Settings   These settings do allow the creation of a special User Role that can bypass the SSO restriction. However, sometimes as people come and go within the company, the users enabled with that User Role could no longer be available.   TIP: Before changing your SSO certificate, create a new user utilizing this User Role that bypasses the SSO requirement. If something goes wrong while setting up the new certificate, you’ll be glad you have a back door into the Marketo instance!   Wait to disable the existing certificate Your IdP will issue a new certificate, but what if something goes wrong while entering the new information into Marketo?   TIP: Get the new certificate and set it up in Marketo before you fully disable the existing certificate within your IdP on their side. If something happens to the new certificate, you’ll be glad you have the do-over available and can switch back to the existing certificate that still works!
View full article
Issue How to use the REST API to check for deleted leads. Solution You would need to use the specific endpoint This will pull a list of leads deleted within a specific timeframe.  Deletions older than 14 days may be pruned.      
View full article
Issue Will custom settings, such as Launchpoint integrations, API configurations and SFDC sync settings, remain in place when doing an instance copy, or will they be overwritten?     Environment Non-Microsoft Dynamics integrated Instance Solution All permanent configuration settings which can be done to a Marketo instance are reset to the default values or settings in the destination instance. Everything is copied except for the below list: Lead Database and activity history are not copied CRM configuration is reset on the destination instance. Users are not copied. CRM Field Mappings are removed in the destination instance except for standard mappings, and must be set during the Field Mapping Stage of CRM sync initialization. RCA information is not copied. Program subscriptions are not copied. Campaign History is not Copied. CNAMES for Email links and LPs are not copied. All Account-string based properties are modified accordingly. Munchkin ID of the destination instance is preserved. Sales Insight Admin Configuration is Reset. Outlook licenses are not copied. All pre-existing data on the destination instance will be destroyed. Asset IDs for emails, landing pages, and programs will match Launchpoint and API integrations are not copied   If data may exist on the destination instance prior to the copy process, this may require that you work with your Success Manager to obtain a replacement instance for the copy to be completed. NOTE* This process is not applicable to customers utilizing the native Microsoft Dynamics integration.
View full article
Issue After going through a modification of a text field type from 'Text' to 'String', the field is no longer available as a filter for smartlists. Don't worry, the field is not gone - it is just temporarly unavailable. Solution Changing the field type from one type to another is a database intensive operation and in some cases where the field values are widely populated across your database records, this can cause the filter to be unavailable until the operation is completed in full. The time it takes for the field filter to become available may vary and it can take up to ~30 hours sometimes until the field filter is available again after the type of the field has been changed.  
View full article
Marketo Support's Mission is: To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success.   Areas of Responsibility: Technical Support Engineers (TSEs) are your initial point of contact for any technical questions or concerns. TSEs are responsible for troubleshooting issues within your Marketo instance and common include:   My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community   Our TSEs are not web developers and as a result they are unable to troubleshoot most types of custom coding (ie. HTML, JavaScript, XML, etc.). Our support team is able to help with the following types of non-custom code:    Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API   Our TSEs are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience.   Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented.   Response Time   Our TSEs are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services.  We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to Service Level Targets.
View full article
Applies to: Email Performance Report, Email Link Performance Report, Engagement Stream Performance Report, Landing Page Performance Report, Program Performance Report, Sales Insight Performance Report When you create a report in the Analytics area, by default the report will only show reporting for the current workspace. This is a article attached image Once the report is created, under the Setup tab, you can add filters to filter by asset. For example, Filter Assets in an Email Report. If you filter for the workspace, it will show reporting for all assets in the workspace, similar to the default view without a filter: This is a article attached image To add reporting across all workspaces, use Enable Global Reporting in the report settings within the Setup tab. Note: Global Reporting is only available in your instance's default workspace.
View full article
  Note: This document applies to the Marketo Secured Domains for Tracking Links product only.   Every link you include in your Marketo emails will have tracking code automatically appended when sent. For those in highly regulated industries, your company may require that you securely encrypt the Marketo tracking links. Remember that Marketo takes the URLs you place inside of emails and shortens them using the "Branded Tracking Link" domain (this is another CNAME you set up in Marketo under Admin--> Email). These tracking links are how Marketo enables you to track engagement with your emails.   Setting Up Secured Domains for Tracking Links instructions - Setting Up Secured Domains for Tracking Links   Do I need to secure my Tracking Links? If your company (likely IT) has implemented HSTS, you WILL need to secure your tracking links for your recipients' email->web page redirect to function correctly. Additional information on HSTS, including how to check if it's been implemented on your domain can be found here: SSL: The HSTS Policy and Your Marketo Subdomains.   HSTS is a web server directive companies may choose to enforce which forces all subsequent requests for resources on that domain to be loaded through HTTPS. This is most common for those in highly regulated industries, such as financial and healthcare institutions. Please note, enforcing HSTS does not also convert Marketo tracking links in emails to HTTPS - that must be done via Marketo Support.   Other Helpful FAQs What is Marketo Secured Domains for Tracking Links? This secures the tracking link domains (which is what makes the URLs appear as HTTPS instead of HTTP) by providing the SSL certificate for each unique domain. Please note tracking links are NOT the same as your SPF/DKIM domain, which is the domain from which your emails are sent., whereas this is the domain located within your emails that tracks click-throughs.   How many domains can I secure with the Secured Domains for Tracking Links? Technically, there is no limit to the number of tracking link domains a customer may have. The base Secured Domains offering included on all subscriptions covers the cost to secure your first tracking link domain; however, if you need more, you may simply add additional domains to your contract a la carte, so you only pay for what you need (in contrast to the previous bundled offering). Contact your Marketo Customer Success Manager for more information.   How is the Secured Domains for Tracking Links product different than the Secured Page Services, SSL for Tracking Links service? Unlike the legacy SSL-only service, Secured Domains not only generates and auto-renews all certificates needed for securing your domains, but provides an exponential layer to what 'secured' entails - it's not just an SSL certificate anymore. For a full explanation of Marketo's Secured Domains offering, and how it differs from just the SSL certificate, please see this Nation Post or check out this Marketo Blog Post about cyber-security and marketing.   What setup/configuration is required before securing my Marketo Tracking Links? You must configure (brand) your CNAMES for Email Tracking links. More information here: Brand Your Tracking Links   Can I secure my tracking links without securing my Marketo landing pages? Technically? Sure. But while secured tracking links have yet to be enforced by email clients, secured landing pages have been enforced by browsers since 2018, which is why we include both in our base bundle. The general public is far more likely to not stick around or enter personal data on an unsecured landing page than they are to not click an unsecured tracking link.   Do I need to provide a TLS/SSL Certificate? No. Secured Domains moves 100% of the SSL ownership to Marketo - all aspects of procuring, managing and renewing certificates is done automatically without human interaction. In fact, we only allow customer-provided certificates on an exception-only basis, OR if you require an Extended Validation (EV) type certificate.   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? As part of our Secured Domains products, each of your fully qualified domain names will get its own certificate. That means you will not be on a shared certificate with other companies.   Can I provide my own SSL certificate(s) to secure my domains? Not unless it's an Extended Validation (EV) type certificate. Marketo can only automatically renew the certificates we generate to secure your domains.   Are security headers applied to my tracking link domain? Security headers are applied to tracked links in emails that are sent to your leads. The tracking link domain itself (e.g. https://click.example.com) will not return all security headers. The subdomain itself does not host content and is not intended to be browsed. Marketo Support will not respond to security scans performed on the tracking link domain itself.
View full article
The Google Apps antispam system uses a unique means of allowlisting. Customers on shared IPs should allowlist Marketo's entire sending ranges, because we sometimes need to move customers between IPs for technical reasons. The way to allowlist a range in Google Apps is to configure a manual IP block with a pass through.   G Suite enables you to specify an IP address or range of addresses within a domain, and allow messages from those addresses only. This feature is sometimes referred to as IP lock. In G Suite, you set up this feature in the Content compliance setting. IP lock is a method that readily enables an administrator to simultaneously whitelist all incoming traffic from a particular domain while equally preventing spoofing by manually defining the allowed IP ranges. The following instructions are particularly useful with domains that do not have an SPF record and/or use third party applications to legitimately spoof their address. Setting up IP lock with the Content compliance setting includes three separate procedures: Adding the domain, defining the allowed IP range, and setting the correct disposition and NDR.   See this page of Google documentation for more information: Enforce 'IP lock' in G Suite - G Suite Administrator Help Instead of using a CIDR range, this interface asks for the first and last IPs in the given range. Here are ours:   199.15.212.0 - 199.15.212.255 199.15.213.0 - 199.15.213.255 199.15.214.0 - 199.15.214.255 199.15.215.0 - 199.15.215.255 192.28.146.0 - 192.28.146.255 192.28.147.0 - 192.28.147.255 94.236.119.0 - 94.236.119.63 185.28.196.0 - 185.28.196.255 103.237.104.0 - 103.237.104.255 103.237.105.0 - 103.237.105.255 130.248.172.0 - 130.248.172.255 130.248.173.0 - 130.248.173.255   Is this article helpful ? YesNo
View full article
Issue After declaring a champion for your Champion/Challenger test, you notice that the test (ex: "Whole Emails" test) in the Marketing Activities asset tree under your Email Asset is missing.   Root Cause When you declare a champion, you select a Declare Date. Once this date/time is reached, only the new champion will be sent. After the test is over, it is expected behavior that the test (ex: "Whole Emails" test) will no longer be shown in the tree. This is because the test is no longer active. If you would like to retain your test data, it is recommended that you save this outside of Marketo.
View full article
Issue You are seeing a discrepancy in email activities (Sent, Delivered, Open, etc.) when comparing the RCE Email Analysis report and Email Performance Report, when looking at the same email and date range.   Root Cause Here are some of the most common reasons for a discrepancy between the RCE and Email Performance Report (EPR): Deleted/Merged Leads: If you have leads that received emails and then were deleted or merged in Marketo, their individual email activities will be included in EPR. RCE will not count deleted or loser leads from a merge Re-sent Emails: If you re-send the same email to the same lead using the same smart campaign, EPR will only show the 1st send occurrence. RCE will show all email activities for a lead. Delivered & Soft Bounce: There are situations where a lead will log a Delivered activity and then shortly after, a Soft Bounce activity. In these situations, EPR will show this lead as a Soft Bounce count, whereas RCE will show this lead as a Delivered count. If you are still seeing a discrepancy between the reports that cannot be explained with the above, reach out to Marketo Support to help advise.
View full article
To enumerate and request all Design studio files programmatically, Marketo offers a REST API endpoint.   Please refer to our official documentation here: https://developers.marketo.com/rest-api/assets/files/#browse
View full article
On September 30th, 2021 we sunset our Sales Navigator integration with Adobe Marketo Engage Sales Connect. When we first built this integration, we aimed to deliver key insights to sellers that allowed them to identify the right customers to engage with. This continues to be our goal as we invest in Marketo Engage Sales Connect and deliver future innovations to drive value to both our marketing and sales users. The sunset is in part due to the planned deprecation of LinkedIn’s Company and Profile API’s which we currently use to support the integration. LinkedIn has decided to no longer support these API’s and has not provided any replacement. There will be no action required on your part and you can expect to see the tab removed in September 2021. Kind regards,   Adobe 
View full article