Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post Launch: Add a "source" field to CTMS contact #255

Open
data-sync-user opened this issue Sep 8, 2021 · 7 comments
Open

Post Launch: Add a "source" field to CTMS contact #255

data-sync-user opened this issue Sep 8, 2021 · 7 comments

Comments

@data-sync-user
Copy link

data-sync-user commented Sep 8, 2021

With SFDC/SFMC, we previously had a "source" field on the contact itself, indicating the source of their very first email subscription. Currently in CTMS, we only track source on a per-newsletter basis. The Foundation needs to know the contact's original source because it tells them how this contact entered the funnel. Potential tasks here include:

  • Add a column to the email table in CTMS and update CTMS logic to populate it moving forward
  • Back-populate this field in CTMS using historical data from BQ
  • Update the API to include this information explicitly
  • Update Cinchy to get this data from CTMS

┆Issue is synchronized with this Jira Story

@data-sync-user
Copy link
Author

➤ Sarah Chu commented:

The work involves: Brian --> Bryan --> Chris

Dependency for Marketing team in addition to MoFo

This work potentially needs to be split up into additional tasks after discussion from BBC

@data-sync-user
Copy link
Author

➤ Sarah Chu commented:

  • This data is needed in SFNP(Target email campaigns), Acoustic & Cinchy
    • Make explicit field in CMTS (Chris to discuss with other devs)

Potential Impact:

  • The longer we wait, there is a data gap.
  • Steph verified, not needed for newsletter source for upcoming fundraising campaign

@data-sync-user
Copy link
Author

➤ Sarah Chu commented:

This sprint: change to add columns to CTMS and API

Next:

  • Bryan to update to Acoustic
  • Chris - Backfill of historical data and hand over to Brian

@data-sync-user
Copy link
Author

➤ Sarah Chu commented:

Issue split into:

OSS442|Add a "source"field to CTMS Update AcousticOSS443|Add a "source"field to CTMS Backfill of historical data

@data-sync-user
Copy link
Author

➤ Sarah Chu commented:

This sprint add source column, engineers to meet to discuss this before starting on OSS-442 & OSS-443

@data-sync-user
Copy link
Author

➤ Sarah Chu commented:

Brian Stack Did we get close with this item?

@grahamalama
Copy link
Contributor

TODO: determine if this is still something that's wanted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants