klaviyo-multi-env-setup

# Klaviyo Multi-Environment Setup ## Overview Configure Klaviyo across development, staging, and production with separate API keys, environment detection, secret management, and production safeguards. ## Prerequisites - Separate Klaviyo accounts or API keys per environment - Secret management solution (GCP Secret Manager, AWS Secrets Manager, Vault) - `klaviyo-api` SDK installed ## Environment Strategy | Environment | Klaviyo Account | API Key | Use Case | |-------------|----------------|---------|----------| | Development | Test account | `pk_test_dev_***` | Local development, exploration | | Staging | Test account | `pk_test_staging_***` | Pre-prod validation, integration tests | | Production | Production account | `pk_live_***` | Real customer data, live sends | > **Important:** Klaviyo does not have a sandbox mode. Use a separate test account for dev/staging to avoid sending real emails. ## Instructions ### Step 1: Environment Configuration ```typescript // src/config/klaviyo.ts import { ApiKeySession } from 'klaviyo-api'; type Environment = 'development' | 'staging' | 'production'; interface KlaviyoEnvConfig { privateKey: string; revision: string; webhookSecret: string; enableSending: boolean; rateLimitConcurrency: number; cacheEnabled: boolean; cacheTtlMs: number; } function detectEnvironment(): Environment { const env = process.env.NODE_ENV || 'development'; if (['production', 'staging'].includes(env)) return env as Environment; return ...