You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Glimpse: add usp support, update params and fpd setup (prebid#3669)
- Add usp support
- Remove demand and keywords bidder params
- Update example on setting up adapter with first party data
- Rename placementId to pid
- Update fpd section description
- remove user.ext.keywords from example
- update contact email address
This section shows how to configure your Prebid.js integration to work with the Glimpse module.
34
-
35
36
### Prerequisites
36
37
37
-
Before you start to configure Glimpse, you will need to build a `prebid.js` file with the Glimpse module included, and include both `gpt.js` and `prebid.js` in the `head` of each page with supply. An example of a typical pair of script tags might be:
38
+
Before you start, you will need to build a `prebid.js` file with the Glimpse module included, and include both `gpt.js` and `prebid.js` in the `head` of each page with supply. An example of a typical pair of script tags might be:
38
39
39
40
```html
40
41
<script
@@ -45,29 +46,16 @@ Before you start to configure Glimpse, you will need to build a `prebid.js` file
|`placementId`| Required | string | A unique identifier associated with a publisher and ad unit, provided by the Glimpse Publisher Portal when registering a unit | 'glimpse-placement-id' |
|`pid`| Required | string | A unique identifier representing an ad unit. It is provided by Glimpse when registering an ad unit. | 'glimpse-placement-id' |
71
59
72
60
#### Example
73
61
@@ -82,11 +70,7 @@ const units = [
82
70
{
83
71
bidder:"glimpse",
84
72
params: {
85
-
placementId:"glimpse-placement-id",
86
-
demand:"glimpse",
87
-
keywords: {
88
-
sticky:true,
89
-
},
73
+
pid:"glimpse-placement-id",
90
74
},
91
75
},
92
76
],
@@ -96,43 +80,47 @@ const units = [
96
80
97
81
### First Party Data
98
82
99
-
Our adapter captures site and user level data that can be passed to all units using the `ortb2` block, as described [here](https://docs.prebid.org/features/firstPartyData.html).
83
+
Our adapter works with first party data providers as described [here](https://docs.prebid.org/features/firstPartyData.html). In this example we add Permutive data to our bidder request using [setBidderConfig](https://docs.prebid.org/features/firstPartyData.html#supplying-bidder-specific-data).
### Can I test my setup without a Publisher Portal Account?
133
-
134
-
Yes, to test your setup, you can trigger Glimpse to respond with randomly-generated bids for your correctly-configured units by setting `demand: 'demo'` in the `params` of each unit.
135
-
136
124
### Can you provide additional support?
137
125
138
-
Of course! You can check the Glimpse Prebid Adapter documentation,[here](https://docs.glimpseportal.io/en/latest/), or reach out to us at [publisher@glimpseprotocol.io](mailto:publisher@glimpseprotocol.io).
126
+
Of course! You can check the Glimpse Prebid Adapter documentation [here](https://docs.glimpseportal.io/en/latest/) or reach out to us at [support@glimpseportal.io](mailto:support@glimpseportal.io).
0 commit comments