-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #266 from mozilla-it/adr-1
Adding doc/diagram around fxa to ctms integration
- Loading branch information
Showing
2 changed files
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Stripe Subscription Event Data Empowering Email User Journeys | ||
|
||
* Status: proposed | ||
* Deciders: Bryan Sieber, John Whitlock, Ben Bangert, Jon Buckley, (Benson Wong, Stephen Hood) | ||
* Date: September 30, 2021 | ||
|
||
Technical Story: [design and document approach for marketing | https://mozilla-hub.atlassian.net/jira/software/c/projects/CTMS/boards/364?modal=detail&selectedIssue=CTMS-73] | ||
|
||
## Context and Problem Statement | ||
|
||
Marketing wants to be able to differentiate customers based on their subscription information to empower marketing campaigns. | ||
|
||
## Decision Drivers | ||
|
||
* Design sustainable system for longterm data-health | ||
* FxA source of Truth | ||
* Stripe rate limits | ||
|
||
|
||
## Considered Options | ||
|
||
* Cloud Function triggered through Firestore | ||
* Background process in CTMS | ||
* New temporary service | ||
|
||
## Decision Outcome | ||
|
||
Chosen option: " Cloud Function triggered through Firestore", because the event snapshots can be captured and published to a Pub/Sub, upon which they can be pushed to CTMS with a JWT. We believe this is a more sustainable option. |
Oops, something went wrong.