Use Datadog RUM as worker input
Updated September 23, 2026 · 1 min read
Once Datadog is connected, use RUM as a batch input on a Scheduled Trigger or Run Worker so each unit represents a real product user, session, or event.
Pick what a run represents
Choose one run per logged-in user (grouped by email or user ID), one run per visitor session, one run per event, or a custom facet under Advanced.
Configure the input
- On a Trigger or Run Worker, set Input to Datadog RUM.
- Pick a RUM application, then an event name — use See suggestions to pick from real recent action names instead of typing one blind.
- Choose the intent, identity field, and lookback window.
- Check the live preview — it shows events matched and runs that will be queued before you commit.
FAQ
What if visitors aren't logged in?
Choose one run per visitor session, or one run per event, instead of grouping by email or user ID.
How many runs can one batch queue?
Up to 1500; a high-volume event may need a narrower filter to stay under the cap.
How far back does RUM data go?
Typically 30 days — a lookback beyond that returns nothing.
Can I see the raw payload before mapping fields?
Yes — the live preview includes up to 5 sample payloads, and Copy sample payload pre-fills Input Settings' test data.
Related articles
- Connect Datadog
Add a Datadog API key then map RUM unique users into scheduled worker batches.
- Set worker input fields
Define typed input fields so Zentesimal maps spreadsheet rows, JSON, or free text into them before the worker runs.
- Add a trigger to a worker
Add a live or scheduled trigger so a worker only runs on the events you choose.