> For the complete documentation index, see [llms.txt](https://docs.relevant-digital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevant-digital.com/technical/integration/advanced-implementation-patterns/edit-bidder-settings-for-schain-and-first-party-data.md).

# Edit bidder settings for schain and first-party data

## **Overview**

This article outlines a method by which a publisher can edit bidder settings using *pbjs.setBidderConfig.*

A publisher may wish set schain nodes or pass first party inventory or user data to a certain bidder but not all bidders.

### **Code**

```
//Pass Schain node
PrebidRequester.instance.pbjs.que.push(function() {
    pbjs.setBidderConfig({
        bidders: ['bidder1'],
        config: {
          schain: {
            validation: 'relaxed',
            config: {
              ver: '1.0',
              complete: 1,
              nodes: [
                  {
                  asi:'domain.com',
                  sid:'1',
                  hp:1
                  },
              ]
            }
          }
        }
      })
});

//pass first party data

PrebidRequester.instance.pbjs.que.push(function() {
pbjs.setBidderConfig({
    bidders: ['bidder'],
    config: {
        ortb2: {
        user: {
          ext: {
            data: {
                fpd: data,
                }
            }
        }
      }
    }
})
});
```

## **Walk-through**

For both cases we are using *PrebidRequester.instance* portion of the Relevant JS api to push [*pbjs.setBidderConfig* ](https://docs.prebid.org/dev-docs/publisher-api-reference/setBidderConfig.html)to the setup.

This code runs when the relevant js library is loaded on the publisher site, thus elements from the site (for example the first party data) can be retrieved and pushed to the bidders.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.relevant-digital.com/technical/integration/advanced-implementation-patterns/edit-bidder-settings-for-schain-and-first-party-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.