How to Set Up Interest Tags in Salesforce Financial Services Cloud

A relationship manager finishes an annual review with a long-standing client. In passing, the client mentions their daughter is getting married next year, they want to renovate the house before the wedding, and they have international travel planned — is there a card with no foreign transaction fees? In one exchange, the client just handed the bank three product signals: home equity lending, wedding financing, and a travel-friendly credit card.

What happens next decides whether those signals become revenue. In many firms they land on a sticky note, in a free-text field nobody queries, or in the advisor's memory — where they can't be searched, reported, or handed to marketing. Interest Tags exist to close that gap. This guide covers what they are, the data model, editions and permissions, the complete setup, the advisor experience, reporting, APIs, and the limits to plan around.

What Are Interest Tags in Salesforce Financial Services Cloud?

Interest Tags are custom labels users attach to client records to capture needs, interests, and prospecting opportunities. Each tag sits under a tag category — a "Lending Needs" category might hold "Home Equity Loan" and "Personal Loan," while "Life Events" holds "Wedding" or "Retirement." Because tags are structured data rather than free text, you can search them, group them in reports, dashboard common themes across clients, and pull segments for campaigns.

One architectural fact drives most of the setup and limits: the Interest Tags object is a virtual object built on the Topic object. Interest Tags inherits Topics plumbing — you must enable Topics for objects and configure Topics user permissions first — and Topics-style constraints, such as no custom fields on the Interest Tags object.

Why Interest Tags Matter: Client Conversations Are Revenue Signals

Advisors hear buying signals every week. The failure mode is rarely that nobody listened — it's that the firm has no governed place to put what it heard. Without Interest Tags, teams fall back on three workarounds, and all three break at scale:

• Notes and sticky pads. Captured, but invisible to everyone else, unsearchable in aggregate, and gone when an advisor leaves.
• Hardcoded multi-select picklists. Reportable, but rigid — every new interest is an admin change, the value list balloons, and values can't be grouped into a browsable hierarchy or reused across objects.
• Advisor memory. Works until the book grows, the advisor is out, or the relationship changes teams.

Interest Tags sit between those extremes: advisors get a fast way to tag a record during or right after a conversation, and the firm gets structured data it can act on. In our opening scenario, the relationship manager tags the client "Home Equity Loan," "Wedding," and "Travel Credit Card" — and the next home equity campaign can pull every tagged client in the territory instead of relying on who happened to remember.

Interest Tags vs. Topics vs. Multi-Select Picklists

Because Interest Tags is built on Topics, admins reasonably ask which tool to use — and where a multi-select picklist still fits:

Recommendation: for client-interest tracking in Financial Services Cloud, use Interest Tags and avoid running standard Topics alongside it — Salesforce itself recommends not using both, because two tagging surfaces on the same record confuse users. Keep multi-select picklists for genuinely fixed attributes, not an evolving catalog of interests.

How the Interest Tags Data Model Works

Four building blocks connect a tag to a client record:

1. Tag Category — the grouping layer. Categories support a hierarchy of up to three levels (for example, "Financial Needs" → "Lending" → "Home Equity"), you can maintain more than one level-one category, and each category can carry an icon.
2. Interest Tag — the label itself, such as "Home Equity Loan." Every tag relates to at least one category, and a single tag can be assigned to up to three categories.
3. Tag Category Assignment — the junction connecting a tag to its categories, which is what makes multi-category membership possible.
4. Topic Assignment — the record connecting a tag to a specific client record: a Person Account, Account, Contact, or Interaction Summary, depending on which objects you enable.

Because the Interest Tags object is virtual and built on Topics, it does not appear in Object Manager — you manage categories and tags through their own setup pages and app navigation items.

Editions and Permissions You Need

Editions. Interest Tags require Lightning Experience and are available in Financial Services Cloud Professional, Enterprise, and Unlimited editions (other industry clouds offer it under their own edition lists).

Core user permission. Admins and users need the "Access Interest Tags for Financial Service Cloud" user permission, typically delivered through a product-provided permission set — Financial Services Cloud Extension, Financial Services Cloud Foundations, or FSC Sales.

Topics permissions. Because Interest Tags runs on Topics behind the scenes, Topics user permissions control what users can do: Assign Topics to attach tags to records, and Create / Edit / Delete Topics to manage tags and categories. Users also need object permissions (Read, Create, Edit, Delete, View All, Modify All as appropriate) on the Interest Tags, Tag Categories, and Tag Category Assignments objects.

Least-privilege pattern. Give most advisors Assign Topics plus Read/View All on the tag objects, and reserve Create/Edit/Delete Topics for a small group of dictionary owners. Salesforce recommends your own permission set plus permission set groups and muting permission sets rather than cloning the product-provided sets. If default internal access for tag categories is Private, add sharing rules — users only see category record types they've been granted in the component.

How to Set Up Interest Tags: The 8-Step Admin Checklist

Work through these in order — each step depends on the last. Do a sandbox pass first.

1. Enable Topics for objects. From Setup, open Topics for Objects and enable Topics for every object that will carry the component — typically Account, Person Account, Contact, and Interaction Summary. Select the fields to make available and save. Chatter is not required.
2. Turn on Interest Tags. In Setup, open the Interest Tags settings (the guided setup walks you through it) and enable the feature.
3. Assign permissions. Assign the product-provided FSC permission set (or your own set with "Access Interest Tags for Financial Service Cloud") plus the Topics and object permissions above. Verify with a pilot user first.
4. Design the tag dictionary. Before creating anything in the org, workshop the catalog with advisors, bankers, and marketing: the list of interests, how they group into categories, and naming conventions — Salesforce suggests tag names of three words or fewer. This governance step keeps the feature useful a year from now.
5. Create tag categories. Build the hierarchy (up to three levels), set each category active, and choose the icons users will see.
6. Create interest tags. Create each tag and relate it to its category — up to three per tag.
7. Add the Interest Tags component to record pages. In Lightning App Builder, add the component to the record pages for the objects you enabled, then activate. Users can only tag records whose pages include it.
8. Build reports and dashboards. Create the custom report type and baseline reports (below) so the data has somewhere to go from day one.

The Advisor Experience: Tagging a Client in Seconds

On a record page with the component, an advisor has three ways to find a tag: start typing to search, filter by category, or open the Browse Tags window to explore the hierarchy and select several tags at once. Saved tags appear on the record grouped by category — "Lending Needs: Home Equity Loan" alongside "Life Events: Wedding" — with no manual sorting. The design goal is that tagging fits inside the conversation workflow rather than becoming a data-entry chore advisors defer and forget.

Reporting: Turning Tags into Campaigns and Dashboards

Reporting requires a custom report type, because Interest Tags is a virtual object on Topics:

1. From Setup, open Report Types and create a custom report type with Tag Categories as the primary object (requires the Manage Custom Report Types permission).
2. Relate the Topics object so tag and assignment records appear in results.
3. Build a report from that type: group rows by Category Name, and add columns for Topic: Name (the tag), Description, and Topic Assignment: Name (the tagged record).
4. To report on tags for a specific object, filter on Record Key Prefix — the first three characters of the record ID, visible in any record's URL.

From there, dashboards can show which interests are most common across a book of business, and campaign workflows can start from "every client tagged Travel Credit Card" instead of from memory. One constraint: this report type doesn't support polymorphic fields — for related objects you get only the KeyPrefix and Name fields.

Automating with the Interest Tagging Business APIs

Salesforce exposes dedicated Interest Tagging Business APIs — Connect-style REST resources under /connect/interest-tags/ for creating, updating, and deleting tags, listing a tag's categories, retrieving tags on a record, and creating assignments. Two things to know before building: the API works only with Interest Tags (not Topics or Communities tags), and one Connect API call can create a maximum of 200 interest tags and tag assignments, so bulk loads from external systems need batching.

Gotchas and Limits to Know Before You Build

• Virtual object: Interest Tags doesn't appear in Object Manager; you can't add custom fields to it or custom actions to its page layout. If a design needs extra attributes per tag, put them elsewhere rather than customizing around the platform.
• Cardinalities: up to three category levels; a tag belongs to at most three categories; a record carries up to 100 tags; tag names cap at 99 characters (aim for three words).
• Deletion is sweeping: deleting an interest tag deletes the tag and every assignment across all records. Treat tag retirement as a governed change with a report export first.
• Don't double-tag: Salesforce recommends not using standard Topics alongside Interest Tags on the same records.
• Chatter is not required to enable Topics for objects.
• Reporting constraint: the custom report type supports only KeyPrefix and Name on related objects — no polymorphic fields.
• Visibility: users see only the category record types they've been granted; plan sharing rules if categories are Private.
• API batch size: 200 tags and assignments maximum per Connect API call.

Go-Live Checklist

• Topics enabled for every object that will carry the component (Account, Person Account, Contact, Interaction Summary as applicable).
• Interest Tags setting turned on and verified in a pilot user's session.
• Permission sets assigned: full access for dictionary owners, assign-only for advisors.
• Tag dictionary signed off by business stakeholders, naming conventions documented.
• Category hierarchy and tags created, deduplicated, spot-checked against the dictionary.
• Interest Tags component added to the right Lightning record pages and pages activated.
• Custom report type, baseline report, and dashboard built and shared.
• Sharing rules in place if tag category access is Private.
• Advisor training delivered: search, filter, Browse Tags — and when to tag (during or right after client conversations).
• A named owner and intake process for new tag requests, so the dictionary stays clean.

What to Do Next

If your org already runs Financial Services Cloud, the fastest validation is a two-week pilot: one category hierarchy, a dozen tags, one record page, and one report for a single team. Measure whether advisors actually tag in the flow of work before scaling the dictionary. If you're planning an implementation, build Interest Tags into the data model and permission design from the start. For the broader roadmap, see our Winter '27 Agentforce Financial Services release guide and how we deliver in Salesforce implementation done right.

How Vantage Point Helps

Vantage Point is a Salesforce Solutions Partner with a dedicated Financial Services Cloud practice for banks, wealth management firms, and insurance organizations. For Interest Tags, our senior consultants facilitate the tag-dictionary workshop, configure Topics and least-privilege permission sets, build the report types and dashboards that turn tags into campaign segments, and train advisors on the workflow. Where tagging connects to broader data work, our Salesforce implementation and advisory team designs the data model, and our managed services keep dictionaries, permissions, and reports healthy as your book grows. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver.

Frequently Asked Questions

What are Interest Tags in Salesforce Financial Services Cloud?

Interest Tags are a built-in Financial Services Cloud feature for attaching structured, reportable labels to client records to capture needs, interests, and product opportunities. Tags are organized into a category hierarchy, and a Lightning record-page component lets advisors search, browse, and assign them during client conversations. Under the hood, Interest Tags is a virtual object built on Salesforce Topics.

Which Salesforce editions support Interest Tags?

Interest Tags require Lightning Experience and are available in Financial Services Cloud Professional, Enterprise, and Unlimited editions. Users also need the "Access Interest Tags for Financial Service Cloud" user permission, typically delivered through a product-provided permission set such as Financial Services Cloud Extension.

What is the difference between Interest Tags and Topics?

Interest Tags is a Financial Services Cloud layer built on Topics that adds tag categories, a browsable hierarchy up to three levels deep, a dedicated record-page component, and purpose-built reporting and APIs. Standard Topics is flat and general-purpose. Because the two overlap, Salesforce recommends not using Topics alongside Interest Tags on the same records.

How many interest tags can a client record have?

A single record can have up to 100 interest tags. Tag names can be up to 99 characters, though Salesforce suggests three words or fewer for readability. Each tag can belong to up to three tag categories, and categories nest up to three levels deep.

Can you report on Interest Tags?

Yes. Build a custom report type with Tag Categories as the primary object and Topics as the related object, then group by Category Name and filter by Record Key Prefix to see tags for a specific object. One limitation: the report type doesn't support polymorphic fields, so only KeyPrefix and Name are available for related objects.

Can you create or assign Interest Tags through an API?

Yes — Salesforce provides Interest Tagging Business APIs, Connect-style REST resources under /connect/interest-tags/ for creating and updating tags, listing categories, retrieving tags on a record, and creating assignments. The APIs work only with Interest Tags, and each call can create a maximum of 200 tags and assignments, so plan bulk loads in batches.

Do you need Chatter enabled to use Interest Tags?

No. Interest Tags requires Topics for objects, but Salesforce confirms you don't need Chatter enabled to enable Topics. You do need Lightning Experience, Topics turned on for each object that will carry the component, and the Interest Tags setting enabled in Setup.

Sources

• Interest Tags for Agentforce Financial Services — Salesforce Help
• Interest Tags (Admin Setup) — Salesforce Help
• Interest Tags Editions and Permissions — Salesforce Help
• Considerations and Limitations for Interest Tags — Salesforce Help
• Build an Interest Tags Report — Salesforce Help
• Interest Tags for Agentforce Financial Services — Salesforce Trailhead
• Interest Tagging Business APIs — Salesforce Developers

Vantage Point is a boutique CRM consulting firm helping businesses transform with Salesforce, HubSpot, and AI. Learn more at vantagepoint.io.