Many organizations have PDF documents on their web properties. Although PDF is a reliable format for storing and distributing content, when the browser is left to determine it, the consumption experience is unfortunately contradictory.
Depending on the device, browser, and user software preferences, the PDF can be:
- Open in an existing window or tab, take them away from your web experience.
- Download directly without opening them on the device (ie: in the “Downloads” folder), possibly lost.
- In the preview or background, open a new window or a new tab.
As a site owner, none of these situations are predictable or ideal.
To make matters worse, a PDF sent to a new tab, window, or local folder becomes an analytical black box. You have no idea how people are interacting with content.
There is a better way.
The PDF embedded API solves this discrepancy by creating an experience of viewing equally high loyalty for all users, regardless of device.
Not only do your PDF browsers look great and open as you intend, but the PDF embedded API also gives you complete control over experiences, including interpretation, analysis, collaboration, and archiving. Control, and more.
Try the demo to get a sense of what the PDF embedded API can do. Oh, and did I mention it’s free to use?
But what about all the PDFs on your site? How can you view all the PDFs posted there without manually coding each one to take advantage of these new features? From here, Adobe PDF Embed API and Adobe Experience Platform Launch work beautifully together.
The Adobe Experience platform enables launch brands to centrally deploy scripts, data collection, and marketing technologies in all of their features.
The instructions below assume that you are already familiar with the Adobe Experience Platform launch. If you’re not sure what it is or want a refresher, check out the launch homepage or product documentation to find out for yourself.
What will we do
- Create an Adobe PDF embed API key.
- Create an Adobe Experience Platform Launch Roll to deploy the PDF embedded API.
Before we start
You’ll need access to your organization’s Adobe Experience Platform Launch Console. If you do not have access, please contact your organization’s Adobe Administrator.
Assumptions and warnings.
Step 1: Get an Adobe PDF embedded API key.
If you already have your PDF embedded API key, go to the next section.
Go to the PDF Embed API homepage and click. Get free credentials. Button, or use this direct link.
On Get started with the Documentation Services API. Page:
- Click on To start I button Create new credentials. Section
On Create new credentials. Page:
- Select. PDF embedded API. As a service
- Give your credentials a Name.
- write Domain The name of the site on which you want to install the embedded API.
- Click. Create credentials..
Step 2: Create the launching roll.
You will now use the Adobe Experience Platform Launch to create a rule:
- Runs on every page.
- Examines the HTML ‘A’ tags page that references PDF documents.
- Adobe rewrites PDF links to use the PDF Embed API.
Make a rule
- Log in to Adobe Experience Platform Launch.
- Select the launch property on which you want to deploy the PDF embedded API.
- Click on Rules tab. For the selected property.
- Click on Add rules. Button
- Recognize your principle easily. Name (Previous: ‘Convert PDF links to PDF embed API’).
- Click on Plus icon. To add an event to Events Section
- Select.
Core
As Expansion - Select.
DOM Ready
As Event type. - Click on Make changes. Button in the top right corner.
On Action configuration Screen:
- Select.
Core
As Expansion. - Select.
Custom Code
As Action type.. - Select.
Javascript
As language. - Click on Open Editor. Button for editing code.
Copy and paste the code into the code editor from the following summary:
GIST: https://gist.githubusercontent.com/whatwork/43eb2ef874f4b662ca5271f690731795/raw/b2ad2098fbe40c93256e5181634e38a163cc1f2c/embedApiLightboxExample
Important: Change the value of the client ID on line 4 to the value you were assigned when you created your PDF embedded API client ID in step 1.
It should look something like this:

Publish the rule.
You will now publish and test your new rule.
- Click. Publication flow From the left hand rail
- Click. Add Library.

- Give your new library a name (example: PDF embed).
- Select environment. Which you want to rule.
- Click. Include all modified resources..
You will see that your new rule appears in the Resource Changes section.
Click on Save and build for growth. Button
Check the rule.
For demonstration, we will use the following HTML as an example. It’s deliberately simple, with only 3 buttons with some PDF links.
Our test page when posted on our web server:
Final thoughts.
With the combined power of the PDF Embed API and the Adobe Experience Platform launch, we’ve been able to enhance the PDF reading experience for our site visitors in just a few minutes.
Now that you see how easy it is to place viewers on a page, check out examples from our Gut Hub to see what possibilities are open to you now with the PDF embedded API.
Enjoy!
.