About Lagging Feeds

A feed is “lagging” when a dealer's DMS has not delivered data to DealerVault in at least 7 days.  This means DealerVault does not have current data and cannot deliver it to Clarivoy.

Investigating DealerVault Lagging Feeds

To determine if a feed is lagging:

1. Go to https://vendor.dealervault.com/Vendor/Feed/CompleteFeeds
   (Alternately, login at https://vendor.dealervault.com and click on Feeds → Complete Feeds)
2. Search for the Dealership Name or Property ID
3. Ensure our property ID is correct in the Dealer ID column.
   1. If the Dealer ID is not correct, we need to make a correction. Open a ticket on the Tickets Board for Ops Team including the incorrect Dealer ID and the correct Property ID.
4. Review the dates shown
   1. Last Poll Date = the last date that DealerVault successfully received sales from the dealer.
      1. If Last Poll Date is recent, but Last Delivery Date is not, then DealerVault is processing data they recently received from the dealer and should deliver it to us with the next 1-2 days.
      2. If the Last Poll Date is before the end of the processing month, this explains why we do not have complete sales for the month. The dealer's DMS has not sent sales to DealerVault.
      3. 7 days is considered officially "lagging" per the DealerVault process. See DealerVault Lagging Feeds process below.
5. Last Successful Delivery = the last date that DealerVault successfully delivered sales data to Clarivoy's SFTP server
   1. If the Last Successful Delivery date was yesterday or today, it may take 1 more day for processing before we can verify the data in Looker.
   2. If Last Successful Delivery date is NOT recent, check Last Poll Date
   3. If Last Poll date IS current, we may need to wait a few days. Note this in the task updates and check again in a few days.
   4. If more than 3 days have gone by and the Last Successful Delivery does not change, there may be an issue. Open a DealerVault Support ticket and put a copy/screenshot in the conversation updates. Continue to follow up on this ticket until the issue is resolved.
6. Max Content Date = the most recent Sales Date in the last data that DealerVault received from the dealer.
   1. NOTE: Max Content Date is the latest date for which DV has sales for this client. Max Content Date is based on the Last Poll Date (NOT Last Successful Delivery). Just because DealerVault has recent sales in the Max Content Date does not mean they have delivered them to us just yet. Data typically takes a day or two for DV to process and send to Clarivoy from the time they receive it. Also, these sales could be B2B Sales (Wholesale/Dealer Trade/Fleet) which we filter out/exclude so you may not see them on the Sales Counts Verification board.
   2. If this does not line up with what we are seeing in Sales Standardized, the most recent sale may have been a B2B sale that got filtered out.
       

Date Scenarios

• If Last Poll Date is recent, but Last Delivery Date is NOT, then DealerVault is processing data they recently received from the dealer and should deliver it to us with the next 1-2 days.
• If Last Poll Date is NOT recent, the feed is lagging.
  • We should have already caught this on the Lagging Feed report and followed the appropriate steps (opened a DealerVault Support ticket if NOT Reynolds & Reynolds or UCS DMS). If so, there will be notes in the monthly task conversation with the ticket info.
  • If there are no notes (Clarivoy has not taken action yet):
    • If the task is DMS Done, leave it as that status
    • If the task is NOT DMS Done and we are waiting on data needed to process a current month, set the status to DealerVault Lagging Stuck.
    • 🚨 Monday automations will set Data required email status column to Send CSL DealerVault Lagging Notification.  See Working a Lagging Feed below for information on what to do.

Requesting DV Help with a Lagging Feed

As of January 2026, it is the CS Team's responsibility to investigate and open tickets for Lagging DealerVault feeds and follow up on them. Follow steps below for Investigating a DealerVault Feed Issue.

1. CS - Check the DMS task on the SA+TVA Monthly Tasks board. If there are no notes on the task (Clarivoy has not taken action yet):
   1. If the task is DMS Done, leave it as that status. We do not want to interrupt processing of the previous months' data.
   2. If the task is NOT DMS Done and we are waiting on data needed to process a current month, see Working a Lagging Feed below.

DV Process for Lagging Feeds

1. When a dealer's data lags for 7 consecutive days, DV will open a Support Ticket and send 3 email communications notifying the dealer of the lag and the impact to their programs - at Day 7, Day 9, and Day 11. After 11 days of lagging data and no response from the dealership, DV communication to the dealership ends.
   1. DealerVault will attempt to work with the dealer to reconnect the DMS and obtain catch-up data.  Dealers need to schedule an appointment with DealerVault at this link to reconnect their DMS:  Lagging Data Appointment
   2. Once DealerVault Support reconnects the DMS and obtains catch-up data, their normal process is to push a catch-up file to Clarivoy.
      1. If the Support agent fails to push a catch-up file to Clarivoy, but you can see that the feed is current (not lagging) in the Complete Feeds view, you can manually request a Catch-Up file.  See Manually Requesting a Catch-Up File.

Lagging Feeds Report

As of January 2026, it is the CS Team's responsibility to investigate and open DealerVault Support tickets for Lagging DealerVault feeds and follow up on them. 

1. DV sends vendors (Clarivoy) a weekly report of lagging feeds.
2. Each week, the CS Team reviews the lagging feeds report
3. Locate the Monthly DMS Task on SA+TVA Ops Monthly Tasks
4. If the task is DMS Done, leave it as that status, but set Data required email status column to Send CSL DealerVault Lagging Notification
5. If the task is NOT DMS Done and we are waiting on data needed to process a current month, set the status to DealerVault Lagging Stuck.
   1. 🚨 This will automatically flip the Data required email status column to Send CSL DealerVault Lagging Notification.
   2. See Working a Lagging Feed below.

Working a Lagging Feed

This Process varies by DMS:

Manually Requesting a Catch-Up File

To manually request a catch-up file be pushed to Clarivoy:

1. Login to DealerVault 
2. Click Feeds
3. Click Completed Feeds
4. Find the feed you need
5. In the Action column, click the Edit Next Delivery clock icon   
6. Select Catch Up and enter the Start Date and End Date.

Reynolds & Reynolds dealers on DV

Dealers on Reynolds & Reynolds DMS must follow manual steps to "push" updated data from their DMS to DealerVault on a regular basis. Step-By-Step Instructions for dealers to push R&R data to DV can be found here: https://clarivoy.helpjuice.com/dms-sales-data/reynolds-reynolds-setting-up-dms-sales-reports#pushing-your-sales-data-to-dealervault-1

Many dealers using R&R DMS fail to do this on a regular basis, resulting in lagging feeds, so we developed a new "reminder" process for these dealers.

• 🚨 When a DMS task is set to status "Waiting on DMS", if Vendor column is "Reynolds & Reynolds DMS", Monday automation will:

Set Data Required Email status column to "Send Reynolds & Reynolds DV Email"

🚨 On select days each month (3, 7, 10, 14, 21, 28), if Data Required Email status column is set to "Send Reynolds & Reynolds DV Email", Monday automation will:

• Send a reminder email to the Contact Email listed on the task (if one exists), reminding the dealer that they need to manually push their R&R DMS data to DealerVault, with a link to the step-by-step instructions.