Tracking Consent Controls Are Now Available

SGEN now ships tracking consent as a native control inside the attribution layer. Teams can manage tracking-related behavior through a unified platform path — audit-ready and conflict-free — rather than patching a script-layer plugin on top of analytics.

What changed

Tracking consent controls are now available inside the attribution surface. In a standard plugin stack, consent management is a separate script-layer concern bolted on top of analytics — the seam between them shows up as legal risk and maintenance overhead. SGEN treats consent as part of the measurement and attribution platform itself, not as a patch alongside it.

SGEN SG-Admin attribution surface with the Tracking Consent toggle enabled, showing consent-aware measurement controls

Why it matters

Two properties of the native approach matter most.

Consistency
One path, not two

Consent-aware behavior is part of the platform's measurement approach, not a separate toggle that needs to stay in sync with it. Your Store, for instance, can audit a single surface rather than reconciling consent state across a plugin and an analytics script separately.

Conflict-free
No plugin tax

A plugin tower adds legal risk each time a new consent script is patched on top of existing tracking. Native controls carry no plugin-layer conflicts — SGEN owns the full path from consent decision to measurement output.

Where it fits

Tracking consent lives inside the attribution surface in SG-Admin. It is part of SG-Modules — the layer that extends the SGEN core with measurement and operational capability.

Module: SG-Modules — Attribution

Tracking consent controls are located inside the Attribution section of SG-Admin settings. No separate plugin install or script embed is required.

Surface: attributions

Consent state feeds directly into the attribution layer. Measurement behavior respects the configured consent preference without a bridging script between them.

Heads up No setup is required. The controls appear inside the existing attribution surface automatically. If you are already using a third-party consent script, review whether it overlaps with the new native controls before leaving both active.

What to do next