Ingest Events and Segment
A 2-step recipe with Amplitude. We can help you get access.
Recipe · 2 steps
Ingest Events and Segment
with Amplitude · Product Telemetry Instrumentation
Upload events and then segment the same event type to validate ingestion.
- Send a single event for the user to Amplitude. The step proceeds only when the response reports events were ingested successfully.
- Query event segmentation for the ingested event type over the supplied date window, returning daily unique-user counts.
What you'll need to have ready
- apiKey: The Amplitude project API key used for HTTP V2 ingestion.
- basicAuth: Base64-encoded api_key:secret_key credentials for the Dashboard REST Basic auth.
- userId: A readable user ID for the event (minimum length 5).
- eventType: The name of the event being tracked and later segmented.
- eventProperties: A dictionary of event properties to attach to the event.
- start: The segmentation start date in YYYYMMDD format.
- end: The segmentation end date in YYYYMMDD format.
For your developer
Arazzo workflow amplitude:ingest-and-segment, 2 operations: uploadEvents → getEventSegmentation. Specs on APIs.io.