E-Planning SSP can be implemented in AMP sites through Prebid Server and compete as any source within it.
AMP (Accelerated Mobile Pages) is a technology that allows to create sites with a faster load time. However, you cannot add any additional Javascript code, so Prebid Server cannot be implemented the same way as it were to be implemented in a traditional site.
To configure Prebid Server correctly, you must create a Stored Request (in case you don’t have one already) and configure the <amp-ad> tags. The only parameter needed for implementation is ci, which has a unique value regardless of the site, space, or size where it is implemented.
To obtain the ci value for your account, access the platform with your ID and then follow these steps:
If you use a Prebid Server shared instance, as the one provided by Appnexus, then you should have a Stored Request already. In case the instance is private and managed by you, then you will have to create one as follows:
stored_requests/data/by_id/stored_imps/<id>.json
Being <id> a random ID that we will use for the Stored Request.
The ID must include the Stored Request configuration json, as established in the official docs, paying special attention to the addition of the sizes to bid, the domain and the auction granularity.
The following example assumes a ci value of 18f66, the monetized domain is example.com, and the granularity value is dense:
{
"imp": [
{
"ext": {
"eplanning": {
"ci": "18f66"
}
},
"banner": {
"format": [
{
"h": 250,
"w": 300
},
{
"h": 90,
"w": 728
}
]
},
"id": "test-imp-id"
}
],
"ext": {
"prebid": {
"cache": {
"bids": {}
},
"targeting": {
"pricegranularity": "dense"
}
}
},
"id": "test-request-id-1",
"site": {
"page": "ejemplo.com"
}
} |
In case you already have a Stored Request, the process is much simpler. You only need to adjust it accordingly to include the eplanning bidder within the field ext and the key-value ci in the configuration object:
{
"imp": [
{
"ext": {
"appnexus": {
"placementId": '4799418'
},
"eplanning": {
"ci": "18f66"
}
},
"banner": {
"format": [
{
"h": 250,
"w": 300
},
{
"h": 90,
"w": 728
}
]
},
"id": "test-imp-id"
}
],
"ext": {
"prebid": {
"cache": {
"bids": {}
},
"targeting": {
"pricegranularity": "dense"
}
}
},
"id": "123456789",
"site": {
"page": "ejemplo.com"
}
} |
You must configure the <amp-ad> tags correctly and add the rtc-config attribute to your Stored Request ID. In the following example, we assume the Stored Request ID is 123456789:
<amp-ad width=300 height=250
type="doubleclick"
data-slot="/77069040/Right1"
rtc-config='{"vendors": {"PrebidAppNexus": {"PLACEMENT_ID": "123456789"}}, "timeoutMillis": 950}'
>
</amp-ad> |
Unlike the Prebid Server implementation in a traditional site, when AMP sites are involved user sync (also called Cookie Matching) is not automatic. This is a key process of the programmatic buying & selling dynamics, where if not plugged in, results will be anything but optimum.
In order to make the user sync, copy & paste the following code right after the <body> tag of your website. It must be in all pages and downloaded as soon as possible.
<amp-iframe width="1" title="User Sync" height="1" sandbox="allow-scripts allow-same-origin" frameborder="0" src="https://ads.us.e-planning.net/uspd/1/?du=https%3A%2F%2Fads.us.e-planning.net%2Fgetuid%2F1%2F5a1ad71d2d53a0f5%3Fhttps%3A%2F%2Fib.adnxs.com%2Fprebid%2Fsetuid%3Fbidder%3Deplanning%26gdpr%3D0%26gdpr_consent%3D%26uid%3D%24UID"><amp-img layout="fill" src="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==" placeholder></amp-img></amp-iframe> |
We recommend the following external links for further reference on Prebid Server in AMP sites: