Attribution Help: Map old program successes to new programs via API | Community
Skip to main content
Kim_Wieczner
Kim_Wieczner
New Participant
March 20, 2019
Question

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

  • March 20, 2019
  • 2 replies
  • 4700 views

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!

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

2 replies

John_Charleswor
John_Charleswor
New Participant
July 24, 2020

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
Jay_Jiang
New Participant
March 21, 2019

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

SanfordWhiteman
SanfordWhiteman
New Participant
March 21, 2019

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
Jay_Jiang
New Participant
March 21, 2019

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?

Terms & ConditionsAccessibility statement

Loading footer...