Knowledgebase

Sort by:
Adobe Marketo offers a number of ways to contact Marketo Support directly for assistance from our different support regions. Further details about your Adobe Success Plan can be found HERE. Note: If your Marketo Instance and Users have been migrated to Admin Console, refer to this Admin Console Overview page for managing the Adobe entitlements across your organization and to engage Marketo Support.   Marketo Support Portal (https://support.marketo.com)   The Marketo Support Portal features a web form to submit support cases to Marketo Support. The form provides 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. We encourage you to leverage our Best Practices when submitting your case to Marketo Support.   Support Services – Regions, Hours, and Languages Authorized Support contacts can engage Marketo Support by calling one of our Adobe Enterprise Phone Numbers for your region. Live Telephone and Online Technical Support Priority 1 incidents: 24x7x365 via phone or online support case Priority 2-4 incidents: Support available during regional business hours via chat or online support case. Regional Business Hours Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents. If Adobe is contacted for support by someone other than the designated Named Support Contacts, Adobe may request that that the support case be resubmitted by a Named Support Contact. Languages Japanese language support is available during Japanese regional business hours, excluding holidays or Adobe days off. Japanese support is not available for Adobe Commerce. With the above exception, all Support will only be provided in English. Support Access Customer will grant Adobe Support access to applicable customer systems via remote support tools controlled by Adobe for the purpose of troubleshooting and support services. Regional Business Hours for Support Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents.   Americas Europe, Middle East & Africa Asia Pacific Japan 6 am – 5:30 pm 9 am – 5 pm 9 am – 5 pm 9 am – 5 pm  
View full article
  Welcome to Marketo Support This guide provides individual links that covers the following topics: Marketo Support Policies Service Level Agreement How to Contact Marketo Support How to Submit a Case Tips on Effective Case Submission Managing Authorized Support Contacts (Support Admins) Managing Your Cases How to Escalate    
View full article
  What is a Blocklist? Can I Still Send My Emails, or Are You Blocking Me from Sending? What Is a Spamtrap and Why Do They Matter? Can You Give Me the Spam Trap Address That Triggered the Blocklist So I Can Remove It from My Database? Can You Give Me More Information regarding the Blocklist Issue? What Is the Quarantined IP Range? I Sent This Email Campaign a While Ago. Why Am I Only Getting Notification of the Blocklist Issue Now, and Am I Still Blocklisted? The Blocklist Notification Went to the Wrong Email Address. Why Was It Sent to That Address? Which blocklists should I be concerned about? - Top Blocklists – What You Need to Know How do blocklist issues get resolved? What steps do I need to take to resolve the blacklist issue? - Blocklist Remediation      
View full article
Setting an email to "operational" does the following No unsubscribe link automatically added Email will be sent to leads set to Unsubscribed Email will be sent to leads set to Marketing Suspended   Note - when sending an operational message, Unsubscribed and Marketing Suspended leads will still be included in the "blocked from email" count on the schedule tab of the campaign.   When is it OK to use the operational setting?   Sending marketing email to unsubscribed addresses is illegal. For this reason, you should be extremely careful to only use this setting in extremely limited circumstances. Using this setting incorrectly violates Marketo's Terms of Service, and most antispam laws. There may be legal consequences for using this setting incorrectly. Good uses of the operational setting fall into two categories: Transactional messages Relationship messages   What's a transactional message? A transactional message is part of a transaction that a lead has initiated and you are responding to. Here's some examples of transactional messages: Receipts for purchases Registration confirmations Download links in response to form fill-outs Requested assets (whitepapers, spec sheets, etc.)   What's a relationship message? A relationship message describes something that affects your business relationship with the lead. Here's some examples of relationship messages: Downtime notifications Changes to terms of service Recall notices End of service notifications   Operational messages should not contain any marketing content at all. In other words, do not use the operational setting to send a message that contains a receipt and a promotion, only a receipt.
View full article
If you have submitted a support case and you feel that the case was improperly handled or that the solution being offered does not meet the communicated Marketo support expectations, then we would welcome the opportunity to look deeper at your specific support engagement and work with you on delivering a better resolution. Caution: If the item you're looking to escalate is related to a Production Down incident, please call the support line for your region to receive immediate assistance. Support Manager escalations are only handled during normal business hours. The phone numbers for each region are listed below, follow the prompts for P1: Americas: +1.877.270.6586, Direct: +1.650.376.2303 Europe, Middle East, & Africa: +353 (0)1 242 3030,  UK: 0800 151 3030 Asia Pacific: +61 2 8031 8188 Japan: +81.03.4233.9014 How to Escalate: Step 1. Navigate to the "Case Management" area of the support portal either by mousing over the Support tab and selecting "Case Management" or clicking the Support tab and click on the “My Case Management” button. NOTE: You will need an open or recently closed case in order to escalate to support leadership. This is a article attached image   Step 2. From here you will need to click on either an open or a recently closed* case:   This is a article attached image   *Support Cases that have been closed for longer than 10 days are no longer eligible to be re-opened and we ask that you open a new support ticket for your current issue prior to escalating to a Support Manager. We ask that you have an open support ticket for a Support Manager to be able to address specific issues. Step 3. After selecting a case, click on the Escalate to Manager button:   This is a article attached image     Step 4. A pop up will display and you will need to the purpose for the escalation and click on the “Escalate” button.   This is a article attached image   Once your support escalation case has been submitted a Marketo Support Leader will contact you within 1 business day of your support region's support hours to address the issue.
View full article
Double opt-in is the gold standard of email permission. Also known as confirmed opt-in or COI, this practice is where a person fills out an opt-in form and is then sent an email and must click a confirmation message before they are added to the mailing list. Here are some great reasons to use double opt-in: Protects against typos and bots Protects against spamtraps Reduces bounce rates, improves deliverability Required in some regions Increases engagement rates   If you'd like to set up double opt-in with Marketo you can do this with the use of the Marketing Suspended function. Marketing Suspended is a status that is functionally equivalent to Unsubscribe - Marketo will not send these leads marketing emails, but will send them operational emails. You'll need an opt-in form and a pair of trigger campaigns. First, set up a trigger campaign such that, when the form is filled out, the flow has a Change Data Value to mark the lead as Marketing Suspended, and then a Send Email step to send an operational email that you will use to confirm their request to join your mailing list. Your confirmation email should be short and to the point, and make sure to set it as an operational email. We recommend that it is clearly branded, use a simple subject line such as "Confirm Your Request to Join Our Mailing List" or similar, and include a link within to a simple confirmation landing page. Set a second trigger campaign such that whenever someone clicks the confirmation link to the confirmation landing page, the flow will change data value Marketing Suspended new value is false. A follow up flow should be set up that if the recipient doesn't activate the link in the confirmation email the address is either deleted or set to Blacklist within the database after a reasonable timeframe, usually 2 weeks.  The Blacklist status will ensure that no email is set to that lead until they have completed the subscription process. This prevents future operational emails from being sent to this email address unintentionally. That's it!  Now, when someone fills out your opt-in form, they will be set to Marketing Suspended until they click the confirmation link in your operational confirmation email. You'll be well on your way to increasing the quality of leads on your mailing list by implementing this simple process.
View full article
Note: Once you have migrated to Admin Console, you can manage your support cases through the feature provided in the Admin Console Platform. To learn more, visit: https://experienceleague.adobe.com/docs/customer-one/using/home.html. 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 Clearing cache and cookies in your browser will fix a number of different problems related to page display, browser errors, and login issues.     Solution Here are links to the support articles on how to clear cache and cookies for the most commonly used browsers. Chrome Clear cache and cookies - Computer - Google Account Help   FireFox How to clear the Firefox cache | Firefox Help   Internet Explorer https://support.microsoft.com/en-us/help/278835/how-to-delete-cookie-files-in-internet-explorer   Microsoft Edge Microsoft Edge, browsing data, and privacy – Microsoft privacy    
View full article
Issue If your IT department or a client asks for your Marketo dedicated sending IP address in order to whitelist your marketing emails, here is how you can find it.     Solution Your Marketo instance's dedicated IP address can be found by sending yourself a live version of one of your Marketo emails, then checking the message headers for the IP address that it was sent from.  It should also be included in the original documentation that Marketo's deliverability team would have provided you when the dedicated IP was set up.  If you are unable to locate the IP address in the emails, or are unable to find your original documentation, please reach out to Marketo Support and we can look it up for you.   Who This Solution Applies To Customers with a dedicated sending IP
View full article
Issue You see a record in the database has something similar to the following Email Suspended Cause: "554- Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means." Solution The 554 error is generated by a hard bounce due to a spam block. It is possible that one of the sending IP addresses used may have been on a temporary blacklist the day of the attempted send. This happens while using shared IPs when another Marketo instance using the same IP hits a spam trap, putting the IP on a blacklist for 24 hours. This error can also happen to users on a dedicated IP if they hit a spam trap with one of their email sends.        
View full article
  Syntax Recommendations Common Look Up mechanisms Common Modifiers Too Many Mechanisms Character String Too Long Null Records in the SPF Record Repetitive Records in the SPF Record - Void Lookups Validation Tools Syntax Recommendations Common Look Up mechanisms a: mx: include: ip4: ip6: exists: ptr: all Common Modifiers redirect= exp=   An A Record must ALWAYS contain IP address (map host to IP) CNAME (Alias) must contain hostnames. No IPs here NS an MX records must contain host names. No IPs allowed. MX records (for mail servers)  should contain hostnames NOT IPs. Too Many Mechanisms Section 10.1, "Processing Limits" of the SPF RFC 4408 specifies the following in regards to DNS lookups: SPF implementations MUST limit the number of mechanisms and modifiers that do DNS lookups to at most 10 per SPF check, including any lookups caused by the use of the "include" mechanism or the "redirect" modifier.  If this number is exceeded during a check, a PermError MUST be returned.  The "include", "a", "mx", "ptr", and "exists" mechanisms as well as the "redirect" modifier do count against this limit.  The "all", "ip4", and "ip6" mechanisms do not require DNS lookups and therefore do not count against this limit. The "exp" modifier does not count against this limit because the DNS lookup to fetch the explanation string occurs after the SPF record has been evaluated. This limit is in place to prevent SPF lookups from being a useful avenue for Denial of Service attacks. Using an example SPF record as an example to illustrate, this record was breaking with 12 look-ups: example.com text = "v=spf1 include:_spf-a.example.com include:_spf-b.example.com include:_spf-c.example.com include:_spf-ssg-a.example.com include:spf-a.anotherexample.com ip4:131.107.115.215 ip4:131.107.115.214 ip4:205.248.106.64 ip4:205.248.106.30 ip4:205.248.106.32 ~all" [ 5 mechanisms] _spf-a.example.com  text = "v=spf1 ip4:216.99.5.67 ip4:216.99.5.68 ip4:202.177.148.100 ip4:203.122.32.250 ip4:202.177.148.110 ip4:213.199.128.139 ip4:213.199.128.145 ip4:207.46.50.72 ip4:207.46.50.82 a:mh.example.m0.net ~all"  [ +1 = 6 mechanisms] mh.example.m0.net a = 209.11.164.116 _spf-b.example.com text = "v=spf1 include:spf.messaging.example.com ip4:207.46.22.35 ip4:207.46.22.98 ip4:207.46.22.101 ip4:131.107.1.27 ip4:131.107.1.17 ip4:131.107.65.22 ip4:131.107.65.131 ip4:131.107.1.101 ip4:131.107.1.102 ip4:217.77.141.52 ip4:217.77.141.59 ~all" [+1 = 7 mechanisms] spf.messaging.example.com text = "v=spf1 include:spfa.anotherexample.com include:spfb.anotherexaple.com include:spfc.anotherexample.com -all"  [+3 = 10 mechanisms] spfa.anotherexample.com  text = "v=spf1 ip4:157.55.116.128/26 ip4:157.55.133.0/24 ip4:157.55.158.0/23 ip4:157.55.234.0/24 ip4:157.56.112.0/24 ip4:157.56.116.0/25 ip4:157.56.120.0/25 ip4:207.46.100.0/24 ip4:207.46.108.0/25 ip4:207.46.163.0/24 ip4:134.170.140.0/24 ip4:157.56.110.0/23 -all" [+0 = 10 mechanisms] spfb.anotherexample.com  text = "v=spf1 ip4:207.46.51.64/26 ip4:213.199.154.0/24 ip4:213.199.180.128/26 ip4:216.32.180.0/23 ip4:64.4.22.64/26 ip4:65.55.83.128/27 ip4:65.55.169.0/24 ip4:65.55.88.0/24 ip4:94.245.120.64/26 ip4:131.107.0.0/16 ip4:157.56.73.0/24 ip4:134.170.132.0/24 -all" [+0 = 10 mechanisms] spfc.anotherexample.com  text = "v=spf1 ip4:207.46.101.128/26 ip6:2a01:111:f400:7c00::/54 ip6:2a01:111:f400:fc00::/54 ip4:157.56.87.192/26 ip4:157.55.40.32/27 ip4:157.56.123.0/27 ip4:157.56.91.0/27 ip4:157.55.206.0/24 ip4:157.55.207.0/24 ip4:157.56.206.0/23 ip4:157.56.208.0/22 -all" [ +0 = 10 mechanisms] _spf-c.example.com  text = "v=spf1 ip4:203.32.4.25 ip4:213.199.138.181 ip4:213.199.138.191 ip4:207.46.52.71 ip4:207.46.52.79 ip4:131.107.1.18 ip4:131.107.1.19 ip4:131.107.1.20 ip4:131.107.1.48 ip4:131.107.1.56 ip4:86.61.88.25 ip4:131.107.1.44 ip4:131.107.1.37 ~all" [+0 = 10 mechanisms] _spf-ssg-a.example.com  text = "v=spf1 include:_spf-ssg-b.example.com include:_spf-ssg-c.example.com ~all"  [+2 = 12 mechanisms] _spf-ssg-b.example.com  text = "v=spf1 ip4:207.68.169.173/30 ip4:207.68.176.1/26 ip4:207.46.132.129/27 ip4:207.68.176.97/27 ip4:65.55.238.129/26 ip4:207.46.222.193/26 ip4:207.46.116.135/29 ip4:65.55.178.129/27 ip4:213.199.161.129/27 ip4:65.55.33.70/28 ~all"  [+0 = 12 mechanisms] _spf-ssg-c.example.com text = "v=spf1 ip4:65.54.121.123/29 ip4:65.55.81.53/28 ip4:65.55.234.192/26 ip4:207.46.200.0/27 ip4:65.55.52.224/27 ip4:94.245.112.10/31 ip4:94.245.112.0/27 ip4:111.221.26.0/27 ip4:207.46.50.221/26 ip4:207.46.50.224 ~all" [+0 = 12 mechanisms] spf-a.secondexample.com  text = "v=spf1 ip4:157.55.0.192/26 ip4:157.55.1.128/26 ip4:157.55.2.0/25 ip4:65.54.190.0/24 ip4:65.54.51.64/26 ip4:65.54.61.64/26 ip4:65.55.111.0/24 ip4:65.55.116.0/25 ip4:65.55.34.0/24 ip4:65.55.90.0/24 ip4:65.54.241.0/24 ip4:207.46.117.0/24 ~all" [+0 = 12 mechanisms] Character String Too Long 255 character limitation in a single string https://kb.isc.org/article/AA-00356/0/Can-I-have-a-TXT-or-SPF-record-longer-than-255-characters.html http://www.string-functions.com/length.aspx You may have more than 255 characters of data in a TXT or SPF record, but not more than 255 characters in a single string. If you attempt to create an SPF or TXT record with a long string (>255 characters) in it, BIND will give an error (e.g. "invalid rdata format: ran out of space".)  Strings in SPF and TXT records should be no longer than 255 characters.  However to get around this limitation, per RFC 4408 a TXT or SPF record is allowed to contain multiple strings, which should be concatenated together by the reading application.  In the case of use for SPF (using either TXT or SPF RRs) the strings are concatenated together without spaces as described below.  Reassembly by other applications of multiple strings stored in TXT records might work differently. 3.1.3. Multiple Strings in a Single DNS record As defined in [RFC1035] sections 3.3.14 and 3.3, a single text DNS record (either TXT or SPF RR types) can be composed of more than one string. If a published record contains multiple strings, then the record MUST be treated as if those strings are concatenated together without adding spaces. For example: IN TXT "v=spf1 .... first" "second string..." MUST be treated as equivalent to IN TXT "v=spf1 .... firstsecond string..." SPF or TXT records containing multiple strings are useful in constructing records that would exceed the 255-byte maximum length of a string within a single TXT or SPF RR record. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26  ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all“ text = "v=spf1 ip4:199.15.212.0/22“ " ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24" " ip4:72.32.243.0/24 ip4:94.236.119.0/26" " ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all" Null Records in the SPF Record A record that is NULL or that does not exist will break an SPF record.  Syntax within the record is very important, if there are extra spaces between mechanisms it will count as NULL. EXAMPLE text = "v=spf1 ip4:199.15.212.0/22“ <- accurate text = "v=spf1 ip4: 199.15.212.0/22“ <- NULL (NOTE the space between IP4: and the IP) Repetitive Records in the SPF Record - Void Lookups If there are too many repetitive mechanisms in the SPF record, including records that cascade (for example when using "include:") the record will break. There is a MAX of 2 void look ups in an SPF record.  More than that and the record will break.  This prevents SPF records from being used in Denial of Service style attacks. Validation Tools SPF checker, syntax validator and SPF tester http://www.kitterman.com/spf/validate.html SPF checker http://vamsoft.com/support/tools/spf-policy-tester SPF validator http://vamsoft.com/support/tools/spf-syntax-validator CIDR Calculator http://www.subnet-calculator.com/cidr.php Nslookup http://network-tools.com/nslook/ SPF creation wizard http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/ Common SPF errors http://www.openspf.org/FAQ/Common_mistakes SPF syntax definitions http://www.openspf.org/SPF_Record_Syntax
View full article
  Marketo Champions are customers who have demonstrated outstanding leadership in the Marketo Community, are experts in Marketo products, are avid contributors in the social world, and are loyal advocates of the Marketo brand. Benefits and perks our Champions receive include:   Access: Meetings with our product and marketing teams to give exclusive feedback Previews: Given early previews to products, features, and releases when available Publicity: Exclusive speaking opportunities at our annual Marketo Summit and other events Networking: Special networking events with Marketo executives and fellow Champions and semi-annual conference calls Ownership: Ownership of content and exclusive activities at our annual Marketo Summit that showcase your expertise and thought leadership Credibility: Special Champion badge on Marketo Community profiles, and profiled on Marketo's corporate website Sweet Swag: Champion-exclusive swag To find out more information and apply, click here. To view a complete list of current Champions, click here. Join the Marketo Elite Today!  
View full article
Issue You are experiencing slow processing of campaigns, smart lists, and reports.     Solution There are three key components that can slow down an instance: Number of trigger campaigns: Trigger campaigns are always on, always listening.  If there are 50 campaigns triggering at the same time, all the 50 triggers will be in queue, slowing down your processing and routing inside Marketo. Solution: Reduce the number of Triggers. Convert some of the triggers to batches: Batches also run all the flow steps for every lead at once, instead of serially, which reduces total processing time.   Complexity of smart lists: The more complex a smart list, the harder it is for the system to figure it out, which increases backend processing and even creates campaign failures from timeouts. Solution: Reduce the number of nested smart lists called in a smart list. Whenever you ask Marketo to call another Smart List, it has to wait until all of the other smart lists finish, before putting together the final counts. Instead of Marketo looking for the list and running it, just put the filters in the trigger itself.   Volume of Leads: With regular cleaning and good systems design, it is fairly easy to keep your system running fast. Reduce the number of leads that can flow through with filters. Clean up the inactive leads at regular intervals.    
View full article
*Updated in September 2024     Leads can be auto unsubscribed due to default Feedback Loop setup with the ISPs listed on this page. You can use the following filters to find leads that have clicked the SPAM button in your emails:       Filter 1: Data Value Changed Attribute: Unsubscribe New Value: True Reason: Contains, complaint   (Optional to Specify what Email Domain)   Filter 2: Email Address Email Address: Contains, @domain.
View full article
Issue You receive a DMARC report from an ISP saying that your email failed to pass the SPF alignment check, but when you check your SPF listing in Admin > Email > SPF/DKIM, SPF is verified. Solution The SPF record in Admin > Email > SPF/DKIM  is tied to your FROM domain.  DMARC alignment (using SPF) aligns the domain in the FROM address with the domain in the “return-path” address.  This “return-path” address, usually using a '*.mktomail.com' domain, is generally unseen by recipients and directs email bounces and errors back to Marketo for processing.    Failed DMARC alignment, between these two domains, is what is triggering the failure your DMARC reporting.   DMARC compliance requires EITHER DKIM or SPF compliance, not both in most cases.  This article reviews the two methods available for DMARC alignment - https://nation.marketo.com/docs/DOC-1202-technical-tip-set-up-dmarc-verified-domains-in-a-few-easy-steps Having DKIM DMARC alignment may be enough and you may not need to rely on full SPF DMARC alignment.   In order to set up SPF DMARC alignment, Branded Return-Path will allow you to align the “return-path” domain with your sending FROM address domain.  If you have a dedicated IP on the current pricing plan or are on the Trusted IP range, Marketo can brand your return path at no additional charge.  If you have a legacy Silver Dedicated IP package, or are on the Shared IP range, you can purchase the Branded Return Path as an add-on.   More technical info can be found here: What is DMARC? - https://nation.marketo.com/docs/DOC-1097 https://nation.marketo.com/docs/DOC-5910-branded-envelopefrom-on-shared-or-trusted-ips https://nation.marketo.com/docs/DOC-5951-branded-envelopefrom-on-dedicated-ips
View full article
  This is a article attached image Upon signing a contract with Marketo you are provisioned a Marketo instance and a Support Service. There are four different types of Support Services which are available to meet different customer support needs: Online (Legacy) Business or PREMIER SUPPORT BUSINESS (Legacy) Premier or PREMIER SUPPORT ENTERPRISE (Legacy) Elite or PREMIER SUPPORT ELITE Each Support Service has a different Service Level Target (SLT). An SLT is the amount of time Marketo Support targets to make first contact with you after a support case has been submitted. SLTs differ for each Support Service and priority level. Priority levels range from Priority P1 to Priority P4. Here are the SLTs and priority levels for each Support Service:   Priority Online (Legacy) Business PREMIER SUPPORT BUSINESS (Legacy) Premier PREMIER SUPPORT ENTERPRISE (Legacy) Elite PREMIER SUPPORT ELITE P1 1 hour 1 hour 1 hour 30 minutes 30 minutes 30 minutes 15 minutes P2 4 hours 3 hours 2 hours 2 hours 1 hour 2 hours 30 minutes P3 6 hours 5 hours 4 hours 4 hours 2 hours 2 hours 1 hour P4 3 days 1 day 1 day 1 day 1 day 1 day 1 day   Here are the descriptions for each priority level: Priority Description P1 Mission Critical: Core business function down or potential loss of mission critical data P2 Urgent: Major feature or workflow is not functioning. Mission critical workflow and majority of user community is not blocked P3 Important: Normal usability or task completion is impacted but functional, or workaround is available P4 Minor: Minor issue requiring a correction. Normal workflow is not impacted   Find more information About Support here!  
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
Issue What BCC options are there for email sends? Solution Marketo support can enable BCC on request.  If an email address is to be BCC'd on a batch email send, they'll get 1 BCC for every 1 email Marketo sends. (10k email sends = 10k BCC emails). This can be useful for archiving and compliance purposes, but should not be used for simple campaign confirmation. If you just want to make sure the email went out as scheduled, the easiest way is to create yourself as record in the database, and include yourself in the batch send. Only one BCC address is supported at this time, if multiple BCC recipients are required then it is recommended to create an alias which will forward the messages. This setting is applied to the entire instance, and will affect all emails sends from all Campaigns and Programs while enabled.  Every email sent while this feature is enabled will result in a corresponding BCC email. CAUTION: Dedicated email address setup for the BCC email traffic must be able to handle high volumes of email. Discuss with your IT Team or email service provider to verify their Email Server can handle the estimated volume of incoming email. If the Email Server is not well equipped this feature can cause your Email Server to backlog, become unavailable temporarily, or reject the BCC emails. If the request is for a single email send, we recommend using the following CC process: Email CC | Adobe Marketo Engage  
View full article
Issue You want to set up a DKIM key on one of your domains or subdomains, but another service has a DKIM key already set up on the selector/domain combo.   Solution Beginning October 2023, Marketo has upgraded it's DKIM feature to allow for a Custom Selector for DKIM Keys.  Most Users will be able to utilize the prior default selector, m1, as their DKIM Key.  However, if another integration is already utilizing the m1 selector, a custom value can be used. Common ones seen are "m2", "a1", "mkto", etc. It can be longer, but shorter is generally better   Afterwards, you'll be able to validate DKIM  as detailed in documentation: https://docs.marketo.com/display/public/DOCS/Set+up+a+Custom+DKIM+Signature  
View full article
Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools.   Solution Our system is specific about how you need to access the Support Portal before we can authorize you to use it. The proper steps to take for us to authorize, and for you to submit cases, are as follows:   Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info   Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 Step 2   Step 3 Step 4   If you experience issues, please email marketocares@marketo.com
View full article