Baseline group that will not be shown any message that the engine may match.
This uses the default (baseline) single-match engine.
Baseline group 'B' used for A/B tests between two default groups on a site (alongside
the baseline group).
This uses the default (baseline) single-match engine.
This uses the (baseline) EVMax V0.1 engine.
The same as BASELINE_EVMAX_V01 but used for A/A testing EVMax.
Baseline group that will not be shown any messages that the engine may match.
This uses the (baseline) multi-match engine, utilizing the single-match engine but with a second layer running in tandem to allow for multi-match configured campaigns to match at will.
Baseline multi-match group 'B' used for A/B tests between two multi-match groups on a site
(alongside the baselineMultiMatch group).
This uses the (baseline) multi-match engine.
The same as baselineMultiMatch but using an updated MultiMatch Engine.
This uses the (baseline) updated multi-match engine, utilizing the predictions first single-match engine but with a second layer running in tandem to allow for multi-match configured campaigns to match at will.
This uses the (baseline) per-placement engine, configured to not allow per-placement matching or multi-match offer persistence.
This uses the (baseline) per-placement engine, configured to not allow single-match slot reset or multi-match offer persistence.
This uses the (baseline) per-placement engine, configured to not allow per-placement matching.
This uses the (baseline) per-placement engine, unrestricted.
This uses the (baseline) per-placement engine without multi-match offer persistence.
This uses the (baseline) per-placement engine, unrestricted.
This uses the (baseline) per-placement engine, unrestricted.
This uses the (baseline) per-placement engine, unrestricted.
Active group that will be shown any single message that the engine may match.
This uses the default single-match engine.
Granify group 'B' used for A/B tests between two default groups on a site (alongside
the granify group).
This uses the default single-match engine.
This uses the EVMax V0.1 engine.
The same as GRANIFY_EVMAX_V01 but used for A/A testing EVMax.
Active group that will be shown any messages the the engine may match.
This uses the multi-match engine, utilizing the single-match engine but with a second layer running in tandem to allow for multi-match configured campaigns to show whenever they are matched.
Granify multi-match group 'B' used for A/B tests between two multi-match groups on a site
(alongside the granifyMultiMatch group).
This uses the multi-match engine.
The same as granifyMultiMatch but using an updated MultiMatch Engine.
This uses the updated multi-match engine, utilizing the predictions first single-match engine but with a second layer running in tandem to allow for multi-match configured campaigns to show whenever they are matched.
This uses the per-placement engine, configured to not allow per-placement matching or multi-match offer persistence.
This uses the per-placement engine, configured to not allow single-match slot reset or multi-match offer persistence.
This uses the per-placement engine, configured to not allow per-placement matching.
This uses the per-placement engine, unrestricted.
This uses the per-placement engine without multi-match offer persistence.
This uses the per-placement engine, unrestricted.
This uses the per-placement engine, unrestricted.
This uses the per-placement engine, unrestricted.
Active Granify platform group that will be shown any messages that the engine may match.
This uses the Granify platform engine, allowing multiple child engines to be configured per-tool pair.
Baseline Granify platform group that will not be shown any messages that the engine may match.
This uses the Granify platform engine, allowing multiple child engines to be configured per- tool pair. This matching group functions as a top-level holdout, so messages are not displayed even for eligible tool pairs.
Used to explicitly identify legacy traffic configured in rules to only match to 1-pixel test only during an active period. Group or matching pair can be used to filter paused traffic in reporting for billing and performance purposes.
Used to explicitly identify legacy traffic configured in rules to only match to 1-pixel test only during an active period. Group or matching pair can be used to filter paused traffic in reporting for billing and performance purposes.
A predictions first matching engine which allows ongoing predictions.
A predictions first matching engine which allows ongoing predictions.
Matching groups that a shopper may be assigned to.
Note that Contextual Commerce configures each site to allow only certain matching groups to be used. Contact your account manager if you are uncertain which values are valid in your case.