What cookies does Maxymiser set on visitor browsers?

It sets mmcore.* cookies (first-party, various expiries) storing visitor ID, experiment variant assignments, and segment membership, plus mmapi.* cookies for campaign engine session data. These maintain consistent experiment experiences across page views and return visits to the site.

How does ConsentStack gate Oracle Maxymiser?

ConsentStack blocks the Maxymiser campaign script until both analytics and marketing consent are granted, since the platform spans both categories. Once consent is obtained, experiment variants load normally. Visitors who decline see the default page content without personalization or variant manipulation applied.

Oracle Maxymiser - A/B Testing Consent Guide

Q: Does Oracle Maxymiser require consent for A/B testing?

Yes. Maxymiser sets persistent mmcore.* cookies that assign experiment identifiers and track behavioral responses across sessions. The personalization component processes visitor attributes to serve targeted content, combining analytics and marketing purposes that both require explicit consent under GDPR.

Back to Vendor Library

Overview

Oracle Maxymiser is an A/B testing and website personalization platform within the Oracle Marketing Cloud suite. It enables marketers to run multivariate experiments on page content, test layout variations, and deliver personalized experiences based on visitor segments. Maxymiser scripts modify page content in real time based on experiment assignments and visitor attributes, measuring the impact of each variation on conversion goals.

What This Script Does

Maxymiser loads a campaign script that evaluates visitor attributes and applies experiment variations to the page.

Scripts loaded: The Maxymiser campaign script loads from Oracle's CDN (typically service.maxymiser.net or a custom domain), evaluating visitor attributes and experiment rules to determine which content variation to display
Page modification: The script manipulates DOM elements to apply experiment variations — changing text, images, layout, CTAs, and page structure. This happens before or during page render, similar to other A/B testing platforms.
Cookies set:
- mmcore.* cookies — First-party cookies with various expiries. Store visitor identification, experiment variant assignments, and segment membership to maintain consistent experiences across page views and sessions.
- mmapi.* cookies — First-party cookies. Store API-related session data for Maxymiser's campaign engine.
Data collected: Page views, click events, conversion goal completions, visitor segment attributes, experiment variant assignments, and interaction metrics. This data feeds Maxymiser's statistical engine for determining winning variations.
Personalization: Beyond A/B testing, Maxymiser delivers targeted content to visitor segments based on attributes like referral source, device type, geographic location, behavioral history, and CRM data segments.

Consent & Compliance

Oracle Maxymiser falls under both analytics and marketing consent categories.

Under GDPR and ePrivacy, Maxymiser requires explicit consent. The mmcore.* cookies assign persistent experiment identifiers to visitors and track their behavioral responses across sessions, constituting non-essential cookie storage under the ePrivacy Directive. The personalization component processes visitor attributes to serve targeted content, which goes beyond analytics into marketing territory under GDPR. Oracle provides consent management integration points within the Maxymiser platform.

Under CCPA/CPRA, experiment assignments, behavioral tracking, and visitor segmentation constitute processing of personal information. If segment data is shared with Oracle's broader marketing platform for cross-channel targeting, this may constitute "sharing."

Should You Block This Without Consent?

Yes. Maxymiser sets persistent identification cookies, tracks visitor behavior for experiment measurement, and delivers personalized content based on visitor profiling. Block the Maxymiser script until the user grants consent for both analytics and marketing purposes.

Is Oracle Maxymiser GDPR compliant?

Oracle Maxymiser typically loads analytics and marketing trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Oracle Maxymiser can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Oracle Maxymiser, not on Oracle Maxymiser itself.

Visit website