First Conversion Tracking | Community
Skip to main content
May 31, 2018
Solved

First Conversion Tracking

  • May 31, 2018
  • 1 reply
  • 3964 views

I recently took over the administration of our Marketo Account and have a few questions regarding conversion tracking. While I used Marketo extensively throughout my career, my expertise lies with Hubspot's automation system, which provided the following read-only fields:

  • First Conversion Date: Hubspot defined this as the date a lead first filled out a form
  • First Conversion Event: Using a list of pre-defined "event" values defined by an administrator (i.e. webinar registration, content download, demo request, etc), Hubspot will record the type of event corresponding to a lead's first conversion
  • First Conversion Campaign: This refers to the first campaign (equivalent to a Marketo program) in which a lead converted. Though Marketo has an "Acquisition Program", this field has been largely misused by past users.

*Please note: Hubspot defines "conversion" as any form fill other than unsubscribe. However, I personally would like to customize what a "conversion" means in my flows

For all future incoming leads, I know how I can record all of this information (i.e. if user fills out form, AND # of form fills = 1, update "First Conversion Date" to {{system.date}}), but I am having trouble figuring out how how to do this for EXISTING LEADS. Specifically, I am looking to:

  • Record "First Conversion Date" for all existing leads in our database
  • Input "First Conversion Event" values to all existing leads based on a set of pre-defined values
  • Delete all existing inputs for "Acquisition Program" and update with the actual name of the first program "Success" (if program is deleted, it can just say "Deleted Program")

Appreciate any help that you guys can offer. (I'm hoping you guys will turn me into a Marketo genius)

Thank you


Update: I realized "# of Form Fills" was another Hubspot thing and not a Marketo field... I now also need to figure out a way to trigger this for all incoming leads as well.

Message was edited by: Christina Wu

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

That's unfortunate, this information has always been very valuable for my reporting. I also realized I was wrong when I said I could track "# of form fields"

You mean "# of form fillouts," right?

While this counter is not automatically available on a lead, you can easily add a score field to increment +1 on every fillout.

As for the backfill, it shouldn't be especially hard for a developer because it's a one-time thing (much of the agony with any API integration comes from OAuth token caching, job scheduling, storing incremental checkpoints -- things you don't have to worry about with one-off downloads).

1 reply

SanfordWhiteman
Level 10
May 31, 2018
For all future incoming leads, I know how I can record all of this information (i.e. if user fills out form, AND # of form fills = 1, update "First Conversion Date" to {{system.date}}), but I am having trouble figuring out how how to do this for EXISTING LEADS. Specifically, I am looking to:
  • Record "First Conversion Date" for all existing leads in our database
  • Input "First Conversion Event" values to all existing leads based on a set of pre-defined values
  • Delete all existing inputs for "Acquisition Program" and update with the actual name of the first program "Success" (if program is deleted, it can just say "Deleted Program")

You can only perform this backfill by doing an Activity Log export using the API, then reupdating the leads.

It's not possible to extract characteristics like the timestamp of the first form fill using a Smart List.

May 31, 2018

That's unfortunate, this information has always been very valuable for my reporting. I also realized I was wrong when I said I could track "# of form fields" -- turns out that was another Hubspot thing...

Thank you Sanford.

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
May 31, 2018

That's unfortunate, this information has always been very valuable for my reporting. I also realized I was wrong when I said I could track "# of form fields"

You mean "# of form fillouts," right?

While this counter is not automatically available on a lead, you can easily add a score field to increment +1 on every fillout.

As for the backfill, it shouldn't be especially hard for a developer because it's a one-time thing (much of the agony with any API integration comes from OAuth token caching, job scheduling, storing incremental checkpoints -- things you don't have to worry about with one-off downloads).