Request a quotation form product field - value overwrites

[Anonymous]

Hello All,

So here's the situation.  A customer completes our Marketo quote form and along with their contact info populates a field with details of the product that they want a quote for.

This value is stored in a field in the database.

If the same customer requests another quotation for a different product this field is over written.

So at the end of the month my how many quote requests report is short, as the customers requesting quotes for more than one product are deduped and only the last product entered into the field is stored.

Im really unsure how best to store this activity and report on all quote forms (including the multiple requests from the same customer).

All help gratefully accepted.

Thanks in advance

Mark

[Anonymous]

Just to add one more thing. It seems the landing page performance report lists all of the quote forms completed.  But you cannot pull a list of who asked for a quote for what.

A filled out form report only lists the unique email addresses that filled out the form.  Not the multiple fill outs.

thanks

[Jenn_DiMaria2]

If you want to keep historic fields, you would actually create two fields: one for the form (let's call this Product_Form) and another to hold the historic data (Product).

When someone submits a form, your flow would then look something like this:

CHANGE DATA VALUE

Attribute: Product

New Value: {{lead.Product_Form}}

For more information about historic fields, check out this post: What's the easiest way to append new comments within the same comments field?

[Pavel_Plachky]

You can add a field called Quote History that will accumulate all quote requests. In a trigger campaign, have a flow step to change data value to set the Quote History to {{lead.Quote}} {{my.linebreak}} {{Lead.Quote History}}

You will not get a report with a list of quotes line by line, but at least you can get a list of leads that requested at least one quote and for each the history of requests.

Good luck,

Pavel

P.S. See Sanford Whiteman's blog entry on the linebreak token {{my.linebreak}}.