I am trying to set up a form for a webinar with a field for the viewer to enter the number of people watching. Does anybody know how I can track this field/number?
If I understand well, you want to know on a webinar program how people attended?
That is surely not a lead information and therefore cannot be entered with a Marketo form.
You may try to use the API to enter it as a token in the program. But it will take the capability to develop a form that then post the info in the right program, in Marketo.
Yes, and we can track single users who access the webinar by filling out the form, but in instances where multiple people are watching on 1 screen, we want to ask on the form how many people are watching.
Since number of people attending isn't lead information, as you mentioned, I'm not entirely sure how to capture this information.
If I REALLY wanted to, couldn't I create a custom lead field "number of attendees" that gets populated on the form fill out, then add that number for all the people that attended? Since that field would only be useful for one program, I can just delete it when the webinar is over. This probably isn't the best solution, but do you think it would work?
Yes this would work, as long as people do enter the field and do write the truth
You may like this idea, which is about having program level fields that could be filled out in forms:
Have extended Marketo Program member fields and use them to full power (with or without SFDC campaign member field sync)
You can't actually delete fields, you can only hide them. That might be fine in this case, but over time it becomes unmanageable. Definitely use the prefix "Temporary" or suchlike when naming a field that you know is destined to be hidden.
If you mean you want to add all the values of that field together for all members of the program, sure. In Excel....
Do you think it would make too much of a mess to create a field that would only be useful for one program?
And yes, I meant add them in Excel. I should have specified.
If it's important to report on, then you should do it. I just wouldn't make a habit of it but instead plan for a more robust solution later. For example, you can have a single field that stores the number of people who attended a sequence of webinars (connecting under the same lead record) but this requires development. There's also the fact as Greg said that this is an honor system thing. If somebody says 2 people watched, I'll definitely believe it was > 1, but it could've ended up being 3 or more.
Retrieving data ...