Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @puregraphx,

    It looks like a LinkedIn set-up with the Complianz integration that goes haywire.

    Could you explain how LinkedIn is set-up at your end?

    regards Aert

    Thread Starter puregraphx

    (@puregraphx)

    Hi,

    Actually a third party has set that up via the GTM code. They say they have not edited any Complianz settings.

    I have asked them to check the GTM code on their end.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @puregraphx,

    If I “block” the GTM script on your website in my own browser, this behavior does indeed not occur. And as you seem to be placing the GTM script with Complianz, this would explain why the behavior no longer occurs with the plugin disabled.

    I would be curious to know if the behavior still occurs when you place the GTM container code (with the same GTM ID) manually on the page, and with Complianz temporarily disabled.

    As in case of the latter, the issue would appear to be related to the tag itself.

    Kind regards, Jarno

    Thread Starter puregraphx

    (@puregraphx)

    I have added the GTM code manually to the footer and disabled the Complianz plugin, the problem is still there, so indeed, it is tag based, and not a Complianz issue.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin injects code between charset and viewport tags’ is closed to new replies.