Asset Intelligence offers two notification types and two delivery channels. This article explains what each one delivers, how alert timing works, and how to decide which combination fits your workflow.
Alert types
When you set up an alert in Asset Intelligence, you choose how you want to be notified about new matching sightings.
Alert type | What you receive | Best for |
Daily Summary | All new matching sightings combined into one daily notification | Routine monitoring where a once-a-day roll-up is enough |
Per Sighting | A separate notification for each matching sighting as it is processed and becomes available | Active investigations or assets you need to follow closely |
Both options draw from the same sighting data. The difference is packaging: one consolidated update versus individual notifications as activity comes in.
Notification channels
Alert type controls how often you hear from us. Notification channel controls where the alert goes.
Channel | What you receive | Best for |
A readable message with the matching sightings, sent to the alert's primary address and any CC recipients | People who review matches directly | |
Webhook | A JSON payload posted to your HTTPS endpoint with full match detail | Systems that ingest matches automatically |
You can use one channel or both. Email is the default if you do not specify a channel. Webhook and email notifications are generated from the same alert rules and sent during the same processing cycle, so enabling a webhook gives you the same matches you would receive by email.
Setting up email notifications
Email requires no additional setup. Every alert has a primary email address, and you can add CC recipients so a team distribution list or a shared inbox receives the same notification.
For step-by-step setup instructions, see Setting Up Asset Locator Email Alerts.
Setting up a webhook
Webhooks are configured separately from alerts and apply at the company level. Once you register a webhook URL, every active alert in your organization sends its matches to that endpoint, including alerts created later. You can register more than one URL.
To set one up:
Confirm your API user has the admin or create-alert-webhook-endpoint permission.
Register your endpoint with a POST to
https://api.genlogs.io/alerts/webhook. The URL must use HTTPS.Provide a secret of at least 16 characters, or let GenLogs generate one for you. The secret is used to sign every payload.
Send a test payload to your endpoint before you rely on it in production.
Each request arrives with an X-GenLogs-Signature header containing an HMAC-SHA512 signature of the payload. Verify that signature against your secret to confirm the request came from GenLogs.
What the webhook payload contains
The payload uses the event type alert.matches_found and includes every match found across your alerts in that processing cycle. Each match carries the sighting time, city, state, road, and coordinates, the identifiers read from the truck, links to the front, side, and rear images, and a link to the result in the GenLogs application. Image URLs expire one month after delivery.
Matches also include a confidence_score for the read overall, along with per-field OCR scores for USDOT number, MC number, VIN, cab number, trailer number, and trailer logo. Each is classified as High, Medium, Low, or N/A. These fields require permission access on your account.
Full field definitions are in the webhook specifications.
How alert timing works
Per Sighting notifications are sent as sightings become available. Note that this is not the same as real time. Several steps happen between a truck passing a sensor and a notification landing in your inbox:
The sighting is captured by a GenLogs sensor.
Sighting data is transmitted over the cellular network.
GenLogs processes the sighting.
The sighting is matched against your alert criteria.
The notification is delivered.
Timing can vary across those steps. For instance, cell tower reception in remote areas may be slower than more urban areas, resulting in a longer data backhaul window in step two.
We measure latency across the full pipeline and continue working to reduce it in the areas we control.
Frequently asked questions
How quickly will I receive a Per Sighting notification?
Per Sighting notifications are sent as matching sightings are processed and become available. Timing varies depending on network conditions and processing time.
Is Per Sighting real time?
No. Per Sighting is not a real-time detection service. A notification is sent once a matching sighting has been transmitted, processed, and made available in Asset Intelligence.
Are Per Sighting alerts sent on a fixed schedule?
No. Per Sighting alerts are triggered by new activity rather than a set interval. You receive a notification when a new matching sighting becomes available, not at a recurring time.
Why did my alert arrive later than I expected?
Timing can vary between when a sighting occurs and when the notification reaches you. Cellular transmission, processing, and delivery each contribute. If a specific alert seems significantly delayed, send us the details so our team can investigate.
Can I change my alert type after setting it up?
Yes. You can update the notification type and channel on an existing alert at any time. The change applies to sightings processed after you save it.
Can I limit an alert to high confidence matches only?
Not at the alert level. Alerts are not configured with a confidence threshold, so every match that meets your search criteria is sent. If you need to filter by confidence, use the webhook channel and apply your own threshold to the confidence_score and per-field OCR score values in the payload.
Choosing what fits your workflow
If you are tracking an asset actively and want to know about movement as soon as it is available, choose Per Sighting. If you are monitoring for general awareness and prefer a single update instead of a stream of notifications, choose Daily Summary.
You can use different options for different alerts. A high-priority asset can run on Per Sighting while everything else stays on Daily Summary.
Choose your channel the same way. Email works when a person reads each match. Webhook works when a system does.
Need help configuring your alerts? Reach out to us at [email protected].