Create a "Buying Timeframe" field

Anonymous
Not applicable
I want to create field that asks the user to specify when they intend to buy with the options being: Now, 1-3 months, 3-6 months or 6 months or more.

I was wondering what a suitable data type would be for this and if there was a way to use it as a filter to follow them up in the future specified timeframe. For example, If "3-6 months" Then, check "Buying Timeframe" is (Today - 3 months). I am thinking the Stored Value of "3-6 months" needs to be (Today's date + 3 months) so I can use filters like "in the past" or "in timeframe." Is this doable? Any suggestions?

Additionally, it will be used to personalise the confirmation page/email with a relevant response. This is pretty easy and can set as part of the form creation. For example,
If "Now" Then, display "...someone will contact you shortly...
If "3-6 months" Then, display "...while you're waiting... check out our..."

Cheers,
Ersel
Tags (1)
5 REPLIES 5
Anonymous
Not applicable
Just an update, I ended up creating a few fields related Buying Timeframe for anyone interested...

Initially, I capture the user input from a web form (E.g. within 6 months = 6, within 3 months = 3, Now = -1) and I set the following fields:
- Buying Timeframe Initial (type Score, user input from web form)
- Buying Timeframe Initial Date (type Datetime, {{system.datetime}})

In the same program, I added a Wait 1 month and update the fields below to initialise the monthly countdown:
Buying Timeframe Updated (Buying Timeframe Initial - 1)
Buying Timeframe Updated Date ({{system.datetime}})

In another program, I monitor changed to Buying Timeframe Updated and Wait 1 month to continue the monthly countdown. This program basically loops every month to set:
Buying Timeframe Updated (Buying Timeframe Updated - 1)
Buying Timeframe Updated Date ({{system.datetime}})


Anonymous
Not applicable
Sorry, just saw that you aren't using SFDC...
Anonymous
Not applicable
Ersel, there was a session on the Summit about workflows in SFDC that hit on just this. I know it's outside of Marketo, but it might work for you. When the sessions become available, take a look. It's called "Robust Business Logic for Marketo."

 

Anonymous
Not applicable
Thanks Josh, I'll think we'll go with the String type option as we are not using SFDC.

Just a thought... What if we created a Date type, displayed the options as a string in a dropdownlist but stored the values as dates? Is this possible?

Display Value: Now | Stored Value: [current date/time]
Display Value: 1-3 months | Stored Value: [current date/time + 1 month]
Display Value: 3-6 months | Stored Value: [current date/time + 3 months]
Display Value: 6 months or more | Stored Value: [current date/time + 6 months]

In the Advanced Editor for Values of a Select Type field, it mentions:
Cut/Past a list of values. Use | to define server values. I wonder what "server values" are?
Josh_Hill13
Level 10 - Champion Alumni
Use Type String if just in Marketo. Your FORM or Upload lists will have to match the picklist values you outlined above.

You cannot use Date Operators on a String field, only a Date field.

So this depends a bit - if you create the field in SFDC first (recommended), then the Type is Picklist and you insert the values. Marketo will pick this up automatically.