Closed jasti closed 4 years ago
@jasti I don't quite understand the 2) and 3).
Ability to pass additional data from the ad so that the component can use it request a certain page dynamically
What is the "component" and "page" referring to?
Ability to append URL params to the destination URL on ad click by simply updating the JS inside of the creative with a new parameter (e.g. ?dfp-keyword=mwb-test)
Are you talking about dynamically changing destination URL? Why runtime is involved here?
For 2) Updated the original description. (Sorry). It's the amp-next-page component.
3) Publishers often use this as a technique for sending additional params to destination URLs that are surveys. On non-AMP, their page would probably just use custom JS to reach the param and append to the destination URL.
I see the request in two parts:
<amp-ad>
and <amp-next-page>
.Has there been a privacy and security discussion?
@ampproject/wg-ads Would the new meta tags accomplish the functionality needed here?
De-prioritized.
There are some use cases when the publisher configuration in the ad must allow the external AMP components to behave differently. Some specific examples are:
<amp-next-page>
component can use it request a certain page dynamically