Today, customer experience is the bridge that connects the brand with existing and potential customers. Currently, of all other tools, none can match the personalization features and advanced capabilities which are included in Adobe Target for the Enhanced customer experience. It was first unveiled at the Adobe Summit of 2014 as an integral part of Adobe Marketing Cloud Suite. Later on, it was integrated with the Adobe Analytics Suite to enrich the marketing profile by leveraging its behavioral data. We all know that the contemporary digital period is being ruled by the mobile or smartphones, so digital marketing is revolving around it. Keeping this in mind and to let brands woo their mobile customers, Adobe has made several improvements in its Target tool. Let’s have a look at some major changes that have been incorporated by the Adobe in Target for Mobile Marketing.

1) Latest Visual Experience Composer:

This new feature makes the personalization experiments effortless on mobile apps and thus help you in creating robust Apps. We all know that App acts as the face and is very significant for every brand to reach their customers. To make any changes it needs to update the developer code and submit the changes to the respective App store, which makes it a time-consuming affair. Further, in the lengthy development processes, it may take a longer time period to accomplish and implement all the changes. With the latest new visual experience composer in the Adobe Target, one can easily exchange text and images in the native mobile app and can easily run A/B/n tests for all the changes. This feature helps you optimize the mobile experience and drive increased utility to your customers.

2) Adobe Target’s Batch Experience Prefetch For Mobile Apps:

Today, mobile devices let you connect with any brand from anywhere and at any time. Of all the internet traffics, about 60 percent is through the mobiles and so an always-on personalization for the mobile visitors is a must. Sometimes due to unavoidable situations or bad network connections, the interaction of users with your brand can be interrupted. This can be a lot frustrating on the users’ part and can be a loss of customer on your side as well. So, in lieu to overcome such situations, Adobe Target Batch Experience Prefetch feature can be very handy. It ensures always-on personalization even in the lack of proper internet by increasing the speed and performance of the App. It can be simply done by using Adobe Mobile SDK and letting Adobe Target fetch all the requests of visitors in batch. Then Target caches all this information on the EDGE network or on local, or both. So, whenever a visitor reaches out to your App, the Adobe Target quickly evaluates and delivers the required experiences throughout the App to the user. This ensures that visitors always have a personalized experience from any place and at any time.

3) Optimization of Node.js Websites and Applications:

Currently, almost every development work for websites and mobile apps are being carried out by using Node.js. It’s so because Node.js uses JavaScript, which makes it easier to port the code on both the client and server-side. Also, the overall development cycle can be increased because Node.js is available in the open source environment and one can get many reusable libraries developed by the other developers.

Apart from the above, the Adobe Target’s Node.js SDK let you optimize your website or mobile apps server side as well. Additionally, Adobe Target has built-in unified Visitor ID service, which lets you avail Adobe Analytics native integration features.

4) Mobile Experience Preview:

This a latest and a unique feature of Adobe Target that lets you test the experiences and personalize the content for the mobile users. One can perform the test based on the different global regional preferences and view the regional content variation directly on their device. Mobile Experience Preview also helps a brand to perform QA analysis of app activities without even activating them. Using this mobile experience preview feature, one just needs to create a preview link and send it to the mobile device and then click or paste the same link into any browser to see the impact it will generate. Along with this, one can also share this link with other stakeholders for review and approval purposes and members with that link can preview those before the live launch activity.

The above-discussed points are the latest changes made by Adobe to enhance Adobe Target Mobile Capabilities for advanced Personalization. We must understand that Today one need to deliver more personalized experiences to numerous consumers located globally. Adobe Target empowers marketers to create and deliver personalized experiences and is a game changer for digital personalization and provides much-needed help to marketers for maximizing revenue.

TechCommGeekMom reviews 2014 - So, how was it? #techcomm #elearning #mlearning

This was part of the Chiluly exhibit that was at the Botanical Gardens while I was at the STC Summit in Phoenix, AZ. It was cool!

As the year 2014 winds down, many have summarized the past year, as a reflection of all that has transpired.  When I started to think about the past year, I wasn’t sure that it was all that great of a year at first, but the more I thought about it, I realized that…

It's a good thing. (Career-wise, that is...) See what I'm talking about here: #techcomm

See, even Martha Stewart needs to take time on her social media accounts.

I know I haven’t been on my blog all that much. What can I say? Life gets in the way. As I’ve mentioned, I’ve had a busy summer, and it is shaping up to be an even busier autumn.

“Why would that be, TechCommGeekMom?” you may be asking. I’m glad you asked.

Work has picked up quite a bit, in a good way. I’ve spent a large…

So with the introduction of Sightly html templating in Adobe's AEM6 CMS you've got a much easier way of creating your cq:dropTargets in .html rather than the longer winded .jsp 

You do your cq:dropTargets in the same manner as you would normally do in CQ5.5/6 (so in our case we'll call ours video).

<div data-sly-test="${wcmmode.edit}" class="cq-dd-video">Drop video here</div>

There are 2 important parts to this:

The data-sly-test attribute, this is testing to see if we're in edit mode, if so then display the div else it will remove it.

The class cq-dd-xxxx. xxxx is the name of the what you've called your cq:dropTarget in our instance we've called it video so our class is cq-dd-video. If you was to call your drop target pdf then your class would be called cq-dd-pdf.

This is one of those annoying traits on CQ5 which I really hate as it generates a lot on unnecessary code and classes within my html and being anal about the quality of my code this really begun to drive me nuts.

This was until working on a project with an SSE (Senior Software Engineer) they came across the parameter cq:noDecoration = true for the component. This was great and worked as expected, but this also removed these when in edit mode and therefore not able to edit the component - which isn't helpful.

A solution which was posted on the Adobe forums was to add the following:

if (WCMMode.fromRequest(request) != WCMMode.EDIT && WCMMode.fromRequest(request) != WCMMode.DESIGN) { IncludeOptions.getOptions(request, true).forceSameContext(Boolean.TRUE); }

Adding this into the component would remove all the unwanted CQ5 generated div's from your clean component code, but if you placed into your global.jsp this will then parse through all your components and only remove all the generated CQ5 tags in preview and publish mode allowing your components to still work... SWEET!!

I'm happy again as my code is now clean and now all unwanted code removed from my page

In CQ5, components may have extra HTML elements included for editing, that then get stripped out for production. It's pretty easy to strip these out on the server side by checking the WCMMode on request. By default however, when you enter preview mode by clicking the button in sidekick the page does not refresh.

You may have noticed that most edit components still disappear, CQ5 iterates over all the editables in the DOM looking for a class containing the string '-placeholder'. It then does a regex replace on that class to append '-off' on the end. We can leverage this behaviour to make our own HTML disappear on preview without a refresh.

Appending a class to the element in the form 'cq-{some identifier}-placeholder' will trigger CQ5 on preview to change the class on the element  to 'cq-{some identifier}-placeholder-off'. This will not explicitly hide the element, however if we include some CSS such as

.cq-{some identifier}-placeholder-off { display:none; }

the element will not display.

If you would rather not write extra CSS to handle this behaviour, you could use some of the CSS classes that CQ5 itself uses for this same functionality. Two of these are

cq-table-placeholder

cq-texthint-placeholder

Published Aug 11, 2013. Length 4:02.