Amazon Simple Affiliatehttps://www.wp-amazon-plugin.com
Upgrade your WordPress Affiliate skills!Sat, 07 Sep 2019 08:44:54 +0000en-US
hourly
1 ASA2 Update 1.11 brings support for WP Cron APIhttps://www.wp-amazon-plugin.com/2019/15360/asa2-update-1-11-brings-support-for-wp-cron-api/
https://www.wp-amazon-plugin.com/2019/15360/asa2-update-1-11-brings-support-for-wp-cron-api/#respondSat, 07 Sep 2019 08:44:54 +0000https://www.wp-amazon-plugin.com/?p=15360WP Cron API With version 1.11 ASA2 gets a new function to use the WP Cron API. With WP Cron time-controlled commands can be executed. This makes WP Cron an alternative for server-side cron jobs that are not available on every web server. ASA2 can now use the WP Cron system to automatically and regularly update products via the Amazon ...

With version 1.11 ASA2 gets a new function to use the WP Cron API. With WP Cron time-controlled commands can be executed. This makes WP Cron an alternative for server-side cron jobs that are not available on every web server. ASA2 can now use the WP Cron system to automatically and regularly update products via the Amazon API.

Disadvantages to server-side cronjobs

The WP Cron API is based on page requests. This means that the configured WP Cron events can only be executed if there are frequent requests to your site. For example, if there is no request at night, the WP Cron events will not be executed.

The other drawback is that running a WP cron event on your website can have a negative effect on the page load time, as the job is run in the background. On older servers this can lead to short blockages, so that the page is only loaded when the cron is finished.

Therefore server-side cronjobs are always preferable to WP crons, especially if you are an ASA2 power user with over 1000 products in your Repo.

Setup WP Cron for ASA2 product update

For the configuration of the WP Crons I recommend the plugin WP Crontol. After installation you can set your own intervals in the “Settings / Cron Schedules” section. For example, to run a WP Cron every three minutes, you can create a new interval of 180 seconds:

In the section “Tools / Cron Events” you can create a new “PHP Cron Event” for the ASA2 Cron. The PHP function “asa2_repo_wp_cron_refresh”, which works with the same parameters as the server-side cron job (see list of all options), must be entered in the code text field.

For example, to update only products that were last updated more than twelve hours (43200 seconds) ago, the command should be like this:

asa2_repo_wp_cron_refresh(array(
'lifetime' => 43200
));

For example, if you only want to set up a cron to update US products, you can do so using the “country_code” option:

More Details

Managed Templates

For the managed templates that can display product features, there is now a new option to determine the maximum text length of each feature. This allows better control over the layout of product boxes.

The template option “Custom CSS” did not work as expected. This was fixed with version 1.11. With this option, which you can find at the end of the template options, you can save your own CSS adjustments for each template included in ASA2.

If a maximum length was defined for the product description, the three points were no longer displayed at the position where the text was truncated. This works again with version 1.11.

For the template “Sortable_table_2” the script used for the table representation has been updated.

]]>https://www.wp-amazon-plugin.com/2019/15360/asa2-update-1-11-brings-support-for-wp-cron-api/feed/0Summer Sale 2019 – Get your 30% discount code!https://www.wp-amazon-plugin.com/2019/15223/summer-sale-2019-get-your-30-discount-code/
https://www.wp-amazon-plugin.com/2019/15223/summer-sale-2019-get-your-30-discount-code/#respondSun, 28 Jul 2019 14:12:58 +0000https://www.wp-amazon-plugin.com/?p=15223The ASA2 Summer Sale is live and offers you 30% discount on all purchases at https://getasa2.com/ Just use this coupon code during checkout: It is valid until the end of August 2019.

RequestThrottled API issue

Concerning the “RequestThrottled” issue there is a small optimization on the setup page which ensures that only one request is sent at once to check the API connection. However, this does not solve the problem in general.

The error message (“You are submitting requests too quickly. Please retry your requests at a slower rate.“) is still coming from the API. There are many reports on the Internet about this problem in the context of other software or own developments. So this is not a problem of ASA2 alone. It is assumed that this account restriction will be applied for some time. The recommended solutions are to create a new account in the form of an IAM user or to change the outgoing IP address, i.e. the web server. However, both did not lead to success in all cases.

Get the update

You can get the update via the auto-update function in the WP plugin backend or in the download section in your ASA2 account:

]]>https://www.wp-amazon-plugin.com/2019/15210/asa2-update-notes-v1-10-8/feed/2ASA2 update 1.10.6 allows using the editor button in the Gutenberg Classic Block and deals with the RequestThrottle API issuehttps://www.wp-amazon-plugin.com/2019/15183/asa2-update-1-10-6-allows-using-the-editor-button-in-the-gutenberg-classic-block-and-deals-with-the-requestthrottle-api-issue/
https://www.wp-amazon-plugin.com/2019/15183/asa2-update-1-10-6-allows-using-the-editor-button-in-the-gutenberg-classic-block-and-deals-with-the-requestthrottle-api-issue/#respondWed, 20 Mar 2019 20:26:29 +0000https://www.wp-amazon-plugin.com/?p=15183Editor Button With the update 1.10.6 you can use the familiar editor button of ASA2 within the “Classic” block of Gutenberg. This is a good solution until there will be native ASA2 support for Gutenberg. The following video illustrates the process. Amazon API RequestThrottle Issue New pause option for the cronjob It has been known for some time that the ...

With the update 1.10.6 you can use the familiar editor button of ASA2 within the “Classic” block of Gutenberg. This is a good solution until there will be native ASA2 support for Gutenberg. The following video illustrates the process.

Amazon API RequestThrottle Issue

New pause option for the cronjob

It has been known for some time that the partner program API of Amazon has problems to correctly control the request limit, which was even more restricted since the end of January (see article). Update 1.10.6 includes a new option to give the Repo items refresh cronjob a fixed pause between two API requests. Otherwise it will be calculated automatically. The pause in seconds can be set either in the options (“Options / Advanced”) or passed to the shell command as a parameter:

bash script.sh Asa2_Module_Repo_Cron_Refresh --pause=3

Use this static pause if you are frequently confronted with the RequestThrottle error. Unfortunately, experience shows that even static pauses of 3 seconds cause the error in the API, which makes no sense at all.

Get the update

As always you can get the update via the auto-update function in the WP plugin backend or, if you are not yet an ASA2 user, via the shop page:

]]>https://www.wp-amazon-plugin.com/2019/15183/asa2-update-1-10-6-allows-using-the-editor-button-in-the-gutenberg-classic-block-and-deals-with-the-requestthrottle-api-issue/feed/0Why does Amazon continue to make life harder for its affiliate partners? A summary of the current grievances.https://www.wp-amazon-plugin.com/2019/15141/why-does-amazon-continue-to-make-life-harder-for-its-affiliate-partners-a-summary-of-the-current-grievances/
https://www.wp-amazon-plugin.com/2019/15141/why-does-amazon-continue-to-make-life-harder-for-its-affiliate-partners-a-summary-of-the-current-grievances/#commentsTue, 12 Mar 2019 13:58:17 +0000https://www.wp-amazon-plugin.com/?p=15141Over the past months and years, Amazon affiliate partners have had to accept a number of restrictions that have confronted quite a few with the collapse of their business model overnight. Since the situation has worsened since the beginning of the year 2019 with another restriction on the use of the Amazon Product Advertising API, I would like to summarize ...

]]>Over the past months and years, Amazon affiliate partners have had to accept a number of restrictions that have confronted quite a few with the collapse of their business model overnight. Since the situation has worsened since the beginning of the year 2019 with another restriction on the use of the Amazon Product Advertising API, I would like to summarize the most striking facts in this article.

On 23 January 2019 Amazon activated an update of its Efficiency Guidelines. It says: “…the request limit for each account is calculated based on revenue performance attributed to calls to the Product Advertising API (PA API) during the last 30 days.” And further: “Each account used for Product Advertising API is allowed an initial usage limit of 8640 requests per day (TPD) subject to a maximum of 1 request per second (TPS).”

Suppose I want to run my Amazon Affiliate website as best as possible and update the product data every hour to save me the price disclaimer ads, this means I can use a maximum of 360 products on my site. Because the allowed 8640 requests to the API divided by the 24 hours of one day results in 360. For a hobby project to improve the pocket money this may be ok, for ambitious projects this means that they are forced to start small.

Furthermore, the maximum of one request per second poses a challenge to the technology. Uncontrolled sending of requests would lead to parallel and therefore too frequent requests, which would lead to the error message “Error: RequestThrottled: AWS Access Key ID: ######. You are submitting requests too quickly.” at an initial limit of 1 per second, which would lead to products no longer being displayed and the income of the affiliate partner would subsequently stop or be reduced.

To avoid the request throttled error, you should only send one request to the API every 10 seconds for 360 permitted requests per hour (10 secs * 360 = 3600 secs ~ 1 hour). This is not easy to implement on the server side, because cronjobs can only be executed on a per-minute interval basis. So a cronjob would have to be executed every minute and update a maximum of 6 products with a pause of 10 seconds. With ASA2’s Cronjob and its “Limit” option in combination with the option “Max requests per second” this is possible, but for the beginner it is too big a technical hurdle.

Amazon API calculates request limit incorrectly

In addition, the new regulation of the Efficiency Guidelines of 23 January 2019 obviously still has problems with the correct calculation of requests per second. I have several reports from users who have already received the “RequestThrottled” error during the setup of ASA1 or ASA2. It has been proven that ASA only sends a single request to the API at this point. Therefore, this error makes no sense at all, because less than one request cannot be sent.

That it is a problem of the Amazon API is proven by reports of the mentioned users that they also get this error with other plugins.

Furthermore, several reports in the AWS Forum prove that the problem lies on the API side. There experiences are described, which were made completely without plugins or WordPress and e.g. report: “I can confirm that my script is sending one request every 4 seconds to amazon.de. The requests are still being throttled randomly.”

The following screenshot is from a real case of a user who gets the RequestThrottled response although there is a pause of 3 seconds between the API requests in the ASA2 cronjob.

A request to the responsible persons of the Amazon Partner Program

Of course, I can understand that the use of the Amazon Product Advertising API should not be unrestricted and immediately accessible to everyone. The deployment and the traffic finally cause cost.

On the other hand, it is not acceptable that these restrictions are so severe and partially still immature that established, long-time users suddenly face immense problems and revenue losses, for which there is no acceptable solution especially in the case of the RequestThrottled API bug.

Especially for longtime users I think the new coupling of the allowed requests to the revenue performance of the last 30 days is excessive. For seasonally dependent websites, such as test pages for grills, this would mean that you would be able to send fewer requests to the API in autumn and winter and would therefore be confronted with technical problems that make it difficult to update the site and might therefore lose good SEO rankings until the next barbecue season.

In my opinion, there is a lack of sensitivity here. We Amazon affiliates have been making sure for years that visitors to our websites become new Amazon customers and we have had to struggle with new restrictions in the recent past in order to be able to continue to provide this service optimally.
Therefore I would be pleased about a reform of the Request Limit restriction and above all that it works correctly for the time being.

API access only after three months

Anyone who registers for the Amazon Partner Program knows this: Access to the Amazon Product Advertising API is only granted after 180 days if at least three qualified sales via your own links have taken place within this period. It behaves like an admission procedure.

The problem I see is the fact that the professional, efficient use of the partner program is only possible with the API. Only with the API you can present regularly updated product data, such as prices, on your own website in a technically reasonable way. Without API, the use of Amazon SiteStripe remains, which is equivalent to manual maintenance.

Maintaining products in large numbers on many pages in these 180 days becomes a task one would like to automate to save life time. After all, this is what API and tools like ASA are for. So you have to work out a completely manual first workflow and then, if you’re lucky enough to get access after 180 days, you have to create a second workflow for automation. What a waste of time!

In my opinion, a better solution would be to grant access to the API immediately after registration, but with the request limit restrictions described above that have been in effect since the end of January 2019. If you have achieved enough conversions after 180 days, these restrictions will be relaxed to allow you to technically expand.

For long-time users who have monthly conversions, the request limit should generally be waived or at least considerably extended in order not to unnecessarily curb them and constantly cause them technical problems.

Disabling or changing RSS feeds without announcement

The use of data feeds is addressed in the policies. These are a great way to automatically process regularly updated product lists on the basis of RSS feeds. Great only if they work. Because for some time now, URLs like these simply don’t work anymore: https://www.amazon.com/gp/rss/bestsellers/home-garden/14162641/

Many Amazon affiliates have made use of RSS feeds and built applications on their websites around them. Suddenly these feeds are simply switched off or changed by Amazon without informing them. I already made a request on this topic in the AWS Forum at the end of last year without having received any feedback.

Again, I wonder why Amazon Affiliates are taken the tools out of our hands.

Conclusion

These are just the most serious issues currently affecting Amazon Affiliates’ lives. There would be more…

If I could give advice to those at Amazon responsible for the Product Advertising API, it would be:

“Please value your affiliates again,
because they work for you!”

]]>https://www.wp-amazon-plugin.com/2019/15141/why-does-amazon-continue-to-make-life-harder-for-its-affiliate-partners-a-summary-of-the-current-grievances/feed/4ASA2 Service Update 1.10.5https://www.wp-amazon-plugin.com/2019/15113/asa2-service-update-1-10-5/
https://www.wp-amazon-plugin.com/2019/15113/asa2-service-update-1-10-5/#respondSun, 03 Mar 2019 13:58:40 +0000https://www.wp-amazon-plugin.com/?p=15113Version 1.10.5 of ASA2 is available and brings a lot of optimizations of the included templates. Unified disclaimer options for all templates Price Disclaimer The options for the price disclaimer and the indication of the affiliate link were previously not available for all templates or were not uniform in their function. This is now guaranteed for all templates. In the ...

]]>Version 1.10.5 of ASA2 is available and brings a lot of optimizations of the included templates.

Unified disclaimer options for all templates

Price Disclaimer

The options for the price disclaimer and the indication of the affiliate link were previously not available for all templates or were not uniform in their function. This is now guaranteed for all templates. In the template options you will find the option “Show price disclaimer” in section “Price”, which is activated by default and shows the time stamp next to the product price.

It is strongly recommended that you enable this option to comply with the Amazon Affiliate Program terms and conditions. I know of a few cases in which users were excluded from the program because they did not sufficiently indicate the date of validity of product prices.

Affiliate Link Disclaimer

In addition, the option to display the affiliate link disclaimer in the template has been unified for all templates. It can be found in the template options in section “Misc”. In addition to the asterisk, the disclaimer text can now also be displayed in each template. The extended variant is standard and also recommended to be on the safe side.

New Template Option “Custom CSS”

Additionally, there is now the new option “Custom CSS” in every template, which makes it possible to store individual CSS specifications within a template. This is update safe and lets you add your individual layout to the managed templates beyond the given options. This CSS will only be embedded once on a page, even if the template is displayed multiple times.

Alignment fixes

With the last update the alignment of some templates was changed to the disadvantage. This was corrected with the new version. In addition, for the templates “Flat_box_vertical” and “Flat_box_horizontal” there is now a new option to choose the image size between “Small”, “Medium” and “High”.

Other improvements

The template “Flex_1“ now has the option to display the prime logo next to the price.

The table templates “Sortable_table” and “Sortable_table_2” have been optically revised to achieve a more compact view. For example, the product title can now be reduced to one line to avoid bloating the height of a table row.

]]>https://www.wp-amazon-plugin.com/2019/15113/asa2-service-update-1-10-5/feed/0ASA2 Service Update 1.10.4https://www.wp-amazon-plugin.com/2019/15090/asa2-service-update-1-10-4/
https://www.wp-amazon-plugin.com/2019/15090/asa2-service-update-1-10-4/#respondMon, 11 Feb 2019 21:28:51 +0000https://www.wp-amazon-plugin.com/?p=15090The new ASA2 Update 1.10.4 brings many minor improvements and bugfixes. Here is an overview. Improved Template Customization The customization window of the included managed templates has been completely revised. The options are now divided into categories to get a better overview. There is also an example of how to use each option in a shortcode. Improved Managed Templates ...

]]>The new ASA2 Update 1.10.4 brings many minor improvements and bugfixes. Here is an overview.

Improved Template Customization

The customization window of the included managed templates has been completely revised. The options are now divided into categories to get a better overview. There is also an example of how to use each option in a shortcode.

Improved Managed Templates

“Flex_1“: This template has received many improvements to present all products in the same height. In addition, you can now adjust the number of columns to be displayed on different screen sizes.

“Carousel“: The initial loading now looks smoother and the display of all products at the same height has been improved. Also, a conflict with the slideshow that occurred when other templates were used on the page was fixed.

“Flat_box_vertical“: Shortcode options are now processed correctly again. The hover effect has been corrected for Firefox.

“Sortable_list_2“: A problem with displaying images on AMP pages has been fixed.

Options

There is a new option to hide the Managed Templates in the administration area, which is useful for those who do not use any of these templates.
In the options section “Advanced” there is a new option that allows to edit managed templates. This should only be used in the context of a support request to solve a display problem, as these changes would be overwritten with the next update.
The option “Reset queue” of the Advanced Ratings mode can now also delete articles from the queue that no longer exist in the repo.

PHP

ASA2 has been further optimized for PHP 7.2, among other things all occurrences of the outdated function “each” have been replaced by “foreach”.
ASA2 was also optimized and tested for the new PHP version 7.3.

Ratings / Proxies

In rare cases, the use of proxies resulted in a rating higher than 5. From now on, proxies are downgraded in such cases.
If a new product is saved in the repo, it will be sorted at the top of the ratings queue when using the Advanced Ratings mode.

Product Picker

The Product Picker now remembers the last settings and search results and displays them the next time you open it, e.g. when managing collections, which saves you having to enter them again.

Minor Fixes

The function for analyzing the use of repo articles now also supports the asa2_textlink shortcode.
The bulk export for templates has been fixed.

]]>https://www.wp-amazon-plugin.com/2019/15090/asa2-service-update-1-10-4/feed/0ASA2 Update 1.10.0 for WordPress 5.0 features completely re-engineered ratings analysis, proxy server support and other useful improvementshttps://www.wp-amazon-plugin.com/2018/14828/asa2-update-1-10-0-for-wordpress-5-0-features-completely-re-engineered-ratings-analysis-proxy-server-support-and-other-useful-improvements/
https://www.wp-amazon-plugin.com/2018/14828/asa2-update-1-10-0-for-wordpress-5-0-features-completely-re-engineered-ratings-analysis-proxy-server-support-and-other-useful-improvements/#respondWed, 05 Dec 2018 22:21:48 +0000https://www.wp-amazon-plugin.com/?p=14828Completely re-engineered ratings analysis The subject of product ratings is familiar to many of you. Since the Amazon API no longer delivers them, ASA2 offers the optional service to retrieve the ratings (can be disabled completely). In the past, this was done using the ratings page provided by the API. This often resulted in the so-called Captcha page, i.e. a ...

The subject of product ratings is familiar to many of you. Since the Amazon API no longer delivers them, ASA2 offers the optional service to retrieve the ratings (can be disabled completely). In the past, this was done using the ratings page provided by the API. This often resulted in the so-called Captcha page, i.e. a block by Amazon when the same source accessed this page too frequently.

With version 1.10.0 of ASA2, this problem is a thing of the past, because from now on ASA2 has several search patterns that are applied one after the other until a successful hit for a product is achieved. The first longer-term tests have shown that with this new approach the captcha page hardly appears at all any more and the ratings were obtained in almost 100% of the cases. This functionality is currently ASA2 exclusive and not included in ASA1!

Proxy server support

If there are still errors despite the new search patterns, e.g. because the IP address of your server is blacklisted at Amazon, ASA2 now supports the use of proxy servers for the analysis of ratings. ASA2 uses a specially developed algorithm to use the proxies in changing order. If a proxy turns out to be incompatible for accessing Amazon pages or is no longer available, ASA2 automatically shuts it down.

If a proxy works successfully, it is evaluated according to a score system that can be used as a criterion for the use of proxies. In the section “Options / Ratings / Proxies” you will find the settings with which you can influence the algorithm.

Since communication via proxies is not very fast, this feature is only supported by the Ratings Cronjob, which is server-side and therefore independent of user access.

WordPress 5, Gutenberg and PHP 7.2

ASA2 is compatible with the new WordPress version 5. The shortcodes continue to work unchanged and can be integrated manually into Gutenberg text blocks. At the moment ASA2 does not offer a special block function for the new WordPress Editor. A special ASA2 integration for Gutenberg will follow at the beginning of 2019, after the first real world experiences could be made with it.

At this point I would not recommend an immediate upgrade to WordPress 5.0. From my personal experience, it is worth waiting for the first bugfix releases in order to avoid unnecessary hassle caused by the initial difficulties of a new major release. Upgrading to WordPress 5 during January 2019 sounds like a good strategy to me.

If you want (or must) deal with the additional stress of the pre-Christmas period and upgrade directly to WordPress 5, you can install the Classic Editor plugin, with which you can switch between Gutenberg and the Classic Editor if necessary, in order to continue using the ASA2 Editor button. The Classic Editor will be supported until 2022.

As always, ASA2 gets tested on all common PHP versions, from the latest 7.2.x versions down to 5.3. However, if you still have a PHP 5.x version on your server, I strongly advise you to upgrade to at least PHP 7.1! Because the support for PHP 5.6 will expire soon. (January 2019, see http://php.net/supported-versions.php).

Analyse ASIN usage

In the Repo section it is now possible to analyze the usage of an ASIN. Move the mouse over a product and click the link “Usage”. You will then be shown a list of pages on which the product is used. Currently only the usage of the shortcodes is supported, because the other shortcodes integrate products dynamically and the usage of ASINs cannot be calculated.

Furthermore, a new filter for the countries was added to the Repo.

Improvements and bug fixes

As always, the update contains a number of minor improvements and bug fixes.

Fixed some problems with feeds where categories were not used when saving feed products in the Repo. Also, the feature to disable the storage of feed products in the Repo did not work.

The placeholder {{ EditorialReviewsContent }}} has been changed to prefer Amazon content.

Internal element names, such as template or feed names, may now contain the minus sign (-).

The handling of the rating queue in “Advanced Ratings” mode has been optimized. An attempt is made to avoid populating by two parallel requests. The ratings cronjob can now process multiple products in one run. For this there are the new options “Cronjob items per run”, “Cronjob pause” and “Cronjob bypasses lock” in the “Options / Ratings” area. These options are also available for the command line as option “quantity” and “pause”, like:

bash script.sh Asa2_Cron_Ratings --quantity=5 --pause=2

There were some layout improvements on the included templates, e.g. “Sortable_table_2“. The navigation elements of the template “Sortable_table” now support multi-language support which is based on the language set in the WordPress configuration.

]]>https://www.wp-amazon-plugin.com/2018/14828/asa2-update-1-10-0-for-wordpress-5-0-features-completely-re-engineered-ratings-analysis-proxy-server-support-and-other-useful-improvements/feed/0Black Friday Sale 2018 – Get your 30% discount code!https://www.wp-amazon-plugin.com/2018/14806/black-friday-sale-2018-get-your-30-discount-code/
https://www.wp-amazon-plugin.com/2018/14806/black-friday-sale-2018-get-your-30-discount-code/#respondTue, 20 Nov 2018 21:04:56 +0000https://www.wp-amazon-plugin.com/?p=14806The week of big offers has started and this year ASA2 is back with a 30% discount! Use the following coupon code for your purchase on https://getasa2.com/. ASA2BLACK18 It is valid until the end of November 2018. The ASA2 Black Friday Sale is live and offers you 30% discount on all purchases at https://getasa2.com/ Just use this coupon code during ...

]]>https://www.wp-amazon-plugin.com/2018/14806/black-friday-sale-2018-get-your-30-discount-code/feed/0ASA2 Update 1.9.1 brings support for Australia and AMP fixeshttps://www.wp-amazon-plugin.com/2018/14791/asa2-update-1-9-1-brings-support-for-australia-and-amp-fixes/
https://www.wp-amazon-plugin.com/2018/14791/asa2-update-1-9-1-brings-support-for-australia-and-amp-fixes/#commentsSun, 22 Jul 2018 20:27:22 +0000https://www.wp-amazon-plugin.com/?p=14791Support for Australian API Recently, the Amazon Product Advertising API also supports Australia. Support for Australia has also been integrated into ASA2 with version 1.9.1. This allows you to use the Amazon Affiliate program for Australia and prepare internationalized products in ASA2 for Australia. AMP improvements Support for AMP pages introduced with the latest version of ASA2 still had some ...

Recently, the Amazon Product Advertising API also supports Australia. Support for Australia has also been integrated into ASA2 with version 1.9.1. This allows you to use the Amazon Affiliate program for Australia and prepare internationalized products in ASA2 for Australia.

AMP improvements

Support for AMP pages introduced with the latest version of ASA2 still had some problems. In cooperation with some users, these problems could be solved successfully. In addition, the templates integrated in ASA2 have been further optimized with regard to their AMP compatibility. With the new update, pages showing ASA2 products are successfully validated by Google’s AMP Validator.

Knowledge Base

In addition, the ASA2 Knowledge Base was launched to collect everything worth knowing about ASA2. The ASA2 dashboard now provides a handy search field for accessing the Knowledge Base contents directly from ASA2.

Minor fixes

As always, many small bugs have been fixed that do not need to be described in detail here. You can find a list of all changes in the ASA2 changelog.