Popular topics: Web Traffic Tracking GuideCDK: Setting Up DMS Sales Reports

CDP Lite: Manually Generating Audience Files in TreasureData

Table of Contents

Automated Process Old Manual Process OLD INCORRECT QUERIES - DON'T USE

This applies to all destinations other than Meta.  Meta has been fully automated.

  • Meta Destinations: Fully automated end-to-end directly inside the DMUI without touching the Google Sheet.
  • Non-Meta Destinations (Google, TTD, Amazon, Konetiq, SendGrid): Must follow the processes outlined here
 

 

Automated Process

  1. 🚦 The Make scenario CDP Lite Audience Refresh - Start (Wed 7:48 AM ET) runs every Wednesday at 7:48 AM ET:
    1. Gets every item in the Active group of the CDP Lite Manual Audience Processing board, plus any item whose Processing Status is Needs Processed.
    2. Checks each item. If something is missing or invalid, it sets the item's Processing Status to Skipped and posts an update on the item with the reason:
      1. LiveRamp File Upload Name is blank, or has characters other than letters, numbers, ., _ and -;
      2. Domain (Website Visitors) or Property ID (other segments) is blank or invalid;
      3. Segment is blank or unrecognized.
    3. Sets Processing Status to Processing on every other item.
    4. Starts the TreasureData workflow:
      1. ⚙️ The TreasureData workflow cdp_lite_audience_refresh:
        1. Runs the Web, Sales, Leads or Service query for each audience, four at a time.
        2. Saves each result as a CSV file in Dropbox under Data Archive/CDP Lite/Audience Refresh, in <run date>/<Segment>/. Each file is named with the item's LiveRamp File Upload Name and needs no editing. A second run on the same day replaces that day's files.
        3. Logs each audience's row count in the TreasureData table cdp_lite_automation.refresh_log.
        4. Sends the results to the Results scenario. If the run fails partway through, it sends the results it has, plus the error:
          1. 🚦 The Make scenario CDP Lite Audience Refresh - Results:
            1. Sets Processing Status to Processed, or to Warning if the file has fewer than 25 rows. A Warning item also gets an update saying the file may be too small to upload.
              1. 🚨 The monday automation Automation 7925899383 (when Processing Status changes to Processed, set Last Updated Date to today) sets Last Updated Date to today.
            2. Sets IDs Shared Last Update to the file's row count, and Last Updated Date to the run date.
              1. 🚦 The next morning, the Make scenario CDP Lite Audiences - Daily: add unlogged Monday deliveries (last 7 days) to Google Sheet (6 AM ET) (see Manual Dashboard Updates for details):
                1. Adds a row for each refreshed item to the dashboard Google Sheet.
                2. Sets the item's Sheet Logged Date.
            3. Sets Processing Status to Error on any item that's still Processing, and posts an update with the reason.
            4. 📧 Sends the digest email to datateam@clarivoy.com:
              1. The subject looks like ✅ CDP Lite Audience Refresh 2026-10-28: 34 processed, or starts with ⚠️ when something needs attention.
              2. Boxes at the top count the audiences that are Processed, Warning, Error and Skipped.
              3. Any audience that isn't Processed is listed under Needs attention, with the reason and a link to its monday item.
              4. The email links to the Dropbox folder.
  2. 🚦 The Make scenario CDP Lite Audience Refresh - Watchdog (Wed 11 AM ET) runs every Wednesday at 11:00 AM ET:
    1. Checks the board for items whose Processing Status is still Processing. That means the results never came back from TreasureData.
    2. 📧 If it finds any, sends an alert email to datateam@clarivoy.com listing them.
  3. Review the digest email and handle each item under Needs attention:
    1. Warning: check that the item's Domain or Property ID is correct. If it is, the audience is just small this week.
    2. Error or Skipped: fix the problem described in the item's update. An item in the Active group runs again next Wednesday.
    3. Watchdog alert: check the latest attempt of the TreasureData workflow cdp_lite_audience_refresh, then the execution history of the Make scenario CDP Lite Audience Refresh - Results.
  4. For new audiences, after they are set up in LiveRamp:
    1. If you process the audience manually, set its Processing Status to Processed and update the monday column IDs Shared Last Update.
      1. 🚨 The monday automation Automation 7925899383 (when Processing Status changes to Processed, set Last Updated Date to today) sets Last Updated Date to today.
    2. Otherwise, if you're OK waiting until next Wednesday, set its Processing Status to Needs Processed. The Make scenario will include it on its next scheduled run.

 

 

Old Manual Process

This is the manual process for querying LiveRamp to generate the audience files which we used to follow prior to automation.

 

 

This video describes the process for manually updating CDP Lite audiences in LiveRamp every Wednesday. This process involves four audience types: web, sales, leads, and service. 

Setting up Queries in TreasureData

TreasureData Query editor is not designed for collaboration or sharing, so multiple users cannot edit the same queries.  The first time you need to run manual audience processing, you must open each of these queries and make your own personal copy of them:

UPDATED QUERIES 10/21/2026

OLD INCORRECT QUERIES - DON'T USE

 
 

 

For each of these queries:

  1. Open the query using the link above.
  2. In the top right, click the button.
  3. You cannot use the same name as the original query, so it is suggested to append your initials to the query Name.
  4. Click Save.
  5. You should now be able to edit the query.

Manual Audience Processing

  1. Open the CDP Lite Manual Audience Processing board in Monday
  2. Reprocessing Web
    1. Start with the Reprocess Web view on the Monday board
    2. Open TreasureData Queries page
    3. For the Web audience, open the “CDP Lite web audience refresh query”
    4. In the query, update the domain name.
    5. Update the current epoch timestamp, looking back 60 days.
      1. Using Epoch Converter:
        1. Get today's epoch timestamp from the Epoch Converter website and replace the END time with this.
        2. Get the epoch timestamp for 60 days ago from the Epoch Converter website and replace the START time with this.
      2. OR Using Google:
        1. Get today's epoch timestamp from Google and replace the END time with this.
        2. Get the epoch timestamp for 60 days ago from Google and replace the START time with this.
    6. Click Run
    7. Download the successful query result.
    8. Move the downloaded file into a dedicated folder and rename it with the LiveRamp file upload name.
    9. Open the file
    10. Delete the first column (IP addresses) and its values
    11. Rename the header of the resulting first column to "CID"
    12. Remove Duplicates.
    13. Upload the file to LiveRamp under authenticated audiences, in the "data in" section.
    14. Move the file into the client’s subfolder, replacing the previous file (keep the last uploaded file as a backup).   WHERE???
    15. Go back to Monday and click the “Reprocessed” button. 
      1. 🚨 An automation runs and removes the item from the filter.
    16. Repeat the steps for every audience in the active category.
  3. Reprocessing Sales
    1. Start with the Reprocess Sales view on the Monday board
    2. Repeat the same steps as Web above, except:
      1. For the Sales audience, open the “CDP Lite Sales audience refresh query”
      2. For sales and leads audiences, the query uses the property ID. The sales query does not require an epoch timestamp because the intervals are already set.
  4. Reprocessing Leads
    1. Start with the Reprocess Leads view on the Monday board
    2. Repeat the same steps as Web above, except:
      1. For the Leads audience, open the “CDP Lite Leads audience refresh query”
      2. For sales and leads audiences, the query uses the property ID. The sales query does not require an epoch timestamp because the intervals are already set.
  5. Reprocessing Service
    1. Start with the Reprocess Service view on the Monday board
    2. Repeat the same steps as Web above, except:
      1. For the Sales audience, open the “CDP Lite Service audience refresh query”
      2. The service audience uses the "manual service target audience query" with the property ID.
 
 

 

After completing this, continue to:

 

 



Keep exploring

Related Articles

CDP Lite Data Integration CDP Lite Overview CDP Audience Management in the DMUI

Can't find what you're looking for?

Our team is here to help.

Contact Support