Today, the web is not just about publishing content anymore. As the web evolves from content management to digital experience management, it's about understanding visitors' interests and preferences, and figuring out how to deliver them an optimal personalized experience. Many organizations are exploring ways to more effectively create and deliver valuable content to site visitors to increase traffic, conversions and revenue. Great content is still gold, but delivering the right content to the right user at the right moment in the right format is platinum.

Today's personalization tools aren't great and put marketers at a disadvantage. This is why I'm excited to announce that we're rolling out Acquia Lift, a solution that equips the site owners with powerful website testing and content targeting tools to optimize content for each visitor. Acquia Lift learns about a visitor's interests and, based on these insights, uses machine learning algorithms to automate the delivery of personalized content. Marketers and site builders can test content, for example using A/B or multivariate testing, and even add rules about the types of user profiles that get specific content. There is implicit learning that takes place as well that continuously helps Acquia Lift provide increasingly more appropriate content to individuals. Attributes of the user, such as location, and even what the current weather is, can be taken into account in providing the right content. Check out this short Acquia Lift video if you want to learn more or see Acquia Lift in action:

As I talked and wrote about earlier, I believe personalization and contextualization will be a critical building block of the future of the web, and I'm excited to help make that a reality.


Rick Vugteveen (not verified):

This is Drupal 7 but with Spark backports in place. This is typically what we demo Drupal with at Acquia. See the Spark, Demo Framework and Lightning distributions. Commons is also adopting much of the same stack.

Dave Reid (not verified):

Guessing that it requires most of the Spark modules.

Dave Ingram (not verified):

Hi Dave, no Spark modules are required. We support Navbar for some of the controls, but there's also a generic UI (using jQuery UI's dialogs) to provide the same front end controls. The only hard dependency is ctools.

Jesse Beach (not verified):

We're making sure that it doesn't :) The Spark modules improve the experience, but they're not required. Everything is built to fall back to core modules and forms. There's also no Navbar requirement.

We'll be posting the functional modules (Personalize and Visitor Actions) to D.O. The "glue" module will remain proprietary, but it just adds UX on top of the basic functionality.

kevin.oleary (not verified):

It's Drupal 7, It looks like D8 because the optimal (but not required) recipe you see includes the Spark modules; edit, navbar, etc. which have been backported from D8.

Dave Ingram (not verified):

It does! We're doing a bit of clean-up on our internal repos and then pushing out three new modules. One is a core personalization framework, one is called "visitor actions" and can be used for tracking arbitrary actions on a site (both client side and server side, with a pretty slick UI), and the third is the connector module to the Lift service.

Jesse Beach (not verified):

Yes, we'll be releasing two modules to contrib.

Django Beatty (not verified):

This looks great, absolutely agree on personalisation and contextualisation. And excellent having a joined-up experience all within the site itself and not the disconnect of a separate app.

Greg Dunlap (not verified):

Does this involve compiling site content on a central server to analyze trends across all participating sites? Or is the analysis limited to just the patterns on each individual site?

Dave Ingram (not verified):

It doesn't do that *yet*, but look for future announcements around this kind of functionality. At the moment it's limited to learning on a single site.

Greg Dunlap (not verified):

I actually consider it a positive that it doesn't, because I would be extremely wary about sending all my site's content to an external service for storage and analysis.

Dave Ingram (not verified):

OK, well in that case, *don't* look for any future announcements ;)

Tom Murdock (not verified):

Hi Robert,

This is a stand alone SaaS offering that does not require Acquia Cloud.

I also received your email and will follow up with some resources for you and the CG team!

- Tom

Cameron Tod (not verified):

At present, it is a packaged solution. Obviously it's still very new, and I'm sure that as adoption begins to happen the product and the way we offer it will evolve.

What did you have in mind?

Dave Ingram (not verified):

Yes, we've set up the project pages, but just doing a bit of clean-up before pushing the repos live. Part of the functionality requires the external service, but the core framework for personalization and for tracking visitor actions are in separate projects and there is a lot of potential in those.

Bill Winett (not verified):

1) Are you a var for Conductrics?
2) Is this only for customers using your site hosting, or can self-hosters also use it?
3) You have a spelling mistake on the "Variation set" page.

mbawazir (not verified):

Great tools for evolving the content , I'm wondering about visitors' interests and preferences,
What's difference between (user behavior) as term like amazon website and digital experience like Acquia lift,

Thanks a lot