About this Integration

After creating an email in Stensul, users can upload the completed email’s HTML to Adobe Journey Optimizer (AJO) as an Email Template. To use this integration, a user needs to have an existing AJO account. Emails from Stensul are sent to the root folder of the email templates section within AJO. Learn more about AJO via their help center.

The integration uses a server-to-server connection with a client credentials grant. Learn more about this authentication method from AJO here.

To set up the AJO integration, you will first need to create a new OAuth based authentication application in your Adobe Console and collect two additional credentials.

When completed you will have 4 integration authentication credentials.

In Adobe Console, select “Create new project“

In the New Project page view, select “Add API“.

In the API page view, locate and select “Adobe Journey Optimizer” and then select “Next“ in the lower right corner.

In the Configure API page, select OAuth Server-to-Server and update the credential name for future reference. We suggest using the name “Stensul Integration Authentication“. When updated, select “Next“ in the lower right corner.

In the next page, select at least one Product Profile and then select “Save configured API“.

You will be taken back to the project page, where you will now see a section labelled “Credentials“. Select the new option “OAuth Server-to-Server“.

Your OAuth Server-to-Server credentials page will load and display all of the credentials needed for authenticating the AJO / Stensul integration.

The Client ID will appear in plain text. Select the “Copy” button and save this value offline.

Next, in the Client Secret field, select “Retrieve Client Secret”.

The screen will load and a new Client Secret will populate. Select the “Copy” button and save this value offline.

Lastly, scroll down to the last value on the page labelled “Organization ID“. Select the “Copy” button and save this value offline. The Organization ID is a string of characters that ends in @AdobeOrg.

Finally, return to the AJO platform instance to collect the final credential, the “sandbox name“

Uniquely, the AJO platform and API refers to all instances as “sandbox“ and a customer is typically provisioned a “Sandbox Sandbox” as well as a “Production Sandbox”.

This value is currently only accessible in the URL bar. In the URL, locate the “sandbox name“ by looking for the keyword sname:(short for: “sandbox name”). The following values are the “sandbox name“. In this example the sandbox name is “prod“. Learn more via the Adobe’s documentation here.

Setup in Stensul

To access the AJO integration in either Admin or Email Builder, certain permissions must be added to your roles.

Next, navigate to the integrations page in Stensul by going to Admin > Platform Settings > Integrations > Available.

Then, scroll down to the AJO integration labeled “Salesforce Marketing Cloud“ and select “Connect”.

Here, you can enter the credentials that you created and collected from the setup process above.

Once each value is entered, select “Save”.

Next, you need to configure the integration. In the “Installed” tab of the integration page, find your installed integration and select the “Configure” button.

Here, you can set the configurations of your integration. See below for all possible configuration options.

The final step of the installation process is to enable the AJO integration to be used in your Stensul email libraries. In the left-hand menu of your Stensul library, enable ESP/MAP, and select the respective integration(s) instance that you would like to add, and select Save. Depending on how you want to set up your library, you can add multiple integrations to any one library.

Stensul supports minified HTML as a default output option. This feature can be set at the Stensul Library level and enables the HTML that is generated by Stensul to be minified by default.

The minify code feature is always available as a setting in the Stensul “complete/output” modal and can be turned off in the complete/output modal prior to uploading to your target ESP/MAP.

To enable minified HTML by default, navigate to the left-rail of your Stensul library and locate the “Output Formats” section. Below the output format selector field, locate the Minify Output by Default toggle and enable it.

When you are ready to send a completed email to AJO, navigate to the top right-hand corner of your page and select “Complete“.

In the modal that appears, select “Upload to ESP/MAP”

Minified HTML

In the Stensul complete modal there is a Minify Code toggle located in the top-right hand corner of the modal. If you have the Default Minified HTML field enabled for your email’s library, this toggle will automatically be enabled.

If you have this default setting enabled, but would like to upload the HTLM without minification, you can simply disable this toggle and proceed to the Upload modal. If disabled, the HTML that will be uploaded to your target ESP/MAP will not be minified.

At this time, the AJO API only supports the ability to add an optional email template description.

The AJO platform does not support folders at this time. Therefor the API does not support folder targeting. At time of upload, the email template that is created is sent to the “Content Templates” tab in the AJO platform.

Technically the HTML of an email uploaded from Stensul is both accessible and editable. However, we recommend making any updates in Stensul and then re-uploading the email to AJO. This is to mitigate creative changes happening outside of the Stensul platform that will not be reflected back in Stensul.

When you re-upload the email, you will see an option to overwrite the content of the asset in AJO.