delivery_instructions.py

# instructions.py

NEXT_STEPS_INSTRUCTIONS = """
Flex Bucket:
If a single flex bucket is flagged as having a delivery drop, that bucket is the most likely source of the issue.
Check whether there was a recent deployment impacting that bucket—refer to the deployment time and bucket name in the flex_section message.
Send the flagged flex bucket details, along with deployment context, to the Ad Code team for investigation.
Include a hyperlink to the related Jira ticket.
If multiple buckets are flagged, the issue may be shared among them. If most or all are impacted, flex buckets may not be the root cause.

Bidder:
If a single hb_bidder is flagged as having a delivery drop, it is likely the source of the issue.
Check for any recent changes in GAM related to this bidder—this includes targeting changes, blocking rules, or budget issues.
Send the flagged bidder information to the Rev Ops team for deeper investigation.
The Ad Ops and Ad Code teams should also verify if there were any recent changes in GAM setup or ad code logic affecting bidder behavior.
If most or all bidders are flagged, it’s likely the drop is not specific to a single bidder.

Device:
If a single device type is flagged (e.g., desktop, phone, tablet), the issue is likely related to that device category.
Investigate whether there were recent front-end or ad code changes that could be suppressing impressions on that device type.
The Ad Code team should verify targeting and rendering conditions. The Ad Ops team should check for any targeting changes in GAM.
If multiple or all device types are flagged, the issue may lie upstream, not within device-specific rendering or targeting logic.

Ad Unit:
If a single ad unit group (e.g., Sidebar, Content, Footer) is flagged, investigate whether recent changes affected the structure or availability of that unit.
Escalate the findings to the Ad Code team. The Ad Ops team should check for any targeting changes in GAM.
If most or all ad unit groups are flagged, the issue is less likely to be specific to a single ad unit and may be campaign- or integration-related.

Refresh:
If a single refresh value (e.g., 1, 2, 3...) is flagged, it may indicate a technical issue affecting impressions during specific refresh cycles.
Investigate whether recent ad code changes modified refresh logic or behavior.
Coordinate with the Ad Code team to confirm if affected refresh values correspond with known logic updates.
The Ad Ops team should check for any targeting changes in GAM.
If most or all refresh values are flagged, the issue likely lies outside of refresh logic, possibly within broader rendering or integration pipelines.
"""