INSIDE 3.3
VIS-009

Page tags and conversation tags

Page tags describe current browsing, while saved tags organise conversations, contacts and other records within a website.

admindeveloperoperator
DraftThis article hasn't been reviewed yet.
Where to find it
Tags

What it is

INSIDE has page tags and saved Tags, which describe different things. Page tags arrive with a tracked page and describe current browsing. Saved tags belong to the website's shared vocabulary and are attached to records such as conversations and contacts.

Who uses it and why

  • Developers send page tags to describe browsing context.
  • Operators apply saved tags to organise conversations and contacts.
  • Administrators maintain consistent saved names and the permissions for changing them.

Where to find it

Page tags come from the website integration, rather than a separate Settings editor. Use Tags in supported conversation and contact controls to work with saved tags. There is no separate global page-tag management screen.

How it works

The tracker accepts a comma-separated list of page tags and trims spaces around each entry. The tags become part of the visitor's current page context. A later tracked page supplies its own list; page tags do not automatically become saved contact or conversation tags.

Saved tags have a name shared within one website. Reusing an existing name reuses that tag. Supported associations include contacts, companies, conversations, file-library items and video shows.

Saved names are normalised to lower case with surrounding spaces removed. The conversation tag input also removes spaces within the entered name. Saved tag names have a 50-character limit.

Visitor-event actions can queue conversation tags before the relevant conversation exists, then apply them to the conversation. This does not turn a page tag into a permanent visitor tag.

Configure it

Agree page-tag values with your developer and send the intended list on each tracked page.

For saved tags, open the record's Tags control. Type in Type to add tag, then select an existing name or create one where your role and that control allow it. The Settings or Manager role provides access to shared tag deletion and supported removal controls. Creating a tag and deleting it have different access checks.

Fields

Field Where Required What it is for
Tags Conversation › Tags No Selects or creates saved tag names for the conversation being edited.

Permissions

Permission Lets you
Settings Manage shared saved tags, including deletion and removal of associations in supported controls.
Manager Manage shared saved tags, including deletion and removal of associations in supported controls.

Limits and good to know

  • A tag on one conversation is not automatically attached to every conversation for that customer.
  • Contact tags describe the contact. They are separate from the browser's current page tags.
  • Removing a saved tag from one record and deleting its shared name are different actions. Check the control before deleting.
  • The recent-tag suggestions are the five newest saved tag names, rather than the five most recently used associations.
  • Tag names are shared within a website, not across every website account.

Depends on and works with

Configured byEnhancesRelated
View all connections as a list

This feature uses

Used by

FAQ and troubleshooting

Why did the tag disappear after navigation?

Check whether it was a page tag. Page tags follow the currently tracked page and its supplied list.

Why does a page tag not appear in the conversation's Tags control?

Page tags and saved conversation tags are separate. Use an appropriate saved-tag action when a conversation needs a lasting classification.

Why can I add a tag but not remove it?

Saved tag creation and removal have different permission checks. Ask someone with the Settings or Manager role to review the tag and your permissions.

Does renaming a saved tag affect other records?

The name belongs to the shared website vocabulary. Treat a rename as a shared change, rather than a label change on one record only.

INSIDE 3.3 · Source commit 992abb980bContent is a pre-release draft© 2026 Powerfront