Conflict with Google's AMP (Accelerated Mobile Pages)

[浩之_田所1]

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

[SanfordWhiteman]

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]

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]

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.

[浩之_田所1]

Hi Sanford,

Thanks again!

Regards,

TAD

On Thu, Mar 31, 2016 at 3:00 PM, Sanford Whiteman <

[浩之_田所1]

Hello, again, Sanford.

Would you mind asking one more question?

- Should I understand I would have the same trouble when it comes to "

Optimizely <https://www.optimizely.com/?redirect=japan>" as per AMP &

Marketo's?

I guess I would because I have to embed JS snippet when I use this service.

Best,

Tad

2016-03-31 15:06 GMT+09:00 田所浩之 <tadokoro@nspc.jp>:

Hi Sanford,

Thanks again!

Regards,

TAD

On Thu, Mar 31, 2016 at 3:00 PM, Sanford Whiteman <

[SanfordWhiteman]

Yes, you'd have the same problem with any tracking or personalization script.

[浩之_田所1]

Hi Sanford,

Appreciate for your advice!

I understood.

Thanks

TAD

2016-04-01 14:42 GMT+09:00 Sanford Whiteman <marketingnation@marketo.com>:

<https://nation.marketo.com/?et=watches.email.thread> The Marketo

Marketing Nation Community

<https://nation.marketo.com/?et=watches.email.thread>

Conflict with Google's AMP (Accelerated Mobile Pages)

reply from Sanford Whiteman

<https://nation.marketo.com/people/63ea064b55e61d1184c4e1e1cc5ee59b25d3a3a1?et=watches.email.thread>

in Products - View the full discussion

<https://nation.marketo.com/message/125274?et=watches.email.thread#comment-125274>