AEM User Guide for Touch UI

Modified on Tue, 22 Nov 2022 at 03:56 PM

These instructions are intended for teams that use AEM's Touch UI. If you need instructions for how to pull Contently content onto a new AEM page using Classic UI, visit the AEM User Guide for Classic UI instead. 


To pull Contently content onto a new AEM page, you will need the Integration name and Story ID from Contently. There are two ways to retrieve this information:


If you have a Contently login: Log into Contently and navigate to the story page for the completed piece of content you want to pull into AEM. Click the "Push to CMS" button. A dialogue will appear with the Integration name and Story ID that you will need.


Note: The "Push to CMS" button will only appear for users with certain permissions once the piece of content is complete.


If you do not have a Contently login: Ask someone who has access to Contently to log in and follow the above instructions. On the dialogue described above, there is an option to email the Integration name and Story ID to someone on their team. Have them enter your email address and click "Send Email." You will receive an email with the details you need to pull the content onto a new AEM page.  


To save your email address for next time, your team member can visit the Integrations page in their Publication Settings on Contently. Have them edit the AEM integration and add your email address to the email list. Each time they complete a piece of content on Contently, they can click the "Push to CMS" button and send an email to notify you that a new piece of content is ready to be pulled into AEM. This email will include the details you need for that piece of content.


Using Contently's AEM Integration 

1. To pull Contently content onto a new AEM page, choose the "Contently Page" option in the "Create" drop down in AEM.  


2. Select an AEM template and click "Next."

Note: Make sure you have created a sample page and mapping for the AEM template that you choose. If you choose a template that does not have a mapping associated with it, you will get an error when you try to create the new page. 

3. On the "Create Contently Page" dialogue, fill in the "Title" field.


4. You will notice a special section called "Contently Options." Fill in the Contently Story ID and Contently Integration fields for the piece of content you want to pull in from Contently. 

  • Contently Story ID: The Contently Story ID is a numeric ID tied to your piece of content in Contently. You can only enter a Story ID for completed pieces of content.

  • Contently Integration: Each Contently integration has its own API key and is tied to a separate cloud configuration in AEM. If your integration does not appear in the drop down, return to the ‘Set up your Contently Cloud Service Configuration’ section in the AEM Install Guide. You will only need more than one integration if you need to create multiple sample pages / mappings per AEM template. Most teams will only have one integration in this list.  

5. Click the "Create" button to create your new page.


6. Click "Open" to view your new page. Your Contently content will automatically appear on your new page. Depending on the settings you chose when you set up your mapping — and the content associated with the Contently Story ID you entered — your body content will appear on the page including any embedded assets. Your page property fields and component fields will also be filled in for you. Any assets from Contently — including embedded images and images or videos from your custom fields — will have also been uploaded to your AEM DAM at the path you specified in your mapping. If you mapped Contently tags to an AEM tags field, all AEM tags with the same tag title as the Contently tags will appear. The tags have to exist in AEM first — and match the tag names in Contently — for this to work.


For help, view our AEM FAQ help center article for details on the AEM fields Contently supports to help you edit your mapping if necessary. The AEM Technical Manual also has information about editing API keys, creating mappings, and supported AEM field types.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article