Beta User Release of Engagement Insights

Our second reporting package for our new Insights Engine comes in the form of Engagement Insights. Lots more information here!

Company Table Configuration

• account_segment on cm_account___* - this column will be configurable in the UI and have access to all of the source account data

• lead_segment on cm_salesforce_lead - this column will be configurable in the UI and have access to all of the source lead data

  • This column can also be configured on cm_lead___salesforce

• company_segment on cm_company - this is a union of account_segment and lead_segment

  • This column will eventually replace account_segment as we know it today

• account_tier on cm_account___* - this column will be configurable in the UI and have access to all of the source account data

• lead_tier on cm_salesforce_lead - this column will be configurable in the UI and have access to all of the source lead data

  • This column can also be configured on cm_lead___salesforce

• company_tier  on cm_company - this is a union of account_tier and lead_tier

  • This column will eventually replace account_tier as we know it today

• account_fit on cm_account___* - this column will be configurable in the UI and have access to all of the source account data

• lead_fit on cm_salesforce_lead - this column will be configurable in the UI and have access to all of the source lead data

  • This column can also be configured on cm_lead___salesforce

• company_fit  on cm_company - this is a union of account_fit and lead_fit

  • This column will eventually replace account_fit as we know it today

Account Region and Subregion Configuration

• account_region and lead_region (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_subregion and lead_subregion (cm_account___salesforce and cm_salesforce_lead, respectively)

• street (cm_account___salesforce)

• city (cm_account___salesforce)

• state (cm_account___salesforce)

• postal_code (cm_account___salesforce)

• country (cm_account___salesforce)

• account_region  and lead_region  (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_subregion and lead_subregion (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_country_latitude  and lead_country_latitude (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_country_longitude and lead_coutnry_longitude (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_state_alpha and lead_state_alpha (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_state_latitude and lead_state_latitude (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_state_longitude and lead_state_longitude (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_city_ascii and lead_city_ascii (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_city_latitude and lead_city_latitude (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_city_longitude and lead_city_longitude (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_country_alpha and lead_country_alpha (cm_account___salesforce and cm_salesforce_lead, respectively)

• account_i_region and lead_i_region (cm_account___salesforce and cm_salesforce_lead, respectively)

These columns are used in cm_company___salesforce to calculate the following new columns:

• company_region

• company_subregion

• company_country_latitude

• company_country_longitude

• company_state_alpha

• company_state_latitude

• company_state_longitude

• company_city_ascii

• company_city_latitude

• company_city_longitude

• company_country_alpha

• company_i_region

MS Dynamics customers have these columns too, however their config screens are not yet in production.

The goal is to eventually replace cm_region and cm_subregion with company_region and company_subregion

Opportunity Configuration Update

campaign_id was added to cm_opportunity. This column is identical to cm_campaign_id. This was added as part of our ongoing effort to standardize our column names, with the intention here that campaign_id will eventually replace cm_campaign_id.