> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/integration-options/mobile/android/tags-usage.md).

# Tags Usage

* It is important that tags be unique for jobs and should be reused only to override existing information like selfies and or user id information.
* When performing a job type 1 with id card capture which is an enrol/register make sure the same tag used to capture selfies is used to capture the id card and lastly used to submit the job

### Usage 1: Selfie Capture (Except for Job Type 5)

The first instance you will get to use a tag is when capturing a selfie and a unique tag should be used keeping in mind that the same tag would be used for final submission eg

```
 smartSelfieManager = new SmartSelfieManager(getCaptureConfig());
        smartSelfieManager.setOnCompleteListener(this);
        smartSelfieManager.setOnFaceStateChangeListener(this)
        smartSelfieManager.captureSelfie($UNIQUE_TAG); <= should be unique per job that you run unless you want to overwrite a job

```

### Usage 2: ID Capture (Optional For Job Type 1)

For job type 1 which is register/enrol if using ID Card capture, make sure the same tag used for selfie capture is used so if these two are in different classes then the tag used in Selfie capture would need to be passed to make sure the ID Card image is associated with the same tag

### Usage 3: Job Submission (All jobs)

All smile id jobs take a SIDConfig instance which has all the information about the job being submitted.The same tag that was used when capturing a selfie should be used to submit the job to make sure all information associated with the job is submitted correctly

```
builder = new SIDConfig.Builder(this)
                    ... //other job settings
                    .build($UNIQUE_TAG);
```


---

# 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://legacy-docs.usesmileid.com/integration-options/mobile/android/tags-usage.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.