Skip to main content

setConfig() API Reference

setConfig() is the generic runtime-override API on MoliTag. It merges a partial object onto the internal runtime config, one field at a time, each field using its own merge semantics. It replaces the older one-method-per-field setters (setTargeting, addLabel, setAudience, setAdUnitPathVariables), which are now deprecated wrappers around it.

Signature​

setConfig(partial: MoliRuntime.MoliRuntimeConfigOverrides): void;

Call it any time before requestAds() — before or after configure(). Multiple calls compose; there is no priority system beyond ordinary call order.

window.moli.que.push(function (moli) {
  moli.setConfig({ adVolume: 7, labels: ['foo'], targeting: { key: 'value' } });
});

Supported fields​

FieldTypeMerge semanticsValidated
adVolumenumberFull replaceYes — integer, 1-10
labelsstring[]Append onto existing runtimeConfig.labelsNo
targetingKeyValueMapMerged per-key into runtimeConfig.keyValues (Object.assign)No
audienceAudienceTargetingFull replaceNo
adUnitPathVariablesAdUnitPathVariablesFull replaceNo

Fields left undefined in the partial object are untouched — setConfig({ adVolume: 5 }) does not clear labels, targeting, or any other field.

Examples​

Ad volume​

window.moli.que.push(function (moli) {
  moli.setConfig({ adVolume: 4 });
});

Must be an integer 1-10. Anything else (0, 11, 4.5, NaN) is dropped and logged as a warning — the previously set value, if any, is kept. See Ad Volume.

Labels​

window.moli.que.push(function (moli) {
  moli.setConfig({ labels: ['mobile', 'premium-user'] });
});

Appends to the existing label list — same additive behaviour as the deprecated addLabel(). Call again to add more; labels are never removed by setConfig().

Targeting​

window.moli.que.push(function (moli) {
  moli.setConfig({ targeting: { category: 'sports', position: 'sidebar' } });
});

Merges per key into keyValues. Existing keys not present in the object are left untouched; keys that are present overwrite the previous value for that key — same as the deprecated setTargeting(key, value), but for several keys in one call.

Audience​

window.moli.que.push(function (moli) {
  moli.setConfig({
    audience: { age: 32, gender: 'f' }
  });
});

Full replace — a later call with audience overwrites the entire object, not just the keys present in it.

Ad unit path variables​

window.moli.que.push(function (moli) {
  moli.setConfig({ adUnitPathVariables: { device: 'mobile' } });
});

Full replace — same semantics as the deprecated setAdUnitPathVariables().

Several fields in one call​

window.moli.que.push(function (moli) {
  moli.setConfig({
    adVolume: 7,
    labels: ['foo'],
    targeting: { key: 'value' }
  });
});

Error handling​

setConfig() never throws. Invalid fields are dropped and logged as a warning individually — one bad field never blocks the rest of the overlay from applying. Today only adVolume has validation (integer, 1-10); the other fields are passed through as-is.

Migrating from the deprecated setters​

DeprecatedUse instead
setTargeting(key, value)setConfig({ targeting: { [key]: value } })
addLabel(label)setConfig({ labels: [label] })
setAudience(audience)setConfig({ audience })
setAdUnitPathVariables(variables)setConfig({ adUnitPathVariables: variables })

The deprecated methods still work — they are now thin wrappers around setConfig() — but new code should call setConfig() directly.