Processing

Between ingestion and delivery, Signal applies a consistent set of controls and transformations to every event:

• Consent enforcement — events are gated by the visitor’s recorded consent before they reach any vendor.
• Bot filtering — multi-signal detection with configurable pass / flag / drop thresholds.
• PII governance — redaction, hashing, and policy enforcement applied centrally.
• Identity stitching — vendor IDs and click attribution attached server-side.
• Per-vendor transformation — events mapped to each vendor’s payload shape via blueprints.
• Idempotency / deduplication — duplicate events suppressed before they leave your environment.

Configuration is per-pipeline in the management UI: which controls are active, what consent categories gate which vendors, and which transformations apply where.

For the customer-facing pipeline configuration model — fields, mappings, conditionals — see the pipeline configuration guide and the event schema reference.