SOLVED

Re: How do you report on Progressive Profiling?

Go to solution
Anonymous
Not applicable

How do you report on Progressive Profiling?

I want to be able to look at a report that tells me how successful my Progressive Profiling is being, not simply by showing conversions, but seeing which fields are getting filled out when they cycle through, so we can see if certain added fields for repeat contacts are more effective than others.

Is there any way to do this that already exists in current reports, or an easy way to set something up?

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
SanfordWhiteman
Level 10 - Community Moderator

Re: How do you report on Progressive Profiling?

I had no idea where to put anything, and none of the suggestions made sense. So any support help goes to Product? It made it seem like that wouldn't hit many people...

Yeah, Products​​ is actually the most active place on the Community.  I agree that it sounds more like "About Marketo Products" at first. But naming changes are coming, and also some places will be merged so people don't need to make that call.

I should just go back to opening cases for everything.

Well I don't know about that.

Anyway...

I want to be able to look at a report that tells me how successful my Progressive Profiling is being, not simply by showing conversions, but seeing which fields are getting filled out when they cycle through, so we can see if certain added fields for repeat contacts are more effective than others.

By default, forms don't post anything to Marketo that specifically reflects which ProgPro subset was visible at the time of the form fillout.

The ProgPro algorithm (deciding which subset is current, based on currently non-empty fields) runs entirely in the browser, and doesn't get stored in its own field/activity context/metadata. 

On a manual level, you can look at a Filled Out Form record (in the Activity Log) side-by-side with the Form Editor and intuit which fields must have been shown on the form (i.e. save for fields that were added and populated using the JS API, the fields reflected in the Activity were the fields visible to the lead).  But this doesn't get you any kind of reportability unless you're downloading the raw Activity Log, and the form descriptors, via the API to report at this level. (I honestly don't know of anyone who's doing both of these things.)

What you could do, though, is use custom Forms JS to tag each form with an additional field representing which fields were dynamically shown to the lead. Then each time that field -- let's call it Last ProgPro Field Block -- is updated, append the value to a history field, like ProgPro History. Or to get more of a many-to-one scenario, you could add the field block to the query string before submitting the form. Then you could constrain Filled Out Form by which dynamic fields came along with each fillout.

View solution in original post

5 REPLIES 5
SanfordWhiteman
Level 10 - Community Moderator

Re: How do you report on Progressive Profiling?

Please move the question to Products​ (Move link is at the right). This space is for discussing the Champs incentive program, not support.

Anonymous
Not applicable

Re: How do you report on Progressive Profiling?

That would have been nice to know when crafting this. The support is such an awful mess, I had no idea where to put anything, and none of the suggestions made sense.

So any support help goes to Product? It made it seem like that wouldn't hit many people...

I should just go back to opening cases for everything.

Thanks!

SanfordWhiteman
Level 10 - Community Moderator

Re: How do you report on Progressive Profiling?

Products is the placr for peer-to-peer support. I'll answer your question in a bit.

SanfordWhiteman
Level 10 - Community Moderator

Re: How do you report on Progressive Profiling?

I had no idea where to put anything, and none of the suggestions made sense. So any support help goes to Product? It made it seem like that wouldn't hit many people...

Yeah, Products​​ is actually the most active place on the Community.  I agree that it sounds more like "About Marketo Products" at first. But naming changes are coming, and also some places will be merged so people don't need to make that call.

I should just go back to opening cases for everything.

Well I don't know about that.

Anyway...

I want to be able to look at a report that tells me how successful my Progressive Profiling is being, not simply by showing conversions, but seeing which fields are getting filled out when they cycle through, so we can see if certain added fields for repeat contacts are more effective than others.

By default, forms don't post anything to Marketo that specifically reflects which ProgPro subset was visible at the time of the form fillout.

The ProgPro algorithm (deciding which subset is current, based on currently non-empty fields) runs entirely in the browser, and doesn't get stored in its own field/activity context/metadata. 

On a manual level, you can look at a Filled Out Form record (in the Activity Log) side-by-side with the Form Editor and intuit which fields must have been shown on the form (i.e. save for fields that were added and populated using the JS API, the fields reflected in the Activity were the fields visible to the lead).  But this doesn't get you any kind of reportability unless you're downloading the raw Activity Log, and the form descriptors, via the API to report at this level. (I honestly don't know of anyone who's doing both of these things.)

What you could do, though, is use custom Forms JS to tag each form with an additional field representing which fields were dynamically shown to the lead. Then each time that field -- let's call it Last ProgPro Field Block -- is updated, append the value to a history field, like ProgPro History. Or to get more of a many-to-one scenario, you could add the field block to the query string before submitting the form. Then you could constrain Filled Out Form by which dynamic fields came along with each fillout.

Anonymous
Not applicable

Re: How do you report on Progressive Profiling?

Thank you so much! That is very helpful, though maybe more trouble than we'll want to go into to get this data. Still, if we decide to move forward, this makes sense.

Thanks again!