(For example, a page representing a PPC ad conversion.) Placing the script globally would record every single page view, regardless of importance, and potentially flood your CRM with too many records to process. TIP-for high-traffic sites, place the ClickDimensions tracking script only on pages that are most important for your sales and marketing users to see within CRM. Page Views (10,000 visitors/day x 1.5 pages viewed x 30 days) Visit records (10,000 visitors/day x 30 days) IP Organization records (95% from different IPs x 30 days) If each visitor only visits your site once a month, then more than 1 million total records per month would be created in your CRM. We recommend retaining these records for 3 months.įor example, let's say your site attracts 10,000 visits per day with most visitors originating from different IP addresses and each visitor views an average of 1.5 pages per visit. Stores each page on your site which a visitor has viewed. We recommend retaining these records for 3 months.
If your organization does not make use of these records, then the historical records prior to release 12.3 can be safely deleted. As of our 12.3 release, these records will no longer sync by default but this syncing can be re-enabled.
Anonymous Visitors (cdi_anonymousvisitor). We recommend keeping these records as multiple visitors may be tied to a single IP Organization. Stores the IP address of visitors to your site not duplicated if multiple visitors share an IP. If your organization needs these records for some reason, then you can open a Support ticket to request the syncing of these records, but this will cause a significant increase in the numbers of records generated. Once an Anonymous Visitor is identified, then the related Page Views, Visits, and IP Organizations will be synced back to CRM. Web AnalyticsĪs part of our 12.3 release, ClickDimensions will no longer sync Anonymous Visitor records or their unidentified Page Views, Visits, or IP Organizations to your CRM. If your company plans on sending weekly emails to 100,000 recipients, this could result in over 560,000 new records being added to D365 each month. Sent Email (or Excluded Recipients) records So if that Email Send results in a 25% open rate, 4% bounce rate, and 12% click-through rate, approximately 140,000 total new records would be added to the D365 environment the email was sent from. Email Events records for bounces, opens, clicks, and more would also be created, with each record containing one interaction per a recipient. For example, if an Email Send has 100,000 recipients, then 100,000 Sent Email (or Excluded Recipients) records will be created. The amount of data generated will vary depending on usage. These records should be kept to respect the subscription preferences of your recipients and to confirm their subscriptions. Store a recipient’s opt-in and opt-out preferences for your subscription lists. Posted Preferences (cdi_subscriptionpreference). We recommend retaining these records for 6 m onths. Store why a recipient was excluded from an Email Send-previous bounces, an unsubscribe (or opt-out preference), a missing email address, etc. Excluded Recipients (cdi_excludedemail). These records should be kept to respect the subscription preferences of your recipients. Hold global unsubscribe data whether that data has been imported from a legacy email marketing system or generated over time using ClickDimensions. This will prevent those types of Email Event records from syncing to CRM to save space, and you can still check the number of these events by viewing the Email Statistics within an Email Send record. You can also reach out via Support ticket to request that the syncing of Email Events for Delivery, Open, Click, Bounce or Spam events be disabled. 
We recommend retaining these records for 6 months.
One Email Event record is created for each interaction-opens, bounces, clicks, etc.-with an email. Store a summary of interactions for each recipient of an Email Send. Please note that these are only suggestions and you may decide to keep records for a longer or shorter period according to your organization's needs. This article will cover the methods by which these records are generated, as well as some of our suggestions for how long data should be retained before deletion to help prevent an over-abundance of data from slowing down your system.
#ESET ENDPOINT SECURITY V8 DRIVERS#
Two primary data drivers can potentially result in large volumes of data-email and web analytics. These entities are provided to allow your users to access ClickDimensions features as well as to store data generated by the integration. When the ClickDimensions solution is installed, it adds custom entities to your Dynamics 365 (D365) database and UI.
0 kommentar(er)
