How do I manage the Trade Desk Audit Pipeline?

This pipeline is used to manage First Audits and ongoing Routine Audits for active accounts.

Key Notes

• Tickets should generally be moved at the end of the day. This ensures all team activity — including work completed later in the evening — is accurately reflected before closing or advancing tickets.

1. First Audits (Newly Launched Accounts)

• The First Audits column contains accounts that have recently launched and require their first audit before entering the ongoing audit cadence.

• First Audits are completed 7 days after the account goes live on Google.

• • These tasks should be assigned only on their specific due dates to allow sufficient learning time before changes are made.

• Once a First Audit task is complete, move the ticket to Closed.
  • When prompted about auditing again next month, select Yes.
  • Enter today’s date as the Last Touch Date to maintain accurate tracking of account activity.

  • Open the ticket and confirm:

    • The task inside the ticket is marked Complete and notes have been added.
      • If anything is missing, flag the assigned team member for follow-up.

2. Routine Audits (Ongoing Accounts)

• Ongoing Routine Audits appear in the New – Ongoing column. There should be one ticket per active client. 

• Tickets may remain in New – Ongoing until completed.
• Moving tickets to In Progress is optional and only used to indicate work is being done that day.
• Once a Routine Audit is complete, move the ticket to Closed. 
  • Open the ticket and confirm:
    • The task inside the ticket is marked Complete and notes have been added.
      • If anything is missing, flag the assigned team member for follow-up. 
        
        

3. When Accounts Are "Touched"

• Any account change that requires a date update in Optmyzr — including optimizations, minor edits, or site transitions — requires the ticket to be moved in this pipeline to reset the next Routine Audit date.

  • For these non-audit updates, delete the task inside the ticket when moving it to Closed, since no Routine Audit was completed. This will prevent multiple Routine Audit tasks from being open at the same time for a single client. 

4. Paused Accounts

• If a Routine Audit is due for an account that is paused due to client request, verification deadline, or CC/ad disapproval issues, move the ticket to the appropriate Paused column. 

  • Delete the task inside the ticket so it does not appear in the task list.
• Once the issue is resolved and the account becomes again again, move the ticket to Closed to automatically trigger a new Routine Audit ticket.
  
  

5. Missing Accounts

• If an active account is missing from the pipeline, click Create Ticket and enter the following details:

  • Ticket Name: Client Name
  • Ticket Status: New – Ongoing
  • Ticket Description: “Routine audit”
  • Company Association: Select the correct company
• Click Create to automatically trigger the ticket and corresponding task in the pipeline.