Execution & Monitoring

Once an orchestration is activated, Zeotap provides real-time visibility into how customers move through the canvas. This page covers the monitoring tools, metrics, and operational controls available for active orchestrations.

Orchestration Dashboard

The orchestration detail view switches from the canvas editor to the execution dashboard when an orchestration is active. The dashboard provides:

Real-time canvas overlay — The canvas displays live counts on each tile and edge, showing how many customers are at each step
Summary metrics — Key performance indicators at the top of the page
Activity timeline — A chronological log of orchestration events (entries, exits, errors)
Export controls — Download orchestration data for external analysis

Summary Metrics

The top of the execution dashboard displays these key metrics:

Metric	Description
Active members	Number of customers currently in the orchestration (not yet exited)
Total entered	Cumulative count of customers who have entered the orchestration since activation
Total exited	Cumulative count of customers who have exited (via exit tiles or exit criteria)
Conversion rate	Percentage of entered customers who exited via a “converted” exit tile
Average duration	Average time a customer spends in the orchestration from entry to exit
Error rate	Percentage of action executions that failed across all action tiles

Metrics update in near-real-time (typically within 1-2 minutes of the underlying events).

Per-Tile Analytics

Click any tile on the execution canvas to view its detailed analytics:

Entry Tile

Metric	Description
Total entries	Cumulative customers who entered through this tile
Entry rate	Average entries per hour / day
Re-entries	Count of customers who entered more than once (if re-entry is enabled)
Entry sources	Breakdown by trigger type (audience join, event, manual)

Wait Tile

Metric	Description
Currently waiting	Customers currently paused at this tile
Completed waits	Customers who completed the wait and proceeded
Timed out	Customers who hit the timeout on a condition wait
Average wait time	Average actual time customers spent waiting

Branch Tile

Metric	Description
Total evaluated	Customers who reached and were evaluated by this branch
Per-branch counts	How many customers took each branch
Per-branch percentages	Actual distribution across branches
Else count	Customers who matched no condition and took the else path

Action Tile

Metric	Description
Total executed	Number of times this action was triggered
Succeeded	Successful executions
Failed	Failed executions (after all retries)
Retried	Executions that required one or more retries
Average latency	Average time to complete the action (including destination response time)
Error breakdown	Errors grouped by type (timeout, rate limit, auth failure, invalid data)

Update Profile Tile

Metric	Description
Total updates	Number of profile updates applied
Unique customers	Distinct customers whose profiles were updated

Webhook Tile

Metric	Description
Total calls	HTTP requests made
Success (2xx)	Requests that returned a success status
Client errors (4xx)	Requests that returned client error status
Server errors (5xx)	Requests that returned server error status
Timeouts	Requests that timed out
Average response time	Average HTTP response time in milliseconds

Exit Tile

Metric	Description
Total exits	Customers who reached this exit tile
Exit label breakdown	If multiple exit tiles exist, shows counts by label

Conversion Tracking

Conversions are tracked by assigning labels to Exit tiles. A common pattern:

Exit Label	Meaning
`converted`	Customer completed the desired action (e.g., made a purchase)
`timed_out`	Customer hit the orchestration’s time limit without converting
`unsubscribed`	Customer opted out during the orchestration
`exit_criteria`	Customer met a global exit condition
`completed`	Customer reached the end of the orchestration naturally

The conversion rate is calculated as:


Conversion Rate = (Exits labeled "converted") / (Total entered) * 100

You can customize which exit labels count as conversions in the orchestration settings.

Conversion Funnel

The execution dashboard includes a funnel view that shows drop-off at each stage:

Activity Timeline

The activity timeline shows a chronological feed of events:

Customer entered — With entry details (trigger type, customer ID)
Customer moved to tile — Which tile the customer advanced to
Action executed — Success or failure with destination response details
Customer exited — With exit label and duration in orchestration
Error occurred — With error type, affected tile, and retry status
Orchestration paused/resumed — Operational state changes

The timeline supports filtering by:

Event type (entries, exits, errors, actions)
Time range
Customer ID (to trace a specific customer’s path)
Tile (to see all activity for a specific step)

Operational Controls

Pausing an Orchestration

Pausing an orchestration stops all processing without losing state:

Click Pause in the orchestration header
Confirm the pause action

When paused:

No new customers enter the orchestration
Active members are frozen at their current tile (wait timers pause)
No action tiles execute
The orchestration status changes to Paused

Resuming an Orchestration

Click Resume in the orchestration header
Confirm the resume action

When resumed:

New customers begin entering based on entry criteria
Active members resume from where they were paused
Wait timers continue from where they left off (the pause duration does not count toward wait times)
Action tiles begin executing again

Editing an Active Orchestration

Active orchestrations support limited edits without pausing:

Edit Type	Allowed?	Notes
Change tile configuration	Yes	Takes effect for new customers reaching that tile
Add new tiles after existing ones	Yes	Only new customers will reach the new tiles
Remove tiles	No	Must pause and create a new version
Change entry criteria	No	Must pause and create a new version
Change exit criteria	Yes	Takes effect immediately for all active members

For major structural changes, the recommended approach is:

Pause the current orchestration
Duplicate it
Make changes to the duplicate
Activate the new orchestration
Complete (archive) the old orchestration, allowing active members to finish

Manually Adding or Removing Members

Add members: Click Add Members and upload a CSV of customer IDs, or use the API
Remove members: Search for a customer by ID and click Remove from Orchestration, or use the API


# Add members via API
POST /api/v1/journeys/{id}/members
{
  "customer_ids": ["cust_123", "cust_456", "cust_789"]
}
 
# Remove a member via API
DELETE /api/v1/journeys/{id}/members/{customer_id}

Alerting

Configure alerts to get notified about orchestration issues:

Alert Type	Trigger	Default Threshold
High error rate	Action failure rate exceeds threshold	> 5% in a 1-hour window
Low entry rate	Fewer entries than expected	< 50% of average entry rate
Stalled members	Customers stuck at a tile beyond expected time	Configurable per orchestration
Orchestration completed	All active members have exited	N/A

Alerts are sent via the workspace’s configured notification channels (email, Slack, webhook).

Exporting Orchestration Data

Export orchestration execution data for external analysis:

Export Type	Contents	Format
Member list	All current and historical members with their orchestration path	CSV
Execution log	Timestamped record of every tile transition and action execution	CSV or JSON
Metrics summary	Per-tile and per-branch aggregated metrics	CSV

Exports are available from the Export menu in the orchestration header. Large exports are processed asynchronously and delivered via download link.

Troubleshooting

Symptom	Possible Cause	Resolution
Active members count is stuck	Wait tiles with long durations or unmet conditions	Check wait tile configurations; verify conditions are achievable
Conversion rate is unexpectedly low	Branch conditions may be routing most customers to a non-converting path	Review branch analytics to see the actual distribution
High error rate on action tile	Destination may be down or rate-limiting	Check destination health; review error details in tile analytics
Customers not entering	Entry criteria may not match any customers	Verify the audience has members or the event is being sent
Orchestration metrics not updating	Processing delay or orchestration may be paused	Check orchestration status; wait 2-3 minutes for metrics to refresh