302 redirect in AMP 1.0 from old /amp/ pages to the new ones /?amp

analytics tracking is set under plugin Analytics tab:
worked fine in previous setup.
Analytics setup is one point, however traffic is definitely not going to amp pages and is down by about 25%.
{
“vars”: {
“account”: “UA-20014268-5”
},
“triggers”: {
“trackPageview”: {
“on”: “visible”,
“request”: “pageview”
},
“trackEvent”: {
“selector”: “#sidebar”,
“on”: “click”,
“request”: “event”,
“vars”: {
“eventCategory”: “ui-components”,
“eventAction”: “menu-click”
}
},
“outboundLinks”: {
“on”: “click”,
“selector”: “a”,
“request”: “event”,
“vars”: {
“eventCategory”: “outbound”,
“eventAction”: “click”,
“eventLabel”: “${outboundLink}”
}
}
}
}

@fredmr I don’t see UA-20014268-5 appearing anywhere in the page source: https://www.lushome.com/warm-metal-accents-bringing-luxurious-glow-modern-kitchen-design/196345?amp

I have analytics configured in the Analytics tab on my own site (running 1.0.1 in native mode) and I’m seeing them successfully added to the page: https://weston.ruter.net/

I tried using a modified version of your config as well, and it appeared in the page.

You may have another plugin that is interfering with the <amp-analytics> tag being output to the page.

Here is the logic responsible for adding amp-analytics: https://github.com/ampproject/amp-wp/blob/efd1d0759d000a82a48ae0a0dd1fca9bdbcf1d8d/includes/amp-helper-functions.php#L575-L610

You may have a plugin that is filtering amp_analytics_entries.

This may be related to https://github.com/ampproject/amp-wp/issues/1498

Thanks, I placed the amp analytics into the template and it is working now.
Not sure what was blocking it before. 301 should be better redirect for old amp links, would you agree?

@fredmr You should not have to manually add it to the template. The AMP plugin should be doing it automatically, as you can see from my own site: https://weston.ruter.net

I did try that route first but it did not work. Will try to investigate more tomorrow.