# Add a New Tag (Server)
## Introduction
Server-side tagging lets you shift tag execution from your website or app to a secure server environment. Instead of loading multiple tags in the browser, data is sent to a server where tags are triggered. This improves site speed, enhances data accuracy, and gives you more control over what data is shared with third parties.
## Procedure
To add a new server-side tag, perform the following steps:
**Step 1**: Select **Tags** from the left navigation panel.
**Step 2**: Click the **Add Tag** dropdown select **For server**.
**Step 3:** The **Select Provider** panel opens on the right side. Select a provider from the list or use the search bar to find and select a provider.
**Step Result:** The **New tag** screen appears.
**Step: 4:** **Trigger**.
**Step 4.1:** Click **Choose Triggers.**
**Step 4.2:** The **Choose Triggers** panel opens on the right side. Choose a trigger from the list or use the search bar to find and select a trigger, then click **Done**.
**Note:** You can select multiple triggers if needed.
**Step Result:** The tag is triggered for the respective trigger data.
**Step 5:** Set Qualification Criteria (Optional).
**Step 5.1:** Click Qualification Criteria (Optional).
Qualification Criteria of a tag are conditions/triggers that inform Ingest Labs when to trigger a particular tag. You can add multiple Qualification Criteria and these criteria are layered.
***Note 1:** This step is optional.*
**Step 5.2:** The **Choose Qualification Criteria** panel opens on the right side. Select an option from the dropdown or use the search bar to find and select a criterion, then click **Done**.
***Note 2:*** You can select multiple qualification criteria if needed.
**Step 6:** Set Tag Info
This is the step where you set a name and validity period for the tag. The default validity period is one year for any new tag that is created and can be set to any desired date.
**Step 6.1: Name:** The Tag name.
**Step 6.2: Validity Period:** Denotes the validity period of the tag including Start Date and End Date.
***Note** : If you don't enter the tag name, an error message appears: **This value is required**.*
Set Validity and Tag Expiry
While creating a tag on Ingest Labs, you can set the validity period of a particular tag and define tag expiry. The default validity period is one year for any new tag that is created and can be set to any desired date. When the expiry date is closer, you will receive reminder e-mail notification about the expiry of the tag. If no action is taken, the tag stops triggering post the set validity period. You can find all expired tags in the “Paused State” in the Publish section and you can remove the expired tags to reduce the size of your SDK.
Set Tag Query Parameters
The Query parameters include the set of dynamic values that are included along with the Base URL while executing the query. These parameters appear in the Attributes section as well along with the values.
**Step 7:** Set Provider Attributes
The Provider is a mandatory setting while adding a new tag. You can add any number of Provider attributes using the Key-Value pair and configure the settings using the Settings option. The user can view the providers attributes added from Provider side configuration.
For a particular Provider attribute, you must set the value either from the Data Elements or Transformers.
After selecting either from the Data Element or Transformer, the value appears in the **Value** column.
**Step 7.1:** Add Attributes
To add Attributes, select **Add Attributes** and set the following values.
**Step 7.1.1: Name**: Set the Attribute name. For example: visitor\_id, user\_id, and so on.
**Step 7.1.2: Value**: Set the value either for the Data Element or Transformer.
**Step 7.1.3: JSON**: Enter the Attribute name and value, and configure the Settings.
* Mandatory - Denotes the value to be mandatory.
* Ignore If Empty - Ignore the field if empty.
* Hash (SHA256) - denotes the value in the HASH format.
**Step 7.1.4: Static**: Denotes the static Value that is known.
**Step 7.1.5:** Attribute Settings:
Enter the **Attribute Settings**.
**Tool-tip!** Select the **Mandatory** check box to display the **Fatal** check box.
**Step 7.1.6:** Set the Data Type Conversion using the following options.
| Data Type Conversion | Description |
| ------------------------ | ----------------------------------------------------------------------------------------- |
| No Conversion | Indicates that there is no conversion required for the data type. |
| Convert to Boolean | Converts the input data to Boolean. |
| Convert to Number | Converts the input data to Number. |
| Convert to Array | Converts the input data to Array. |
| Convert to Object Spread | Converts the JSON attributes under a parent level attribute to the root level attributes. |
**Step 7.1.7:** Select one the following Transformer types and click **Confirm**.
| Transformer Type | Description |
| ---------------- | ----------------------------------------------- |
| URL encode | Converts the URL into the encrypted format. |
| HASH (SHA256) | The value is converted to HASH (SHA256) format. |
| Ignore if empty | May be ignored if the value is empty. |
**Step 7.1.8:** Select the **Ignore Redaction** checkbox to display the data elements. Redaction is a setting for each data element, which allows the server-side processing to apply the redaction strategy - like anonymize for email.
**Step Result:** The Provider Attribute is created.
**Step 7.1.9:** To delete the Provider Attribute, select the **Delete** icon at the right-hand corner of the screen.
**Step 7.1.10:** Click **Save** to save the settings.
**Step Result:** The new tag is created.
{% embed url="" %}
---
# Agent Instructions: 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:
```
GET https://docs.ingestlabs.com/tag-manager/tags/add-a-new-tag-server.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.