I’m pretty relaxed about the logic of BE.. namely creating a job, polling for status, downloading file when ready. Manually, sure. But there are numerous exceptions and retry handlers that you have to code for when automating it. Enqueuing can fail, and status checks need to be on a timer. The download can be interrupted and need to be Range-resumed. Etc.   Does the lead query not takes dates in the comma separated list? Right, Date fields are not indexed as lookup fields. ... View more

Depending on your subscription, you may not be able to use only Bulk Extract for this particular scenario.   If your BE supports Smart Lists then run an extract on a corresponding SL.   If your BE only supports Static Lists then you'd have to run daily batch(es) to add people to a list. Then clear all the existing people in that list (or you could run that clearing run the night before, getting the order right is the point). Then extract that List.    Or, given the small number of leads, you could use the Lead by Filter Type export (as in fact Bulk Extract is quite complex to reliably automate, if you're not familiar with building that kind of logic).  Copy your Date field to a String field whenever it changes, then that "stamped" date-like String can now be used as a filter.       Alternately you could copy  ... View more

This will give you all email client-driven Unsubscribes (which includes both Unsubscribe and Report as Spam type buttons):   ... View more

The List-Unsubscribe header is an unsubscribe atttributed to a specific email asset. You can see an Activity Log entry to that effect. ... View more

It's not unpredictable, it's that you haven't figured out what the variables are. 🙂   N.B. It's basically impossible to have truly random behavior on a web page without deliberately invoking a random number generator -- and browsers' (P)RNGs weren't even random enough until recently! Of course, you can have behavior that varies based on network/server responsiveness, and those other factors can make the overall result appear to be random, but once you figure out the inputs you can get predictable output. In this case it isn't going to be related to network/server behavior. I'm sure it's down to the order in which cookies are set, stored, and reset. You shouldn't have needed my pURL fix anymore - that's one thing that tells me something is non-traditional about your testing and/or setup.   It isn't related to those Chrome warnings. (You can and should test in other browsers to rule that out anyway.)   What you need to make sure you're doing is not "clearing your cookies" but working in Incognito/Private mode and making sure all Incog/Private tabs are closed if you want a clean slate again (Some people don't understand that Incognito tabs do store cookies, as long there's at least 1 such tab open.)   Note in Firefox, when you work in Private mode Tracking Protection is on by default. You want to turn off TP while testing, because in this particular case you're using Private mode to emulate a fresh browser with no cookies, not for privacy protection.   ... View more

Thanks Jay, yes, I suppose my response wasn't self-explanatory!   @Nancy_Rosentha4 the reason you can't do it in a SL is the same reason you can't do anything with tokens in that context. The webhook is the workaround for that.  Or, as Jay says, export and import.   Note there is a way to compare certain values without using any external webhook-compatible service. You still need to use Call Webhook, though. And this only works for case-sensitive comparisons of values that are not allowed to have spaces. Will write about it someday... ... View more

Set the default value to {{lead.Email Address}} ... View more

If you use a predictable JSON indenting format (more to the point, no indenting or whitespace at all), then even though Marketo can't actually parse JSON internally (for that, you'd use a webhook, and I certainly recommend you do for advanced logic) you can use the Contains operator. ... View more

Please highlight the JS code using the syntax highlighter so it's readable.   From what I can read it's clear there's a lot of duplication (and you must not duplicate, since you're then adding multiple onValidate events).   checkboxGroups is an Array. It's already designed to have multiple items. There's no need for checkboxGroups2 and checkboxGroups3.   var checkboxGroups = [ { fieldNames: ["selectDeselectBrand", "Opt_in_Aston_Martin__c", "Opt_in_Audi__c", "Opt_in_BAC__c", "Opt_in_Bentley__c", "Opt_in_Bugatti__c", "Opt_in_Ferrari__c", "Opt_in_Lamborghini__c", "Opt_in_Lotus__c", "Opt_in_HROwen_Bodytechnics__c", "Opt_in_HROwen_Group__c", "Opt_in_HROwen_Insurance_Services__c", "Opt_in_HROwen_Specialist_Cars__c", "Opt_in_Maserati__c", "Puritalia__c_contact", "Rimac__c_contact", "Opt_in_Rolls_Royce__c", "Unsubscribed" ], minChecked: 1, maxChecked: Infinity, minMessage: “You must check at least one box in each group!” }, { fieldNames: ["selectDeselectContent", "Opt_in_Accessories__c", "Opt_in_Events__c", "Opt_in_MOT_Reminders__c", "Opt_in_News__c", "Opt_in_Offers__c", "Opt_in_Parts__c", "Opt_in_Sales__c", "Opt_in_Service__c", "Opt_in_Service_Reminders__c", "Opt_in_Warranty_Reminders__c", "Unsubscribed" ], minChecked: 1, maxChecked: Infinity, minMessage: “You must check at least one box in each group!” }, { fieldNames: ["selectDeselectChannels", "Opt_in_Email__c", "Opt_in_Mail__c", "Opt_in_Phone__c", "Opt_in_SMS__c", "Unsubscribed" ], minChecked: 1, maxChecked: Infinity, minMessage: "You must check at least one box in each group!" } ];   ... View more

@SanfordWhiteman can you elaborate on the solution you propose? Well, the simplest way (without even any custom JS or CSS) is to have a String field Business Unit that's a Hidden field on the form, Auto-Filled from a query param. Then use Visibility Rules to show only the Business Unit-specific unsubscribe. ... View more

You can't compare 2 fields in that way. You must use a webhook. ... View more

Add the system Email field to the form as a Hidden field with Pre-Fill enabled. ... View more

What's an actual (p)URL so I can look at it? ... View more

Are you attempting to change the Email Address of the existing lead by using a different value on the form? ... View more

(9) has incorrect info. The click tracking server does not set the Munchkin tracking cookie. This is solely done by the Munchkin JS library. It's possible to have a Clicked Email recorded with no Munchkin cookie at all on the destination domain; it's also possible to have a Clicked Email and an anonymous (unassociated) cookie; and it's possible to have an untracked link and still end up with an associated cookie. Cookies and click tracking are typically found together, but are *not* in fact dependent on one another. ... View more

Also, next time pls post to the Products space, this isn't the correct space for community support questions. ... View more

Velocity 1.7, Tools 2.0, Java 6. ... View more

As I said on your other thread, the inner attribute of a Filled Out Form activity reflects the processed POST payload. It is stored as a serialized PHP object, not as a JSON object. Your app needs to know how to deserialize it.   Presumably your integration app is broken and can't handle the nesting of CSV, JSON, and PHP. That's not a problem with the data, it's a problem with the app. Any modern language can handle this kind of data. ... View more

You're still in the wrong space, as I said on the other thread this should be in Products. "University" is the wrong area for peer-to-peer support. ... View more

FWIW – I don’t think it’s a problem, as long as it’s proven to be manageable and everyone is on the same page. There’s only so much you can do with a single image, and since you can’t A/B test mobile vs. desktop with separate emails, this is the closest you’ve got. ... View more

Your subject line seems at odds with the actual question.   If you must create a person in CRM (via an intermediate app), and you also must create a person directly in Marketo before that person in the CRM has synced over, then there's no game you can play with query params/UTMs to solve for that.   It's clearly at odds with the Marketo-CRM sync model, which is that one (and only one) side creates the person, the other side receives the new person request, always in a predictable order.   The best practice is to ensure the person flows in a predictable, error-free way from one side or the other.  Since you say there's critical data that's only present in the UTMs, and those are currently dropped in the app-to-CRM leg, then the natural flow would be to create the person in Marketo, sync to CRM, then have the CRM sync to the app.    If you absolutely can't make such a change, then you need a lead auto-merge solution, something like RingLead or homegrown code called using a Marketo webhook perhaps.         ... View more