Re: Floodlight Tag - getting this Limited Access error message.

SanfordWhiteman · ‎12-08-2017

That's all commented out anyway. (It's inside an HTML comment.) So in that screenshot you have no active pixels at all.

Are you looking at a rendered email in your mail client here?

Kirstin_Mahoney · ‎12-08-2017

Yes, unless I'm using the wrong method to see a rendered email's html? Clicking 'view online' link and then 'inspect' to see the html? I'll expand more in the inspect view to see more comments.

Kirstin_Mahoney · ‎12-08-2017

I just realized I cut of the floodlight tag in the previous screen shot:

SanfordWhiteman · ‎12-08-2017

You need to remove the comments in your HTML area because they're overlapping with the Marketo tracker when parsed, that is, your HTML is malformed. Only include the <img> tag for Floodlight and not any of the  chaff.

Kirstin_Mahoney · ‎12-08-2017

So instead of this:

<!--

Start of DoubleClick Floodlight Tag: Please do not remove

Activity name of this tag: #### - Email

URL of the webpage where the tag is expected to be placed: https://email

This tag must be placed between the <body> and </body> tags, as close as possible to the opening tag.

Creation Date: 12/04/2017

-->

THIS:

SanfordWhiteman · ‎12-08-2017

Yes; be aware that [Random] has no meaning as you're not inserting a random number there btw.

Kirstin_Mahoney · ‎12-08-2017

I see, so we could really use the below?

SanfordWhiteman · ‎12-08-2017

Yep. Or generate using Velocity.Think I'm going to do a quick blog post on this because it's frequently misunderstood.

Kirstin_Mahoney · ‎12-08-2017

Thank you Sanford! Would love to read it.

What's your benefit to helping all of us Marketo novices?! You're the best!!!

SanfordWhiteman · ‎12-08-2017

Yes, unless I'm using the wrong method to see a rendered email's html? Clicking 'view online' link and then 'inspect' to see the html?

Ah, no. You should never use this method because it will inaccurately show HTML that is stripped out by mail clients, particularly webmail clients like Gmail. For one glaring example, you can see (and run) script tags in the View as Web Page but these will never be executed by mail clients. Web View is a not a representation of the non-Web View experience.

You want to look at the source of the message in the inbox, and more important, you need to trace the network requests made when someone opens the message (to see which pixels are actually fetched).