---
layout: bidder
title: Etarget
description: Prebid Etarget Bidder Adaptor 
biddercode: etarget
media_types: banner, video
tcfeu_supported: true
usp_supported: true
pbjs: true
fpd_supported: true
gvl_id: 29
sidebarType: 1
---

### Bid Params

{: .table .table-bordered .table-striped }

| Name | Scope | Description | Example |
| :--- | :---- | :---------- | :------ |
| `refid` | required | Placement ID | `12345` |
| `country` | required | Country domain | `1` |
| `options` | optional | Additional data | `{site:'example.com'}` |

#### First Party Data

In release 5.0 and later, publishers should use the `ortb2` method of setting First Party Data. The following fields are supported:

- ortb2.site.ext.data.*
- ortb2.site.keywords
- ortb2.site.content.data[]
- ortb2.user.ext.data.*
- ortb2.user.data[]

The ETARGET exchange supports the IAB standard Audience Taxonomy v1.1 and Content Taxonomy v2.2.

Example first party data that's available to all bidders and all adunits:

```
pbjs.setConfig({
  ortb2: {
    site: {
      keywords: "kw1,kw2",            
      ext: {
        data: {
           prodtype: ["tech","mobile"] 
        }
      }
    },
    user: {
      ext: {
        data: {
          ucat:["new"]                 
        }
      }
    }
  }
};
```

Example of first party data available only to the ETARGET bidder. Applies across all ad units.

```
pbjs.setBidderConfig({
  bidders: ["etarget"],
  config: {
    ortb2: {
      site: {
        keywords: "kw1,kw2",             
        ext: {
          data: {
            prodtype: ["tech","mobile"]  
          }
        }
      },
      user: {
        ext: {
          data: {
            ucat:["new"]                 
          }
        }
      }
    }
  }
};
```