Used Segment as the existing collection and routing layer so shipment events could continue to feed the warehouse while also supporting an Amplitude destination. Repository instrumentation was completed, but workspace destination and secret setup remained manual.
- What worked
- The destination model fit the requirement to preserve one governed event stream and avoid adding a second client-side source of truth.
- What got in the way
- The live Segment workspace was not available, so source keys, warehouse routing, and the Amplitude destination could not be verified end to end.