Module signals 

Reserved signal type constants defined by TelemetryDeck

See the signals module documentation for usage examples. Reserved signal type constants defined by TelemetryDeck

This module provides pre-defined signal type names for common telemetry events. Using these constants ensures consistency with the TelemetryDeck platform’s built-in analytics and dashboards.

Example

use telemetrydeck_wasm::{TelemetryDeck, signals};

let client = TelemetryDeck::new("YOUR-APP-ID");

// Send a session started signal
client.send(signals::session::STARTED, None, None, None, None);

// Send a purchase completed signal
client.send(signals::purchase::COMPLETED, Some("user123"), None, None, Some(49.99));

Available Signal Categories

• session - Session lifecycle events
• navigation - Navigation and routing events
• purchase - Purchase and monetization events
• acquisition - User acquisition and onboarding events
• signal - General signal metadata

Modules

acquisition

Acquisition-related signals

navigation

Navigation-related signals

purchase

Purchase-related signals

session

Session-related signals

signal

General signal parameters