Attribution Help: Map old program successes to new programs via API

[Kim_Wieczner]

We are in the process of restructuring our instance to split out a highly used channel into more specific sub-channels for more accurate reporting. We are rebuilding ~250 programs but want to mark all of the successes in the old programs as successes in the new programs with their historic success date. We can export all of the contact records with their success dates in each program via RCE and can easily say what each of their new successes would be in each new program.

For example:

RECORD ID

Old Program Name

Old Program Success Date

New Program Name

New Program Status

Is it possible (perhaps via API), to import these records in mass into the new programs and assign them success with the historic date?

Thanks!

[John_Charleswor]

Hi @Kim_Wieczner, I am going through the same process you outlined in your original post. I've tried populating the PSD with a token hoping that it's been updated, but no success. Were you able to find a solution?

[Jay_Jiang]

As far as I'm aware, the system membership fields related to programs can only be read and are write protected so you can't edit or specify date of success

A workaround would be to create your own custom field or custom object to record it

[Jay_Jiang]

Are you using Salesforce? because there's a lot of posts pointing out it's not possible to change the First Responded Date on the Campaign Member object - which is the equivalent of reached success date under memberships of Marketo programs.

[SanfordWhiteman]

Are you using Salesforce?

Yes, that screenshot is from a SFDC-integrated instance.

[SanfordWhiteman]

The Program Success Date can be changed in a flow. However, the problem is in automation. While the PSD appears to accept a {{lead.token}} -- so you could use a date field and have a trigger campaign run in response to a change to that field -- in my tests, it only works if hard-coded. Which, to put it mildly, doesn't scale.

EDIT: Let me retest this, the token may work but there's another blocker. I did retest and my memory holds.. the token doesn't work for me, only a hard-coded date.

[Jay_Jiang]

There's no such field available in filters or flows called Program Success Date in our instance. Are you sure you're not looking at a custom field?

[SanfordWhiteman]

Not at all, this is a standard flow step.

[Jay_Jiang]

Sanford Whiteman Are you getting the reachedSuccessDate from get leads by program Id? I'm not seeing it even though reachedSuccess = true

as per docs:

[SanfordWhiteman]

Tbh I didn't check the API for reading the info. Kim said she'd be exporting from the UI, so the reading part was taken care of.

I can look at this at some point. Wouldn't be surprised if my findings mirror yours. Do you concur that a {{lead.token}} is not functional in the flow, while a hard-coded date with the same value works?

[Jay_Jiang]

Yes that looks to be the case.

I tried with no luck a {{my.token}} as well in hope of using the trigger smart campaign api with variable token values.

[SanfordWhiteman]

Updated ​ to show it's still not successfully implemented.

Would be nice to hear back from the Kim Wieczner​ too.

[Kim_Wieczner]

Thank you! Yeah that's really too bad about the date token value...that was going to be my backup. We spoke with someone in support who indicated that it could be possible to import members into a program with specified values via API but we haven't yet been able to confirm this...are you familiar with what is possible in this "import via API" concept?

[SanfordWhiteman]

It's not possible via only API, that's what Jay and I were getting at. And the chain of API to flow, which is supposed to work, is unfortunately broken.

[Jay_Jiang]

Honestly did not know that was there, went straight to APIs

[SanfordWhiteman]

I did retest with a Date {{lead.token}} and continue to find that it doesn't work, despite no red squiggly. So it doesn't really suffice.