Data must be “pushed to Prod” in order to appear in the Production Dashboard (DMUI).  Data is pushed to Prod by inserting the Property ID and corresponding month into the Postgres table sales.production_ready.

When the Dashboard is determining what months are available in the date selection box for a specific property, it references the sales.production_ready table.  Dealers should only be able to select a month if it exists in the production_ready table for the selected property.  If not, the month should be disabled in the date selector.

As of 2024, this process has been fully automated.

Push to Prod for MTSA Pro/Pro+

Push to Prod for MTSA paid subscription levels is done from the Ops Overview board.

Standard Time (Nov-Mar) = At 11:00 AM EST and 5:00 PM EST daily
Daylight Saving Time (Mar-Nov) =At 12:00 PM and 6:00 PM EST daily
auto_push_to_prod will insert rows into the sales.production_ready table for all items with status=“Approved for Prod”. The status then gets changed to “Prod In Progress”. Alert in Slack #airflow-alerts only if failure. 
The mid-day Push to PROD run was eliminated in December 2024 by Engineering. Contact Engineering with any questions.

Overnight - approx. 3:00-4:00 AM EST daily = auto_push_to_prod sa_build_clicktrails (the rebuild_prod_clicktrails_mv_and_dependents step) will:

• For all items with status=“Approved for Prod”, insert rows into the sales.production_ready table. The Processing Status then gets changed to “Prod In Progress”. Alert in Slack #airflow-alerts only if failure. 
• Refresh the dashboard and actually publish the data in the Prod Dashboard. If the run is successful, all items that were “Prod In Progress” get changed to “Verify Prod”. This run can take approx. 1-3 hours to complete. Processing Status is flipped to "Verify Prod" only after the run has successfully finished.
  Alert in both Slack channels #salesattribution and #customersuccess if Success or Failure.

Push to Prod for Source Reports

A dealer's data will be "always live" in the DMUI, meaning we will not push data to Prod after the processing cycle as we do for full MTSA. This means a dealer can login and see their data at any given time once it has been loaded and processing starts.

For full details on the process, review the Confluence documentation.

Every day at 12:05 PM EST, the push_to_prod_source_reports Airflow DAG will check the clarivoy.mongodb.prod_properties_ft table.

For all properties where the product array contains 'source_rpts' (meaning the flag Is Source Reports=TRUE on the property in the DMUI), the current processing month's data (the previous calendar month) will be automatically "pushed to prod" (the corresponding property and month row will be inserted in the sales.production_ready table).

Manual Push to Prod

For the old Manual Push to Prod instructions, see: Manual Push to Prod for Ops Team.  This process is used only in exceptional cases.