Skip navigation
All Places > New York User Group > Blog > 2017 > April
2017

A good question from a reader today who asks, My client claims you can't have a From: or Reply-To: domain that's exactly the same as your click tracking domain (what Marketo calls the branding domain). Is this true?

 

Yep, within the confines of Marketo this is true.

 

That is, you can't send with the From: header:

 

From: All Eyez on Me <alleyez@example.edu>

 

and have your rewritten tracked links use the exact same domain:

 

<a href="https://example.edu/saz95jf81235jhg8712sj">Learn more</a>

 

You can of course use a subdomain

 

<a href="https://click.example.edu/saz95jf81235jhg8712sj">Learn more</a>

 

… which is what we're used to (branding domains are click-dot-whatever, landing page domains are pages-dot-whatever).

 

But why? It's not merely a tradition but based on a longstanding technical rule.

 

 

Read the full post on TEKNKL :: Blog →

Quick: How big are your Marketo LPs?

 

I know you don't have the size in KB at your fingertips. But you're probably thinking, Smallish... tiny bit of CSS, forms JS, optimized images. Definitely smaller than our corporate home page, I can tell you that much.

 

What if I told you that your Marketo LPs may be forcing users to download your home page's full HTML, twice in addition to downloading the LP and its own assets?

 

(And I do mean your home page. Not something the size of your home page,  but your actual home page.)

 

Read the full post on TEKNKL :: Blog →

Newbie Q: Where do I click to see X?

 

Oldie A: You don't.

 

the least happy type of Community thread

 

New users may search in vain for a log of all Filled Out Form events plus their point-in-time form data. (That is, even if field updates were blocked or values were later overwritten, you see the values that were on the form when each person clicked Submit).

 

First: it's not correct to say that Marketo doesn't store the original data from form posts: in fact, the REST Activity API includes historical POST payloads, including since-overwritten values. But it's true that it's not easy for a non-developer to see form data history across leads.

 

When seeking such a report outside of Marketo, users tend to say a Google Sheet (as opposed to XLS/CSV, Excel 365 online workbook, or something else). I'm not a Sheets user myself unless forced, but I know how it's done, and it's reeeeeally easy. So that's what we'll use today.

 

Read the full post on TEKNKL :: Blog →

A pesky problem with Munchkin is that you can't selectively turn it off based on visitor characteristics.

 

You can choose Disable Munchkin Tracking on Marketo LPs, but that's for every visitor, and on your corporate site you're unlikely to have access to an on/off switch. So internal visitors show up in your stats (okay when testing, but bad after go-live) and it would be great to be able to exclude them, wouldn't it?

 

Although the best place to check IPs would of course be on the Munchkin server itself (thus no extra requests) we can ping a remote service to get the end user's IP, then use a l'il JS wrapper to conditionally load Munchkin based on whether the IP appears in allowed/disallowed Access Control Lists (ACLs).

 

Read the full post on TEKNKL :: Blog →