Race Notifications
Race Notifications allow event organizers to automatically send email and SMS updates based on race activity.
Notifications can be triggered by race results or live race progress, and can be delivered to both participants and subscribed fans in the Events App.
Overview
Race notifications are managed in RUFUS Cloud and are triggered by activity coming from RUFUS Race Manager (RRM).
They are part of the live event flow:
RRM generates race data (results, checkpoint passings).
RUFUS Cloud evaluates notification rules.
Notifications are sent to participants and/or fans.
Supported Notification Types
You can create:
Email notifications
SMS notifications
Both types share the same trigger logic and audience configuration.
Notification Triggers
Notifications can be triggered by:
Finish Result
Sends a notification when a participant receives a valid finish result.
Typically used for final race summaries.
Triggered once per participant when results are published.
Checkpoint Progress
Sends a notification when a participant passes selected checkpoints.
Can be configured for one or multiple checkpoints.
Useful for live tracking during the race.
Can trigger multiple notifications per participant.
Creating a Race Notification
To create a notification:
Go to RUFUS Cloud → Events → Notifications.
Click Create notification.
Select the notification type (Email or SMS).
Configure the message and delivery rules.
Activate the notification.
Message Configuration
Email
Supports subject and message body.
Allows dynamic fields.
SMS
Supports a single message field.
Character limits apply depending on encoding.
Credit usage is calculated per message.
Dynamic Fields
Both email and SMS messages support dynamic fields, such as:
{{name}}, {{lastname}}
{{racetime}}, {{pace}}
{{race}}, {{event_name}}
{{bib}}, {{club}}, {{team}}
{{global_rank}}, {{gender_rank}}, {{age_group_rank}}
These fields are replaced with participant-specific values at send time.
Delivery Rules
Each notification includes delivery configuration:
Send when: Finish result or checkpoint progress
Race scope: Whole event or specific race
Watched checkpoints (for progress notifications)
Audience
Notifications can be sent to:
Participants All participants with valid contact information (email or phone)
Fans Users who subscribe to specific participants in the Events App
Both audiences can be enabled independently.
Estimates and Credits
Each notification shows real-time estimates:
Audience size
Number of sends
Credits required (for SMS)
Delivery status
For SMS notifications, you can configure:
Maximum credits per message
This helps control costs when messages exceed standard length.
Activation and Management
Notifications can be:
Activated or deactivated at any time
Edited while inactive or active
Deleted when no longer needed
You can also:
Monitor delivery status (sent, success, pending)
Reset notifications to allow re-sending
Test configurations before activation
Fan Subscriptions
When enabled, fans can subscribe from the RUFUS Events App to receive updates for specific participants.
Subscriptions are linked to:
Selected participant
Notification type
Event
Participants do not need to subscribe. They can receive notifications directly if they have valid contact details and are included in the audience.
Race Day Behavior
During the event:
Checkpoint progress notifications are triggered as participants pass configured checkpoints.
Finish result notifications are triggered when results are published or updated.
Notifications are processed automatically based on configured rules.
This enables real-time communication with both participants and followers.
Notes
Notifications depend on published event data.
Participant contact information must be valid.
SMS delivery consumes credits based on message length.
Resetting notifications is required to re-trigger already sent messages.
Race Notifications provide a flexible communication layer for live events, combining real-time race data with automated delivery to participants and audiences.
Last updated