Adobe Support fixes problems with the Marketo Engage product itself: outages, defects and questions about how features work. A Marketo support partner works inside your instance: building campaigns, running admin, configuring integrations and advising on strategy. Most teams need both, because Adobe Support won't build your campaigns and a partner can't fix Adobe's platform.
This post compares what each covers, using Adobe's own support documentation, and shows how they work together.
What's the difference between a Marketo support partner and Adobe Support?
Adobe Support is responsible for the software. A partner is responsible for what you do with it. That's the simplest way to split any request.
Think about a broken email send. If sends are stuck across the platform and Adobe's status page shows an incident, that's Adobe's problem. If your email went to the wrong list because a smart list filter was set up badly, that's configuration. A partner or your own admin fixes it.
Adobe Support works on cases you open. It aims to respond within published targets, diagnoses the issue and either fixes the product or explains how a feature should work. It doesn't take ownership of your programs, data model or campaign calendar.
A partner works on your instance under a contract you negotiate. It can own a backlog of builds, keep the CRM sync healthy, design scoring and train your team. Its response times are whatever your contract says, not Adobe's.
What does Adobe Support cover for Marketo Engage?
Adobe Support covers technical issues with the Marketo Engage platform, raised by your named support contacts. Adobe's Marketo support page describes these service hours:
- Priority 1 incidents. Available 24 hours a day, every day of the year, by phone or online case.
- Priority 2 to 4 incidents. Available during regional business hours, by chat or online case.
Some practical rules come with that. Only Named Support Contacts should open cases. Adobe says that if someone else contacts Support, it may ask for the case to be resubmitted by a named contact. Support is provided in English, with Japanese available during Japanese business hours.
Adobe also expects access. Its support terms say the customer grants Adobe Support access to relevant systems through remote support tools that Adobe controls.
Adobe's Marketo documentation names some tasks Support helps with directly. These include setting up a custom Salesforce sync filter, and advising on whether workspaces suit your setup. On subscriptions using the Adobe Identity Management System (IMS), Adobe tells customers to open a Support ticket to implement Single Sign-On (SSO).
For outages, Adobe runs a status site. You can subscribe to notifications for your Marketo data center and pod at status.adobe.com, by email or Slack.
What are Adobe's support plans and response times?
Adobe documents two success plans for Experience Cloud products: Expert and Ultimate. Adobe says the Expert Success plan is included with all Adobe Experience Cloud licenses. Ultimate adds a designated team and faster targets.
Here are the targeted initial response times Adobe publishes.
| Priority | What it means | Expert target | Ultimate target |
|---|---|---|---|
| P1 | Production down, or major data loss | 1 hour | 15 minutes |
| P2 | Major degradation, or a major feature impacted | 2 hours, business hours | 30 minutes, business hours |
| P3 | Minor degradation, with a workaround | 4 hours, business hours | 1 hour, business hours |
| P4 | General question or enhancement request | 1 business day | 1 business day |
These are targets for a first response, not for a fix. A one-hour response to a P1 means an engineer engages within the hour. It doesn't promise a resolution in that time.
The plans also differ in who you work with:
- Expert. A pooled team of support engineers, with P1 cover around the clock and P2 to P4 in business hours.
- Ultimate. A designated Technical Account Manager (TAM) and Customer Success Manager (CSM). P2 and P3 issues get cover 24 hours a day on weekdays, with prioritized outage handling and designated escalation management.
- Named contacts. Up to four Named Support Contacts per product on Expert, and up to fifteen on Ultimate.
Adobe also lists a Priority Queue Bundle add-on. It offers faster response times and a single point of contact. Adobe shows it as available on Expert and included in Ultimate. Older Marketo contracts may use different plan names, so check your order form or ask your account team.
What doesn't Adobe Support do for Marketo?
Adobe Support doesn't run your marketing. It won't build programs, write emails, clean your database or design your lead lifecycle. Those jobs sit with your team or a partner.
Adobe's documentation is explicit about one boundary. Its Munchkin setup page says Marketo Technical Support isn't set up to help troubleshoot custom JavaScript. That covers custom tracking code and custom form behavior, which often cause "missing data" complaints.
Adobe's success plan page also lists Field Services activities. For Marketo Engage these include a health assessment, a maturity roadmap and basic use case development. Adobe describes that last one as a single use case with limited execution support. It adds that Field Services aren't meant to replace Adobe Consulting engagements.
So Adobe's proactive help is advisory and bounded. It's useful for a second opinion on your instance. It isn't a standing team that clears your build backlog.
Your own configuration is your responsibility too. If a Salesforce validation rule blocks the sync, Adobe can confirm that's the cause. The fix is a change in Salesforce, made by your CRM admin or a partner.
What does a Marketo support partner do?
A partner does the hands-on work inside your instance that Adobe Support doesn't. The exact scope depends on your contract, but most services draw from the same list.
- Campaign operations. Building, testing and launching programs from your requests. Our guide to Marketo campaign operations support covers that day-to-day work.
- Administration. Users, roles, fields, folders, naming rules, communication limits and Audit Trail reviews.
- Integrations. CRM sync health, API users, webhooks and LaunchPoint services. Our guide to Marketo integration troubleshooting services covers the failures and fixes.
- Data quality. Deduplication, normalization and suppression rules.
- Strategy. Lead lifecycle, scoring, nurture design and reporting.
- Enablement. Training your team and writing the runbook.
A partner also brings context Adobe Support doesn't have. It knows why a field exists, which campaigns are fragile and who on the CRM side to call. That context is often what turns a two-day investigation into a two-hour fix.
What a partner can't do is change Adobe's code, restore a platform outage or override Adobe's limits. When the problem is the product, a good partner says so quickly and helps you open the right case.
Marketo support partner vs Adobe Support: how do they compare?
The two cover different layers, with a small overlap around how-to questions and diagnosis.
| Area | Adobe Support | Marketo support partner |
|---|---|---|
| Platform outages | Owns the incident and fix | Reports impact, keeps your team informed |
| Suspected product defects | Diagnoses and fixes | Gathers evidence, reproduces the issue |
| How-to questions | Explains how features work | Explains them in your instance's context |
| Campaign builds | Not covered | Core service |
| Instance admin | Advice on settings | Hands-on changes |
| CRM sync | Helps with platform side, sync filters | Works with your CRM admin on configuration |
| Custom JavaScript and forms | Not set up for it | Covered if in scope |
| Strategy and scoring | Not covered | Covered if in scope |
| Response times | Adobe's published targets per plan | Whatever your contract sets |
| How you pay | Expert is included with licenses | Separate contract with the partner |
Use the table as a starting split, then write your own version into the partner's statement of work. Grey areas cause most of the friction, so name them.
How do a Marketo partner and Adobe Support work together?
They work best with a clear escalation path that everyone has agreed in advance. Without one, cases bounce between your team, the partner and Adobe while the problem sits there.
A workable setup looks like this:
- Triage first. The partner checks whether an issue is configuration or product. Many issues turn out to be configuration.
- Evidence pack. For a product issue, the partner gathers record IDs, exports, screenshots and steps to reproduce.
- Named contact opens the case. Either someone on your team or partner staff you've made a Named Support Contact.
- Partner follows up. The partner answers Adobe's questions and tests proposed fixes.
- Close and record. The outcome goes into your runbook, so the next person doesn't start from scratch.
Deciding whether partner staff should be named contacts is a real choice. It speeds things up, because the person who understands the issue talks to Adobe directly. But it uses some of your limited named contact places, and you must remove them if the partner leaves.
Adobe's P1 rules also matter here. Adobe says the customer commits to continuous engagement until a P1 is mitigated. It may lower the priority if it can't get critical information from named contacts. If your partner handles out-of-hours incidents, make sure one of them can act as a named contact.
The quality of the case matters as much as who opens it. A good case states the business impact, the exact steps to reproduce, when it started and what changed just before. It includes record IDs, screenshots and exports, not just a description. Partners who open cases often tend to write them this way by habit, which is part of their value.
Which Marketo issues go to Adobe and which go to a partner?
Route by cause, not by how urgent it feels. The examples below show how a typical split works once both sides are in place.
- No one can log in to Marketo. Check status.adobe.com first. If there's no posted incident and logins fail across users, open a P1 case with Adobe.
- One user can't log in. On IMS subscriptions this is usually access in the Adobe Admin Console. Your admin or partner checks it first.
- Emails stuck in the queue for hours. If a campaign is huge or badly scheduled, that's configuration. If small sends are also stuck, raise it with Adobe.
- Leads not syncing to Salesforce. Read the Sync Errors tab. A validation rule or missing field is a CRM fix. A platform-wide sync stall goes to Adobe.
- A form stopped capturing a field. Usually a form or picklist change, so it's partner or admin work.
- Web visits missing on known people. Usually Munchkin placement or custom code, which is partner or developer work.
- A feature behaves differently from the documentation. Collect evidence and open an Adobe case as a possible defect.
- You want a new nurture program. Partner or in-house work, with no Adobe case needed.
If you aren't sure, let the partner triage for an hour before anyone opens a case. Many issues turn out to be configuration, and a well-documented case moves faster when it is a product problem.
Do you need both a partner and Adobe Support?
Almost every Marketo customer has Adobe Support already, because Expert is included with Experience Cloud licenses. The real question is whether you also need a partner, and that depends on your team.
- You have a strong in-house admin. Adobe Support plus occasional specialist help for projects may be enough.
- You have one admin and a growing backlog. A partner for campaign builds frees your admin for the work only they can do.
- You have no Marketo specialist. A partner on a managed service is usually the safer route.
- You run several regions or business units. You'll likely need a partner and may want Ultimate for faster Adobe response.
If you're weighing outsourcing at all, our piece on why companies outsource Marketo support covers the common triggers and risks. Our guide to Adobe Marketo Engage support services explains what a managed plan typically includes and how service levels are written.
What to do next
Before you weigh a Marketo support partner vs Adobe Support, get clear on what you already have.
- Find out which Adobe success plan you hold and who your Named Support Contacts are.
- Subscribe your team to Adobe status notifications for your pod.
- List last quarter's issues and mark each as product, configuration or build work.
- Write a one-page escalation path covering your team, any partner and Adobe.
- Decide whether partner staff should be named contacts.
- If you need a partner, define the scope before you speak to firms.
To find firms that offer Marketo support, browse the Adobe Marketo Engage partner directory or the filtered partner list. Brief them with our Marketo Engage RFP template, then line up the replies in our comparison tool.
Frequently Asked Questions
Is Adobe Support included with Marketo Engage?
Yes. Adobe's success plan documentation says the Expert Success plan is included with all Adobe Experience Cloud licenses, which gives you pooled support engineers, round-the-clock Priority 1 cover and business-hours cover for lower priorities. Ultimate is a higher plan with a designated team and faster targets. Check your order form to confirm which plan applies to you.
How fast does Adobe respond to a Marketo P1 issue?
Adobe publishes a targeted initial response of one hour for a Priority 1 issue on the Expert plan and fifteen minutes on Ultimate. That's the time to first engagement, not to resolution. Adobe also expects you to stay engaged around the clock until a P1 is mitigated, so plan who will be available.
Can Adobe Support build Marketo campaigns for me?
No. Adobe Support handles technical issues with the product and questions about how features work. Building programs, emails and smart campaigns is your team's job or a partner's. Adobe's Field Services activities include limited help with a single basic use case, but they aren't a substitute for ongoing campaign operations or a consulting engagement.
Can my Marketo partner open cases with Adobe Support?
Yes, if you make partner staff Named Support Contacts. Adobe may ask for a case to be resubmitted if someone outside that list contacts Support. Plan places carefully, because Adobe allows up to four named contacts per product on Expert and fifteen on Ultimate, and remove partner contacts promptly if the relationship ends.
Who fixes Marketo Salesforce sync errors, Adobe or a partner?
It depends on the cause. If the sync platform itself is failing, Adobe Support leads. If the error comes from your Salesforce setup, such as a validation rule, a hidden field or a missing permission, the fix happens in Salesforce, usually by your CRM admin or a partner. Adobe can also help set up a custom sync filter.
Do I need Adobe Ultimate Success if I already have a Marketo partner?
Not necessarily. A partner covers hands-on work, while Ultimate speeds up Adobe's side, adds a designated account team and expands named contacts. It tends to matter more for large, multi-region instances where outages or defects cost a lot. If most of your issues are configuration or build work, a partner often addresses more of them.