GAM & Tag QA Environment

NEXBID · Next Generation Bidding · Creating Value in Every Bid.

Live GAM + isolated tag testing

Two independent checks: Live GAM mode sends a real Google Publisher Tag request to the ad-unit path you enter. Tag Lab mode executes any trusted HTML/JavaScript tag in an isolated iframe and classifies observable outgoing requests, incoming responses, creatives, trackers, media, render events, and errors. The QA page itself supplies no mock demand.

Live GAM request settings

Uses Google Publisher Tag

GAM ad-unit path

Replace the sample network ID and ad-unit code with the real publisher GAM path.

Slot size

Observation window

Custom targeting — one key=value per line

The recommended QA line item should target qa=true, keeping it away from production traffic.

Request non-personalized ads for this QA request

Collapse the slot when GAM returns empty

Ready

Enter a real GAM ad-unit path. A sample path cannot return your publisher’s line item.

GAM placement and request lifecycle

Inbound and outbound classification

Ad requestWaiting

GAM responseWaiting

Creative resultWaiting

ViewabilityWaiting

Real GPT/GAM publisher slot

Enter the real ad-unit path and send a GAM request.

Generic HTML/JavaScript tag

Editable for every tag

Paste the complete tag

Publisher slot size

Observation window

Allow same-origin access — use only with trusted tags

Leave unchecked for stronger isolation. Some publisher-domain-dependent tags may need a same-origin hosted test.

Ready

The tag will run in a publisher-sized iframe. No bid or creative is generated by this QA page.

Tag execution and traffic analysis

Request/response nature

Tag executionWaiting

Network activityWaiting

Visible renderWaiting

ErrorsWaiting

Isolated publisher tag slot

1. Create a dedicated QA ad unit

In the publisher’s GAM account, create a test-only ad unit such as:

/NETWORK_ID/NEXBID_QA

Do not use a production placement for the first technical checks.

2. Create the QA line item

Line-item type: Price Priority
Rate: ₹10 CPM, or the agreed QA rate
Inventory: only the dedicated QA ad unit
Custom targeting: qa=true

3. Add the tag inside a GAM creative

Use the included gam-creative-template.html. Replace the marked test-tag section with the tag under review, then paste the complete creative code into GAM.

<script src="https://example.com/tag.js"></script>

4. Request the real GAM slot here

Enter the real ad-unit path in the Live GAM tab, send the request, and verify the event sequence:

slotRequested slotResponseReceived slotRenderEnded slotOnload impressionViewable

5. Correlate the request with a test ID

The page sets qa_test_id. The creative template reads it using the GAM pattern macro:

%%PATTERN:qa_test_id%%

This helps match the page request, GAM creative, tag activity, and exported QA report.

6. Important browser limitation

The page can classify request URLs, event types, response status for observable fetch/XHR calls, and render behavior. It cannot read arbitrary cross-origin response bodies when the remote endpoint does not permit CORS. Use Chrome DevTools or server logs for the full payload.