> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/live-tracking/map-url.md).

# Choose the event slug

Choose the slug in your tracking map's web address, and keep one address for a series that moves on to a new event every week.

Every activated event gets a URL like `racemap.com/player/berlin-marathon/`. The last part, `berlin-marathon`, is the slug. Racemap picks it from the event name. If another event already uses that slug, the date is added: `berlin-marathon_2026-09-27`.

You can change the slug in the event editor under **Provide event information** → **Slug**. The field appears once the event is activated. Below it you see the full address as you type.

{% hint style="success" %}
Old links keep working. Anyone who opens a previous URL of the event lands on the current one, so printed QR codes and shared links stay valid.
{% endhint %}

Racemap turns what you type into a valid slug: `Berlin Marathon!` becomes `berlin-marathon`. A slug needs between 3 and 64 characters.

### One URL for a weekly series

Running a series, like a weekly evening run, with a new event each week? Give every new event the same slug, e.g. `evening-run`.

When the slug is already used by one of your other events, Racemap asks whether to move it. Confirm, and:

* `racemap.com/player/evening-run/` now opens this week's event.
* Last week's event goes back to the slug it had before, e.g. `evening-run_2026-09-30`. If it never had another one, Racemap gives it a dated slug.

Your participants keep one bookmark for the whole season.

{% hint style="info" %}
You can only move a slug between events of the same account. A slug that belongs to another account, also of a deleted event, stays with that account. Racemap support can move a slug between accounts, e.g. when an event changes hands.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.racemap.com/live-tracking/map-url.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.