Kristen_Malkov1

Reachforce is your best option for this. They match company data and have a database that's updated quarterly. They're the best option for company data matching.

Have you tried creating a batch campaign that runs nightly to un-mark the email suspended addresses? You could also export them, delete them from the instance, then re-import them and then that would reset their suspended status.

I'd recommend using a hidden field to update the lead source or a flow step in a smart campaign (If filled out form, then lead source equals _____). I don't recommend having Marketo create a new lead each time someone fills out the form because you will essentially be ensuring duplicates within your...

Always defer to your SFDC admin. If they don't want to delete them out (and you're cool with losing history in Marketo, which you should be!), then go ahead and just delete them in Marketo.

The field organizer can also help you with troubleshooting what fields are mapped where, and also allow you to group fields when pulling (non RCA) reports. If there's a group of fields that you want Marketo to look at as a group (say product usage?) you can group fields there as well.

Instead of creating a variety of static lists, why don't you just create a custom field, and when the list is updated, the custom field is populated (or just a checkbox that's checked), then when you create your segmentations, they can be based off the field.In my experience, the 'added to list' is ...

I would just set the time earlier in the file. Reminder times prior to events are set by the user themselves; you can't set the time before that they're reminded but you can just change the start time for the event.

Hi Rachel,A work around (although imperfect and not as good of a solution as Cvent) would be to create a landing page and form that isn't cookied and submit people to the form as they visit your booth. You could then match this list that is created in Marketo against the registration list. If you ma...

If you look at the admin section of your instance under "Muchkin", you'll have the option to enable/disable ignoring cookies. Based on what you wrote above, it seems as though this might be the best course of action for this instance.

As an aside, if you use progression statuses, that data is never archived after 90 days...it's there forever! Yay!