What’s important to know about implementing Adobe Target?
Implementing Adobe Target is done by referencing the at.js Target library file in the head of your web pages. The easiest way to do that is through a tag management solution, but that’s not required. You can use a third-party tag management solution, but Adobe Experience Platform launch further facilitates the implementation process and is included with all Adobe Experience Cloud products. Target works client-side, server-side or through a hybrid approach. Its server-side offering works via real-time API integrations, batch delivery or NodeJS SDK, giving you the flexibility to choose the right solution for your scenario.
How does Adobe Target work with single-page apps?
The at.js client library for Target was built from the ground up with single-page apps in mind. We’ve developed Angular JS and React extensions to tie into those single-page application frameworks. The at.js library also includes a framework-independent Universal SPA extension that can trigger Target calls on both initial page loads and following view changes.
What kind of data can be used for personalisation?
You can use indirectly identifiable data (e.g. cookies, declared IDs) from your own customer relationship management (CRM) system, data management platform (DMP), the environmental data that Target already pulls from web browsers, Adobe Audience Manager, Adobe Analytics and a variety of other sources.
Where is the content actually hosted?
You can host image assets or HTML code snippets in the Target Content Library or host them yourself and simply reference the asset’s location using the Adobe Visual Experience Composer. You can also reference asset locations directly in your HTML or in your CSS files.
For more frequently asked questions, read our conversation guide.