${tagname} with the real value from that activity — so your activity names and descriptions always reflect actual data without any manual editing.
Write a tag anywhere in a name or description action value by wrapping the tag name in ${ and }. For example:
${city} on an activity without GPS data) are replaced with an empty string, so the surrounding text flows cleanly.
Activity data tags
These tags draw directly from the activity’s recorded metrics.Location tags
Location tags are reverse-geocoded from the activity’s GPS coordinates. They require that the activity has location data.The
${cityStart}, ${cityMid}, and ${cityEnd} tags require a PRO subscription. ${city} is available to all users.Weather tags
Weather tags fetch conditions at the activity’s location and time. They require GPS data and a configured weather provider.
Replace
.temperature with any other weather property to get start/end-specific values, e.g., ${weather.start.windSpeed}.
Music tags
Music tags pull track information from Spotify or Last.fm for the activity’s time window. Link your account in account settings to enable them.${spotify.trackEnd}, ${spotify.trackList}, ${spotify.lyricsStart}, ${spotify.lyricsEnd} and the equivalent Last.fm tags require PRO.Gear tags
Gear tags reference the bike or shoes assigned to the activity at the time of processing.
The gear tag uses the gear’s name as stored in your Strava equipment list.
Counter tags
Counter tags display the value of an automation’s built-in cumulative counter.
Configure the counter in the automation’s advanced settings. Choose Counter property to accumulate a metric (e.g., total distance across all matched activities) instead of a simple event count. Counters reset annually unless you disable the reset.
Example:
Commute #${counter} — ${distance} produces Commute #47 — 12.4 km on your 47th commute of the year.