Extensions and Connectors

DropBox Connector for Tridion Sites

Anand Sarangapani — Mon, 19 Jun 2023 15:09:32 GMT

The Tridion Connector for Dropbox provides access to assets stored in Dropbox, like images, documents, videos and more. With this connector, you can build websites using the Dropbox assets, and then share this content across the whole organization. Please find the documentation link for more details.

The Connector for Dropbox provides the following key capabilities:

List folders and files
View asset metadata, including asset size and content type
Download asset files
Publishing Dropbox content from Content Manager

These capabilities make it possible to implement the following use cases (among others):

Navigate Dropbox assets from one single interface, Tridion Sites
Consume Dropbox assets in your Component and Pages managed in Tridion Sites

To get started, there are a few quick steps.

Download the zip file in the upper right-hand corner and unpack it. You'll find the JSON configuration file and the connector zip file.

Open up the JSON configuration file and make the following changes. Create an account on DropBox and login using your account.

Creating an OAuth access token for Dropbox

In the Dropbox Developer's area (https://www.dropbox.com/developers, open the App Console.

Create a new app.
- Choose the appropriate API.

Choose the appropriate type of access (folder or full).

For the app name, you can use whatever you like.

Open the newly created app
- Under Permission Type click on Scoped App

Select all the following for permission for the app created

Generate a new Oauth 2 access token and immediately copy it before closing the window. You need this for your configuration of Dropbox in the Connector.

Open a postman instance and create a new collection.
On that new collection select the authorization tab where you need to add some info to generate a refresh token:
1. type : OAuth 2.0
2. Add auth data to : Request url
3. Token name: the name you want
4. grant type : authorization code
5. callback url: keep is as it is and copy that value in your dropbox app from app console at redirect uri and press add
6. Auth url: https://www.dropbox.com/oauth2/authorize?token_access_type=offline
7. Access token url: https://api.dropboxapi.com/oauth2/token
8. client ID : app key from you dropbox app
9. Client Secret : app secret from dropbox app
10. Scope: empty string
11. State: empty string
12. Client authentication: send client credentials in body

Go to dropbox and add the redirect URLs for OAuth 2 ( https://oauth.pstmn.io/v1/browser-callback )

Auth url: https://www.dropbox.com/oauth2/authorize?token_access_type=offline

Access token url: https://api.dropboxapi.com/oauth2/token

Copy the App Key and click on Show to display the App Secret Key and copy the Secret Key

client ID : app key from you dropbox app

Client Secret : app secret from dropbox app

Client authentication: send client credentials in body

Press Get New Access token button. A web window will open where you need to allow access

After the authorization is successful a window will open with some authentication information, copy the refresh token to configuration file from connector.

So, at this point you should have updated the configuration JSON to include AccessToken, RefreshToken, ClientId, ClientSecret. HostUrl , BearerTokenUrl and DisconnectUrl no need to change its configured as part of the attached zip file.

The final configuration that you need to do is to set up a Stub Folder in Tridion Sites. What exactly is a stub folder? The easiest way to think of it is a virtual folder that points to a set of outside resources. The interesting thing about it is that you can use Tridion's inheritance model to determine if you want to have the connectors available to all publications by putting it high up in the BluePrint hierarchy or by putting lower down for only a few publications. So create your folder and copy the folder's magical TCM ID - it will look something like tcm:2-71-2.

Update the stubFolders field in the JSON file with this information, save and for the configuration part, you are DONE!

So now let's head over to the Tridion Sites Add-On Manager where you will upload the connector. After uploading the zip file, you will need to upload the configuration JSON file that you modified. At this stage you'll notice that the connector is awaiting activation. Simply browse over to Experience Space (or the Content Explorer) and it will activate.

Brightcove Connector for Tridion Sites

Anand Sarangapani — Tue, 13 Jun 2023 14:20:28 GMT

The Tridion Connector for Brightcove provides access to video assets stored in Brightcove Video Cloud. You can build Tridion Sites websites using these assets and then share this content across the whole organization. Please find the documentation link for more details.

The Brightcove connector can be used on both Content Manager to access the assets and Content Delivery via the GraphQL interface to retrieve video content from Brightcove Video Cloud

The Connector for Brightcove provides the following key capabilities:

List folders and files
View asset metadata, including state, duration, cue points and other information
Search for Brightcove video assets
Publish references to Brightcove video content that stream from the Brightcove Video Cloud

To get started, there are a few quick steps. It should take less than 10 minutes.

Download the zip file in the upper right-hand corner and unpack it. You'll find the JSON configuration file and the connector zip file.

Open up the JSON configuration file and make the following changes. If you want to see a video for the basic steps go to: https://studio.support.brightcove.com/admin/managing-api-authentication-credentials.html

Go into the Account section to get your AccountID:

Then go into API Authentication and Add application.

Here are the APIs that we exposed – you can adjust them as well.

Then generate your Client Secret and put it and the Client ID into the JSON configuration file.

Go into the Custom Fields section and add these fields. They will help you organize videos to make things easier for Tridion authors.

Go into the Player Settings section and copy the Player ID into the configuration JSON file under GlobalPlayerId.

So at this point you should have updated the configuration JSON to include AccountId, ClientId, ClientSecret, and GlobalPlayerId. As an option, you can also adjust the HtmlFragmentTemplate field to adjust the output.

Update the stubFolders field in the JSON file with this information, save and for the configuration part, you are DONE!

YouTube Connector for Tridion Sites

Greg Guttmann — Thu, 18 May 2023 01:02:01 GMT

Some of our customers have been asking about our YouTube Connector for Tridion Sites, so I'd like post some instructions on how to download and use it. Mind you, it's not an officially supported connector, but quite honestly it's so straightforward that there's not a whole lot to support :). If you do run into problems, just hop on over to the forums to get some help from the community.

From a functional standpoint, when you add the YouTube Connector via the Add-On Manager, your channels will become available so that content authors can easily browse the channels and add videos as part of a Component.

To get started, there are a just a few quick steps. It should take less than 10 minutes.

Download the zip file and unpack it. You'll find the JSON configuration file and the connector zip file.
Open up the JSON configuration file and make the following changes.
1. Change the apiKey to your YouTube. Instructions to do so are available at https://developers.google.com/youtube/registering_an_application. And yes there is a YouTube video explaining the process :) https://www.youtube.com/watch?v=yuM7KH-JLu8
2. Get the Channel IDs that you want to use. This is different than the Channel Name. To do this:
  1. Go to YouTube and sign in.
  2. Click on your icon in the upper right and at the bottom click on Settings
  3. In the "Your YouTube channel" section click on "View advanced settings"
  4. Now copy this Channel ID and paste it into the channels section of the JSON file. Repeat these steps for any other channels that you have.
3. The final configuration that you need to do is to set up a Stub Folder. What exactly is a stub folder? The easiest way to think of it is a virtual folder that points to a set of outside resources. The interesting thing about it is that you can use Tridion's inheritance model to determine if you want to have the connectors available to all publications by putting it high up in the BluePrint hierarchy or by putting lower down for only a few publications. So create your folder and copy the folder's magical TCM ID - it will look something like tcm:2-167-2. Update the JSON file with this information, save and for the configuration part, you are DONE!

So now let's head over to the Add-On Manager where you will upload the connector. After uploading the zip file, you will need to upload the configuration JSON file that you modified. At this stage you'll see that that the connector is awaiting activation. Simply browse over to Experience Space (or the Content Explorer and it will activate.

Happy YouTubing!

HTML Campaign Upload Connector v1.0.0

Niclas Cedermalm — Tue, 28 Feb 2017 13:51:01 GMT

The HTML Campaign Upload connector make it possible for digital agencies to create HTML based campaigns in their own tool suites. When ready they can package all campaign assets (HTML, CSS,JS, images etc) into a ZIP and upload it into SDL Web. The benefit of this extension is that digital agencies are given the freedom (within some defined boundaries of the brand guidelines, used CSS framework etc) to build campaign content with unique layout and interaction elements. And that without the need of creating specific templates in SDL Web for the created campaign.

For more info please refer to: https://github.com/sdl/dxa-flexible-campaign-content

See README.md in the ZIP for installation instructions.

Social Connect Module DXA .net 1.0

Raj Kumar — Sun, 11 Dec 2016 14:28:05 GMT

This Modules adds social login capabilities to DXA application. Currently Facebook and Google connects are provided in this version.

Installation on CMS:

Extract the module zip
Open Power shell in admin on CM machine.
Run ./ cms-import.ps1
Provide CMS URL when prompted.

Publishing :

_System/Publish Htmldesign
_System/Publish Settings
Include/Header
Social Connect/LogOff
Social Connect/Social
Social connect/SocialCallback

Don't forget to do Admin/refresh

Installation on Website:

Open Module folder
Browse to \SocialConnect\web\web8
Run ./web-install.ps1
Provide application root path when prompted

- After installation, Refresh Home page and you will see Login link in menu. Click on that and click on any social media you like.

- If you give your application Host http://dxa4.rri.com/ it should work as i have provided my test keys in the installation for now, which i will change later. Otherwise you have to do home work to set Key/Secret in https://Console.developer.google.com and https://developers.facebook.com

Enable/Disable

- After installation it will be active

- if you want to disable it. Remove the keys from Appsettings.

Note: Limitation due to OWIN, this Enable/Disable can not happen from CMS. because OWIN gets trigger way before Localization object is created so app URL is not resolved before that so settings from CD can not be retrieved.

Compatibility

DXA: Tested on DXA 1.4 and 1.5.

CMS: Tested on WEB 8.

Developer: Raj Kumar
License agreement: Apache License, Version 2.0
Version: 1.0

SDL DXA Audience Manager Module

Rick Pannekoek — Wed, 09 Nov 2016 12:37:23 GMT

The Audience Manager module offers integration with Contacts stored in the SDL Web Audience Manager database, allowing visitors to log in as one of those Contacts. This module is exposed through a Current User Widget in the Header, and through a separate login form.

Usage

See documentation on the module:
http://docs.sdl.com/SDLDXAModules

Developer: SDL DXA team
License agreement: Apache License, Version 2.0
Version: 1.7
Source repository: https://github.com/sdl/dxa-modules

SDL DXA Context Expressions Module

Rick Pannekoek — Tue, 05 Jul 2016 19:05:16 GMT

The SDL DXA Context Expressions module makes it possible to include or exclude Entities based on Context Expression Target Group conditions defined in the Content Manager.

Usage

See documentation on the module:
http://docs.sdl.com/SDLDXAModules

Developer: SDL DXA team
License agreement: Apache License, Version 2.0
Version: 1.7
Source repository: https://github.com/sdl/dxa-modules

SDL DXA 51Degrees Module

Rick Pannekoek — Tue, 24 May 2016 15:13:21 GMT

The DXA 51Degrees Module makes it possible to let your DXA 1.5 Web Application use the Device Detection functionality provided by 51Degrees instead of the default device detection provided by of the SDL Web Context Engine.

51Degrees

Analyze and optimize web traffic by SmartPhone, Tablet, Bots/Crawlers or other device types, physical screen size, price band, amongst hundreds of other properties. Device, operating system and browser characteristics are all available both client and server side. Over 450,000 combinations of device are supported, with over 170 new devices added weekly. 51Degrees is the fastest and most accurate device intelligence solution available.

Full List of Properties

What Can It Do?

51Degrees device intelligence compliments Responsive Web Design (RWD) providing a wider range of features to optimize for different devices both client and server side. For example:

Understand how goal completion varies by device characteristics such as physical screen size by adding additional data to existing reporting and analytics.
Utilize the superior power of the web server and SDL DXA to make macro level decisions concerning page layout, navigation and design leading to superior performance, user experience and profit.
Implement device specific user interface features such as;
a. Prominent “Tap to Call” or “Tap to SMS” on devices that always support such features.
b. Rich hover optimised mega menus on non-touch screen devices.
c. Optimize navigation on complex sites for different screen sizes.
Reduce regression testing by using templates selected on browser capabilities. That is: no need to regression test leading edge enhancements on legacy browsers.

Who Benefits?

Common business sectors who increase profits using device intelligence include:

Advertising – maximise click through rates
eCommerce – increase checkout completion
Publishers – improve performance and dwell time
Finance – optimise financial transaction completion
Travel – better search and booking experience
Gaming – faster performance

Contact 51Degrees

Usage

See documentation on the module:
http://docs.sdl.com/SDLDXAModules

Developer: SDL DXA team
License agreement: Apache License, Version 2.0
Version: 1.7
Source repository: https://github.com/sdl/dxa-modules

JW Player Module for SDL DXA .NET

Raj Kumar — Thu, 14 Apr 2016 15:00:18 GMT

JW Player Module for SDL DXA powers you to use world's most popular video player's in your DXA MVC application without investing much in the development. This module covers basic/mostly used features of JW player including Skin and responsiveness.

It leverages cloud hosted JW Player.

Installation

In Content Manager

Run a PowerShell script to install the Jwplayer module in the Content Manager.

Access the module installation media.
Open a PowerShell command prompt in the administrator mode.
Go to the `modules\JWPlayer` folder and run the following command:

.\cms-import.ps1 -importType <IMPORTTYPE> -cmsUrl "http://cms.example.com:81/"

where:

-importType module-and-permissions Installs the module and sets rights and permissions for the default User Groups in the Content Manager (default setting).
-importType module-only Only installs the module.
-importType permissions-only Only sets rights and permissions for the default User Groups in the imported Content Manager.
-cmsUrl Web address of the Content Manager Explorer.

In Web application

Access the module installation media.
Open a PowerShell command prompt in the administrator mode.
Go to the `modules\JWPlayer folder and run the following command:

& '.\web-install.ps1' -distDestination "c:\inetpub\wwwroot\site"

where:

-distDestination The location of your site directory.

Usage:

When you install the module it gets added to "000 Home" page in "3-Column" region, home page is added with \400 Example Site\Building Blocks\Modules Content\JWPlayer\video component of JWPlayer schema with Component Template.

RePublish the Home Page & Publish Settings from '400 Example site\Home' and '400 Example Site\Home\_System' respectively.

Use your JW player Key in JWplayer setting Component to remove Jw player logo while playing.

Disclaimer:

This module is tested with only DXA 1.2. Video used as sample might be taken offline after few days, Please replace another video URL as per requirement. it does not use all available features of JW Player, as player has long list of features.

Developer: Raj Kumar
License agreement: Apache License, Version 2.0
Version: 1.0
Source repository: Coming soon

Publication Mappings (only for SDL Web 8.1.x)

Andrii Kushniruk — Thu, 18 Feb 2016 16:32:41 GMT

Update: Note that this Publication Mappings extension only applies for SDL Web 8.1.x. Do not use this extension for SDL Web Cloud or subsequent on-premise releases as this functionality is already included in the product.

Use the Publication Mappings extension to easily add, edit or remove Topology Manager mappings, which map a Publication to a URL. With this extension in place, you can manage your mappings using the Content Manager Explorer GUI rather than by running PowerShell scripts.

About this extension

When you add a new Site Publication, the system provides default configuration settings that you can use as the basis for your mappings for that Publication. On the one hand, you can see publishing environments that you can map to; on the other hand, you can see any mappings that have already been added to the current Publication previously, and that are not yet related to any environment.

The functionality of this extension will be included in a future release of the product itself.

Only Publications that use the new publishing framework introduced in SDL Web 8 can use this extension.

Sources

This extension package contains artifacts as well as source of all the SDL.Web.UI.PublicationMappings.*.DLLs to give you insight in how the solution is built and what is there available for you.

Support statement

The SDL Publication Mappings extension is intended as a toolkit to help the SDL Web community and is not an officially supported SDL Web product. If you encounter problems, reach out to the community: http://tridion.stackexchange.com/

Developer: SDL Web UI Team

License agreement: Apache License, Version 2.0

Version: 1.0

SDL Digital Experience Accelerator Java

Bart Koopman (former member) — Fri, 06 Nov 2015 14:43:50 GMT

The SDL Digital Experience Accelerator (DXA) is a reference implementation of SDL Web 8 and SDL Tridion 2013 SP1(*) intended to help you create, design and publish an SDL Web/Tridion-based website quickly.

(*) SDL Tridion 2013 SP1 is only supported up to DXA version 1.6. See https://github.com/sdl/dxa-web-application-java/releases

What is it

The SDL Digital Experience Accelerator helps you create, design and publish an SDL Tridion-based Web site quickly by doing the groundwork for you: it consists of Publications that are ready to publish to a dynamic, responsive and device-independent Web site with a customizable HTML design.

The SDL Digital Experience Accelerator creates a foundation for you to build on and reduces the SDL Tridion domain knowledge required to develop front-end (Web application) functionality. It provides a standard for creating and sharing content-related Web application functionality and widgets to optimize and accelerate the delivery of SDL Tridion-driven Web sites with rich user experiences.

Audience

Using the Digital Experience Accelerator requires the following familiarity with SDL Tridion:

Developers or Implementers are expected to know how to set up Content Delivery and publish content from Content Manager.
Editors are expected to be familiar with the Content Explorer and Experience Manager user interfaces.

Objective

You can use the Digital Experience Accelerator to create a basic Web site quickly with as goal to get developer familiar with SDL Tridion and its concepts, or as a foundation to kick start your own SDL Tridion implementation.

Example Site

An example Web site is installed with the Digital Experience Accelerator containing stock content and pages used to illustrate the different content types and layouts available. The content is royalty free, so you can build your site by extending the example site. You can also start from scratch and create a new Web publication to manage your Web site.

Disclaimer

The SDL Digital Experience Accelerator is not intended to be a one-size-fits-all solution for all requirements. SDL Tridion is an enterprise CMS which can be implemented to support almost any publishing model and web application architecture, the reference implementation is just one example of how SDL Tridion can be implemented and may not be the best solution for your organization's requirements.

Architecture

The SDL Digital Experience Accelerator Web application uses an MVC architecture.

Features

FEATURE	IMPLEMENTATION
Web Application	Web Application uses a Java Spring MVC architecture (and DD4T-based Content Provider) and requires a database as its Content Data Store.
BluePrint	The default BluePrint structure is linear and consists of 3 Publications. You can implement your own BluePrint.
Security Model	Three Roles are defined: Site Manager, Editor and Developer.
Templating	Templating is implemented on the Content Delivery side using ASP.NET Razor Views. Some (.NET) Content Manager based template building blocks are used to publish navigation, configuration and resource data assets and the HTML design assets.
HTML design	The HTML design combines the Bootstrap framework with a number of third-party plugins and can be customized/extended on a number of levels.
Responsive design	The example site is responsive both client-side and server-side, the design changes adapts to the device from which it is viewed.
Navigation and sitemap	The organization of Structure Groups and Pages in the Publication is exposed in the following Web site items: Top navigation, showing the top-level Structure Group names Left navigation, showing the sibling Structure Groups and sibling Pages for the current page Breadcrumb, showing the site structure to the current page Sitemap, showing all visible pages in the site Google sitemap, available at WEBSITE/sitemap.xml, where WEBSITE is the URL of the example Web site.
Example site content	The contents of the site consist of "lorem ipsum" dummy content combined with royalty-free stock images.
Image resizing	A single high resolution version of each image is managed and published from the Content Manager. This is resized by the web application to fit the design of the content element where it is displayed, and the display properties of the client device.
Multi-language support	The Web site is set up to support multiple languages. Content Manager elements (schema and template names etc.) are all in English only.
Experience Manager	The majority of pages and content are fully editable in Experience Manager, and the example site contains a set of page types to create new content.
Site Features	The web application includes: Separately managed header and footer Separately managed navigation elements (Top, Left, Breadcrumb, Language Selector, Sitemaps) Separately managed and localizable labels/resources and configuration A variety of page layouts: Home page, Section pages, Content pages (with and without navigation) Configurable social sharing toolbar, and links to social network pages. Auto-populated open graph metadata for social sharing Dynamic content lists based on broker queries Various types of content: Articles, maps, downloads, videos, teasers Various types of content list: Link lists, carousels, tabbed lists, accordions, paged lists and image galleries Notification bars for cookie usage, and unsupported/old browser versions Extensionless URLs, and internal/external redirect/short URLs Client device detection using the Context Engine
Integration	The Web site allows the following integrations: Integration with the most common social networks Integration with YouTube Integration with Google Maps Integration with Google Analytics

Sources

This distribution does not contain source code. On GitHub you can find a repository containing the full source of the DXA Framework to give you insight in how the project is built and what is there available for you to extend.

Old versions

Older versions of DXA can be downloaded on the corresponding GitHub repository from the releases tab: https://github.com/sdl/dxa-web-application-java/releases

Support statement

The SDL Digital Experience Accelerator is intended as a toolkit to help the SDL Tridion community and is not an officially supported SDL Tridion product. If you encounter problems, reach out to the community: http://tridion.stackexchange.com/

Developer: SDL DXA team

License agreement: Apache License, Version 2.0

Version: 1.7

Source repository: https://github.com/sdl/dxa-web-application-java

SDL DXA Search module

Bart Koopman (former member) — Wed, 23 Sep 2015 09:39:47 GMT

This module adds basic search capabilities to your DXA website. When installed, the module provides a search box in the header and a search results page showing a paginated list of published web pages and PDF/MS office docs matching the entered search term. The modules supports both Apache Solr and Amazon CloudSearch Managed Search Service.

The Search module uses SI4T and the Apache Solr search engine (which you have to install and configure separately) or Amazon CloudSearch. This provides a framework to easily configure and build more advanced search features from content-type specific searches with customized result listings to auto-suggest features. SI4T de-couples the CMS and publishing process from the search implementation, so you can also use this module as an accelerator for integration with other search engines.

Documentation on the module:
http://docs.sdl.com/SDLDXAModules

Digital Experience Accelerator

Developer:    SDL DXA team
License agreement:    Apache License, Version 2.0
Version:    1.7
Source repository:    https://github.com/sdl/dxa-modules

SDL DXA Impress module .NET

Bart Koopman (former member) — Fri, 11 Sep 2015 14:08:54 GMT

The SDL DXA Impress module adds the impress.js presentation framework into DXA, so you can create and publish presentations directly from SDL Tridion.

The Impress module demonstrates how a DXA module can have its own HTML design, for more details on this, you should take a look at the `impress-html-design.zip` in `100 Master\Building Blocks\Modules\Impress\Admin`

impress.js

It's a presentation framework based on the power of CSS3 transforms and transitions in modern browsers and inspired by the idea behind prezi.com. http://impress.github.io/impress.js

Installing Impress module in Content Manager

Run a PowerShell script to install the Impress module in the Content Manager.

Access the module installation media.
Open a PowerShell command prompt in the administrator mode.
Go to the `modules\Impress` folder and run the following command:

.\cms-import.ps1 -importType <IMPORTTYPE> -cmsUrl "http://cms.example.com:81/"

where:

-importType module-and-permissions Installs the Impress module and sets rights and permissions for the default User Groups in the Content Manager (default setting).
-importType module-only Only installs the Impress module.
-importType permissions-only Only sets rights and permissions for the default User Groups in the imported Content Manager.
-cmsUrl Web address of the Content Manager Explorer.

Installing Impress module in Web application

Access the module installation media.
Open a PowerShell command prompt in the administrator mode.
Go to the `modules\Impress` folder and run the following command:

& '.\web-install.ps1' -distDestination "c:\inetpub\wwwroot\mysite"

where:

-distDestination The location of your site directory.

Usage

The Impress module contains a `Message` and a `Slide` Schema, and Component Templates for each of these. The example impress.js presentation from http://impress.github.io/impress.js is already setup for you in the `400 Example Site\Home\Impress` Structure Group, you can Publish the Page in there and you will also have to republish the `Publish Settings` & `Publish HTML Design` Pages in `400 Example Site\Home\_System`.

Developer: SDL DXA team
License agreement: Apache License, Version 2.0
Version: 1.7
Source repository: https://github.com/sdl/dxa-modules

SDL DXA Media Manager module

Bart Koopman (former member) — Mon, 07 Sep 2015 11:45:15 GMT

This module allows you to use Media Manager distributions (video, image, audio, download) just like you were using any other media item, including embedding them in rich text fields. This module depends on the SDL Tridion Connector for Media Manager.

Documentation of the Media Manager connector:
http://docs.sdl.com/LiveContent/web/pub.xql?action=home&pub=SDL%20Tridion%20Connector%20for%20Media%20Manager-v2&lang=en-US

Digital Experience Accelerator

The SDL Digital Experience Accelerator creates a foundation for you to build on, and reduces the SDL Tridion domain knowledge required to develop front-end (Web application) functionality. It provides a standard for creating and sharing content-related Web application functionality and widgets to optimize and accelerate the delivery of SDL Tridion-driven Web sites with rich user experiences.

What is Media Manager

Media Manager allows you to manage and distribute multimedia Assets such as audio, video, images for display on various devices and for delivery to various channels such as the internet.

Developer:    SDL DXA team
License agreement:    Apache License, Version 2.0
Version:    1.7
Source repository:    https://github.com/sdl/dxa-modules

SDL DXA Experience Optimization Module

Bart Koopman (former member) — Wed, 02 Sep 2015 09:31:14 GMT

The Experience Optimization module (formerly known as SmartTarget module) will give your content editor team direct access for setting up promotions, and using these on their website.

Before rolling out the promotions to live, the editor can preview the different scenarios by changing the footprint in Experience Manager.

Documentation of SmartTarget:
[View:https://docs.sdl.com/SDLSmartTarget2014SP1:940:50]

Documentation of Experience Optimization 8:
[View:https://docs.sdl.com/SDLWebExperienceOptimization8:940:50]

Digital Experience Accelerator

The SDL Digital Experience Accelerator creates a foundation for you to build on, and reduces the SDL Tridion domain knowledge required to develop front-end
(Web application) functionality. It provides a standard for creating and sharing content-related Web application functionality and widgets to optimize and
accelerate the delivery of SDL Tridion-driven Web sites with rich user experiences.

What is Experience Optimization / SmartTarget

SDL Experience Optimization / SmartTarget enhances the SDL Tridion Web Content Management platform by adding targeting and personalization capabilities to every aspect of the user journey,
including content, promotions, navigation and onsite search. SDL SmartTarget is built with technology from SDL Fredhopper, a leading sales and marketing
optimization software provider.

SDL SmartTarget leverages dynamic relevancy and predictive targeting to deliver meaningful and tailored website experiences and offers based on a consumer's
individual profile. As a result, click-through and transaction rates climb, resulting in increased revenue and consumer satisfaction

Developer: SDL DXA team
License agreement: Apache License, Version 2.0
Version: 1.7
Source repository: https://github.com/sdl/dxa-modules