Interest Tags are a built-in Salesforce Financial Services Cloud feature that captures client needs, life events, and product interests as structured, searchable labels on client records — organized under tag categories so the data can be reported on and fed into campaigns. Setup is eight admin steps: enable Topics for objects, turn on Interest Tags, assign permissions, design a tag dictionary, create tag categories, create the tags, add the component to Lightning record pages, and build reports. This guide is for Salesforce admins and operations leaders at banks, wealth management firms, and insurers running Financial Services Cloud (branded Agentforce Financial Services in Salesforce's current documentation). All steps and limits are verified against Salesforce Help and Trailhead, linked under Sources, as of October 2026.
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.
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.
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:
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.
Because Interest Tags is built on Topics, admins reasonably ask which tool to use — and where a multi-select picklist still fits:
| Criteria | Interest Tags | Topics (standard) | Multi-select picklist |
|---|---|---|---|
| What it is | FSC/industry-cloud tagging layer on Topics, with categories and a record-page component | Core Salesforce feature for tagging records with keywords | Custom field with a fixed value list |
| Best for | Client needs, interests, and product opportunities in financial services | General collaboration and feed-based tagging | Small, stable lists of fixed values |
| Organization | Tag categories in a hierarchy up to three levels; browsable by category | Flat list, no categories | Flat value list |
| Searchable / reportable | Yes — dedicated custom report type and dashboards | Yes, via Topics reporting | Yes, but awkward (values concat in one field) |
| Who adds values | Controlled — admins manage the dictionary; most users get assign-only rights | Any user with topic permissions, often ad hoc | Admin only |
| API support | Dedicated Interest Tagging Business APIs (Connect-style REST) | Standard Topics APIs | Standard field APIs |
| Key limit | 100 tags per record; no custom fields | No hierarchy; Salesforce recommends not mixing with Interest Tags | Hardcoded values; no cross-object reuse |
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.
Four building blocks connect a tag to a client record:
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. 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.
Work through these in order — each step depends on the last. Do a sandbox pass first.
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 requires a custom report type, because Interest Tags is a virtual object on Topics:
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.
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.
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.
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.
Whether you're setting up Interest Tags for the first time or untangling a tagging model that grew without governance, a working session with a senior Vantage Point consultant will leave you with a clean dictionary design, a permissions plan, and a go-live checklist tailored to your org. Talk to our team about a Financial Services Cloud working session.
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.
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.
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.
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.
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.
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.
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.
Vantage Point is a boutique CRM consulting firm helping businesses transform with Salesforce, HubSpot, and AI. Learn more at vantagepoint.io.