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.

Sign up for GitHub

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

Adding doc/diagram around fxa to ctms integration #266

Merged
merged 1 commit into from
Oct 12, 2021
Merged

Adding doc/diagram around fxa to ctms integration #266

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions adrs/madr-fxa-ctms.md
View file
Open in desktop
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.
Loading