Need to combine with: https://clarivoy-squad.monday.com/docs/2450180928?blockId=45d20829-6fa3-4f23-945f-8795b37e1e73

Processes

1. CSLs perform Sales Count Verification during Onboarding
2. CSLs perform an initial investigation into Sale Count Discrepancies
3. If CSLs are unable to determine the cause of the discrepancy, they complete this Monday form:  Sale Count Discrepancies Investigation Request
   1. If the cause of the issue can be determined by the Monday form answers, 🚨 the CSL receives an automated email explaining the reason
   2. If the cause cannot be determined by the form answers, 🚨 Monday automations create a ticket on the Tickets board assigned to the Ops team.
4. Ops Team will investigate and notify the CSL of the results.

Looker Links

 Sales Count Verification 

Verify Sales here:
https://clarivoy.cloud.looker.com/dashboards/52?&Sales+Standardized+Sales+Date={item's NEW Start Date}+to&Property+ID={item's NEW Property ID}

Check for Wholesale/Fleet/DT not marked properly:
https://clarivoy.cloud.looker.com/dashboards/52?Sales+Standardized+Sales+Date=2+month&Sales+Raw%2FCDK+Raw+Sale+Type=-WHOLESALE%2C-W%2C-FLEET%2C-F%2C-X%2C-COMMERCIAL%2C-C%2C-Wholesale%2C-Fleet%2C-D%2C-DEALER+TRADE%2C-%22DEALER_TRADE%22%2C-DEALERTRADE%2C-DT&First+Name=EMPTY&RAW%2BCDK+ONLY%3A+Full+Name=-%25%5E%2C%25&Property+ID={item's NEW Property ID}

Possible Causes for Sale Count Discrepancies

• Dealer Counting Incorrectly
  • Not the same source
  • Not the same date field
  • Dealer may be including other deal statuses besides Finalized in their counts
  • Dealer is including "B2B" sales in their counts (Wholesale, Fleet, Dealer Trade, Commercial)
• Dealer is not marking Sale Type field properly in their DMS (Wholesale, Fleet, Dealer Trade, Commercial)
• Dealer is using custom B2B Sale Type values (ex: 1=Wholesale)
  • Solution: 
• Dealer is using a custom Sale Type field in their DMS
  • Solution for CDK = We can custom map this field, or custom map value exceptions.  Delete all existing sales data and run a manual query to repull the data.
  • Solution for DealerVault = You can request custom mappings from DealerVault for a specific dealer.  You need to know the exact name of the DMS field and specify that you want it mapped to Sale Type, overriding the default mapping.  Delete all existing sales data and have DV push only the data we need.
  • Tekion SFTP = We are unable to custom map fields for our Tekion integration.  The dealer will need to switch to COLLECT.
  • Other SFTP = Correct the mappings in clarivoy.claripedia.sales_schema_mapping_custom_headers.  Delete all existing sales data and reload the files.
  • Collect = Correct the mappings in clarivoy.claripedia.sales_schema_mapping_custom_headers.  Delete all existing sales data and reload the files.
• Missing Sales - We do not have a full range of data for the month, or are missing some sales.
  • DealerVault or Tekion = the vendor may have failed to push all sales to Clarivoy
  • CDK =  there may be issues with the dealer's CDK data lake
  • Solution = Open a support ticket with the data source (DealerVault, CDK, Tekion)
• Missing Backdata
• Date Field - Dealer is counting using a different date field than what our integration supports.
  • Solution = Dealer adjusts how they are counting sales
  • Solution =  Dealer changes to uploading a sales file each month (COLLECT).
• Filtering by ETL DAG
  • B2B Record
  • DB Duplicate
  • Duplicate
  • Invalid/Empty Date
  • Invalid VIN
  • Missing VIN
  • No PII
  • Property Not Active for This Date
  • Unparsable Vehicle Year
     
• Blank VINs - Often times CRMs include sales with no VIN number.  Clarivoy does not take in any sales without a VIN.  (This is because the VIN is used to “dedupe” sales data)
  • Solution = Dealer needs to fill in the VIN number on all sales in their CRM
  • Solution = If the dealer's DMS is syncing data with their CRM, there may be data sync issues.  Dealer should investigate with their DMS and/or CRM vendors.
• Blank or Invalid data - Sales are coming through with missing or unparsable information (Blank or Invalid Sale Date, Blank or Invalid Vehicle Year, No PII) - these sales would get filtered out as they do not meet our minimum data requirements.
  • Solution = Could be a mapping issue on DealerVault's end, our end, or an issue on the dealer's end.
• Sale Date changes - If a dealer enters a sale, then later changes the date on that sale,  both entries count as Sales in the dealer's data.  We have no way of identifying that the new date is a sale that was changed (instead of just the same car being sold multiple times within a month).  We dedupe based on same VIN, same Sale Date, same Property ID.
  • Solution = If the dealer is updating sale dates and this is causing duplicate sales, the dealer needs to switch to uploading a sales file each month (COLLECT).  This is the only way to ensure we receive only the final data and do not have duplicate sales for the same VIN on different dates.
• Finalized Sales only - Dealer is including sales that are not yet Finalized (pending financing, on order)
  • Solution = Clarivoy does not report on sales that are not yet finalized.
• Start Date Changes - If a dealer's Start Date is pushed up earlier and we attempt to load sales before the new Property Active Date is entered into the system, sales can be excluded/filtered out due to “Property Not Active for this Date”
• If Combo Property:  Missing DV feeds or CDK Subscriptions -  Is this property multiple stores combined into one Clarivoy property?
  • IF YES, does the dealer have multiple -FI instances (CDK) or multiple DMS accounts (all other DMS) for the property in question? 
  • Do we have all of those -FI instances or DMS Accounts setup to receive data?   We may not have all of the DV Feeds or CDK Subscriptions setup for a particular store.
  • Verify that we are receiving all Makes for this dealership by reviewing their sales data.  If any makes are missing, we are likely missing a sales feed/subscription.
• Sales Counts too High - Only IF our sales counts are "too high", the dealer could be sharing a DMS with another store and we are getting too many sales.
  • Is this store sharing an -FI instance (CDK) or DMS account with another store?  Check the sales data to ensure the New vehicle Makes we are receiving are as expected.  For example, if we have a Volkswagen only store with New Audi sales, that could indicate the store is sharing a DMS with another store (often on the same property).
    • Solution = if DV or Tekion, see if the vendor is able to split out the sales feed using a custom field in the dealer's DMS.
      • If yes, we will need to delete all existing sales data and have the vendor repush only the data we need
      • If not, we can ONLY report on this property as combined.  We may need to combine multiple properties on our end, marking another property as “DO NOT USE”
    • Solution = if CDK, we can only setup properties in the same manner as the CDK -FI instances are setup.  We may need to combine multiple properties on our end, marking another property as “DO NOT USE”
• Deduping - If the same VIN was sold more than once on the same day at the same property, our Sales Processing DAGs will filter out all but one of the sales as duplicates.