Different Meta Values on my site

Hi, thanks for your query. I will be happy to help.

Data such as your domain and account number will not be found in the meta tags. This is normal and the code snippet you have provided me looks valid.

The ca-host-pub-** is your publisher ID (ie. your AdSense account ID). So that’s all that’s needed to associate the AdSense snippet to your account.

Hope this helps to explain. Are you having any difficulties with the Site Kit plugin at this time or is everything working fine?

Thanks.

The ca-host-pub-** is your publisher ID (ie. your AdSense account ID).

The one I have provided here is not mine.

My ID is different and that is why I asked.

Can I please ask if it was you who set up the Site Kit plugin on the site or was this done by another administrator?

The reason I ask is because when you set up AdSense from Site Kit, it uses the AdSense account associated with the Google account used to set up the plugin. So if that was set up by somebody else then it would have used their Google account and not the one you are expecting.

Thanks.

As we haven’t received a response, I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist. Thanks.

Hi,

My publisher ID is showing correctly on the Site Kit Dashboard.

But when I check the source code, the one there under the <!– Google AdSense snippet added by Site Kit –> is different.

I am the one who set it, so there is no chance I set a different account.

See Screenshots
https://ibb.co/y6C4PVS
https://ibb.co/c24ZWHy

• This reply was modified 3 years, 1 month ago by Emmanuel Chekumbe.

I have same issue and when we search for this ID on the internet, we see a lot of similar issues. There is this ID (2644536267352236) in Site-Kit downloaded directly from WordPress, and after Site.Kit is installed on the site, you can see this ID in the site meta tags when you directly CTRL+U. But obviously The developers of the Google Site-Kit have no intention of investigating the reason for this.

@adsenser77 If you’d like to open a new support topic we’d be happy to help you out with this.

Note that any site that is using Site Kit to insert the AdSense snippet will have the below:

<meta name="google-adsense-platform-account" content="ca-host-pub-2644536267352236">
<meta name="google-adsense-platform-domain" content="sitekit.withgoogle.com">

These are AdSense for platform account identifiers are not individual users AdSense publisher ID’s. Individual users AdSense account ID will look similar to the below, when placed via Site Kit:
<script async="async" src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-3467*******403" crossorigin="anonymous" type="text/javascript"></script>

The AdSense for platform ID doesn’t impact ads.

I hope that helps, but do feel free to open a support topic if you’d like further information.

We are also facing same issue. Could you please give a better solution to resolve this issue.
Thanks

<!-- Google AdSense snippet added by Site Kit -->
<meta name="google-adsense-platform-account" content="ca-host-pub-2644536267352236">
<meta name="google-adsense-platform-domain" content="sitekit.withgoogle.com">
<!-- End Google AdSense snippet added by Site Kit -->
      <meta name="onesignal" content="wordpress-plugin"/>

@smartkenyan

• This reply was modified 2 years, 3 months ago by softisky.

Hi @softisky,

The snippet you shared above is added if a user placed their AdSense snippet via Site Kit. If you don’t allow Site Kit to insert your AdSense snippet, and add your Auto ads code manually yourself, this won’t appear.

Note that as mentioned above, this google-adsense-platform-account meta tag is only used to indicate that Site Kit was used to insert your own AdSense code. It doesn’t impact ad serving on your site.

<meta name=”onesignal” content=”wordpress-plugin”/>

This particular meta tag was not inserted via Site Kit. This seems to come possibly from the One Signal plugin.

For any further queries please open an individual support topic, and we can communicate from there.