Leads Data Combined

Any Leads data that cannot be mapped specifically or accurately to a specific rooftop may be loaded to the parent property.  Reasons may include:

• Multiple stores share 1 CRM account
• Multiple stores share 1 Call Tracking account
• The dealer group has only 1 website, in which case the Chat data would be loaded to the parent property
• The dealer group has a separate parent website with Chat on it
• A vendor's system is unable to produce a leads file that contains a Dealership Name column
• The dealership names in the Dealership Name column are not specific enough to be mapped to individual properties (for example, if values were: Chevrolet, Honda, Ford)
• CRMs may often contain leads attributed to the auto group name only (example: store name is ABC Auto Group).  Load these leads to the parent property.

Exceptions

• If a CRM contains only 1 store for all properties, load the data to the Parent Property.
• If a CRM contains multiple stores but some properties are combined, then for each combined store simply choose 1 of the properties it contains to map it to.  The reason we do this is so the dealer can enter ad spend for the sources on one of these properties.
  • Example:  A CRM contains these stores:
             ▫︎  ABC Ford            ← load data to the ABC Ford property
             ▫︎  ABC Toyota        ← load data to the ABC Toyota property 
             ▫︎  ABC BMW/Mini  ← if we have separate properties for ABC BMW and ABC Mini, choose one of the properties to map this data to)

Process for Loading Leads Data to a Parent Property

1. During Onboarding:
   1. Ops Team is to notify the CSL the first time data must be loaded to a Parent Property so the CSL is aware.  Typically, this is done in the Onboarding task in Rocketlane.
   2. In the Rocketlane Onboarding Task, go to the Additional Info tab, then under the private section Core Data Task Fields:
      1. Enter a note in the Task Note field indicating what stores are sharing an account and where the data was mapped.  Example:  Chevy and Ford stores are combined in the CRM as “ABC Autos Eastgate” and data is mapped to the parent property (12345).
      2. Update the Task Property ID field to either add the parent property ID or replace with the parent property ID.
2. After Onboarding:
   1. Ops Team is to notify the CSL the first time data must be loaded to a Parent Property so the CSL is aware. Tag the CSL in an update on the SA+TVA Monthly Tasks board item.
   2. In the Monthly Tasks board item, add a note to the Notes field indicating what stores are sharing an account and where the data was mapped.  Example:  Chevy and Ford stores are combined in the CRM as “ABC Autos Eastgate” and data is mapped to the parent property (12345).
   3. Add the parent property ID to the monthly task name.
   4. If API or Scraper, clear the Processing Link column.  Make.com will automatically generate a new leads verification link the following morning.
3. Loading Data:
   1. API:  In the DMUI Property setup, enter the API key on the parent property on the 3P Keys page.
   2. Scraper and Automated Report:
      1. Map Property Alias - Make sure you map the property alias to the parent property ID.
   3. Download, Collect, or Automated Report:  
      1. Dropbox - Follow the same DropBox folder hierarchy structure are normal, except name the property folder with the automotive group and the word "Parent" and the Property ID # appended to it in parenthesis.  Example: Cardinale Automotive Group Parent (49831)
4. Update the Clients Board.  This step is important so that we include the parent property data in the Prelim QA.
   1. Locate the client on the Clarivoy Clients board
   2. Enter the parent property ID number in the Parent Property ID column.
   3. This field is mirrored to the Clarivoy Properties board (hidden) and subsequently the SA+TVA Ops Overview board.
   4. The following morning, Make.com will update the Ops Overview QA Link column to include the parent property ID for all delivery items for that particular client.

Sales Data Combined

Clarivoy's Sales Attribution reporting is based on how the dealer's DMS accounts are split up.  Clarivoy can report 1 property for every DMS account.  We can also combine multiple DMS accounts into 1 Clarivoy Property, but we typically cannot split 1 DMS account into multiple Clarivoy Properties - see exceptions below.

If Sales data cannot be mapped specifically or accurately to a specific property because multiple stores share 1 DMS account:

• DealerVault - DealerVault can sometimes split sales from 1 DMS account into multiple feeds.  They usually need a specific field in the DMS to identify which store each sale belongs to.  Occasionally they can split sales by filtering the stock numbers.  You will need to open a DealerVault Support ticket to ask if this is possible.
• CDK - There is no way to split CDK sales feeds.  We will be unable to report on these properties separately as multiple Clarivoy properties UNLESS the dealer wants to go COLLECT and manually split their sales into multiple files before uploading the files to us each month.
• Tekion - There is no way to split Tekion sales feeds.  We will be unable to report on these properties separately as multiple Clarivoy properties UNLESS the dealer wants to go COLLECT and manually split their sales into multiple files before uploading the files to us each month.