Configure your applications to use the cookieless experience

Customers who develop their own integrations can request the Acrobat Sign Support team to allow a cookieless experience for the Request Signature/Authoring and Create Template environments, providing a smoother user experience.

Overview

Customer applications that embed the Request Signature or Create Template experience may cause their users to encounter an error due to the use of third-party cookies (if third-party cookies are disallowed in the user's environment). In this case, the error provides a button to open the Compose page in a new tab.

Administrators can avoid this error and workaround by enabling the cookieless Compose pages in the application definition.

Availability:

Cookieless embedded workflows are available for the Acrobat Sign Solutions plans.

Configuration scope:

Cookieless workflows are enabled at the application level when the app is created or edited.

How to enable cookieless workflows for existing applications

Cookieless workflows are enabled at the application level when creating or editing the application itself.

Once the configuration is saved, any new use of the application will use the code path that provides the cookieless experience.

Disable the cookieless experience

Disabling the cookieless experience is achieved by unchecking the option and saving the configuration.

Once the configuration is disabled and saved, any new use of the application will use the classic code path that does not employ the cookieless experience.