Designed to qualify and verify applications developed by our partners, App Assurance helps you distinguish your integration through a designation on your Exchange Marketplace listing. In addition, your total number of App Assured solutions will appear in your Partner Directory listing.
By completing this program, you’re demonstrating a commitment to product excellence, while customers can trust that Adobe has diligently assessed the functionality and quality of these applications. The App Assurance designation must be reviewed every two years.
white background spacer inserted when cta buttons aren't present
anchor
overview
style
two up, container
layout
1 | 2
Timeline
The process to review App Assurance requests can take up to 6 weeks from start to finish. See the Process section below for more detail on the specific timelines and deadlines.
anchor
timeline
style
two up, max-width-10-desktop
layout
1 | 2
Limitations
Adobe Audience Marketplace: we do not offer this program for integrations that source 3rd party data into the Marketplace. It is beyond the scope of our process to analyze the quality and value of 3rd party data sources.
Adobe Experience Manager Translation: we can only offer this program for connectors that have been built using the Adobe Experience Manager translation framework and support the documented translation workflows.
anchor
limitations
style
two up, max-width-10-desktop
layout
1 | 2
Before you apply
The following items must be completed before your App Assurance request can be reviewed for the App Assurance badge. This is a high-level summary, with additional information further down in this guide.
Publish listing. Your application integration must already be a published listing on the Adobe Exchange Marketplace.
Include installation documentation. Your Exchange listing must include thorough installation instructions documented for customers, as our technical integration team reviews these as part of the evaluation process.
Share customer references. Your application integration should be successfully in use by at least three (3) customers. Partners will be asked to submit deployments to use these customers as references. Deployments can be entered both independent of and within the context of your App Assurance evaluation request.
The process to review App Assurance requests can take up to 6 weeks from start to finish. See the Process section below for more detail on the specific timelines and deadlines.
Request evaluation. To initiate the App Assurance review process, you will request this benefit through the Partner Benefits Center (starting March 1, 2026).
Initial evaluation request received. Adobe will review your request, determine if your application is eligible for this benefit, and move forward with the evaluation.
Submit additional information. Once you submit the request from the Benefits Center, you will get an email asking you to complete a detailed form via Workfront with specific information about your integration required for the evaluation. Please complete this form within three (3) weeks or fifteen (15) business days.
Validate customer references. If you have not already done so, you will need to submit three (3) customer references using the submit deployments form.
Adobe evaluation process. Once all information has been received in Workfront, an Adobe reviewer will complete the evaluation within three (3) weeks or fifteen (15) business days. The reviewer may also request changes as needed.
If changes are required, please submit revisions within five (5) business days and the Adobe reviewer will also respond within five (5) business days. Adobe and the partner can also establish a distinct timeline for changes and review if needed.
Evaluation complete. Once the evaluation process is complete and all App Assurance standards have been met, the App Assurance badge will appear on your solution listing in the Adobe Exchange Marketplace.
anchor
process
style
two up, max-width-10-desktop
layout
1 | 2
Renewal
Your App Assurance designation will need to be renewed every two years. A renewal goes through the same process of requesting an App Assurance evaluation through the Partner Benefits Center. The program will also send reminders when any earned App Assurance designation is approaching renewal.
During renewal, if your integration or extension has not changed in the last year, the Adobe reviewer will validate that nothing has changed or broken. However, if your solution has changed since the previous evaluation, you will be required to fill out a form describing the changes and the evaluation process will proceed from there.
anchor
renewal
style
two up, max-width-10-desktop
layout
1 | 2
Supplemental information needed for App Assurance evaluation
anchor
info
style
two up, max-width-10-desktop
layout
1 | 2
General information
URL for the Adobe Exchange Marketplace listing for the application integration you would to be evaluated
URL for a demo video illustrating the customer implementation steps and actions the customer must take to realize value from the app
Data and/or content interactions
List of all programmatic interactions the integration makes with Adobe, including each API call and/or data transfer action, including an example of each programmatic interaction.
API calls should include the endpoint, request payload, and response
File-based transfers should include the delivery location, file name, and 10-100 sample records for each
Error handling and logging
List the error codes/conditions the app is built to gracefully handle
Provide system logs that show the handling of at least 3 of the error codes/conditions in the list above
Describe how the customer experience is optimized by your error handling strategy
Provide system logs that show the occurrence of an expired auth token and how the application recovers by obtaining a new token
To support troubleshooting, all API requests, response codes, and errors should be written to a trace log file and include granular timestamps
Describe the caching strategy of the app including which objects are cached and for how long
Explain how you've designed your app to efficiently use Adobe services and resources
Security
Describe how the app is securely transferring and storing data and/or content
Explain how the app keeps data and/or content stored separately across customer instances
Describe how the app collects and stores authentication information provided by customers
Provide a video or screenshots showing the authentication/authorization UI experience of the app (acceptable if this was already shown in the demo video mentioned above)
Describe what security and privacy standards are upheld by your solution and provide certification evidence if applicable
List of tools or services used to validate against security vulnerabilities
Documentation
Customer-facing app documentation. Provide clear and detailed customer-facing documentation that guides customers on the installation, usage, maintenance and uninstallation of the app
Internal documentation for solution continuity. Share evidence of internal documentation created by the app developer that covers all aspects of functionality and maintenance to insure partner’s knowledge of the app is maintained in the event a developer leaves.
Customer references
Use the submit deployments form to provide references for three (3) customers who are successfully using your integration/extension and have agreed to provide brief feedback about their experience.
Designed to qualify and verify applications developed by our partners, App Assurance helps you distinguish your integration through a designation on your Exchange Marketplace listing. In addition, your total number of App Assured solutions will appear in your Partner Directory listing.
By completing this program, you’re demonstrating a commitment to product excellence, while customers can trust that Adobe has diligently assessed the functionality and quality of these applications. The App Assurance designation must be reviewed every two years.
ContentType
Tags
industry
Details
cta1Text
cta1URL
BadgeText
BadgeImage
Authoring Tips
For more information and advanced features see theSend to Caas documentation page.
