---
schema_version: "1"
id: b6b17764215ab2afdf59584a383f307a5593e7e87c04df4025714291844761a4
title: InterestTaggingSettings
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_interesttaggingsettings.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_interesttaggingsettings.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 40f2b8ed6c38f3845cffa2f4d02b5114961b3fd663e5dd5a3c4976144c620522
description: Represents settings for Interest Tags, which your users can add to client records to capture client needs, interests, and prospecting opportunities.
---
# InterestTaggingSettings

Represents settings for Interest Tags, which your users can add to client records to capture client needs, interests, and prospecting opportunities.

## Parent Type and Manifest Access

This type extends the [Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/metadata.htm "The base class for all metadata types. You can’t edit this object. A component is an instance of a metadata type.") metadata type and inherits its fullName field.

In the package manifest, all the settings metadata types for the org are accessed using the “Settings” name. See [Settings](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type.") for more details.

## File Suffix and Directory Location

InterestTaggingSettings values are stored in the InterestTagging.settings file in the settings folder. The .settings files are different from other named components, because there’s only one settings file for each settings component.

## Version

InterestTaggingSettings components are available in API version 54.0 and later.

## Special Access Rules

Before you enable Interest Tags, you must enable Topics for Financial Services Cloud objects and assign Interest Tags permissions to users. See [Interest Tags](https://developer.salesforce.com/docs/atlas.en-us.264.0.financial_services_cloud_admin_guide.meta/financial_services_cloud_admin_guide/fsc_admin_interest_tags.htm).

## Fields

| Field Name | Description |
| --- | --- |
| enableInterestTagging | 
Field Type

boolean

Description

Enables Interest Tags in your org when set to true.



 |

## Declarative Metadata Sample Definition

The following is an example of an InterestTaggingSettings component.

<?xml version="1.0" encoding="UTF-8"?>
<InterestTaggingSettings xmlns="http://soap.sforce.com/2006/04/metadata">
  <enableInterestTagging\>true</enableInterestTagging\>
</InterestTaggingSettings\>

The following is an example package.xml that references the previous definition.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types\>
        <members\>InterestTagging</members\>
        <name\>Settings</name\>
    </types\>
</Package\>

## Wildcard Support in the Manifest File

The wildcard character \* (asterisk) in the package.xml manifest file doesn’t apply to metadata types for feature settings. The wildcard applies only when retrieving all settings, not for an individual setting. For details, see [Settings](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type."). For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/file_based_zip_file.htm "The deploy() and retrieve() calls are used to deploy and retrieve a .zip file. Within the .zip file is a project manifest (package.xml) that lists what to retrieve or deploy, and one or more XML components that are organized into folders.").