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
We changed how AMP supports First Party Data (FPD) a while back, but there's a legacy holdover, which is that site is essentially a reserved word. Publishers trying to use site in the new (appropriate) way will receive this message:
targeting.site field ignored, expected type was object but was array.
This value is ignore and not sent to bidders on imp.ext.data.
In 4.0, we should drop this warning and treat site like any other field.
The text was updated successfully, but these errors were encountered:
We changed how AMP supports First Party Data (FPD) a while back, but there's a legacy holdover, which is that
site
is essentially a reserved word. Publishers trying to usesite
in the new (appropriate) way will receive this message:This value is ignore and not sent to bidders on imp.ext.data.
In 4.0, we should drop this warning and treat
site
like any other field.The text was updated successfully, but these errors were encountered: