1. Tags not firing or tag rejections from the publisher
   
2. Discrepancies in impressions/clicks discovered via reporting (outside of the 15% discrepancy threshold, 1st party and 3rd party number will almost never align exactly)
   
3. Floodlight discrepancies
4. Viewability reporting discrepancies (IAS viewability outside the viewability threshold)
   

Typically, AdOps will need any variation of the below to begin troubleshooting:

1. For Ads:
   

1. From the publisher/supplier:
   
1. Full Page Screenshots of the placement configuration including the following:
   
1. start date
   
2. end date
   
3. geo
   
4. any indicator that the placement is turned on/live
   
2. Full page screenshot of the creative level configuration including the following:
   
1. start date
   
2. end date
   
3. creative assignment to placement
   
4. 3p tag implementation or impression tracker implementation
   
5. click through url areas 
   
3. Screenshots must be the full browser window - not a small portion.
4. If the publisher is unwilling to send full page screenshots, please inquire if they would be willing to participate in a live screenshare call, should the XM AdOps team determine that is the best course of action.
   
5. The tag sheet with the specific placements highlighted that are experiencing an issue
6. reporting by day (preferably in excel or formatting)
   
7. any change logs related to the ad and placement
2. from xm:
   
1. Provide any context that would be helpful to diagnose the issue more quickly:
   
1. Ex. If you are noticing a reporting discrepancy in impressions, how long has this issue occurred? Have you submitted any additional tickets with a similar issue, from this supplier or client in general? Did the publisher change anything in how they were running the campaign previously (if this is not a new campaign)? 
   
2. campaign details: campaign name, placement ids
   
3. any reports you've pulled
   
1. make sure this is the same timeframe that the supplier is sending over
   

2. For Floodlights
   

1. Depending on the type and placement of the floodlight, AdOps may or may not be able to troubleshoot for you.
   
1. AdOps can only troubleshoot a floodlight live on site if it is not a purchase complete or application complete.  Anything purchase or application complete will have to be verified by reporting.
   

1. Acct/Inv/OM can pull their own reporting.  Do not submit a ticket to AdOps for reporting requests.
   
2. For any floodlight questions after the validation was successful, pull your own reporting from CM360.
   
1. If you need help pulling a floodlight report, see this tiny training which will show you how to steal an existing report set up and copy it to use for your own.
   
1. the report will show you if the floodlight is firing and where, if there are custom variables and if those variables are pulling in information (and what).
   
1. To find out if a floodlight is firing after the initial validation, use the report. Do not submit a ticket to AdOps.
   
2. 
   
1. if you see the floodlight is not getting metrics in reporting, check to make sure your parameters are correct and that your reporting period is within the last 60 days.
   
2. if your report is still showing no metrics on a floodlight, reach out to Nickki or Julie via teams for next steps.
3. For any floodlight that is not showing metrics in reporting and is not a purchase complete or application complete, submit a ticket to adops to troubleshoot the pixel live on site.
   
1. send adops the following in a ticket:
   
1. name of the floodlight
   
2. site(s) the floodlight is supposed to fire on
   
3. the report you pulled showing the floodlight isn't firing
   
4. context on what the issue is you're trying to solve