# Testing and Debugging

The Nexx360 Prebid adapter supports several parameters for testing and debugging, passed through the OpenRTB `ext` object or detected from the page URL.

## Debug mode

Debug mode enables detailed information in the bid response, including SSP transaction details and eligibility logs.

Debug mode is activated when any of the following is true:

* `test: 1` is set in the bid request
* `nexx360_debug=1` is present in the page URL (`site.page`)
* `nexx360_debug: 1` is set in the request `ext`

### Enabling via page URL

Simply add the query parameter to your page URL:

```
https://example.com/page?nexx360_debug=1
```

### Enabling via request ext

```javascript
pbjs.setConfig({
    nexx360: {
        // ... your config
    }
});

// In the bid request ext:
{
    "ext": {
        "nexx360_debug": 1
    }
}
```

## Force test creative

You can force a Nexx360 test creative to validate your integration without relying on live SSP demand. This is useful for verifying that ad slots render correctly.

### Via page URL

Add one of these parameters to your page URL:

* `nexx360_test=1`
* `nexx360_force_creative=1`

```
https://example.com/page?nexx360_force_creative=1
```

### Via request ext

```json
{
    "ext": {
        "nexx360_force_creative": 1
    }
}
```

## Force test creative at a specific price

To test pricing flows end-to-end, you can force a test creative at a specific CPM. This automatically enables the test creative (no need to also pass `nexx360_force_creative`).

### Via request ext

```json
{
    "ext": {
        "nexx360_force_creative_price": 10
    }
}
```

### Via the page URL

You can also force the creative price by adding the parameter to the publisher page URL. The exchange reads it from the bid request's `site.page`:

```
https://example.com/article?nexx360_force_creative_price=10
```

If both the page URL and the body `ext` are provided, the body value wins.

The test creative will bid at CPM 10 in the auction currency.

## Force bids

By default, Nexx360 applies bid reduction rules to optimize traffic. You can bypass this for testing purposes.

### Via request ext

```json
{
    "ext": {
        "nexx360_force_bids": 1
    }
}
```

## Summary

| Parameter                            | Location                                | Description                           |
| ------------------------------------ | --------------------------------------- | ------------------------------------- |
| `nexx360_debug=1`                    | Page URL or request `ext`               | Enable debug output                   |
| `nexx360_test=1`                     | Page URL                                | Force test creative                   |
| `nexx360_force_creative=1`           | Page URL or request `ext`               | Force test creative                   |
| `nexx360_force_creative_price=<cpm>` | Request `ext` or page URL (`site.page`) | Force test creative at a specific CPM |
| `nexx360_force_bids=1`               | Request `ext`                           | Bypass bid reduction                  |
| `test=1`                             | Bid request field                       | Enable test mode and debug output     |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.nexx360.io/integration-methods/prebid-adapter/testing-and-debugging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.