CRM Facts

fact_dailycalldetails__v

This fact summarizes multichannel activities captured in Veeva CRM that have occurred with an Account, User and Product. The types of activities in this fact include Call Details, Call Samples and Call Key Messages.

Call Detail Related Facts

Call Details recorded in CRM allow field users to capture product detail related activities in CRM. This includes products discussed and product priority. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • User: Identified as the owner of the related Call record
  • Product: Identified on the Call Detail record

Fact

Description

total_call_details__v

Count of total call detail records

total_call_details_on_parent_calls__v

Count of total call detail records where related call is marked as a parent call.  call2_vod__v.is_parent_call_vod__v = 1

total_primary_call_details__v

Count of total call details records where the record equals call2_detail_vod__v.detail_priority_vod__v = 1

total_secondary_call_details__v

Count of total call details records where the record equals call2_detail_vod__v.detail_priority_vod__v = 2

total_tertiary_call_details__v

Count of total call details records where the record equals call2_detail_vod__v.detail_priority_vod__v = 3

Call Sample Related Facts

Call Samples recorded in CRM allow field users to capture product sample related activities in CRM. This includes products disbursed and type of disbursement. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • User: Identified as the owner of the related Call record
  • Product: Identified on the Call Sample record

Fact

Description

total_brc_samples_disbursed_on_calls__v

Sum of Call Sample quantities where the product disbursed is of type “BRC”

total_call_samples_disbused__v

Sum of the values of all call2_sample_vod__v in the quantity_vod__v

total_calls_with_samples__v

Distinct count of Calls with related Call Sample records

total_promotional_items_disbused_on_calls__v

Sum of Call Sample quantities where the product disbursed is of type “Promotional”

Call Key Message Related Facts

Call Key Messages recorded in CRM allow field users to capture key messages in CRM. This includes key messages delivered during calls. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • User: Identified as the owner of the related Call record
  • Product: Identified on the Call Key Message record

Fact

Description

sum_call_key_message_duration__v

Sum of the values in the duration field on Call Key Messages when the field clm_presentation_vod__c has a value

total_call_key_messages__v

Count of all Call Key Message records

total_call_key_messages_clm__v

Count of Call Key Message records where there is a value in the field CLM Presentation

total_call_key_messages_non_clm__v

Count of Call Key Message records where there is no value in the field CLM Presentation

fact_CRM_calls__v

This fact summarizes call related activities where a Call Detail and Call Sample have occurred with an Account and a Product. It is at the Call, Call Detail, Call Discussion, Call Sample, Product, Territory and User level.

Call Detail Related Facts

Call Details recorded in CRM allow field users to capture product detail related activities in CRM. This includes products discussed and product priority. All of the following facts can be analyzed by the following dimensions which are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • Call Discussion: Identified as the Call Discussion records for the related Call record
  • Call Sample: Identified as the Call Sample records for the related Call record
  • User: Identified as the owner of the related Call record
  • Product: Identified on the Call Detail record
  • Territory: Territory is captured from the stamped value on the call record

Fact

Description

total_call_details__v

Count of total call detail records

total_call_details_on_parent_calls__v

Count of total call detail records where related call is marked as a parent call.  call2_vod__v.is_parent_call_vod__v = 1

total_primary_call_details__v

Count of total call details records where the record equals call2_detail_vod__v.detail_priority_vod__v = 1

total_secondary_call_details__v

Count of total call details records where the record equals call2_detail_vod__v.detail_priority_vod__v = 2

total_tertiary_call_details__v

Count of total call details records where the record equals call2_detail_vod__v.detail_priority_vod__v = 3

Call Sample Related Facts

Call Samples recorded in CRM allow field users to capture product sample related activities in CRM. This includes products disbursed and type of disbursement. All of the following facts can be analyzed by the following dimensions which are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • Call Discussion: Identified as the Call Discussion records for the related Call record
  • Call Detail: Identified as the Call Detail records for the related Call record
  • User: Identified as the owner of the related Call record
  • Product: Identified on the Call Detail record
  • Territory: Territory is captured from the stamped value on the call record

Fact

Description

total_brc_samples_disbursed_on_calls__v

Sum of Call Sample quantities where the product disbursed is of type “BRC”

total_call_samples_disbused__v

Sum of the values of all call2_sample_vod__v in the quantity_vod__v

total_calls_with_samples__v

Distinct count of Calls with related Call Sample records

total_promotional_items_disbused_on_calls__v

Sum of Call Sample quantities where the product disbursed is of type “Promotional”

Call Discussion Related Facts

Call Discussions recorded in CRM allow field users to capture product discussion topics in CRM. All of the following facts can be analyzed by the following dimensions which are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • Call Detail: Identified as the Call Detail records for the related Call record
  • Call Sample: Identified as the Call Sample records for the related Call record
  • User: Identified as the owner of the related Call record
  • Product: Identified on the Call Detail record
  • Territory: Territory is captured from the stamped value on the call record

Fact

Description

total_call_discussions__v

Count of all Cal Discussions that have been recorded

fact_crm_engage_best_times__v

This fact provides recommendations for the best time to schedule Engage Meetings with Accounts. To populate this table, we look at all interactions with Accounts across all territories, products and users, to provide the best time at the Account level. Recommendations are provided in two hour increments based on the quantity and length of meetings that have occurred.

Meetings used to calculate values if the following criteria are met:

  • Meeting_outcome_status_vod__c on the Remote Meeting object have the value of “Meeting_started_with_attendees_vod”
  • Meetings last fewer than 180 minutes
  • Meetings last longer than 3 minutes

All of the following facts can be analyzed by the following dimensions which are based on the following values:

  • Account: Identified as the account on the call record which is recorded on the Remote Meeting Attendee record.
  • Attendee Type of “Host” is excluded from this fact

Fact

Description

email_address_last_used__v

Email address on the Sent Email record for the most recent Approved email with the status of “opened”

first_day_component__v

Day of the week with the most meetings attended

first_meeting_average_duration__v

Average length of time for meetings that have occurred during this time slot

first_meeting_total__v

Count of meetings that have occurred during this time slot

first_time_component__v

2 hour window when the most meetings have occured. Provided in UTC

second_day_component

Day of the week with the second most meetings attended

second_meeting_average_duration__v

Average length of time for meetings that have occurred during this time slot

second_meeting_total__v

Count of meetings that have occurred during this time slot

second_time_component__v

2 hour window when the most meetings have occured. Provided in UTC

third_day_component__v

Day of the week with the third most meetings attended

third_meeting_average_duration__v

Average length of time for meetings that have occurred during this time slot
third_meeting_total__v Count of meetings that have occurred during this time slot
third_time_component__v 2 hour window when the most meetings have occured. Provided in UTC

fact_crm_engage_end_to_end__v

This fact displays metrics around Engage Meetings metrics to help with planning the meetings and interacting with the Accounts around these meetings.

fact_crm_daily_account_mc_activity__v

This fact summarizes multichannel activities captured in Veeva CRM that have occurred with an Account. The types of activities in this fact include Calls, Engage Meetings, Medical Events, Approved Emails, Medical Inquiries, Call Details and Call Key Messages.

Call Related Facts

Calls recorded in CRM allow field users to capture all aspects of their direction interactions with their accounts. This includes products discussed, content shown as well as channel of the activity. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • Territory: Assigned based off Account and User alignments on date of activity
  • User: User record that is used for this assignment is the owner of the call record

Fact

Description

total_calls__v

Count of all call2 records that aren’t marked as deleted

total_call_detail_only__v

Count of all call2 records with call type of “Detail Only” and aren’t marked as deleted

total_calls_detail_with_sample__v

Count of all call2 records with call type of “Detail With Sample” and aren’t marked as deleted

total_calls_submitted__v

Count of all call2 records with call status of “submitted_vod” and aren’t marked as deleted

total_calls_saved__v

Count of all call2 records with call status of “saved_vod” and aren’t marked as deleted

total_calls_planned__v

Count of all call2 records with call status of “planned_vod” and aren’t marked as deleted

total_calls_clm__v

Count of all call2 records with the field clm_vod__c marked as “1” and aren’t marked as deleted

total_calls_sampled__v

Count of all call2 records with the field sampled_call_vod__c marked as “1” and aren’t marked as deleted

total_calls_parent__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1” and aren’t marked as deleted

total_calls_group_detail__v

Count of all call2 records with call type of “Group Detail” and aren’t marked as deleted

total_calls_group__v

Count of all call2 records with call type of “Group Detail” or “Group Detail With Sample” and aren’t marked as deleted

total_calls_group_detail_with_sample__v

Count of all call2 records with call type of “Group Detail With Sample” and aren’t marked as deleted

total_calls_call_only__v

Count of all call2 records with call type of “Call Only” and aren’t marked as deleted

total_calls_event_only__v

Count of all call2 records with call type of “Event Only” and aren’t marked as deleted

total_calls_event_detail__v

Count of all call2 records with call type of “Event Detail” and aren’t marked as deleted

total_calls_parent_engage__v

Count of parent call2 records with an associated remote meeting and isn’t marked as deleted

total_calls_no_content_parent_engage__v

Count of parent call2 records that have no call key messages associated to them but do contain an associated remote meeting and isn’t marked as deleted

total_calls_parent_f2f__v

Count of parent call2 records with no associated remote meeting and the call is not marked as deleted

total_calls_submitted_parent_engage__v

Count of parent call2 records that are submitted, contain an associated remote meeting and aren’t marked as deleted

total_calls_submitted_parent_f2f__v

Count of parent call2 records that are submitted, don’t contain an associated remote meeting and aren’t marked as deleted

total_calls_saved_parent_engage__v

Count of parent call2 records that are saved, contain an associated remote meeting and aren’t marked as deleted

total_calls_saved_parent_f2f__v

Count of parent call2 records that are saved, don’t contain an associated remote meeting and aren’t marked as deleted

total_calls_planned_parent_engage__v

Count of parent call2 records that are planned, contain an associated remote meeting and aren’t marked as deleted

total_calls_planned_parent_f2f__v

Count of parent call2 records that are planned, don’t contain an associated remote meeting and aren’t marked as deleted

total_calls_clm_parent_f2f__v

Count of parent call2 records that don’t contain an associated remote meeting or call key messages and isn’t marked as deleted

total_call_key_message_duration_parent_f2f__v

Sum of duration field on call key messages for calls where the related call has is_parent_call_vod__c marked as “1”, there is no associated Remote Meeting record and the call isn’t marked as deleted

total_call_key_message_parent_f2f__v

Total call key messages for calls where the related call has is_parent_call_vod__c marked as “1”, there is no associated Remote Meeting record and the call isn’t marked as deleted

total_call_key_message_duration_parent_enage__v

Sum of duration field on call key messages for calls where there is an associated remote meeting, the call is marked as a parent call and isn’t marked as deleted

total_call_details_parent_engage__v

Count of detail records with an associated remote meeting, the call is marked as a parent call and isn’t marked as deleted

total_call_details_parent_f2f__v

Count of detail records with no associated remote meeting, the call is marked as a parent call and isn’t marked as deleted

total_call_details_parent__v

Count of call detail records where the associated call is a parent call and isn’t marked as deleted

average_remote_meeting_duration_parent_engage__v

Average duration for each remote meeting attendee. To determine average, the earliest join time is used as well as the latest leave time for each account on a single remote meeting

Medical Inquiry Facts

  • Account: Identified as the Account on the Medical Inquiry record
  • Date: The created date of the Medical Inquiry
  • Territory: Assigned based off Account and User alignments on date of activity
  • User: The User record that is used for this assignment is the creator of the medical inquiry record

Fact

Description

total_medical_inquiries__v

Count of all medical inquiry records that aren’t marked as deleted

total_medical_inquiries_new__v

Count of all medical inquiry records with a status of “New” and aren’t marked as deleted

total_medical_inquiries_closed__v

Count of all medical inquiry records with a status of “Closed” and aren’t marked as deleted

total_medical_inquiries_submitted__v

Count of all medical inquiry records with a status of “Submitted” and aren’t marked as deleted

total_medical_inquiries_saved__v

Count of all medical inquiry records with a status of “Saved” and aren’t marked as deleted

Sent Email Facts

  • Account: Identified as the Account on the Sent Email record
  • Date: Identified as the created date of the Sent Email record
  • Territory: Assigned based off Account and User alignments on date of activity
  • User: The User record that is used for this assignment is the owner of the sent email record

Fact

Description

total_sent_emails__v

Count of all sent email records that aren’t marked as deleted

total_sent_emails_scheduled__v

Count of all sent email records with a status of “Scheduled_vod” that aren’t marked as deleted

total_sent_emails_group__v

Count of all sent email records with a status of “Group_vod” that aren’t marked as deleted

total_sent_emails_saved__v

Count of all sent email records with a status of “Saved_vod” that aren’t marked as deleted

total_sent_emails_pending__v

Count of all sent email records with a status of “Pending_vod” that aren’t marked as deleted

total_sent_emails_sent__v

Count of all sent email records with a status of “Sent_vod” that aren’t marked as deleted

total_sent_emails_delivered__v

Count of all sent email records with a status of “Delivered_vod” that aren’t marked as deleted

total_sent_emails_bounced__v

Count of all sent email records with a status of “Bounced_vod” that aren’t marked as deleted

total_sent_emails_unsubscribed__v

Count of all sent email records with a status of “Unsubscribed_vod” that aren’t marked as deleted

total_sent_emails_failed__v

Count of all sent email records with a status of “Failed_vod” that aren’t marked as deleted

total_sent_emails_marked_spam__v

Count of all sent email records with a status of “Marked_Spam_vod” that aren’t marked as deleted

total_sent_emails_dropped__v

Count of all sent email records with a status of “Dropped_vod” that aren’t marked as deleted

total_sent_emails_opened__v

Count of all sent email records marked as opened and aren’t marked as deleted

total_sent_emails_clicked__v

Count of all sent email records marked as clicked and aren’t marked as deleted

total_sent_emails_click_count__v

Sum of the click count field on all sent email records that aren’t marked as deleted

Call Key Message Facts

  • Account: Identified as the Account on the Call Key Message record
  • Date: Identified as the call date on the Call record
  • Territory: Assigned based off Account and User alignments on date of activity
  • User: The User record that is used for this assignment is the owner of the call record

Fact

Description

total_call_key_messages_clm__v

Total call key messages for calls where the related call has clm_vod__c marked as “1” and isn’t marked as deleted

total_call_key_message_duration__v

Sum of duration field on call key messages for calls where the related call has clm_vod__c marked as “1” and isn’t marked as deleted

Event Attendee Facts

  • Account: Identified as the Account on the Event Attendee record
  • Date: The created date of the Event Attendee record
  • Territory: Assigned based off Account and User alignments on date of activity
    • User: The User record that is used for this assignment is the creator of the event attendee record

Fact

Description

total_event_attendees__v

Count of Event Attendee records which aren’t marked as deleted

total_event_attendees_invited__v

Count of Event Attendee records with status of “Invited” and aren’t marked as deleted

total_event_attendees_accpeted__v

Count of Event Attendee records with status of “Accepted” and aren’t marked as deleted

total_event_attendees_attended__v

Count of Event Attendee records with status of “Attended” and aren’t marked as deleted

fact_crm_daily_account_product_content_mc_activity__v

This fact summarizes multichannel activities captured in Veeva CRM that have occurred with an Account with the following dimensions: Account, Product, Territory, User, Channel, Date and CRM Content. The types of activities in this fact include Calls, Medical Events, Approved Emails, Call Details and Call Key Messages.

Call Related Facts

Calls recorded in CRM allow field users to capture all aspects of their direct interactions with their accounts. This includes products discussed, content shown as well as channel of the activity. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • Channel: If a call has an associated Remote Meeting record it is set to “Engage”. If no associated Remote Meeting record than it is set to “Face to Face”
  • User: The User record that is used for this assignment is the owner of the call record
  • Territory: Assigned based off Account and User alignments on date of activity
  • Product: Call Detail facts use the product on Call Detail record. Call Key Message facts use the product from the Call Key Message record
  • CRM Content: Identified as the Key Message on the Call Key Message record

Fact

Description

calls_parent_submitted__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “submitted_vod” and aren’t marked as deleted

calls_parent_saved__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “saved_vod” and aren’t marked as deleted

calls_parent_planned__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “planned_vod” and aren’t marked as deleted

calls_parent_submitted_detail_only__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “submitted_vod”, call_type_vod__c is “Detail Only” and aren’t marked as deleted

calls_parent_saved_detail_only__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “saved_vod”, call_type_vod__c is “Detail Only” and aren’t marked as deleted

calls_parent_planned_detail_only__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “planned_vod”, call_type_vod__c is “Detail Only” and aren’t marked as deleted

calls_parent_submitted_detail_with_sample__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “submitted_vod”, call_type_vod__c is “Detail with Sample” and aren’t marked as deleted

calls_parent_saved_detail_with_sample__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “saved_vod”, call_type_vod__c is “Detail with Sample” and aren’t marked as deleted

calls_parent_planned_detail_with_sample__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “planned_vod”, call_type_vod__c is “Detail with Sample” and aren’t marked as deleted

calls_parent_submitted_call_only__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “submitted_vod”, call_type_vod__c is “Call Only” and aren’t marked as deleted

calls_parent_saved_call_only__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “saved_vod”, call_type_vod__c is “Call Only” and aren’t marked as deleted

calls_parent_planned_call_only__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “planned_vod”, call_type_vod__c is “Call Only” and aren’t marked as deleted

calls_parent_submitted_group_detail__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “submitted_vod”, call_type_vod__c is “Group Detail” and aren’t marked as deleted

calls_parent_saved_group_detail__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “saved_vod”, call_type_vod__c is “Group Detail” and aren’t marked as deleted

calls_parent_planned_group_detail__v

Count of all call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “planned_vod”, call_type_vod__c is “Group Detail” and aren’t marked as deleted

calls_submitted__v

Count of all call2 records with the field status_vod__c is “submitted_vod” and aren’t marked as deleted

calls_saved__v

Count of all call2 records with the field status_vod__c is “saved_vod” and aren’t marked as deleted

calls_planned__v

Count of all call2 records with the field status_vod__c is “planned_vod” and aren’t marked as deleted

calls_submitted_detail_only__v

Count of all call2 records with the field status_vod__c is “submitted_vod”, call_type_vod__c is “Detail Only” and aren’t marked as deleted

calls_saved_detail_only_v

Count of all call2 records with the field status_vod__c is “saved_vod”, call_type_vod__c is “Detail Only” and aren’t marked as deleted

calls_planned_detail_only__v

Count of all call2 records with the fieldstatus_vod__c is “planned_vod”, call_type_vod__c is “Detail Only” and aren’t marked as deleted

calls_submitted_detail_with_sample__v

Count of all call2 records with the field status_vod__c is “submitted_vod”, call_type_vod__c is “Detail with Sample” and aren’t marked as deleted

calls_saved_detail_with_sample__v

Count of all call2 records with the field status_vod__c is “saved_vod”, call_type_vod__c is “Detail with Sample” and aren’t marked as deleted

calls_planned_detail_with_sample__v

Count of all call2 records with the fieldstatus_vod__c is “planned_vod”, call_type_vod__c is “Detail with Sample” and aren’t marked as deleted

calls_submitted_call_only__v

Count of all call2 records with the field status_vod__c is “submitted_vod”, call_type_vod__c is “Call Only” andaren’t marked as deleted

calls_saved_call_only__v

Count of all call2 records with the field status_vod__c is “saved_vod”, call_type_vod__c is “Call Only” and aren’t marked as deleted

calls_planned_call_only__v

Count of all call2 records with the fieldstatus_vod__c is “planned_vod”, call_type_vod__c is “Call Only” and aren’t marked as deleted

calls_submitted_group_detail__v

Count of all call2 records with the field status_vod__c is “submitted_vod”, call_type_vod__c is “Group Detail” and aren’t marked as deleted

calls_saved_group_detail__v

Count of all call2 records with the field status_vod__c is “saved_vod”, call_type_vod__c is “Group Detail” and aren’t marked as deleted

calls_planned_group_detail__v

Count of all call2 records with the fieldstatus_vod__c is “planned_vod”, call_type_vod__c is “Group Detail” andaren’t marked as deleted

calls_clm_submitted__v

Count of Call2 records with the field status_vod__c is “submitted_vod”, clm_vod__c is true and aren’t marked as deleted

calls_no_clm_submitted__v

Count of Call2 records with the field status_vod__c is “submitted_vod”, clm_vod__c is false and aren’t marked as deleted

calls_clm_saved__v

Count of Call2 records with the field status_vod__c is “saved_vod”, clm_vod__c is true and aren’t marked as deleted

calls_no_clm_saved__v

Count of Call2 records with the field status_vod__c is “saved_vod”, clm_vod__c is false and aren’t marked as deleted

calls_clm_parent_submitted__v

Count of Call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “submitted_vod”, clm_vod__c is true and aren’t marked as deleted

calls_no_clm_parent_submitted__v

Count of Call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “submitted_vod”, clm_vod__c is false and aren’t marked as deleted

calls_clm_parent_saved__v

Count of Call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “saved_vod”, clm_vod__c is true and aren’t marked as deleted

calls_no_clm_parent_saved__v

Count of Call2 records with the field is_parent_call_vod__c marked as “1”, status_vod__c is “saved_vod”, clm_vod__c is false and aren’t marked as deleted

call_details_parent_submitted__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “submitted_vod” and aren’t marked as deleted

call_details_parent_saved__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “saved_vod” and aren’t marked as deleted

call_details_parent_planned__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “planned_vod” and aren’t marked as deleted

call_details_parent_submitted_detail_only__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “submitted_vod”, call_type_vod__c as “Detail Only” and aren’t marked as deleted

call_details_parent_saved_detail_only__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “saved_vod”, call_type_vod__c as “Detail Only” and aren’t marked as deleted

call_details_parent_planned_detail_only__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “planned_vod”, call_type_vod__c as “Detail Only” and aren’t marked as deleted

call_details_parent_submitted_detail_with_sample__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “submitted_vod”, call_type_vod__c as “Detail with Sample” and aren’t marked as deleted

call_details_parent_saved_detail_with_sample__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “saved_vod”, call_type_vod__c as “Detail with Sample” and aren’t marked as deleted

call_details_parent_planned_detail_with_sample__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “planned_vod”, call_type_vod__c as “Detail with Sample” and aren’t marked as deleted

call_details_parent_submitted_call_only__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “submitted_vod”, call_type_vod__c as “Call Only” and aren’t marked as deleted

call_details_parent_saved_call_only__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “saved_vod”, call_type_vod__c as “Call Only” and aren’t marked as deleted

call_details_parent_planned_call_only__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “planned_vod”, call_type_vod__c as “Call Only” and aren’t marked as deleted

call_details_parent_submitted_group_detail__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “submitted_vod”, call_type_vod__c as “Group Detail” and aren’t marked as deleted

call_details_parent_saved_group_detail__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “saved_vod”, call_type_vod__c as “Group Detail” and aren’t marked as deleted

call_details_parent_planned_group_detail__v

Count of Call Detail records where the associated call has the fields is_parent_call_vod__c marked as “1”, status_vod__c as “planned_vod”, call_type_vod__c as “Group Detail” and aren’t marked as deleted

call_key_message_duration_parent_submitted__v

Sum of duration field on Call Key Messages for calls where the Call is marked as a parent call and isn’t marked as deleted

call_key_message_duration_submitted__v

Sum of duration field on Call Key Messages for calls where the Call is marked as a parent call, status is submitted and isn’t marked as deleted

call_key_message_duration_parent__v

Sum of duration field on Call Key Messages for calls where the Call has status is submitted and isn’t marked as deleted

call_key_message_parent_submitted__v

Count of Call Key Messages where the Call is marked as a parent call, is submitted and isn’t marked as deleted

call_key_message_submitted__v

Count of Call Key Messages where the Call is marked as submitted and isn’t marked as deleted

call_key_message_parent__v

Count of Call Key Messages where the Call is marked as a parent call and isn’t marked as deleted

Remote Meeting Related Facts

Remote Meetings recorded in CRM allow field users to capture all aspects of their remote interactions with their accounts. This includes products discussed and content shown.. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Call record
  • Date: Identified as the call date on the Call record
  • Channel: Engage
  • User: The User record that is used for this assignment is the owner of the call record
  • Territory: Assigned based off Account and User alignments on date of activity
  • Product: Identified as the product on the associated Call Detail record
  • CRM Content: Identified as the Key Message on the associated Call Key Message record

Fact

Description

remote_meeting_duration_parent_submitted__v

Max duration value from all attendees for a single remote meeting where the related Call is marked as a parent Call, is submitted and isn’t marked as deleted

remote_meeting_duration_submitted__v

Max duration value from all attendees for a single remote meeting where the related Call is marked as submitted and isn’t marked as deleted

remote_meeting_duration_parent__v

Max duration value from all attendees for a single remote meeting where the related Call is marked as a parent Calland isn’t marked as deleted

Sent Email Related Facts

Sent Meetings recorded in CRM allow field users to capture all aspects of their email interactions with their accounts. This includes products discussed and content shown. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Sent Email record
  • Date: Identified as the created date on the Sent Email record
  • Channel: Approved Email
  • User: The User record that is used for this assignment is the owner of the Sent Email record
  • Territory: Assigned based off Account and User alignments on date of activity
  • Product: Identified as the product on the Sent Email record
  • CRM Content: Identified as the Template on the Sent Email record

Fact

Description

sent_emails_sent_delivered__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod” that aren’t marked as deleted

sent_emails_sent_delivered_opened__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have a been marked as opened and aren’t marked as deleted

sent_emails_sent_delivered_clicked__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have been marked as clicked and aren’t marked as deleted

sent_emails_sent_delivered_account__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have a record type of Account and aren’t marked as deleted

sent_emails_sent_delivered_opened_account__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have been marked as opened with an Account record type and aren’t marked as deleted

sent_emails_sent_delivered_clicked_account__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have been marked as clicked with an Account record type and aren’t marked as deleted

sent_emails_sent_delivered_call__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have a record type of Call and aren’t marked as deleted

sent_emails_sent_delivered_opened_call__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have been marked as open with a record type of Call aren’t marked as deleted

sent_emails_sent_delivered_clicked_call__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have been marked as clicked along with a record type of Call and aren’t marked as deleted

sent_emails_sent_delivered_engage__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have a record type of Engage and aren’t marked as deleted

sent_emails_sent_delivered_opened_engage__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have been marked as opened with a record type of Engage and aren’t marked as deleted

sent_emails_sent_delivered_clicked_engage__v

Count of all sent email records with a status of “Sent_vod” or “Delivered_vod”, have been marked as clicked with a record type of Engage and aren’t marked as deleted

Event Attendee Related Fact

Sent Meetings recorded in CRM allow field users to capture all aspects of their email interactions with their accounts. This includes products discussed and content shown.. All of the following facts can be analyzed by the following dimensions where are based on the following values:

  • Account: Identified as the Account on the Event Attendee record
  • Date: Identified as the start date of the Medical Event record
  • Channel: Medical Event
  • User: The User record that created the Event Attendee record
  • Territory: Assigned based off Account and User alignments on date of activity

Fact

Description

event_attendees_attended__v

Total Event Attendee records with the status of Attended and aren’t marked as deleted

Total Activities

Sum of top level multichannel activities recorded in CRM. Activities are defined as:

  • Sent Emails
  • Calls
  • Event Attendee

All of the following facts can be analyzed by the following dimensions which are based on the following values:

  • Account: Account listed on the Sent Email/Call/Event Attendee records
  • User: Owner of the Call/Sent Email or the creator of the Event Attendee records
  • Date:
  • Sent Email - Sent Date
  • Calls - Call Date
  • Event Attendee - Medical Event Start Date
  • Territory: Assigned based off Account and User alignments on date of activity

Fact

Description

total_activities__v

Sum of Sent Emails, Calls and Event Attendee records that aren’t marked as deleted, with the following criteria:

  • Sent Emails are marked as Sent or Delivered and have a Sent Date
  • Event Attendee are marked as Attended

total_activities_parent__v

Sum of Sent Emails, Calls and Event Attendee records that aren’t marked as deleted, with the following criteria:

  • Sent Emails are marked as Sent or Delivered and have a Sent Date
  • Event Attendee are marked as Attended
  • Calls are marked as parent Calls