Template Change Process

The Template Change Golden Rule

All template changes require external notification and must allow time for external review.

How the Template Change Process Works

Make development changes to templates as normal.

Deploy Native (test) Template to GAM.

Submit to QA.

Upon QA approval, notify

#tbrand-creativetech-help⁠

AND

#adsolutions_prod⁠

channels that a native Template change has been made. Include a summary of the change, native test GAM link, and a request to test currently running ads. The message should also contain anticipated date of deployment. (Sample Slack/E-Mail Notification below.)

Email key stakeholders: Request Originator, adsolutions_internal@nytimes.com, Erica Super, Neil Anand, Catherine Scambler, owneddisplay@nytimes.com, Joe Lucatuorto, Sarina Goldstein

Resolve issues that come up.

Go live after one week with changes if no issues OR if any issues were resolved.

The Template Change Process “Flow”

⁠

Sample Slack/E-Mail Notification

A native template change was made to the [TEMPLATE NAME] template. The changes included: [CHANGE LIST]. Whereas we do not anticipate issues, any change to a native template could have an adverse affect on a currently running ad. We recommend you check any live ads using the [TEMPLATE NAME] template with our test AD unit, [TEMPLATE TEST NAME, LINK]. If you find any issues, please report them back to this thread or directly to me, [YOUR NAME]. These changes are expected to go live after one week of review on [DATE]. Thank you.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.