Acquisition Program Name and Date Not Automatically Set

[Sean_Hardaker]

Hi

When a new lead is acquired via one of our programs in Marketo such as a form fill-out for gated content, the system is not automatically setting Acquisition Program Name and Date and is leaving them blank each time.

The forms are Marketo forms embedded onto our webpage.

Can anyone shed some light on this?

thanks

Sean

[Sean_Richards]

Hi Dan, I assume you would not need to CDV flow on AP for an Email program, since you already have acquired the person?, but you would still leave the other flows to stamp the last program?

In other words, only stamp AP for programs that actually can generate new people. E.g. any program with a form, or typically has people imported (list import programs, events, tradeshows).

Am I right?

[Grégoire_Miche2]

Hi Sean,

better open a new thread to get a quick answer, rather than reopening an old one.

-Greg

[Sean_Richards]

You always get me GM!!

[Anonymous]

This discussion has really helped me a lot here, but it raises another question.  If Acquisition Program is a "system locked down field", as you say, why are we able to Attribute a new value to this field?  I would think the only field we could attribute a new value to would be the Acquisition Program Name, but this screen shot example above leads me to believe we are able attribute a new value to Acquisition Program, but not Acquisition Program Name, so I'mstill a bit confused?  I also believe that both Acquisition Program Name and Acquisition Date would need to be set for those that have not gone through a Marketo Program, i.e. these leads came in through salesforce or a 3rd party form with an API Call.  Love to hear you insight.

Thanks

[Dan_Stevens_]

AP is "locked down", meaning if there is already a value, there is no way to change it.  I know - it's confusing.  So if you're running a smart campaign to test if AP is empty - so that you can backfill them with the proper program names - then you use APN as your conditional field (e.g., "if APN is empty") and populate the value in the actual AP field.

You might want to direct users here to the thread you started the other day: Re: Acquisition Program and Acquisition Program Name

I also came across this post (Setting Acquisition Program Names in Bulk) where Tabitha Adams​ mentioned that she uses program tokens to populate the AP value.  When we used tokens, this didn't work - and therefore we always use a hardcoded value.  I may need to do some more testing to see if it's now possible using program tokens (vs. "my" tokens set at the program level).

[Nico_Veltri]

Hi @Dan_Stevens_ and @Grégoire_Miche2  !

For New People Created that DO NOT have an associated Acquisition Program, it appears they will correctly show blanks in the AP and AP Date fields. This however leads to incorrect updates when AP and AP Date conditionally update when blank and skews reporting new names, based on the suggested flow steps.  

Have you ever recommended or heard of users who fill AP with default values to prevent from this conflict?  I'd considered potentially backfilling all blank AP Dates = Create At, and AP = No Acquisition Program.  

[Matjaž_Jaušove2]

Actually, there is a way to change the AP even after it has been assigned. You have to just remove the person  (Change Status -> Not in Program) from the assigned program and the AP value will become empty.

[Josh_Hill13]

Marketo does not automatically do this all the time.

1. Did you use a campaign to stamp the lead as a Member or Success?
2. Best to ensure that you run CDV at the correct times like Acquisition Program IS EMPTY, set to this Program and then set Acquisition Date={{system.dateTime}}.

[Grégoire_Miche2]

Hi Sean,

This is the expetced behavior: no acquisition credit will given for a Marketo form on a non Marketo page.  you will have to set it up with a smart campaign: trigger: fills out form, flow steps: 2 change data value:

-Greg

[Marie_Ligier]

Just learned that marketo forms embedded into non-marketo pages will not update the acquisition program ! Good to know and that explains a lot

Thanks Grégoire !