Manual Mappings and Customizations

When working with server-side tags, JENTIS provides full flexibility to either:

• Use the default dynamic values provided by JENTIS (recommended).

• Or apply a custom value (static string or your own variable) to override the defaults.

This is especially useful when you need to fine-tune how Google Consent Mode parameters are submitted, beyond the standard vendor-based mapping.

Controlling Consent Mode Parameters

For all tags affiliated with Google (GA4, Google Ads, Floodlight, etc.), you can configure every available Consent Mode parameter.

Parameters Available for Manual Mapping

• npa: Non Personalized Ads flag (true/false)

• gcut: Google Consent Update Type

• gcd: Google Consent Default

• gcu: Google Consent Update

• gcs: Google Consent Status

• dma_cps: Digital Market Act Parameters

Default Behavior

By default, JENTIS automatically maps these parameters to system variables that it provides out-of-the-box. These variables always reflect the latest consent information based on:

• Vendor settings in the JENTIS Data Capturing Platform (DCP)

• The user’s consent status from your CMP (if mapped)

This ensures your tags are kept in sync without requiring manual input.

Overriding Defaults

If you need a different behavior, you can override the defaults:

• Static values: Enter a fixed string or boolean ("true", "false", "granted", "denied", etc.).

• Custom variables: Use your own JENTIS-defined variables to inject dynamic values.

For example:

• You could force npa = true for a specific tag, regardless of vendor consent.

• Or you could use a custom variable that determines gcs (Consent Status) based on business rules outside of JENTIS vendors.

Why Use Manual Mappings?

Manual mappings are useful when:

• You need to apply different Consent Mode values for specific Google tags.

• You want to test or enforce static consent states.

• Your organization has custom requirements not fully covered by vendor-based mappings.

Key Takeaway

JENTIS defaults provide a safe and consistent mapping for all Consent Mode parameters. However, you retain full control to customize or override them on a per-tag basis.

This flexibility allows you to:

• Rely on automated vendor-driven consent management.

• Or enforce custom rules for advanced consent handling scenarios.