Conflict with Google's AMP (Accelerated Mobile Pages) | Community
Skip to main content
浩之_田所1
浩之_田所1
Level 2
March 31, 2016
Question

Conflict with Google's AMP (Accelerated Mobile Pages)

  • March 31, 2016
  • 1 reply
  • 5007 views

Hi all,

Would anybody know whether or not I could have any conflict problems (e.g. display/tracking problems) when I converted websites in which Munchikin is embedded into Google's AMP (Accelerated Mobile Pages) ?

Thanks in advance!

TAD

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
March 31, 2016

You absolutely will have problems.  AMP is ultimately a static page renderer.  Tracking snippets, no matter how small (and necessary) can't run in a main AMP document.  You can convert Munchkin to run in an iframe within an AMP document, but this will ensure that you miss tracking hits (even more than you already do).  You'll still get some hits, maybe even most... just don't complain when your stats are inaccurate, because that's the choice you make when going "static first."

浩之_田所1
浩之_田所1Author
Level 2
March 31, 2016

Hi Sanford

Appreciate for your immediate advice, which is a good help to us.

We won't do so.

Yet, I guess this would be something that could have greater influence to

all of Marketo users in the future.

Regards,

TAD

On Thu, Mar 31, 2016 at 2:37 PM, Sanford Whiteman <

marketingnation@marketo.com

<http://go.contentmarketinglab.jp/ol/jE5YecfLLFxQsRp44uyJLaf%2DjzbFdIytqb9yK%5FLy08wrylwzIqGfdRGi2J5BDp02KLnYDBEXGpQ8kEpcE%2DTILdITrrNOBRziHj72hPzQZptLPOUlhZcxpv7xjDJI%2DImMmxGeRB0BS3dMaQeUZfEthS%5FsNYQsEQmO7H7OO8kgkyVOkLQAi8LteKug6XL92HDr9DOmGkhEts2Q2miVWbdkg8M4iE036WcXJM3C1i%5F%2DkJU%5FhwEWpcFAtAtA0tlqD%5FFw7RCEBzDT3L3wdc83ULfhuvTDm6gzbDkanoQgWTbSem26DoDJShhF%5FhS7xxchM2lcdwkJO%5FUWoTGRlF50YekDfDO1rwdz7Uclxax%2D2Y7K43aHUiryMwqtjBea%5Fl6RAKIK4E3AtdMiwhzOCDvc89VAc2ujXNzPrmmFQaXqnU8OdtFZAIZUbA%2C%2C/j0lRd8LJK1xYvEti5KaUI7vmmiHJdJ%2Dmuqh0BvnG384s0k1qfaLMN0ywhdhFI4Y9brTMGTcxOKpr4w9uEtCGXY9O7PRlO0Kke2zm0obpQdVcKaBx6dZWqLn1i2M0%5FpjQsGn6TB0oRTQ%2DRiW%5FR4oE3Tq%2DCrYGBhTT%2DEuEZ6UhuC8QgJguj4E%2C>

SanfordWhiteman
SanfordWhiteman
Level 10
March 31, 2016

Yet, I guess this would be something that could have greater influence to all of Marketo users in the future.

Maybe.  But there's an essential "conflict of interest" which can't be satisfactorily resolved.  It's the same when you use a static page generator to "burn" a single page with all of your rendered content, including elements originally fetched via Ajax and/or created by JS.  A fully static page has an inherent "conflict of interest" with script-based analytics -- you'd have to use a partially static page generator, or use an old-school tracking pixel, which will offer a fraction of what Munchkin offers.

Terms & ConditionsAccessibility statement

Loading footer...