Now, onto the fun stuff.  How can we modify (or create) a system.d init script that will work with AEM?  Well, I’ll walk you through how to do this using the standard init.d AEM script.  If you have your own already, feel free to substitute it into the instructions.

You can grab a copy of the standard AEM init.d here (or here).

And here is the corresponding system.d file.

Now that we’re on the same page, lets get a few things straight:

• If you generated your init.d script (from above) these instructions use the filename aem and location /usr/bin/aem for the location of this script.  If you are using different values, please ensure the aem.system script is updated accordingly.
  • This script should be readable and executable by the root
  • AEM_USER
    • The system user in which AEM is expected to run under.  Be certain to start up an AEM instance using this user prior to going through these instructions to be sure they have appropriate permissions to the crx-quickstart folder
    • Default value is “aem”
  • AEM_ROOT
    • The root folder of AEM, or the parent folder of the crx-quickstart folder.
    • ex. if your crx-quickstart folder is /opt/aem6/crx-quickstart, the root folder would be /opt/aem6
    • Default value is /opt/aem6
• aem.system is a (very) basic system.d script generated for your standard AEM init.d.  In it there are several places which reference the existing aem script.  It is assuming that your aem init.d script (see above for link) is located at /usr/bin/aem.  This location can be modified to any you like, just ensure that:
• • It must be readable and executable by the root user
  • If the location of your aem script is not /usr/bin/aem, update references to ExecStart, ExecStop, and ExecReload accordingly
  • If your aem script does not include a restart, feel free to remove the ExecReload line as it will not function as expected.

Now for the official instructions:

1. (If no existing init.d) Download the sample init.d script here
   1. Open the file and modify the AEM_USER and AEM_ROOT variables to suit your environment (see above for description)
   2. Save the file to your file system.  This can be saved anywhere – the example aem.system file uses /usr/bin/aem.
   3. Ensure that the file is readable and writable as root:
      # sudo chmod u+rwx /usr/bin/aem
   4. Test the file works as expected
      # ./usr/bin/aem start
2. Download the aem.system file.
   1. (If you are not using /usr/bin/aem) – Modify the aem.system file by updating the location referenced by ExecStart, ExecStop, and ExecReload to match the scripts location
   2. Save the script to /etc/system.d/system/aem.system
   3. Ensure that the file is readable and writable as root:
      1. # sudo chmod u+rwx /etc/system.d/system/aem.system
   4. Enable the system.d entry:
      1. # cd /etc/system.d/system
# systemctl enable aem.system

That’s it!  On your next reboot, AEM should be started as expected.

Millennials approach information sources differently than previous generations. This, coupled with their increased customer experience expectations presents a challenge for B2B companies.

Rise of the Millennials

As shown in the illustration below, there are over 53 million millennials are in the workforce, making up 28.5% of the overall total. With Millennials focused on promotions and Baby Boomers retiring, soon Millennials will hold many purchasing positions.

Millennials, having grown up exposed to technology, no longer see technology as an add-on or gimmick. Instead, they expect technology to complement all experiences whether digital or analog. At the same time, Millennials emphasize the human factor. In an era of digitization, providing a humanized, personal experience sets a company apart.

Because Millennials view technology as a part of the human experience, they also expect technology to adapt to them. These expectations will especially challenge B2B companies, which already struggle with digital marketing.

B2B: Laggards in Digital Marketing

While many B2B companies have made tremendous strides in their digital marketing, many still struggle. The industry lags far behind their consumer-facing peers. In a recent survey, 70% of digital marketers from B2B companies said: “their organization’s digital advertising strategy fails to meet expectations”. This is due to the difficulty in gathering quality leads and in measuring the return on digital marketing spend.

This challenge is especially acute in personalizing experiences. B2B companies are struggling to deliver personalized experiences, often citing technical challenges. Another major challenge is the inherent differences in how B2B and B2C companies go to market.

B2B companies personalize based on company and role, rather than individuals. By personalizing too much to individuals, B2B companies can actually hurt sales cycles. This reduces the number of data-points available and requires a judicious approach to personalization.

Another challenge for B2B companies is the disconnect between digital experiences and the actual sale. While B2B buyers research online, most do not buy through digital platforms. Without direct conversions, companies struggle to attribute leads and personalize experiences.

Millennials: New Challenges for B2B Marketers

The rise of millennials poses another digital marketing challenge to B2B companies. According to a recent survey by the Arketi Group, Millennials expect more of digital experiences than other generations. This is especially true at the top of the buying funnel, Millennials’ favored channels include:

• Blogs
• eBooks
• Infographics
• Online Ads
• Vendor Texts
• Social Media

Millennials find traditional B2B sales and marketing channels less effective throughout the buying process, and view the following channels significantly less engaging than other generations:

• Analyst Reports
• Vendor Websites
• In-Person Demos and Meetings
• Phone Calls
• Product brochures, datasheets, sales literature
• Trade shows and conferences
• Whitepapers

A few patterns emerge when looking at different methods millennials prefer for B2B marketing. Millennials favor channels that are digital, interactive, and social. In-person, print, and traditional channels are far less popular than for previous generations.

Contrast these channel preferences to these indicated by B2B marketers as the most effective in reaching their goals:

• Events (exhibitions, conferences, trade shows etc) 84%
• Print Media 13%
• Direct Mail 22%
• Outdoor Ads 6%
• Television 4%
• Radio 4%

This poses a challenge, as the channels preferred by B2B marketers are the ones millennials find less engaging. If B2B companies do not evolve their marketing to better serve millennial workers’ desires and expectations, millennials will leave for competitors.

B2B Digital Marketing for Millennials

So how do B2B marketers market to millennials?

First, B2B marketers need to lay a foundation for excellent digital marketing experiences. This means eliminating data silos, developing customer 360 profiles and building a strong platform. This requires an effective implementation team and modern technical platform.

With this solid platform, marketers can build technology-enabled solutions to market to every generation. This includes omni-channel marketing, to message consistently across all forms of media, and building personalized experiences across all digital platforms to deliver the correct message. Finally, sales and knowledge enablement platforms help deliver the best content.

Finally, Digital marketers need to market specifically to millennials. Marketers should include mobile, social, and interactive media to capture and hold the attention of millennial buyers. These new forms of media also offer the benefits of increased conversion points and data. These grant marketers a richer data source to inform their marketing efforts.

The rise of the millennial generation poses significant challenges to B2B marketing strategies. They are less likely to be persuaded by traditional B2B marketing approaches. Yet, this presents an opportunity to companies that choose to implement technology-enabled digital marketing. Companies that embrace this opportunity will win Millennials’ business from their less-agile competition.

Source: https://blogs.adobe.com/digitalmarketing/analytics/why-new-adobe-marketing-cloud-id-service-should-be-on-your-radar/

Migrating from Adobe Analytics Legacy Visitor ID
This migration will either store the legacy cookie (s_vi) to the AMCV cookie or create a new AMCV cookie, which will be used as its replacement all together.

Implementing AMCV in Adobe Dynamic Tag Mangement

Prerequisites – Adobe Requirements

1. Contact Client Care to obtain the Marketing Cloud Organization ID ie. (MCOrg ID)
2. Ensure your scode is on AppMeasurement version 1.3 or later, scode H.27 or later.
3. Make sure your Adobe Adobe server calls are going to Regional Data Collection, meaning your image requests are being sent to RDC tracking server ( ie. .sc.omtrdc.net) instead of a Non-RDC tracking server, (ie. .2o7.net).
4. Next, deploy your new VisitorAPI Javascript library. Log into your Admin Console and get the VisitorAPI.js file from the Code Manager. This can be in your scode file or in DTM in the tool’s setting, but it must be placed at the beginning of the file. Important Note: The placement of this code needs to fire first in the order sequence in order to be leveraged by the other Adobe JS libraries.
5. Configure your Visitor ID service.
6. Set Visitor ID in a Custom Variable (sprop or eVar) to test quality assurance. (Below is the Custom JS to capture the AMCV in a DTM Data Element that is ready to be mapped to a custom variable.) You can also set the AMCV in a cookie using a native DTM function to either map or verify in the Developers Console. (_satellite.setCookie(‘cookie name’,’cookie value’,days to expire)
7. As precaution, please be sure to check Adobe Analytics server call as there should be an additional parameter called “mid”, the Marketing Cloud Visitor ID.

Now that you have the foundation for your Adobe Target, Adobe Analytics, Adobe Media Optimizer and Adobe Audience Manager tools, you can feel confident about your data being unified and now you are finally ready to start building your campaigns, profiles, activities, and reports.

Overview

Perficient was self tasked to feature a highly interactive, visually compelling Adobe Summit App built in AEM Mobile that allows users to see real-time analytics from Adobe Workbench, an interactive analytics application part of Adobe Analytics that allows you to build visualization dashboards, as well as experience personalized content based off their responses on the survey taken from their mobile device.

Challenge

Integrating DTM and Target on a single page application in AngularJs, a JavaScript front-end framework.

The application was built with Cordova (formally known as Adobe PhoneGap), a hybrid app development framework which consist of HTML, CSS and JavaScript, we were able to leverage the mobile platform’s Web view to render content. Since DTM is a JavaScript based container, we were able to integrate many of the other Adobe Marketing Cloud products that we come so accustom to.

Using DTM as a host for Adobe Tools such as Adobe Analytics and Target, you are able to push, configure, track, integrate and perform marketing initiatives such as performing A/B tests with different components on the page and tracking user activities on your app.

STEP 1

We built a base template for each page (“mobileapps/components/angular/ng-page”) and we extended our pages from that template by creating an AEM (CQ) project using Apache Maven, a building management tool.

STEP 2

After configuring our property in Adobe Dynamic Tag Management, we went to our first page in the app, in this case the login page, and inserted the DTM bootleg snippet.

“<script src=”https://assets.adobedtm.com/3215e845c9690cbe968752c99b825440070e111f/satelliteLib-21077d4adfcbef88029b6d7609a4be07d51b0616-staging.js”></script>”

Notes: Place snippet before the end of <head> section in the head.jsp;

Screenshots from CRXDE Lite (Adobe AEM) and Maven Project

STEP 3

In the login page component, go to body.jsp, and insert the DTM snippet in the body of the page.

“<script type=”text/javascript”>_satellite.pageBottom();</script>”

Notes: Place snippet before the end of <body>;

Screenshots from CRXDE Lite (Adobe AEM) and Maven Project

STEP 4

Since the summit app is an Angular SPA, we just needed to put the snippets in the first page, and the JS will be loaded/available for all other pages.

Therefore the next step was to UAT/QA and verify the JS was getting downloaded correctly.

STEP 5

Now we are ready to add our Adobe Analytics and Adobe Target tools in DTM, where we were able to implement our analytics solution design and run different personalize tests based data being collected from Adobe Analytics including custom variables and success events.