Embedded forms and hidden fields

[Anonymous]

Will an embedded form 2.0 with hidden fields still accept data via URL parameters? 

[Anonymous]

Do I have to use utm parameters or can I name my own parameters?

[SanfordWhiteman]

There is no need to use standard UTM parameters (which are Google-linked, even if people treat them as generic).

[Iryna_Zhuravel4]

Hi Noar, 
yes, your assumptions about my method are all correct. The parent program works as the aqusition program; the thing is we often use same ad channels for several campaigns, so if we used utm source based programs as aqusiotion programs, it would end up very misleading. 

Parent-child program method we use allows to see a total number of leads acquired by that particular form and I can also track performance of each ad channel by the number of leads in each child program. 

As for utm_campaign name - I get this from our GA guys, they also track channels performance in GA using utm links and have their own flow, usually campaign name would include the name of the product and time when it runs, roughly for a product "XYZ" we are promoting in Q4 the campaign name would be - XYZQ42014

[Anonymous]

By the way. What do most people put for utm_campaign? Would it be the name of the parent program (like the whitepaper name, or "ASSET" as some people would call it) or is it something else? 

[Anonymous]

Iryna thanks for the details here!! 

If I can dig deeper into your method: You have a PARENT program for a whitepaper, for example. Then you create a program with child tag (to the parent campaign) for each utm_source (advertising channel, I imagine). Then within the parent campaign (?) you have one triggered campaign looking at the utm_source field submission and changing the status within the correct child program. Is this correct? My question is this: If there is one form within the parent campaign, are you OK with the acquisition program being this parent campaign vs. the source (child) campaign? I always wondered about this. 

 

[Iryna_Zhuravel4]

We usually capture the following parameters:
UTM_source
UTM_medium
UTM_campaign

and naturally use fields with the same name for them

Sample setting for capturing utm_source:
1. Create a hidden UTM_source field in the form
2. Click Autofill: Edit
- Default value - No source
- in "Get value from" choose "URL parameter"
- in parameter name put "utm_source"

We create a parent program for each embedded form, a child campaign for each utm_source, and one trigger campaign that adds people to a corresponding child campaign depending on which utm source they came from.

Also if there is no utm_source, but "original search phrase is not empty" -> change utm_source to "Unpaid search"

[Anonymous]

Thanks for the responses, this helps save some time in testing.

[Anonymous · Accepted solution]

Yes it works, i created a hidden field in the form and passed a utm paramter via url "utm_campaign=adwords".  Also because i did not want the existing fields in Marketo to get affected i had created a custom field intially for testing. 

[Anonymous]

I have used jquery to populate hidden fields and it works pretty well.

[Iryna_Zhuravel4]

yes, it should, we embed forms quite often. Just make sure to specify the url parameter you want the form to capture.