Adenty Release Update 2.3 – What’s New?

A familiar setup: emails and visitor data collect through the day, load into the system in the evening, and the follow-up reaches the person the next morning. By then the visit is over, the comparison tab is closed, and the same person has opened two or three competitors.

Buying attention is short, and a response that arrives outside it is a response to a decision already forming somewhere else. 

Adenty 2.3 Release puts the response inside the visit. Two new Data Activation modules: A-Creative for building website creatives inside Adenty, and A-Script for running any JavaScript on the site. 

A-Creative Module

Visual actions triggered by the conditions you configure. Two ways to get started: use a predefined template for common use cases, or choose Blank and add your own code.

Under the hood:

• Pop-ups, banners, and inline views that can be reused across multiple conditions
• Pop-ups can be positioned anywhere on the screen; inline blocks can be placed by ID, CSS selector, XPath, or else
• Content can pull from live variables, including DataLayer values, event parameters, query strings, and API responses
• Custom mode for running scripts within a creative one

What changes for you: 

An on-site message used to mean filing a dev ticket or adding another tool to the stack. With A-Creative, marketing owns the wording and the look. Every text element can pull from a variable, so the same creative can adapt to the visitor in front of it: incognito or known, subscribed or not, returning to the same section for the fourth time this month.

The event decides which creative fires. The variables decide what it says.

A-Script Module

Run any JavaScript based on the same conditions used by A-Creative. Use it for widgets, currency rates, weather blocks, pop-ups with custom logic, or anything else a visual editor can’t cover.

Under the hood: 

• Reusable script actions running within the visitor processing flow
• Third-party widgets, chat tools, and embedded views
• Button handlers, input capture, and local storage writes Scripts loaded from a CDN or written directly in Adenty
• A replacement for the cookie-based integrations deprecated in the previous release

What changes for you: 

Engineering keeps control of the code, and the trigger logic stays in Adenty. There’s no separate personalization tool to maintain and no need to duplicate conditions across systems. The team writing the script can focus on what it does, while Adenty determines when it runs.

Also in This Release

• Trigger actions across standalone modules, with each module running on its own defined conditions
• Predefined templates for faster action setup
• Account isolation, so nothing is shared between accounts

Behavioral signals are read and acted on in the moment. Interests, section history, and returning visits can determine who sees a banner, a topical news block, or nothing at all.

The right content reaches the visitors it’s meant for, while everyone else can keep browsing.