Parse parameters from query string

[Tamir_Belzer_TB]

Hi, what is the most effective way to parse custom parameters from a URL into custom fields in Marketo? preferably from within Marketo 

[SanfordWhiteman]

Very simple with a webhook-compatible service, impossible without.

[Jo_Pitts1]

@Tamir_Belzer_TB , in what context?  If it's a form fill then you can do it easily using hidden fields, and Marketo's inbuilt functionality.

Anything else, then I agree with @SanfordWhiteman 

Cheers

Jo

[SanfordWhiteman]

Yeah, I assumed this was referring to a URL already stored in a Marketo field, not one that could be parsed on the client side.

[Tamir_Belzer_TB]

Hi, thanks. I was referring to the query parameters that is on the form fill out activity. Also, do you know if there's a way BTW to capture these parameters on a custom field? 

[SanfordWhiteman]

On the server side? If you trigger on Fill Out Form you can pass the whole {{trigger.referrer}} to a webhook and write back query params to individual custom fields. It's easy but again not something you can do in a native flow step.

[Tamir_Belzer_TB · Accepted solution]

Thanks. We're using Workato to parse the params from a custom Marketo field. This is working, the only challenge is getting the full URL with the params to a custom field in Marketo. I'll try the trigger.referrer but from several tests I did it didn't copy the whole URL with the params. Not sure if it's something I did wrong or this is how Marketo works. 

[SanfordWhiteman · Accepted solution]

@Tamir_Belzer_TB apologies for the delay — and for being too optimistic about the {{trigger.referrer}} value!

It looks like not only is {{trigger.referrer}} empty here, {{trigger.web page}} has a major bug that makes it unusable as well. (Otherwise, we’d still be able to tweak the _mktoReferrer before submit to include the query string in the hash, which we used to be able to do back in the day.)

Looking at our production setup, we haven’t been relying on any {{trigger.tokens}}. What we’re actually doing is fetching the Filled Out Form activity from the Activity Log after triggering on Fills Out Form. That is, ignoring the {{trigger}} context and instead looking up the {{lead.id}}’s ActLog. We set the ActLog window to last 15 minutes and it hasn’t missed anything, while being a near-instant lookup.