Developer Help Centre > Oracle Maxymiser Cookies Explained

Oracle Maxymiser's Campaign Design API (CD API) sets the following browser cookies:

1st-party cookies

CD API tag (mmapi.js) sets different cookies depending on its configuration. Starting from mmapi.js version 1.10 four storage types are supported:

  • "cookie" (default) – centralised cookie storage in JSON format that includes all the CD API data; this format helps to:
    • retain consistency of visitor tracking, i.e. avoid partial data loss leading to discrepancies in reports or user experience
    • decrease the amount of cookies set by Maxymiser on a domain
  • "cookie-key-value" – individual key-value pair for every CD API data item; this storage type has been introduced as an alternative for "cookie" storage to resolve:
    • some server-side filters blocking requests with JSON data in headers
    • larger "cookie" storage size as a result of JSON structure encoding and expiration dates storing
  • "cookie-secure": same as the "cookie" storage, but used for HTTPS-only
  • "cookie-key-value-secure": same as the "cookie-key-value" storage, but used for HTTPS-only
For more information on setting a storage type please review "Configuring the JavaScript library" section of CD API Guide.

"cookie" storage

Example of a decoded value:

mmapi.store.p.[0..N]

Persistent storage set for a duration of one year from the visitor’s last visit on the site. It stores the following data:

  • Customer profile information: anonymous visitor id, historical visitor profile (generated experiences and tracked actions).
  • Maxymiser Content Generator service node name.
  • Personalization criteria (custom attributes) - persistent values captured from the site pages with the help of CD API custom scripts (using visitor.storeAttr(); e.g., VisitorType=Customer).
  • Campaign data captured from the site pages using CD API scripting (with the help of campaign.setData(); e.g., MostViewedCategory=Bikes).
  • External visitor ids captured by CD API scripts (using visitor.storeId()).

[0..N] in the name indicates that the cookie may be broken to multiple partitions. Each part contains up to 3000 characters. As soon as mmapi.store.p.0 reaches 3000 characters, a new mmapi.store.p.1 is created to store the next 3000. The expiry period for each cookie is defined individually.

mmapi.store.s.[0..N]

Session storage set for the duration of the browser session. It stores the following data:

  • Postponed actions to be passed to the Maxymiser CG service with the following request (usually used to capture successful journey after a link click).
  • Personalization criteria (custom attributes) - session values captured from the site pages with the help of CD API custom scripts (using visitor.storeAttr() with expiry period 0; e.g., loggedIn=yes).
  • Campaign data captured from the site pages using CD API scripting (with the help of campaign.setData() with 0 expiration; e.g., PagesViewed=5)
  • Oracle Maxymiser Utilities to be activated by an authenticated Oracle Maxymiser user (i.e., QA tool, debug tool, etc.)

[0..N] in the name means that the cookie may have multiple parts. If a cookie value is longer than 3000 bytes, it is split into multiple parts and saved with the syntax mmapi.store.s.{n} – each file containing a maximum of 3000 bytes.

mmcore.tst

Helper cookie to test whether cookies are enabled in visitor's browser.

"cookie-key-value" storage

Example of a decoded value:

mmapi.p.{name}

Persistent data set for a duration of one year from the visitor’s last visit on the site. It includes:

  • pd and mmid: Customer profile information: anonymous visitor id, historical visitor profile (generated experiences and tracked actions).
  • srv: Maxymiser Content Generator service node name.
  • uat: personalization criteria (custom attributes) - persistent values captured from the site pages with the help of CD API custom scripts (using visitor.storeAttr(); e.g., VisitorType=Customer).
  • ids: external visitor ids captured by CD API scripts (using visitor.storeId()).
  • un: Oracle Maxymiser Utilities to be activated by an authenticated Oracle Maxymiser user (i.e., QA tool, debug tool, etc.)
  • cfgID: testing environment, activated only for an authenticated Oracle Maxymiser user (i.e., Sandbox or Production)

mmapi.d.{name}

Dynamically set data to support CD API methods functioning:

  • uv: postponed actions to be passed to the Maxymiser CG service with the following request (usually used to capture successful journey after a link click).

mmapi.e.{name} and mmapi.{name}

Campaign data captured from the site pages using CD API scripting (with the help of campaign.setData(), visitor.setData(), etc.; e.g., MostViewedCategory=Bikes).

3rd-party cookies

These cookies are not set by default. They may be enabled by either Oracle Maxymiser for cross-domain testing ("pd" and "mmid", legal restrictions may apply to this functionality) or by a visitor ("optout", set on the Opt Out Status page) for turning off Maxymiser testing:

maxymiser.optout

Determines whether a visitor should be excluded from Maxymiser testing.

maxymiser.pd

Customer profile information: anonymous visitor id, historical visitor profile (generated experiences, tracked actions).

maxymiser.mmid

Anonymous visitor id.

Obsolete cookies

These cookies exist for campaigns built with CD API's predecessor library - mmcore.

mmid

Anonymous visitor id

mmcore.{name}

Visitor identification info, Content Generator service node name, postponed actions, personalization criteria, CRM visitor id, etc. (depends on the custom implementation)

mmpa.{name}

Product recommendations: ratings, views and history.

mm_{name}

Custom cookies created in Maxymiser Campaigns as part of testing (e.g., StayLength=8)