junpeizaki

Hi, thanks for all of the support.

It seems it was just a matter of Google updating the pages it had cached – which is probably why you were able to find the analytics tag since it updated overnight.

Hopefully, anyone else having a similar problem can benefit from my struggles.

@schlessera Thanks for the reply and suggestions.

Your suggestion is very plausible and is kind of the conclusion I came to after testing many many different options.

One thing I would like to point out is that the cached version as far as I can tell is, in fact, the valid AMP version of my site. As I am sure you are probably well aware, I am using Twenty Twenty which is an AMP-compatible theme meaning the look and feel of the site should stay cohesive between AMP and non-AMP versions of my site.

What I am worried about is if Google is stripping the tracking code I implemented within the Analytics sections of the AMP plugin when it caches AMP versions of my page on its servers.

I tried cleating the page in question’s cache using the method you described but to no avail. Considering the page I used as an example isn’t only that page that seems to be affected – I don’t think I am currently able to track any mobile traffic coming from Google via AMP, I thought this could potentially be a much greater problem.

Thanks for all the help.

Any suggestions anyone?

I understand what you are saying, but don’t fully understand how this would prevent Google Analytics from tracking impressions to my site. I added the tracking code within the Analytics section of the official AMP plugin, following the instructions shown here.

Why would AMP strip code that has obviously been formatted for AMP pages?

To clarify, Google Analytics does track impressions for my AMP pages with the URL’s ending in “/?amp” for example https://edamame.reviews/taxi-rush-review/?amp

It does not, however, track impressions for content that is cached on Google’s servers. For example https://www.google.com/amp/s/edamame.reviews/pineapple-pen-ketchapp-review/%3famp

I hope this makes more sense.

• This reply was modified 5 years ago by junpeizaki.

You can also recreate the issue using Chrome Inspect Element > Simulate Mobile Device > Open this Gppgle AMP Search Result link: https://www.google.com/amp/s/edamame.reviews/pineapple-pen-ketchapp-review/%3famp

Hi

I tested OneSignal with the Classic Editor Plugin disabled (i.e. The standard Gutenberg Editor) but OneSignal still sent out push notifications… Have you got any other ideas as to what could potentially be the cause?

• This reply was modified 5 years, 5 months ago by junpeizaki.
• This reply was modified 5 years, 5 months ago by junpeizaki.

Hi

I uploaded an unlisted screen-recording of the issue I am experiencing to YouTube. (At the time of writing the video can only be viewed at 360p as higher resolutions have yet to be processed)

Video: https://www.youtube.com/watch?v=cVf97pgaHlw

As far as I can see the console doesn’t seem to be working the way it should base on what I read at Debug with Gutenberg

Hi sorry for the late response.

I installed the build you sent but unfortunately it didn’t seem to work – OneSignal still sent out notifications.

Here are all the plugins I currently use.

AMP
BackWPup
Classic Editor
Contact Form 7
Gmail SMTP
OneSignal Push Notifications
Revive Old Posts
Revive Old Posts Pro Add-on
Simple Revisions Delete by b*web
tagDiv Composer
tagDiv Mobile Theme
Webcraftic Disable Admin Notices Individually
Yoast SEO

@onesignal

I’m using the WordPress Classic Editor plugin ver 1.5
The theme I am using is Newspaper By tagDiv Version: 9.6.1

Thanks.