Skip to content

Duplicate GPT slots per ad unit (TS container slot competes with publisher inner-div slot) #944

Description

@jevansnyc

Summary

TS defines a slot on a ...-container div alongside the publisher's own inner-div slot on the same GAM unit path (/88059007/prospect-a/homepage), yielding ~9 registered slots for ~3-4 real placements. Risk of competing defineSlot / double ad requests.

Evidence

googletag.pubads().getSlots() shows both ad-header-0-_R_...-container (TS) and ad-header-0-_r_1_ (publisher) for the same unit; same pattern for fixed_bottom and in_content. Observed on a live Next.js App Router publisher with TS enabled.

Acceptance

  • One registered GPT slot per placement, or a documented rationale for the container/inner split with dedup so no double request occurs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions