Skip to main content

​
Pre-Built Tooling

​
Objects Supported

Alloy Automation supports sending the following event types to Segment:
  • Track Events - User actions and behaviors
  • Identify Events - User profile information
  • Page Events - Page views
  • Screen Events - Mobile screen views
  • Group Events - Account-level data
  • Alias Events - User identity mapping

​
Set Up Guide

​
Trial Access

​
Authentication (Write Key)

Segment uses a Write Key for server-side authentication. This is a simple API key approach.

​
Use Cases

​
1) Unified customer data pipeline

Send user behavior events from your application to Segment, which then routes the data to downstream tools like analytics platforms, marketing automation, and data warehouses, creating a single source of truth.

​
2) Cross-platform user tracking

Track user actions across web, mobile, and server-side applications by sending events to Segment from multiple sources, enabling comprehensive user journey analysis.

​
3) Real-time personalization triggers

Send identify and track events to Segment when users perform specific actions, triggering personalized experiences in marketing tools, email platforms, or in-app messaging systems.

​
4) Product analytics enrichment

Enhance product analytics by sending custom events with detailed context (user properties, product interactions, feature usage) to tools like Amplitude, Mixpanel, or Heap via Segment.

​
5) Customer lifecycle automation

Trigger lifecycle workflows in CRM and marketing automation platforms by sending key milestone events (signups, activations, churns) through Segment’s event routing.

​
API Gotchas

  • Event Batching: Segment supports batch API calls to send multiple events in a single request. Use batching for high-volume scenarios to reduce API overhead and improve throughput. Batch size limit is 500 KB or 15,000 events per request.
  • Timestamp Handling: Segment accepts an optional timestamp field for events. If omitted, Segment uses the time the event was received. For historical data imports or delayed events, always include an explicit ISO 8601 timestamp.
  • User Identity Resolution: Segment uses userId and anonymousId to track users. For logged-in users, always send userId. For anonymous users, send anonymousId. Use the alias call to merge anonymous and identified user profiles.
  • Event Naming Conventions: Follow Segment’s event naming best practices: use Title Case (e.g., “Order Completed”), keep names concise, and avoid past tense. Consistent naming ensures proper routing and analysis in downstream tools.
  • Rate Limiting: Segment enforces rate limits based on your plan. The free tier allows up to 1,000 visitors/month. Higher tiers support more volume. If you exceed limits, requests will be throttled or rejected with 429 status codes.
For questions or troubleshooting, contact support@runalloy.com.