...
Identify visitors who have sales potential, but avoid aggressively identifying those who do not. Visitors without potential pollute Salesforce records and generate unnecessary requests.
The Send2CRM client offers various ways to record and calculate visitor intent purely on the client side which can help funnel only the useful leads into Salesforce.
Goals, Facets Segments and general data still allow Personalization to occur on the client side for anonymous visitors.
...
The shared key system rejects requests with HTTP error codes and a bare minimum of processing time when the key doesn’t match. This can be changed as often as you like.
Data storage
Salesforce also places limits on data storage, a total of 10GB for most production orgs. For very high traffic websites with a large number of visitor conversions additional data maintenance may be necessary.
Check the current Salesforce usage by searching for ‘Storage Usage’ in Setup.
Avoid identifying un-interesting website visitors. See Identified visitors section above.
Configure the Maximum Sessions and Store Event Data custom settings to avoid keeping un-wanted data.
Consider a scheduled job to delete visitor (send2crm__s2cVisitor__c) records that have not been modified for some time. The master-detail relationships will cause most related records to be deleted also, however this does not apply to lookup-related objects such as Leads and Contacts.