-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Sticky ads to version 1.0 #6169
Comments
Nice, new close UX is much better. |
Deployment process for #5432 |
Just wondering if this needs to remain open or can be closed? |
let's keep this open as a track issue to the deployment process. |
Quick update - this is meant to go live in 2 weeks for those who haven't upgraded already. |
jasti
changed the title
Action Required - AMP Sticky Ads Component Upgrade Notice
Upgrade Sticky ads to version 1.0
Apr 13, 2017
close by #9042 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tl;dr: Upgrade sticky ads component from v0.1 to v1.0 within the next month.
Introducing AMP Sticky Ads v1.0
The amp-sticky-ad component was developed as an extension to help publishers monetize ads on AMP pages in a user-friendly manner. We’ve added some improvements to sticky ads which we are launching as version 1.0 to ensure that existing, customized sticky ad implementations that are using version 0.1 don’t break. If you haven’t customized the sticky ads implementation on the page, you can safely upgrade to v1.0
What’s changing?
Based on publisher & user research feedback, we are making 3 changes:
1. UX change to default close button
The new close button is integrated in a way that it’s part of the sticky ad container, giving it a better look and feel. Moreover, this same close style is also applied to the amp-app-banner for consistency.
2. Restrictions on transparency of the ad container
User studies at Google (to be released early next year) have shown that an ad that doesn’t span the entire width of the device is considered bad user experience since it may appear as if it’s blocking primary content. Although the default implementation of v0.1 applied an automatic padding so that the sticky ad was always full width, some publisher implementations changed the padding to transparent. With v1.0 we ensure that the ad always spans the entire width of the mobile device, as shown in the picture above.
3. Removal of intermediate state
In order to minimize perceived ad loading latency, especially on slow networks, we have removed the intermediary “ad loading” UX. In v1.0, the user will directly see the ad appear soon after the user scrolls past the first viewport. If you previously customized this state, please update your implementation.
What should I do next?
The amp-sticky-ad v1.0 has launched. Simply update your AMP page to use
instead of
If you didn’t customize the sticky-ad implementation, you are all set. If you did, make sure the new version works as expected with your changes.
You can see a sample implementation here.
What if I don’t upgrade?
In order to avoid supporting backwards incompatible changes for too long, we want to ensure that all pages upgrade to the latest version within 1 month of this announcement date. AMP documents that don’t upgrade to the latest version within this time will be automatically upgraded to v1.0 which may cause breaking changes.
What if I have feedback about the change?
As always, we welcome your feedback. You can comment on this issue or reach out directly to @jasti for questions or clarifications.
CC @ampproject/ads @zhouyx
The text was updated successfully, but these errors were encountered: