Workbook setup for ticket submits

Workbook setup for ticket submits

This article is under construction!

This article will provide instructions on how to separate workbooks for ticket submission. It will also provide tips and tricks on filling out workbooks to avoid ticket closures. 

Breaking your campaign work into smaller tickets enables AdOps to complete the work more quickly than if everything is submitted in one large request.  It also ensures there is no hold up in receiving tags should there be an issue with another part of your campaign.  For programmatic, the site refers to the DSP, not the deal site.

All builds and trafficking associated requests must be split by site/publisher.  You'll list the site/publisher name in the ticket webform.  Example: Your campaign has New York Times, Pandora, and ESPN. 

Alert
Remember to download any workbooks fresh from Toolkit each time you need to populate a template.  They are updated in real time.
Do not reuse an older template saved on your computer or sharepoint.


Campaign builds for OneStrata

The AdOps Campaign Managers will build the media schedule in OneStrata for direct and programmatic buys, this is inclusive of any direct or programmatic lines that do not receive ad tags.  Select the tab below to learn more.

Media schedule creation
Media schedule additions
Media schedule revisions
Cancelations
Media schedule creation
What you'll submit: OSD builder
How you'll submit it:
  1. Tickets and workbooks should be separated by supplier
  2. Ad serving for Mightyhive/Monks and IAS is the only time you may submit a builder with two suppliers present
  3. Your builder may have 1p served, 3p served and not served placements on it
What you'll receive from AdOps when the ticket is completed:
    1. Email confirmation that the build has been completed.
Media schedule additions
What you'll submit: OSD builder
How you'll submit it:
  1. Tickets and workbooks should be separated by supplier
  2. Ad serving for Mightyhive/Monks and IAS is the only time you may submit a builder with two suppliers present
  3. Your builder may have 1p served, 3p served and not served placements on it
  4. You'll include only the new lines to be added to an existing media schedule
    1. If the lines are child placements to be added to an existing package, you must note the OSD package ID in the notes column of your builder.
What you'll receive from AdOps when the ticket is completed:
    1. Email confirmation that the additional lines have been added to the media schedule.
Media schedule revisions
What you'll submit: nothing.
How you'll submit it: you won't.

Media teams are responsible for the upkeep of the campaigns in OSD after AdOps has built the media schedules for you.  You'll update dates, rates, units on your own.
Cancelations
What you'll submit: the advertiser view from the OSD campaign
How you'll submit it: 
  1. NOTE: you will need to update the lines that you want to cancel to have DNU- before the line name.  You'll also need to zero out that line(s)
  2. Tickets and workbooks should be separated by supplier
  3. Your advertiser view sheet may have 1p, 3p, or not served lines included.
  4. Remove any lines that do not need to be cancelled.
  5. Submit a push request and note that the lines in the push need to be cancelled.
What you'll receive from AdOps when the ticket is completed:
    1. Email confirmation that the lines requested to be cancelled have been unlinked from the ad server.  Once you receive that confirmation, you may cancel the lines. 
      1. Do not cancel the lines without confirmation that the ad server has been disconnected.

Pushes from OSD to CM360

A push connects the media schedule from OSD to CM360.  Only the lines that require ad tags should be pushed to the ad server.  Updates you make in OSD are not automatically updated in CM360.  The push controls that update.  The following actions require a a ticket to AdOps to request a push from OSD to CM360:
  1. New lines that need ad tags
  2. Name changes (consult AdOps before you change any names!)
  3. Date changes
  4. Rate changes
  5. Unit changes
  6. Cancelling lines in OSD
Push request
Push request
What you'll submit: the advertiser view from the OSD campaign
How you'll submit it: 
  1. You may submit a push requests that includes multiple suppliers.  Push requests do not need to be separated by supplier like builds do.
  2. Your advertiser view sheet may have 1p, 3p, or not served lines included.
  3. Remove any lines that do not need to be pushed to the ad server.
What you'll receive from AdOps when the ticket is completed:
    1. Email confirmation that the push has been successful

Trafficking

1p served placements - aka the site is hosting the creatives

1p served creative is tracked by Crossmedia in CM360.  The Site is responsible for the creative rotations, live date, pausing and end date of creative.  AdOps will close any tickets requesting 1x1s to be paused.  For 1p served creative, there are no swaps, only additions.  The site controls swaps and removals.  AdOps is responsible for generating one set of trackers per creative you need to track, setting the live and end date for the trackers, assigning a click through url and collecting any relevant 4th party impression trackers for your request. Select the tab below to learn more.
1p served trafficking
1p served adjustments | ad and creative date changes, url updates
1p served trafficking
What you'll submit: A trafficking workbook
How you'll submit it: 
  1. 1p served placement trafficking should not be mixed with 3p served trafficking.  1p served should be kept separate.
  2. Tickets and workbooks should be separated by site.
  3. You may combine placements that have never been trafficked with previously trafficked 1x1s on the same workbook, so long as they are for the same site.
  4. You will not provide assets of any kind for 1p served tickets.
What you'll receive from AdOps when the ticket is completed:
    1. Impression and click tracking tags for each creative assigned to a placement.
    2. IAS impression trackers listed within the CM360 impression tracker cells.
    3. 4th party impression trackers if applicable to your client and campaign.
1p served adjustments | ad and creative date changes, url updates
What you'll submit: A trafficking workbook
How you'll submit it: Pull a Summary export from CM360
  1. 1p served adjustments should not be mixed with 3p served adjustments.  1p served should be kept separate.
  2. Tickets and workbooks should be separated by site.
  3. You will not provide assets of any kind for 1p served tickets.
  4. Prepare your summary export
    1. Do not delete any COLUMNS - this is extremely important! If columns are deleted your export will not be accepted.
    2. You should delete rows of the placements/creatives not being changed.  Only submit what needs to be worked on.
    3. You should delete any rows that are packages.  Only submit what needs to be worked on.
    4. You should delete any rows that are default lines.  Only submit what needs to be worked on.
    5. DO NOT HIDE OR FILTER ANYTHING.
    6. Add a column(s) to the very end of the export outlining the change you need: Example: "url change" or "End Date Change" etc.  Label the column then populate the cells to reflect the adjustments you'd like AdOps to make.
    7. Do not edit over anything on the export aside from the new column you made at the end of the export
What you'll receive from AdOps when the ticket is completed:
    1. Date adjustments: a confirmation email that the request has been completed.
    2. URL updates for any site except YouTube: a confirmation email that the request has been completed.
    3. URL updates for YouTube: 1x1 impression and click trackers.
      1. YouTube requires transparent click trackers, which require hardcoding the url into the click tracker.  For all other sites, this is a backend change.

3p served placements - aka XM is hosting the creatives

3p served creative is hosted by Crossmedia.  The assets the client's team sends to you gets uploaded to the campaign in CM360 and assigned to the placements you instruct AdOps to within the trafficking workbook.  AdOps is responsible for setting the creative rotation, live date, end date, pausing a creative, assigning a click through url and applying any relevant 4th party impression event tags within the ad server. Select the tab below to learn more.

3p never trafficked placements
3p creative updates
3p ad/creative date or url adjustments
3p never trafficked placements
What you'll submit: Trafficking workbook
How you'll submit it:
  1. 3p served fresh, never before trafficked placements should not be mixed with 1p served trafficking or adjustments to previously trafficked 3p served placements, this includes adding creative to rotations, removing creatives, updating dates, urls, etc.  3p served placements that have never been trafficked should be kept separate.
  2. You can include display & video on the same ticket so long as they are all never before trafficked placements and are for the same site.
  3. Tickets and workbooks should be separated by site.
  4. If you have questions on how best to convey the trafficking instructions, please Teams message a member of AdOps.
What you'll receive from AdOps when the ticket is completed:
    1. Ad tags for each placement.
    2. IAS tracking integrated within all display and video placements
    3. 4th party impression tracking integrated within the ad tags if applicable to your client and campaign.

3p creative updates
Follow this for adding or removing creatives to previously trafficked placements

What you'll submit: Trafficking workbook
How you'll submit it:
  1. 3p served adjustment requests should not be mixed with 1p served trafficking or never before trafficked 3p served placements
  2. You can include display & video on the same ticket so long as they are previously trafficked placements and are for the same site.
  3. Tickets and workbooks should be separated by site.
  4. Include only what needs to be worked on for the request.
  5. If you have questions on how best to convey the trafficking instructions, please Teams message a member of AdOps.
What you'll receive from AdOps when the ticket is completed:
  1. An email confirmation that the adjustments have been made.  All 3p changes are back-end, in system swaps. 
  2. You will not receive new ad tags, nor a repull of an ad tag.

3p ad/creative date or url adjustments
What you'll submit: A trafficking workbook
How you'll submit it: Pull a Summary export from CM360
  1. 3p served adjustments should not be mixed with 1p served adjustments.  3p served should be kept separate.
  2. Tickets and workbooks should be separated by site.
  3. You will not provide assets of any kind for date or url adjustmentes
  4. Prepare your summary export
    1. Do not delete any COLUMNS - this is extremely important! If columns are deleted your export will not be accepted.
    2. You should delete rows of the placements/creatives not being changed.  Only submit what needs to be worked on.
    3. You should delete any rows that are packages.  Only submit what needs to be worked on.
    4. You should delete any rows that are default lines.  Only submit what needs to be worked on.
    5. DO NOT HIDE OR FILTER ANYTHING.
    6. Add a column(s) to the very end of the export outlining the change you need: Example: "url change" or "End Date Change" etc.  Label the column then populate the cells to reflect the adjustments you'd like AdOps to make.
    7. Do not edit over anything on the export aside from the new column you made at the end of the export
What you'll receive from AdOps when the ticket is completed:
    1. An email confirmation that your requested adjustments have been made.

Avoiding Ticket Closure

Check the Fire Blanket! It has all the info you will need to avoid ticket closures and submit tickets correctly.

Why a ticket will be closed before the request is complete

The ticket and workbooks are the instructions you provide to AdOps to ensure that your campaigns are built and trafficked properly.  When tickets, workbooks, assets and urls are incorrect, conflicting or out of spec, that's how you've told AdOps to complete a ticket for you.  Not good, huh.

If your ticket has incorrect or conflicting information, is missing necessary parts, assets are out of spec, etc, AdOps cannot complete your request.  Issues like those listed below steal valuable time from working on tickets and add lag where there should be none.  If any of the following occur on your ticket, AdOps is instructed to close your ticket.  Your ticket will not be reopened.  You must correct the problem and submit a new ticket.  The lead time clock will start over with new ticket; it will not jump the line in the queue. 

Your ticket will not be worked on and will be closed if any of the following occur (this is an evolving list):
  1. Webform information doesn't match the rest of your ticket or is missing
    1. examples: client name on ticket doesn't match the workbook and assets, the request category doesn't match the workbook provided, site/supplier name doesn't match the workbook, serving method doesn't match the workbook, campaign name is missing or incorrect, partner integrations are missing or incorrect
  2. More than one workbook is linked to a ticket.
  3. More than one site is included in a ticket unless it's a push ticket
  4. Workbook's site/supplier doesn't match the site/supplier you listed on the ticket webform.
  5. The campaign name in the workbook doesn't match what you listed on the ticket webform Include the correct campaign name in both the ticket properties and traffic workbook
  6. if an old workbook is used your ticket will be closed 
  7. Check that your placements and creatives follow the correct naming convention - including duplicated CTV assets 
  8. Check that placements and creatives do not contain prohibited characters or typos 
  9. Make sure your workbook does not contain archived or duplicated placements and that nothing is hidden or highlighted 
  10. Double check that your creative assignments are correct. For example, a 300x250 placement should not have a number assigned that correlates to a video creative, etc 
  11. Your traffic workbook should not contain multiple publishers - one publisher per ticket
  12. Your traffic workbook should not include net new and previously trafficked placements in one ticket
  13. 1x1s and 3p media should not be on the same traffic workbook.
  14. If your supplier is not yet in OSD and you submit a build request your ticket will be closed 
  15. If creative is not packaged correctly or is sent to AdOps in many folders it may result in your ticket being closed
  16. If static assets are above 150 KB your ticket will be closed as we will not be able to traffic assets that heavy


When in doubt, reach out!
We're happy to help look over workbooks or answer any questions you have may have. Please reach out if you have any questions or concerns :-)

Sharing Assets with AdOps

Follow the instructions in this KB.  Noncompliance may result in a ticket closure.

DO. NOT. HIT. SEND.  When you hit send, it sends an email to every member of the AdOps team and spawns another ticket.  Just don't.



7. Filling out your traffic workbook
Always download a fresh workbook from XM Haus 
Please read the 'workbook instruction' tab of the workbook and column headers thoroughly - they'll explain how & what to fill out 
As mentioned, ensure your workbook is for one site/supplier/publisher only 
Do not duplicate placement lines! If creative assignments or url assignments seem tricky please reach out Julie or Nic for assistance
Do not duplicate creative lines! Duplicating lines is never the answer and if you need help conveying information please reach out to Julie or Nic for assistance 
Only list creative that needs to be assigned under the creative tab. 
for example- if you need to explain weight changes for creative that is already assigned please do so under notes
Use the notes field!! - Notes are your friend and help AdOps better understand what's being requested or any nuances we should be aware of 
Fill out all fields of the workbook and fill them out correctly please :-)
Make sure nothing in your workbook is hidden
QA for typos, correct assignments etc prior to submitting the workbook

    • Related Articles

    • Submitting a ticket to AdOps| how to use the ticket webform

      The XM AdOps team manages all ad tech execution for direct and programmatic display, native, audio and video buys across the agency. Sending the detail needed for efficient and effective request fulfillment is key. There are over 90 active ...

    • Materials Needed for AdOps Troubleshooting

      Are you in need of AdOps help with your troubleshooting ticket? This guide will help you make sure you have all the materials the AdOps team might ask you to provide. By preparing these items ahead of submitting a ticket, you save time for all teams ...

    • URL best practices & troubleshooting guide

      The url an ad clicks to is an integral part of the campaign trafficking process. In order to optimize QA and implementation, the following are some best practices that should be adhered to when sending click through urls for your campaigns: Url must ...

    • Need a rush request?

      Please make sure the director or group director on your account is emailing Nickki & Julie to request the reprioritization of your ticket. If your account doesn't have a director, the supe may send the email. Requests submitted from anyone else on ...

    • Dynamic Creative Optimization (DCO) and You - executing with AdOps

      Your client team or their creative house says 'let's do DCO!' First thing's first. Reach out to technology@xmedia.com The immediate next steps are not included in this KB. This KB will focus on the after a DCO partner is chosen, not the steps to ...