Web Channel Using Pages Matching Rules

​@Lala-Pen 

There are two factors determine this, 

• Page Matching Rules
• Audience Criteria.

1. Page Matching Rules: Controlling Where Personalization Can Trigger

Page matching rules serve as the initial gatekeeper for any personalization experience. Their sole function is to define the specific set of web pages where a given personalization campaign is technically allowed to be initiated or 'trigger.'

• They control the location—the specific URLs, URL patterns, or page metadata—on a website where the webSDK should even attempt to look for and execute a personalization activity.
• It is critical to understand that these rules only control where the experience can trigger. They do not determine if a specific visitor will actually see the modification; they only narrow down the set of applicable pages. A visitor could be on a matching page, but if they don't meet the audience requirements, the experience will not render.

2. Audience Criteria: Determining Who Sees the Personalization

The second is the audience criteria defined for the personalization campaign. This step filters the visitors on the matched pages to ensure the experience is shown only to the intended segment.

• AJO will only proceed to apply and render the defined web personalization if the visitor meets the audience criteria. This check is performed in real-time after the page matching rules have been satisfied.
• Result of a Match: If a visitor is on a page that matches the rules and they belong to the campaign's target audience, AJO retrieves and attempts to apply the specified content modification (e.g., changing a headline, swapping an image, hiding an element).

3. Default Experience

AJO's web personalization is its inherent focus on site stability and integrity, even when a personalization experience fails to render or is not applicable.

• No Audience Match: If a visitor lands on a page that meets the location criteria, but their profile does not match the audience criteria, the personalization modification will not render. The page will load as the original, default version.
• The failure of a personalization to render will not break the underlying page layout or functionality. In other words, pages with different layouts that may share a personalization zone, or pages where the modification involves are protected. The modification simply won’t render if the conditions are not met, allowing the original page content to display uninterrupted.