optimizely-exp-events

Optimizely Events Agent

Analyze event tracking implementation, conversion events, and event properties.

Analysis Areas

1. Sensitive Data in Events

EVT-001: Sensitive Data in Event Properties (Critical)

Events should not contain PII or sensitive data:

Grep: track\(.*email
Grep: track\(.*password
Grep: track\(.*ssn
Grep: track\(.*creditCard
Grep: track\(.*phone

Bad Pattern:

// PII in event properties!
optimizely.track('signup_completed', userId, {
  email: user.email,           // PII!
  phone: user.phone,           // PII!
  address: user.address,       // PII!
});

Good Pattern:

// Anonymized/aggregated data only
optimizely.track('signup_completed', userId, {
  signupMethod: 'email',       // Category, not actual email
  country: user.country,       // Aggregatable
  userType: 'free',            // Segment
});

2. User Context in Events

EVT-002: Events Without User Context (Warning)

Events need user context for proper attribution:

Grep: track\(\s*["'][^"']+["']\s*\)
Grep: track\(\s*["'][^"']+["']\s*,\s*null

Bad Pattern:

// No user context!
optimizely.track('purchase');

// Or null user ID
optimizely.track('purchase', null, { revenue: 99 });

Good Pattern:

// With user context
const userContext = optimizely.createUserContext(userId, {
  membershipTier: user.tier,
  country: user.country,
});

userContext.trackEvent('purchase', {
  revenue: 9900, // In cents
  currency: 'USD',
});

3. Event Batching

EVT-003: No Event Batching Configured (Warning)

Events should be batched for efficiency:

Grep: eventBatchSize
Grep: eventFlushInterval
Grep: eventDispatcher

Good Pattern:

const optimizely = createInstance({
  sdkKey: SDK_KEY,
  eventBatchSize: 10,           // Batch 10 events
  eventFlushInterval: 1000,     // Flush every 1s
});

4. Event Documentation

EVT-004: Custom Events Not Documented (Info)