> 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/api-import-and-export-data.md). # Import participant data Synchronize participants' data from your timekeeping system or online registration with the events in your RACEMAP account. * Keep the participant list up-to-date and prevent mistakes. * Use your system to add tracking devices (GPS trackers, transponders, decoders, track boxes) to specific athletes. Synchronize the tracking devices with RACEMAP. * Manage participant information such as name, race number, key, status (DNF, DSQ, DNS), start- and finish time, and much more.

Import athletes from various sources in the participants section >> import/export

![Organize athletes for live tracking](https://1672210197-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSRNxaH2Ju9Flr7JhJD%2Fuploads%2FRSjz8fxHcZFoNB4jFhk2%2Fscreenshot-racemap.com-2022.10.11-15_24_29.png?alt=media\&token=33fe4031-78a1-4060-8885-672d7e279960) {% content-ref url="/pages/-LXTN05KRuN3LHs0iY6u" %} [Import with API, automatically](/api-import-and-export-data/import-basics.md) {% endcontent-ref %} {% content-ref url="/pages/-MBKork\_GNvfGpnpwShV" %} [Import with CSV file](/api-import-and-export-data/import-data-from-csv.md) {% endcontent-ref %} ### Import and visibility rules Import of RACEMAP tracking keys: Only those keys are imported, that belong to this RACEMAP event. To show a participant in the visualization its device id must be known. The visibility of different devices depends on the activation of predictive tracking. | Device id | Predictive tracking | NO predictive tracking | | ----------------------- | :-----------------: | :----------------------------------------------------------: | | IMEI of GPS tracker | ✔️ | ✔️ | | Id of tracking app | ✔️ | ✔️ | | Id of uploaded activity | ✔️ | ✔️ | | Transponder code | ✔️ |

➖
participants with a transponder id are not shown

| | No device id | ➖ | ➖ | --- # 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/api-import-and-export-data.md?ask=&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.