SanfordWhiteman

I'm not sure what you're asking because certainly any Smart List/Campaign is capable of filtering on hidden fields that you use to record lead source. But SL./SC and Segs don't have the same purpose. What exactly do you mean by "separate out" -- to customize a single mailing?

That makes sense... had your original description of the situation been accurate I hope you can see how my workaround would apply.However, I don't see two separate trigger campaigns being a full solution, because as the support tech says, "... if a lead has a Click Link activity in its Activity Log....

The Clicked Link activity is being logged in the context of the current page, thus you end up searching on the current page.By changing the Clicked Link to being logged on the target page/download, the same search will match the target, not the source.

@Dan If you're into JS, think about replacing the automatic Munchkin click tracking with custom calls to clickLink. That way -- I'm pretty sure, at least -- you can use the target link in place of the referrer and Marketo will log the link as having come both "from" and "to" the link you're looking ...

Well, yes and (I think) no. You can post previously unknown fields with the form and they will be stored in the Filled Out Form activity. But AFAIK they can't be transformed into tokens unless you first used the API to scan the records and then did an API Request Campaign.

@Christine the form embed code is Javascript (though you copy-and-paste it, so you don't need to actually be a JS developer.)You can also do quite deep customization of the embedded form using custom Javascript and the Forms 2.0 API.So there really are 3 options: plain-vanilla (JS-based) embed, cust...

OK... assumed so but it seemed to not mesh with @Bruno's request because he didn't mention countries at all!While I agree you'll get true positives if someone comes from an enterprise with their own AS, you can't assume you're counting all the visits on behalf that enterprise, since direct mobile (n...

@Jim While I understand the need for enforcing uniqueness in different ways, bear in mind that coupling site requests to a tightly-governed resource like the REST API (you only get 10,000 API calls per day) is a dangerous practice from a security standpoint. You've basically added in a DDoS vulnera...

@Jaclyn in addition, note that Clicks are associated with an implied Open even if the user never downloaded the tracking image. This can give a false impression of the accuracy of Open tracking on its own, which as Josh said is not reliable.

@Adam what is the significance of excluding those countries?