Alerts and Scheduled Digests

Use SiteTrax.io notifications when you want an email about a new matching detection, a check on a list of expected units, or a scheduled summary of stored readings. Set them up through a connected assistant, review the exact settings, and confirm before anything is created. A request for a report does not automatically authorize a recurring email. Once a notification exists, you can also pause, resume or cancel it from the Intelligence screen in the application.

Choose a notification

Need	Choose	What it does
Tell me when this identifier is next observed	Detection alert	Watches for a new stored detection matching a supported identifier or filter. A one-time alert completes after the first match.
Keep watching for matching detections	Repeating detection alert	Continues watching until cancelled, paused or expired. The repeat rule suppresses further emails for the same asset text at the same project for six hours; a matching detection at another project is evaluated separately.
Tell me when all of these units have arrived, or what is still missing by a deadline	Expectation watch	Records each listed identifier's first matching detection without emailing, then sends one email: when every listed unit has arrived, or at the deadline with the units still missing.
Send a regular operational breakdown	Scheduled digest	Emails a saved query at a local time on the chosen days, covering the period since the previous edition.
Check a condition every few minutes or hours	Interval digest	Runs a saved query every 15 to 1,440 minutes and emails only when the result is not empty, for example when a visit has exceeded a stated duration.

Any of these can carry an instruction for an AI-written summary at the top of the email; see AI-written email text. They are defined notification workflows over SiteTrax.io detections. They do not provide arbitrary automation, a custom-recipient mailing service, actions in other systems, or a guarantee of real-time physical presence. A new observation means the unit was recorded at that time; it does not prove where it is now.

Before you start

• Connect a supported assistant using your active, verified SiteTrax.io account. See Account Access and OAuth.
• Check that the intended projects are shared with that account.
• Allow read access to list notifications and inspect delivery history. Creating an alert or digest, or cancelling either from an assistant, also needs notification-management permission.
• Use your own verified account email as the destination. The tools do not accept another person's address or an arbitrary distribution list.

Your assistant may request notification permission when you first connect or when you ask to create or cancel something. The timing depends on the client. Permission allows the capability; it does not replace your confirmation of each proposed change.

Notification creation and cancellation through an assistant require the client to request and receive sitetrax:notifications:write in addition to read access. A read-only connection cannot perform those actions, and repeating the same read-only authorization request does not add permission. Check your provider’s dedicated setup section for its supported tools and consent flow.

Create a detection alert

Decide the full identifier or supported condition, the projects to watch, whether it should stop after one match, and when it should expire. Ask the assistant to resolve ambiguous project names and confirm the identifier before proposing the alert.

Using SiteTrax.io, help me prepare a one-time email alert for the next new detection of the container I specify at the project I choose. First confirm the full identifier and project. Then show the exact condition, whether direction is included, one-time behavior, recipient policy, title and expiry. Ask for my explicit confirmation before creating anything.

For an arrival or departure alert, ask the assistant to check how gate direction is configured. The alert tool's optional direction filter always uses the detection's heading and direction configuration. For a dedicated ingate or outgate project or camera, select that project or camera and leave the heading filter out unless you intend to apply both conditions.

After you approve, the assistant should return the saved notification ID and summary. Ask it to list the notification so you can check its status and expiry. Saving an alert confirms its configuration; it does not prove that a matching detection has occurred or that an email has reached your inbox.

Detection alerts evaluate newly stored matching rows. They do not trigger simply because time has elapsed without another detection, and an interactive analysis does not automatically become an alert. To be told when a calculated condition such as a long visit becomes true, use an interval digest.

Watch for an expected list

An expectation watch answers "have all of these arrived by this time?". Give the assistant the complete identifiers (up to 500), the projects to watch and a deadline with an explicit timezone offset, for example 2026-11-02T17:00:00-05:00. The deadline must be in the future and within 366 days.

Using SiteTrax.io, prepare an expectation watch for these trailers at the project I choose, with a deadline of Friday 17:00 America/Chicago. Show the exact identifiers, projects, deadline with its offset, and title, then ask me to confirm before creating it.

Arrivals are recorded silently in delivery history as they are matched. You receive exactly one email: as soon as every listed unit has a matching detection, or at the deadline listing the units that have not been observed. A missing unit means no matching detection was stored in the watched projects; it does not prove the unit is absent from the site.

Create a scheduled digest

Choose the project scope, what to measure, optional filters, the schedule, an IANA timezone and the expiry.

A scheduled digest has one local send time on each selected day: daily, weekdays, weekends, weekly on Monday, or specific weekdays such as Monday, Wednesday and Friday. The defaults are daily at 08:00 UTC. Specify a timezone such as America/New_York instead of an ambiguous abbreviation. Monthly recurrence is not supported.

An interval digest replaces the send time with a repeat interval of 15 to 1,440 minutes, still limited to the selected days. It skips any run whose result is empty, so it suits "tell me when something qualifies" checks.

Using SiteTrax.io, propose a weekday digest for the project I choose, sent at 08:00 America/New_York. Use stored-reading counts grouped by processing status and asset type, with a 30-day expiry. Show the exact project, filters, measures, schedule, recipient policy, title and reporting-window rule, and preview it first. Ask for my explicit confirmation before scheduling it.

Each edition covers the interval since the preceding edition, starting from creation for the first. A Monday weekday digest includes the weekend. Ask to see the stored window in delivery history when comparing two editions.

What a digest can report

A basic digest groups stored readings by up to two fields, such as project, camera, processing status or asset type, and reports stored-reading count (count), distinct stored text values (distinct_assets) or A0 reading count (a0_count).

A digest can also save a fuller query using the same server-side analytics an assistant uses interactively: typed measures, group-level conditions, consecutive-event gaps, ordered-stage sequence analysis such as gate-in to gate-out visits, and supporting records. The schedule supplies the reporting window, so a saved sequence query does not set its own start and end. Video analytics are not available in digests.

Ask for a preview before saving. A preview runs the proposed query once over the last 24 hours, returns the result and saves nothing, which shows whether the query is valid and useful. Any AI-written text is produced only when a real edition is sent.

A basic digest groups hour, day, weekday, week or month buckets in UTC. A digest with a saved query, an AI instruction or an interval groups those buckets in the digest's timezone. Ask the assistant which applies when the boundaries matter.

A digest displays up to 200 groups, ordered by its first metric. The overall totals cover the full filtered reporting window, so a long grouped table may omit smaller groups and may not add up to the overall total. Narrow the scope or choose a broader grouping when a complete breakdown is needed.

A count of stored readings is not a count of physical equipment. Distinct identifier metrics also need a clear definition. Ask the assistant to explain the returned measure and any incomplete or bounded result instead of relabelling it as inventory, throughput, or financial savings.

AI-written email text

An alert, expectation watch or digest can include a short instruction (up to 2,000 characters), such as "Summarize which trailers have been on site longest and flag anything over 48 hours." When the notification sends, a language model writes a short summary from that edition's result. The deterministic result table is always included beneath it.

• The model receives only that edition's result and your instruction. It has no tools and cannot take actions.
• Numbers above 10, and any number with decimals, must appear in the data, and links other than SiteTrax.io application links are removed.
• Model-written summaries are limited to 50 per user per day. If the limit is reached or the model step fails, the email is sent with the table alone.

Treat the summary as a reading aid. The table and the linked records remain the evidence.

Give it a title

Ask the assistant to add a short, plain title, such as "Morning gate activity", when it creates a notification. The title identifies the notification on the Intelligence screen and in notification lists. It does not change what is matched or scheduled, and emails continue to use the generated summary. Notifications created without a title are shown by their summary.

Review, pause or cancel a notification

In the application

Open Intelligence in app.sitetrax.io. The Notifications section lists your alerts, expectation watches and digests with their last match, last send, projects and expiry. Use Current and Ended to switch between live and finished notifications, and All, Alerts or Digests to filter by kind. The controls on each row pause, resume or cancel that notification.

Live application screenshot, captured 26 October 2026. Customer names are blurred.

• Pause stops matching and sending, including deliveries already queued. Detections stored while a notification is paused are not replayed afterwards.
• Resume restores an active notification. It is refused if the notification has already expired or you already have the maximum number of active notifications. A digest's first edition after resuming covers everything since its last send.
• Cancel ends the notification permanently.

From an assistant

Listing notifications and delivery history is read-only. You can ask:

Using SiteTrax.io, list all my notifications with their IDs, titles, types, status, project scope and expiry. Include recent delivery statuses, expectation progress and the reporting windows for digests. Do not change anything.

Notification status can be active, paused, completed, cancelled or expired. Delivery history can show queued, sent, failed, suppressed or recorded entries; recorded entries are the silent arrivals of an expectation watch. A sent entry means the mail service accepted the message; it does not prove inbox delivery, opening or reading. A failed send is retried three times before it is marked failed. Project access and verified recipient status are checked again when notifications are processed.

To cancel from an assistant, give the exact notification ID, ask it to show the proposed cancellation, and confirm. The same cancellation tool applies to alerts, expectation watches and digests. Pausing and resuming are done in the application. To change a saved condition or schedule, cancel and create a replacement; there is no general edit command.

Limits and missing emails

Notifications expire after 30 days by default. Ask for the intended expiry explicitly and check the saved value; an expiry setting of zero means the 30-day default, not an indefinite subscription. An expectation watch stays open at least until its deadline. The current limit is 50 active notifications per user across all kinds; cancel an unused one if you reach it.

Notifications are processed asynchronously. A detection must be stored and matched before its email is queued, and a due digest or expectation deadline is picked up by the scheduled runner. Allow for ingestion, processing and mail-delivery delay rather than treating the selected time as an exact delivery guarantee.

If an email does not arrive, first inspect the notification and its delivery history. Check whether it is paused, expired, cancelled or completed, its filters, current project access, email verification, the digest timezone and selected days, repeating-alert suppression, and whether an interval digest simply had an empty result. An event alert needs a new matching detection; a digest needs a due schedule. Then check your inbox filters and contact [email protected] with the notification ID, expected time, and visible status. Never include credentials.