Analytics library is a set of tools that are used for collecting, aggregating, and processing the user behavior data. It monitors the user behavior and collects user actions in the form of events on the web pages. For example, product views, page views, add product to cart.
Acoustic Personalization supports the commonly used analytics libraries, such as Google Analytics, Digital Analytics, and Adobe Analytics.
In Acoustic Personalization, a channel is the mode by which personalization is delivered, such as a website, email, or mobile text messages. Acoustic Personalization currently supports websites as a channel.
When you register your organization in the Acoustic Personalization, you can register one or multiple channels as part of the organization. For example, CityCool Inc. (organization) can have multiple channels (websites) such as https://www.citycool.com , https://www.citycool.in or https://www.mycitycool.org registered under it.
To display personalization, you create one or more zones on the channel.
Acoustic Personalization currently supports the following types of channels:
Multi-Page applications (MPAs)
In Acoustic Personalization, each channel tenant is identified by a unique identifier, called as channel tenant ID or simply channel ID.
The channel ID is generated when new channel is registered in Acoustic Personalization. This ID helps to uniquely identify each channel registered for personalization. This channel tenant ID is required when you configure Personalization with Exchange. The channel ID is not case-sensitive.
A content management system (CMS) manages the creation and modification of digital content. It typically supports multiple users in a collaborative environment. Acoustic Personalization currently supports Acoustic Content.
MPA is a traditional type of web application. Every time the application needs to display the data or submit data back to server it must request a new page from the server and then render it in the web browser.
Nothing is wrong with this approach for simple applications. But if there is a need to create a rich user interface then the page might become complex and to be loaded with a large amount of data. Generating complex pages on a server and transfer them to the client over the internet and rendering them into the browser takes time and degrades the user experience.
For example, Simple HTML website is an MPA.
A single-page application (SPA) is a web application that interacts with the user by dynamically rewriting the current page rather than loading entire new pages from the server.
In a SPA, either all the code is retrieved with a single page load, or the appropriate resources are dynamically loaded and added to the page as necessary, usually in response to user actions.
X1ID is like a primary key. Every event record or audience record is identified by an X1Id.
Every user is assigned a unique X1Id. Acoustic Exchange uses the information available in the events data or in the audience data and assigns a new X1ID depending on whether that visitor is a new visitor and reuses the existing X1ID for a repeating visitor.
X1VisitorID is created when a new session is opened on a browser and it behaves like any other identifier. As a new value is generated for X1VisitorID every time a new session is started, multiple X1VisitorIDs can have the same value. Different sessions can be identified by Exchange when there is some identifier common in two sessions. In this case, events for both session will have same X1ID.
In Acoustic Personalization, a zone is an area of interest on the channel (for example, a website) on which you can display content personalization or product recommendations.
For example, consider a corporation that sells cutting-edge consumer technology. If the marketing channel owner for this corporation decides to start a new campaign that targets new visitors as potential buyers, then the channel owner can select an area (zone) on the website to display the personalized content. The zone can be in the form of a header or a side bar or in any other form as the channel owner desires.
In the case of Multi-Page Applications, zone is defined using HTML elements, for example, the div element. In the case of Angular Single-Page Applications, zone is defined based on the component used for content rendering or building the UI.
You must configure the zones of your channel by adding the personalization script, so that Acoustic Personalization can interact with your channel to display the personalized content.
For a zone, you can configure either content personalization or product recommendation at a time.
Zone is the area on your channel (website) on which you want to display the personalized content. Each zone has a unique identifier, referred to as the zone ID. When registering a zone for personalization, you must provide this zone ID.
In the case of Multi-Page Applications, the zone ID is specified by the website developer while creating the HTML source code for the web page.
In the case of Angular Single-Page Applications, the channel developer must identify the components where personalization is to be applied and subscribe those components for personalization by passing a unique ID that is same as the Zone ID specified in Acoustic Personalization.
The combination of zone name and the Zone ID must be unique within the channel being personalized.
The valid characters for a Zone ID are A-Z, a-z, 0-9, hyphen (-), and underscore ().
Zone ID should not contain a space, or special characters, except hyphen (-) and underscore () characters.
To view a zone ID in a website, complete the following steps:
- Open the website that you want to personalize in a web browser, for example Google Chrome.
- On the website, decide the section (zone) that you want to personalize. For example, header banner.
- Right-click on the selected zone and click Inspect from the context menu in Google Chrome. If you are using Mozilla Firefox or Microsoft Internet Explorer / Edge browsers, click Inspect Element.
The div element associated with the zone is highlighted.
Note the unique ID for the HTML element. For example, div id = “WelcomeBanner”
This is the zone ID that you need to specify during zone registration.
If the website that you want to personalize does not have unique identifiers for the section, then it is recommended to assign a unique zone ID to each HTML element that needs to be personalized.
Updated over 2 years ago