AA Monthly Measurement Processing Procedure

Measurement Process

In the last 2-3 days before the month ends, start the Measurement process (Invoicing Process must have been started):

I do not think any of the steps in this section are being completed today by Ops Team.

• Is Engineering completing any of these steps today?
• Are they necessary?  
• Do any of these integrations or automations still function?

1. Product Manager is to click the Start Process button. An automation will create new items in the AA Customer - Sales & Lead Data to Collect group.
   
2. Link AA Invoicing column to the matching client from the Invoice Prep group then assign Sales and Leads file subitems to Ops Specialist. Set Due Date to five days into the month.
   
3. After the sales and leads are collected, the Ops Specialist will change the status to Sales/Leads Collected, an automation will move the item to the Sales/Leads Data Collected group and will assign to the VP of Engineering.
   
4. VP of Engineering will ship data to LiveRamp for FBR(File-Based Recognition) and change status to Sales Shipped to LR, an automation will run and move item to Data Sent to LiveRamp for FBR group.
   1. Notes from Sean:
      [process sales and leads into “SA HOPPER” ending ultimately in sales.sales_standardized and sales.leads_standardized. I pull two versions of the sales and leads files for each location. One set is only PII and one set is PII plus demographics. The PII set goes to liveramp for processing and the PII+ set goes to Roman for processing. When liveramp returns RampIDs for the data shipped, those files get picked up and joined to the PII+ files that Roman has and that combined file gets matched to TheTradeDesk Impression logs, and then Roman’s process spits out a matched sales file and matched leads file by rooftop… LOTS OF STEPS multiplied by number of rooftops.
      
      [Link to Slack conversation]Proposed process, your part is the same. Roman’s new automation will be triggered when all the data is ready 6 rooftops or 600…. then it will query sales_standardized and leads_standardized for everything. It will output bulk PII files to Liveramp. When the rampIDs come back it will match those to the data that Roman has stored, match to impressions, and then spit out individual rooftop sales and leads matched data.]
5. VP of Engineering runs scripts in Data Grip and ships to LR, Nix pulls both sets of sales data to rejoin.
   
6. When the IDLs (RampIDs) are received back from LiveRamp, VP of Engineering will change the status to Logs Matching, an automation will move the item to Nix Matching Logs. Nix picks up the FBR files returned from LiveRamp from the S3 bucket and this triggers the next automation, which is impression log matching. When this process is complete the output data is deposited in a Google Bucket.
   1. Note from Sean: WE NEED TO DEFINE THE HEADER FOR THE OUTPUT FILE TO FURTHER 'CLEAN UP' THE PRODUCT DATA.

Output Files Ready

Notes from CG/Ops:  I think parts of this section are the processes .

1. When the output files are ready from Nix, Dailey Ops retrieves the files from the Google Bucket, and preps them as INTERNAL files. Output data is tidied up and organized in a more readable format.  The Summary tab is added and the Ad Group pivot table is added.  This process is detailed in Programmatic Reporting.
   1. I think this is the part Ops is doing currently & we need automated:  
2. Final "Internal" file for both Leads and Sales then gets posted to the property in Monday. 
   1. I do not think this part is being done; Is it necessary for anything?
3. Dailey will then change the status to Ready for Reporting. 
   1. I do not think this part is being done; Is it necessary for anything?
   2. 🚨 When the status changes to Ready for Reporting, an automation will move the item to Matching Reports Ready for QA.
      1. [Note from Sean: NEED TO UPDATE AUTOMATION to also reassign to Product Manager and CSL].
4. Note from Sean: Need to get with Roman for changes on the Internal file needs.
5. The CSL and/or Product Manager will deliver reporting to the client.
6. Once completed, the CSL and/or Product Manager will change the Status to Done/Delivered. 
   1.  I do not think the CSL [I am told Nur is the CSL for Alpine] is doing this.
   2. 🚨 When the status changes to Done/Delivered, an automation will move the item to the Completed Reports group.