From 54257c561bf6271ebe9252f15219e8865a4aead7 Mon Sep 17 00:00:00 2001 From: Demetrio Girardi Date: Thu, 7 Mar 2024 10:26:52 -0800 Subject: [PATCH] Update load-cookie documentation --- prebid-server/developers/pbs-cookie-sync.md | 31 +++++++++++---------- 1 file changed, 16 insertions(+), 15 deletions(-) diff --git a/prebid-server/developers/pbs-cookie-sync.md b/prebid-server/developers/pbs-cookie-sync.md index 96bcb5e483..c85ffe10b5 100644 --- a/prebid-server/developers/pbs-cookie-sync.md +++ b/prebid-server/developers/pbs-cookie-sync.md @@ -73,9 +73,6 @@ Cookie sync for AMP works in a way quite similar to Prebid.js. ``` - {: .alert.alert-info :} - If the publisher has an AMP Consent Management Platform, they should use `load-cookie-with-consent.html`. - 3. At runtime, the `load-cookie` script just calls the Prebid Server /cookie_sync endpoint. The rest works similar to what's described for Prebid.js above. One difference is that the bidders are not known on the AMP page so those aren't passed. Another difference is that AMP doesn't support iframe syncs, so load-cookie passes instructions to PBS so only pixel syncs are returned. ### Cooperative Syncing @@ -155,27 +152,31 @@ Here's how you could invoke it with an iframe: