Set up a Hidden Field

[Anonymous]

Hi All,

I've a banner on a third party website, clicking on which takes someone to our website, which has forms - filling on the forms generates alerts that goes to our inbound team.

The Question is -  I need to distinguish between the alerts that gets generated when Lead directly fills out the forms on our website vs when they have been referred form that third party site on to ours and fill out form.

(The link from the third party website to ours is UTM tagged with utm_Source=CA%10 and utm_medium=CB) But the utm tagged url stays only if the lead has landed on it as so as they start navigating on our website the url goes n its just our website url

Could anyone help me set up the hidden field that I can put as a token on my alert email? That tells the sales team the referrer URL was the "UTM tagged URL" and set a default value as "Source = Test Lead".

Thanks,

[David_Jackman1]

Haha, well thank you. We'll see how it all pans out!

[Anonymous]

On the first interaction of the lead (visitor) with your website, you can check for the query string. If the query string is present, you can then just continue appending it to all the URLs that lead (visitor) is browsing through.

I wanted similar option in different scenario and I did that. With little server side coding that is possible.
Hope this will give you at least some direction.

[Anonymous]

Thanks Kundan, could you please share the how did you do append the query string to all the URL's, like the code and where have you put that code

[SanfordWhiteman]

This is not the move, Addy. Yanir's cookie forwarder is simpler and less prone to error. Appending data to all your links is not necessary *unless* they are exit links (leaving the parent domain and thus crossing the cookie barrier). Dynamically created links are particularly hard to manage in this way.

[David_Jackman1]

Hey Sanford. Thanks for your input on this topic. I have a similar need to track attribution, organic visits vs. digital/social ad sources, but am I right in thinking that if we cookie them, and one of the leads happens to be in/belong to an EU country, and they end up not double-opting in, that we risk gdpr compliance issues?

[SanfordWhiteman]

Yes, if you don't get opt-in before setting cookies, if the transaction is subject to a jurisdiction in which that matters, then... it matters.

[David_Jackman1]

Got it. Thank you for confirming! On a side note, I wonder if Adobe's acquisition of Marketo might end up providing a long term solution for this. We use Adobe Analytics right now to track traffic, and have been wanting to integrate that into our instance. I also recently discovered Put It Forward, available via Adobe Exchange that promises to easily map the systems. I would have to research more on how this fusion of tracking would speak to gdpr, and I imagine this is something Marketo is probably also looking into.

[SanfordWhiteman]

I am impressed by your enthusiasm, even if I don't share it.

[Anonymous]

Thanks San, it makes sense.. I could not see the coding by Yanir.. as git-hub is blocked, I'll get IT to unblock it and have a look at Yanir code so where  will the codes be added do I need to create fields in Marketo?

[SanfordWhiteman]

You'll create hidden fields as you normally would, then because the values are being preserved in individual cookies you'll set the AutoFill source to each cookie name.

[SanfordWhiteman]

You don't need server-side coding to do what you describe. It can (and on Marketo pages, must) be done in JS.

[Yanir_Calisar2]

Thanks Sanford Whiteman​

Hey Addy Sharma​

Check out this Javascript that captures both first touch and last touch UTM params and stores them in the top level domain ( .yourdomain.com):

UTM Capturing and Storing in Cookies

[Anonymous]

[Anonymous]

[Anonymous]

I get the above, accessing the link

[Yanir_Calisar2]

Strange

Try:

UTM Capturing and Storing in Cookies

[Anonymous]

Thanks Yanir, dont know but it just doesnt open

[Yanir_Calisar2]

Please try the updated link.

If that doesn't work try:

UTM Capturing and Storing in Cookies

[Anonymous]

Hi All,

can anyone please help me with how can I make the UTM tagged URL persistent throughout the session, so that we do not lose the inital source of the user and can set up the hidden field on the form as campaign source and parameter UTM_souce and then use it as a token on my alert email.

I have worked around a workaround by creating a smart campaign that checks if user has visited the page (UTM tagged URL) in the time frame today then change data value campaign source = "CA" and then added the campaign source token on the alert email. I'm not sure if this is the right approach...

Thanks

[SanfordWhiteman]

Like I said above... search LaunchPoint for comprehensive solutions like ConversionPath and a few others. These apps automatically manage the UTM attribution lifecycle (so you don't need to add hidden fields in Form Editor, this is all done for you), including tracking sessions by referrer domain, referrer UTMs, and target UTMs across multiple touches.

Yanir Calisar also recently posted some simple JS to persist UTMs to cookies.