Event Information

Timer Tip Tuesday: Race Result Integration with RunSignup

Learn how to integrate Race Result with RunSignup

1. Understand how to connect the two platforms to sync participant registration data and push results directly to RunSignup
2. Discover best practices for setup and configuration to ensure accurate, real-time results delivery to participants

Who should attend: Timers using Race Result software who want to leverage RunSignup’s registration and results integration

View Slides

Webinar Summary

Overview

This Timer Tip Tuesday covers the full Race Result integration with RunSignup in two parts. The first and primary focus is the new results publishing feature, which allows timers to map Race Result listings directly to RunSignup result sets and publish live results automatically — with divisions, splits, notifications, and dynamic field management all included. The second part is an update on the bidirectional registration sync, with key reminders and recent improvements relevant to timers who are adding results publishing to their workflow.

All setup documentation referenced throughout this session is available directly on your Race Result dashboard under Race Day Tools > External Partners > Race Result > Setup Instructions.

Part 1: Results Publishing — Race Result to RunSignup

Key Terminology

Before diving into setup, it helps to understand how the two platforms map to each other:

The most important concept: a single Race Result listing maps to a single RunSignup result set. Race Result timers accustomed to multi-section reports with contest dropdowns will need to rethink their listing structure — one table in, one result set out.

Required Fields for Results Publishing

Two fields are required in every Race Result listing used for RunSignup results publishing:

• RunSignup Participant ID — This is the registration ID from RunSignup. It is the critical link between Race Result data and RunSignup participant records. The mapping will not work without it.
• Place — The field that drives the row index (overall placement) for the result set. You choose whichever data expression in your listing controls placement and map it to this special RunSignup field.

All other fields in your listing will be brought over dynamically as custom fields in the RunSignup result set. You do not need to manually define fields at RunSignup — they are created automatically based on your listing.

A handful of additional standard fields are recognized by RunSignup and will be mapped accordingly if present in your listing, including bib, gender, pace, chip time, and clock time. Anything outside of these will simply become a custom field.

Setup Steps

1. Build your Race Result listing with the required RunSignup fields (Participant ID and Place) and any additional fields you want to display
2. Map the listing to a RunSignup result set from the Results area on your Race Result dashboard
3. Optionally configure rankings to divisions if you want filter dropdowns on the RunSignup result set (e.g., age groups, gender place, masters)
4. Optionally configure splits to publish if you want split data to drive RunSignup notifications
5. Set your results sync period — define the date and time window during which results should publish. Results will push every 60 seconds during this window.

Important: There is no default sync period for results publishing. Results will never publish unless you explicitly define that window. This is intentional — you are in full control of when results go live.

Rankings to Divisions (Optional)

If you want filter dropdowns on your RunSignup result set, map your Race Result rankings to RunSignup divisions. A few things to know:

• You can map any ranking you’ve built in Race Result — gender rank, masters rank, age groups, custom rankings, etc.
• If your ranking uses group by gender, the integration will automatically split that one ranking into separate male, female, and (if applicable) non-binary divisions at RunSignup
• You do not need to map your overall rank as a division — your table is already ordered by overall placement
• Divisions are completely optional. If you just want a clean single table with no filter dropdowns, skip this step entirely

Splits to Publish (Optional)

If you want split data to drive RunSignup notifications, you’ll need to set up a splits mapping. A few things to note:

• Splits mapped through this process are treated as a special data type at RunSignup, which is what enables notifications
• An optional label field can be added to each split in Race Result — this label will be used for display and notifications instead of the default split name
• If you do not set up the splits mapping, split data will still come over — it will just be treated as custom fields without driving any notification behavior

How RunSignup Manages the Result Set

Once you save your mapping and your sync period is active, RunSignup takes over management of the result set:

• The result set and all its fields are created automatically
• If you change a field in your Race Result listing, the change is reflected in RunSignup on the next 60-second sync cycle
• If you change or add rankings or splits, those updates are managed automatically as well
• If you delete a mapping, the associated result set is removed

Troubleshooting tip: If something doesn’t look right, the simplest fix is to delete the mapping and start fresh once your listing is configured the way you want. The result set will be recreated cleanly on the next sync cycle.

Preliminary Results

When setting up your result set mapping, you have the option to mark results as preliminary. When this setting is on, results will display on the race website with a “preliminary” tag, but they will not appear on individual participant profiles at RunSignup until the preliminary flag is removed.

FAQs and Important Notes

Can I create multiple result sets for the same contest? Yes. You can map multiple listings to the same contest — for example, an overall result set and a separate team result set. Each listing maps independently to its own result set.

Does team result linking work between result sets? Not at this time. Linked team/individual result sets (like those available in RaceDay Scoring) are not supported in the Race Result integration. You can still create a team result listing and publish it as its own table, but there will be no cross-linking between the team and individual result sets.

What if I have multiple contests mapped to one event and someone is added in Race Result? Adds and event transfers from Race Result will not sync back to RunSignup in a multi-contest mapping scenario. You will need to manage those additions manually at RunSignup. Single-contest mappings do support contest changes and event transfers.

What happens if there are duplicate Registration IDs in my result set? RunSignup will not accept duplicate registration IDs in the same result push. If duplicates are detected, the first record will publish and the second will be skipped. You will receive an automated email every 60 seconds alerting you to the issue with the result set name, row index, and registration ID until it is resolved. To pause alerts while you troubleshoot, temporarily turn off your results sync period.

Part 2: Registration Sync Refresher

The bidirectional registration sync between RunSignup and Race Result has now been used for over 1,600 events and is a well-established part of many timers’ workflows. This section covers key updates and reminders — particularly relevant for those adding results publishing to the mix.

Single-Directional vs. Bidirectional Sync

• Single-directional — Data flows from RunSignup down into Race Result only
• Bidirectional — Changes made in Race Result (via webhook) also push back up to RunSignup

If you are planning to use results publishing, you will almost certainly want the bidirectional sync enabled. Without it, corrections made in Race Result — including participant record updates — will not reflect in RunSignup, and those participants may not have a valid Registration ID linkage for results publishing.

Webhook setup tip: You only need to enable the Participant Update webhook. You do not need to add separate webhooks for new adds — new participants will flow through on the participant update event.

Sync Time Controls

A new feature now exposes sync time controls directly to you:

• Registration sync — Defaults to running from the moment you enable the sync through approximately 5–7 days after the event end date (to allow for corrections)
• Results sync — No default. You must explicitly define this window. Nothing will publish until you do.

You are in full control of both windows and can adjust or shut them down at any time from the sync times area on your dashboard.

Offline Mode Considerations

If you are working in offline mode in Race Result, the webhook will not fire changes back to RunSignup unless online forwarding is enabled. This means:

• Participant records updated while offline will not automatically sync to RunSignup
• You will need a process to trigger a change on those records after reconnecting to force the sync to recognize them
• Timers using kiosk for on-site adds should be especially aware of this behavior

Contest Name Matching

When you first enable the registration sync, RunSignup checks whether a contest with a matching name already exists in Race Result:

• If the names match — RunSignup will use your existing contest and will not create a new one
• If the names do not match — A new contest will be created

To avoid duplicate contests, temporarily align your Race Result contest names to match the event names your race director set up in RunSignup at the moment you enable the sync. Once the ID mapping is established, you can rename the contest back to whatever you prefer.

Bib Number Management

• Syncing blank bibs is off by default and is generally recommended to stay off
• Duplicate bib numbers in a sync batch will no longer fail the entire batch — instead, RunSignup will push all valid records and send you an automated email listing the registration IDs, first names, and last names that could not be synced
• Work closely with your race directors to keep bib assignments clean across all events in RunSignup

Additional Field Syncing

Most additional fields (custom questions, giveaways, USAT membership fields, fundraiser fields) are off by default. Turn on the ones you need from the sync settings. A few notes:

• Field names must contain no spaces and only alphanumeric characters when syncing to Race Result — display labels can be customized freely after creation
• If you change a field mapping name on the RunSignup side, the label in Race Result will be updated on the next sync cycle
• Multi-select fields from RunSignup are not supported in Race Result — coordinate with your race directors to avoid using that field type where possible

Key Takeaways

• Results publishing from Race Result to RunSignup is now available in beta — timers who have completed this training can begin using it
• Every listing maps to one result set — plan your listings as single-table, contest-specific views
• The RunSignup Participant ID and Place fields are required — you cannot map without them
• Divisions, splits, and notifications are all optional add-ons configured at mapping setup
• Results will never publish without an explicitly defined sync window — this is by design
• If you use results publishing, enable the bidirectional sync to keep participant records in sync
• All documentation is available on your Race Result dashboard under Race Day Tools > External Partners > Race Result > Setup Instructions
• Questions during the beta period can be directed to the Race Day support team