> For the complete documentation index, see [llms.txt](https://docs.motus.org/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motus.org/en/tags/tag-metadata-management/tag-registration.md).

# Tag Registration

{% hint style="warning" %}
Deploying tags without registration is futile – always ensure tags are registered to your Motus project prior to deployment.
{% endhint %}

All tags used with Motus must first be registered before any data can be acquired from Motus stations.

## Automatic Registrations

With some exceptions, all tags purchased from Lotek or CTT are registered automatically to a Motus project upon shipment. This means you must provide the tag manufacturer with your Motus project ID when ordering your tags.

1. [Register](https://motus.org/data/user/new) with Motus
2. Create or join a project
3. Provide the manufacturer (CTT or Lotek) with your project ID when purchasing tags.

{% hint style="warning" %}
Double check that your tags are registered to the **correct project** before deployment.
{% endhint %}

## Manual Registrations

In some specific instances, it may be necessary for you to register your tags manually. ***Only do this if you have been instructed by Motus.***

{% hint style="warning" %}
Please do not register tags more than once. If you need tags transferred between projects [contact us](https://motus.org/contact/).
{% endhint %}

1. [Register](https://motus.org/data/user/new) with Motus
2. [Register your tags](https://archived.sensorgnome.org/VHF_Tag_Registration): Instructions on registering tags can be found [here](https://archived.sensorgnome.org/VHF_Tag_Registration). To register a tag, you need to make a short recording of its output using a [funcubedongle](http://www.funcubedongle.com) attached to a PC. Tag Registration Kits can be purchased from Motus. Each kit includes a funcube, whip antenna, and tag activator. We strongly encourage you to test and register all tags immediately after receiving them to ensure they’re ready for deployment. **Always check your Manage Tags page after registration to ensure they have all been uploaded correctly.**
3. [Upload tag registrations](https://motus.org/data/project/sgJobs): Send us your completed tag registrations from step 2 here using your Motus login information.

{% hint style="warning" %}

### Incorrect Burst Intervals

Sometimes bad recordings can result in tag registrations with burst intervals that are an ***integer multiple*** of the true burst interval. This is because the recording quality was poor and certain tag bursts were skipped during the registration process.

This issue should be resolved in a timely manner by [contacting us](https://motus.org/contact) with the details including the [<mark style="color:green;">**Motus Tag ID**</mark>](/en/glossary.md#tags) and the true burst interval that should have been recorded.

If this issue is not resolved it will result in missed detections and at least 50% shorter [<mark style="color:green;">**runs**</mark>](/en/glossary.md#tags).
{% endhint %}

## Tag Fees

There is a one-time data service fee applied while purchasing tags from manufacturers. This fee covers approximately half of the cost of data curation while the remainder is supported by Motus Central at Birds Canada. Details on data service fees can be found in the [Motus Collaboration Policy](https://motus.org/resources/policy/) in section 3.5.

Please[ contact us ](https://motus.org/contact)if you have any questions regarding tag fees.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.motus.org/en/tags/tag-metadata-management/tag-registration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.