Quantcast
Channel: Microsoft Dynamics CRM Forum - Recent Threads
Viewing all articles
Browse latest Browse all 79901

email settings: tracking/matching questions?

$
0
0

Hello - I'm trying to get a better understanding of email tracking/matching functionality in CRM:

tracking:
----------
* Prefix: Is this field required? Or generally recommended? Do you generally use a simple word/acronym for the prefix to reflect the crm org?
* Deployment base tracking number: Not sure what this is?
* Number of digits for user numbers: Does CRM generate a "user number" for a user the first time he sends *or* receives an email in CRM? What happens if the value for this setting is set to 2 but then the system grows to 100 users who are sending/receiving email?
* Number of digits for incremental message counter: Is this number incremented for a particular email thread? Or is this number cumulatively incremented for all emails that a user sends/receives?  If the total number grows beyond the configured setting then what happens?  Does it grow as needed?  Or does the email fail at that point?

matching:
----------
* Filter subject keywords: has a default value of "^[\s]*([\w]+\s?:[\s]*)+"  What is the purpose of this regex?  What does it do?
* Max # of subject keywords or recipients: The default of 20 seems reasonable but what would be the downside of setting it to 40?
* Max diff allowed between subject keywords: The default is 0. I've seen e-mails with an extra keyword in the subject line simply not get delivered.  Do you allow any leniance with this process by bumping up this number?  Otherwise, what is your process for handling emails that don't get imported into CRM simply because there's an extra word in the subject line?
* Minimum # of recipients required to match: Why is this set to 2? Seems like most e-mails will only have 1 recipient?  Maybe I'm not clear on what this setting means?


Viewing all articles
Browse latest Browse all 79901

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>