Configuration Guide
The Glood Hydrogen SDK supports both basic and advanced configuration patterns to fit different use cases and environments.Configuration Overview
The SDK follows a zero-configuration principle with sensible defaults, while providing full customization options for advanced use cases.Configuration Hierarchy
- Basic Configuration - Only API key and domain required
- Client-Level App Config - Override app settings in main config
- App-Level Config - Individual app module configuration
- Environment Variables - External configuration management
Basic Configuration
Minimal Setup
The simplest configuration requires only your API key and Shopify domain:- ✅ All apps enabled with default endpoints
- ✅ Pixel tracking enabled for all apps
- ✅ Default consent requirements per app
- ✅ Automatic event subscriptions
- ✅ Production-ready configuration
Basic with Debug Mode
Enable debug logging for development:Selective App Usage
Enable only specific apps to reduce bundle size:Advanced Configuration
Client-Level App Configuration
Override app settings in the main client configuration:App-Level Configuration
Configure individual apps with custom settings:Environment-Specific Configuration
Multi-Environment Setup
Configure different settings for different environments:Environment Variables
Use environment variables for external configuration:Privacy & Consent Configuration
Default Consent Requirements
Each app has different default consent requirements:Custom Consent Configuration
Customize consent requirements for compliance:Consent Scenarios
Different configurations for different privacy requirements:Event Subscription Configuration
Default Event Subscriptions
By default, each app subscribes to all relevant events:Custom Event Subscriptions
Limit events for specific use cases:Performance Configuration
Development Optimization
Optimize for development experience:Production Optimization
Optimize for production performance:Testing Configuration
Test Environment Setup
Configuration for testing environments:Mock Configuration
For testing with mocked services:Configuration Validation
Runtime Validation
Add validation for production deployments:TypeScript Configuration Validation
Use TypeScript for compile-time validation:Best Practices
1. Environment-Based Configuration
Use different configurations for different environments:2. Gradual Rollout
Start with minimal configuration and gradually add features:3. Privacy-First Configuration
Design configurations with privacy in mind:4. Configuration Documentation
Document your configuration choices:Configuration Examples
See the Examples section for complete configuration examples:- Basic Setup - Simple configuration
- Advanced Configuration - Custom endpoints and settings
- Privacy Configuration - GDPR/CCPA compliance
- Environment Configuration - Multi-environment setup
See Also
- Installation Guide - Getting started
- API Reference - Complete API documentation
- Content Security Policy - CSP configuration
- Types Reference - TypeScript interfaces