This component enables seamless integration between Edgee and Google Analytics, allowing you to collect and forward analytics data while respecting user privacy settings.

1. Download the latest component version from our releases page
2. Place the ga.wasm file in your server (e.g., /var/edgee/components)
3. Add the following configuration to your edgee.toml:

[[components.data_collection]]
id = "google_analytics"
file = "/var/edgee/components/ga.wasm"
settings.ga_measurement_id = "G-XXXXXXXXXX"  # Your GA4 Measurement ID

The component maps Edgee events to Google Analytics events as follows:

User events serve multiple purposes:

• Triggers an user custom event call to GA4
• Stores user_id, anonymous_id, and properties on the user's device
• Enriches subsequent Page and Track events with user data
• Enables proper user attribution across sessions

[[components.data_collection]]
id = "google_analytics"
file = "/var/edgee/components/ga.wasm"
settings.ga_measurement_id = "G-XXXXXXXXXX"

# Optional configurations
settings.edgee_anonymization = true        # Enable/disable data anonymization in case of pending or denied consent
settings.edgee_default_consent = "pending" # Set default consent status if not specified by the user

Control which events are forwarded to Google Analytics:

settings.edgee_page_event_enabled = true   # Enable/disable page event
settings.edgee_track_event_enabled = true  # Enable/disable track event
settings.edgee_user_event_enabled = true   # Enable/disable user event

Before sending events to Google Analytics, you can set the user consent using the Edgee SDK:

edgee.consent("granted");

Or using the Data Layer:

<script id="__EDGEE_DATA_LAYER__" type="application/json">
  {
    "data_collection": {
      "consent": "granted"
    }
  }
</script>

If the consent is not set, the component will use the default consent status.

Prerequisites:

• Rust
• WASM target: rustup target add wasm32-wasip2
• cargo-llvm-cov: cargo install cargo-llvm-cov

Build command:

edgee component build

Interested in contributing? Read our contribution guidelines

Report security vulnerabilities to [email protected]