Amphtml: amp-iframe: make client-ID accessible
We want to display personalized content in an amp-iframe. Therefor we need to access the Client-ID in the embedded document.
From my understanding this would be possible in iframes served from the same origin as the document by reading the cookie, but not if the document is delivered via the AMP-CDN.
Would it be possible to solve this by enabling the "URL Variable Substitutions" for amp-iframe, or maybe by taking a similar approach to amp-ad?
eike-hass
All 13 comments
URL substitution does sound a reasonable solution to me.
What amp-ad approach were you talking about?
lannka
on 17 Aug 2016
/cc @rudygalfi
dvoytenko
on 17 Aug 2016
@lannka from what i understand the ad is able to access the "AMP client id". Am I mistaken? I thought maybe a similar behavoir could be applied.
eike-hass
on 17 Aug 2016
I've encountered the same problem when creating the amp-analytics sample for ABE. Support for variable substitutions in iframes would've definitely helped.
sebastianbenz
on 17 Aug 2016
@eike-hass I see what you mean. But that's probably not what you want. That gives you the ad-cid, which has its own scope per ad network.
lannka
on 17 Aug 2016
@lannka gotcha. thank you for clearifying
eike-hass
on 17 Aug 2016
@rudygalfi do you see any risk of exposing all runtime variables to iframe src? Otherwise I think it's something we can do.
lannka
on 17 Aug 2016
At first glance, I don't see concerns.
rudygalfi
on 25 Aug 2016
We do not want to make variable substitution available to amp-iframe, because that opens up usage of it for undesired purposes such as ad serving and analytics.
cramforce
on 30 Aug 2016
Closing per https://github.com/ampproject/amphtml/issues/4573#issuecomment-243470304.
jridgewell
on 30 Aug 2016
The initial request was to only make the CLIENT_ID available in iframes. Not necessarily all variable substitutions. Would this be viable?
iframes are often the only way to realise complex integrations. Being able to personalise their content is a common use case which AMP currently doesn't support.
sebastianbenz
on 2 Sep 2016
Basically we'd be more comfortable to allow everything but CLIENT_ID.
cramforce
on 2 Sep 2016
why are ad serving and analytics undesired purposes?
AndrewKGuan
on 15 Aug 2019
Related issues
aghassemi
路
3Comments
akshaylive
路
3Comments
cvializ
路
3Comments
mrjoro
路
3Comments
jpettitt
路
3Comments
Most helpful comment
The initial request was to only make the CLIENT_ID available in iframes. Not necessarily all variable substitutions. Would this be viable?
iframes are often the only way to realise complex integrations. Being able to personalise their content is a common use case which AMP currently doesn't support.