How to use Strava Beacon for a run or ride

Set up Beacon from the phone you will carry

This walkthrough covers recording in the Strava phone app. Follow your actual recording setup: a watch or bike computer may have different requirements. Set aside time before departure so you can check the recipient details without rushing, and choose someone who is available for this outing.

Make the message useful to the person receiving it

A location link makes more sense alongside a short description of your outing. Give the contact your route, the finish you expect and any section where reception may be uncertain. Be specific about the endpoint: finishing the timed portion of a workout and getting home may be different moments.

For example, adapt this message: “I am doing [route] and expect to be back at [time]. This is the link for today. Please confirm it opens. I will message when I finish. If I miss that time and you cannot reach me, use the plan we discussed.” This is a suggested message, not an automated Beacon notification.

The pre-run information guide helps you fill in those details. A contact who knows the intended route has more context than one who only sees a line on a screen. Tell them if you substantially change the outing while you still have a way to communicate.

Keep a live link out of public group posts. Send it to the people you intend to involve, and tell them whether you are asking for occasional viewing or a specific follow-up at the finish time. Those are different levels of responsibility, so make the request explicit.

Show your contact how to read the activity

The recipient can view Beacon in a browser without a Strava account. The page includes position, traveled path, recording status, update time and expandable activity and battery details. Once recording finishes, it no longer exposes your current position.

Ask your contact to locate the timestamp before focusing on the dot. A point close to a road junction can suggest where the phone last reported, but an older update cannot show which turn you took afterward. They should describe what the screen actually says instead of interpreting every pause as an injury or every missing update as a dead battery.

An illustrative example: you stop to refill a bottle, then continue through a patch with poor reception. The map may look similar during both periods even though one was a planned stop and the other was a reporting gap. Your contact needs the time of the information and the outing plan to decide what to check next.

Send the Guardian guide to someone taking on this role for the first time. It covers the conversation around a share: availability, contacting you and using the details you left. Watching a map is only one part of that job.

Troubleshoot the part that failed

Separate a missing message from a page that opens but does not update. Start by having both people describe exactly what they see. “It is not working” could mean no message, an old activity link, an unexpected recording state or a position that has not changed.

Beacon needs cellular service for location updates. For an iPhone with poor GPS acquisition, Strava recommends starting with a clear view of the sky and allowing extra time to obtain a position. Do troubleshooting while stopped somewhere suitable, rather than changing settings while running or riding.

Arrange a missed-return check separately

Strava says Beacon does not notify your contact just because you stop. An expected finish written in your message is therefore something you and your contact agree to act on. It does not become an automatic check-in timer simply because it sits beside a tracking link.

If you want the contact to receive a prompt when you fail to check in, choose a compatible check-in service and configure it before the outing. The tracking and check-in decision guide explains the different triggers. Avoid giving your contact several unfamiliar alerts without first explaining which one means what.

Holler offers an optional return time saved on its server. If you have not checked in after that time plus the five-minute grace period, it sends selected Guardians an overdue alert through the configured email or push channels. The plan must save successfully, message delivery can fail or be delayed, and someone still needs to respond.

You can consider a separate arrangement alongside workout recording, but test the intended combination on your own phone. This guide does not establish how two apps will behave together in the background. In particular, Holler browser sharing needs the page open and screen on; the native iPhone app remains in private beta.

Practice the start and finish before a longer outing

Choose a short familiar route and a contact who knows it is a practice outing. Send the link, ask them to open it and agree on a time for a brief follow-up. When you finish, tell them directly. Write down any confusing step so you can fix the arrangement before using it on a longer or less familiar route.

Keep the result specific. “The link opened and showed this outing on this phone” is a useful observation. It does not establish future delivery, continuous reception or emergency response. Do not deliberately trigger an emergency call to test an ordinary sharing flow.

If battery life is a concern, review battery use during location sharing and practice with the settings and phone carry you intend to use. Check both the recording and the contact experience instead of looking only at your own app.

For a feature comparison, use Holler versus Strava Beacon. If the missing piece is an agreed finish, work it out with the return-time planner, then save it in the service you choose. A calculation on the tool is preparation; it does not itself activate an alert.