Tagging

New in Nov 2026 is the conversation tagging feature.

When an email is used or filed the conversation is also stored and this is used to surface any matches.

This feature requires some new fields or for the full installer to be run and the metadata installer to be run again.

The advantage of this is that users then do not need to manually tag items (as per below) though this is a popular feature and will remain.

Also this was done as within the 365 clients tagging of an email is not possible in read mode and only in compose mode (when you are writing the email)

---

Tagging emails allows us to associate emails with something other than the person,company or lead (matched on email address).

Normally matching works as per https://accelerator.crmtogether.com/index.php?title=Email_Matching

---

Please review this video for a complete explanation on the power of tagging with Accelerator https://vimeo.com/869527759

---

Optional way of customising the tagging so different companies with Accelerator don't clash on tags.

WE RECOMMEND THIS DONE ON A NEW INSTALL

Update the web.config setting with a prefix and suffix separated by a comma

Default

     <add key="tagPrefixSuffix" value="Ref:#,#" />

EG

     <add key="tagPrefixSuffix" value="Ref:(,)" />

---

Notifications and tagging

If you wish to put the tags on notification emails then you need to use the code map as follows

 "Lead":"AA";
 "Cases":"BB";
 "Company":"NN";
 "Person":"II";
 "Opportunity":"YY";
 ",":"X";
 "1":"M";
 "2":"D";
 "3":"Z";
 "4":"R";
 "5":"T";
 "6":"U";
 "7":"K";
 "8":"P";
 "9":"F";
 "0":"L";
 So for Opportunityid = 14782 
 The code would be 
     #YYXMRKPD#
 And unencoded 
     #Opportunity,14782#

1. cmli_comm_personid# in CRM templates/notifications actually give you the person name but we want the value. To get the value you must edit the view and alias the field

 https://community.sagecrm.com/user_community/f/84/t/10464.aspx 

So to code for a person you would set it up as follows (assuming your tags use Ref:[…] structure)

 Ref:[Person,#cmli_comm_personid#]

---

How to add a custom field as the tag (in this example we create a field on opportunity called 'oppo_projectno')

Set up the subject fields with the new field

 <add key="opportunity_subjectfields" value="Opportunity,oppo_projectno" />

These fields should contain unique values

Tell the system not to code the tag

 <add key="opportunity_codetag" value="false" />

The data comes from the view here

 <add key="opportunity_summaryview" value="vCRMTogetherOpportunity" />

You can change this to us “vsummaryopportunity”. The reason we use “vCRMTogetherOpportunity” is because it returns less data and so is quicker. You could also opt to update vCRMTogetherOpportunity to include the “oppo_projectno” field (but when you update Accelerator and re-apply the metadata you must remember to apply your update again.

 <add key="opportunity_summaryview" value="vsummaryopportunity" />

Note: Entity translations are not used, the key must have the actual table name in it.