DynamoDB Tables

Key schema PK / SK; entities share the table and are told apart by their SK prefix and the db_type attribute. GSI1–GSI5 exist with KEYS_ONLY projection; GSI1 and GSI2 are used. Every write carries an event_type attribute that the kinesis-feeder forwards as the Kinesis event type for USER and MEMBERSHIP records — see Users stream.

Shared with other FloatMe systems; no environment prefix. Region from USR_LEGACY_DYNAMO_REGION / LEGACY_DYNAMO_REGION.

PK = FLOATMETRIC#<user_id> (or ANONFLOATMETRIC#<install_id> when no user id), SK = EVENTTIME#<time_of_event>#<event_name>; attributes user_id, install_id, event_name, app_version, app_build_number, time_of_event, time_of_event_storage, metric_properties (JSON string), ttl (2 days). Written by the floatmetrics Lambda from {env}-floatmetrics-queue; events missing an id, name, version, build or time are dropped with a warning.

Source: pkg/repository/floatmetrics.go, pkg/floatmetrics/floatmetrics.go

One item per settlement claimant: fmsdk’s user.SettlementParticipant, shared with the Subscription Service. Defined in the infrastructure repo with no stream, so the participant list never reaches the data lake. Same region and client as the users table; name from USR_SETTLEMENT_DYNAMO_TABLE.

Attributes: db_type (SETTLEMENT_PARTICIPANT), claimant_id, user_id, email, name, phone_number, street_address, city, state, postal_code, needs_manual_review, review_user_ids, started_at, reviewed_by, reviewed_at, cancelled_at, forfeited_at. Each GSI SK is the item’s PK.

ImportSettlementParticipant writes one item per claimant; a claimant already in the table is returned as stored, not written again. An account with the list email sets user_id, and starts the waiver (started_at now, to the hour) when the account is a current subscriber: ACTIVE with a membership that is not cancelled. For a started participant, import then calls the Subscription Service’s ApplySettlementWaiver with the period’s ends_at, which cancels the user’s past-due cycles and prices their upcoming SCHEDULED and PAUSED cycles inside the period at 0.00. It is called also when the claimant was already imported, so a rerun retries it. A transport error, 409 (billing lock held), 429 or 5xx is retried with fmsdk backoff (4 attempts over about 4.5s); any other answer is final. A failure after that is logged and the import still succeeds. Anyone else starts it by reactivating. Otherwise an account with the phone number sets needs_manual_review and lists every matching account in review_user_ids, for a person to confirm the match on name and phone; user_id stays unset until then.

Activation (ActivateUser, ActivatePrequalify) matches a new member before their subscription is activated and, for a participant whose waiver has started, is not forfeited and has not ended, sends the settlement waiver (program and ends_at) with the activation, so the Subscription Service writes their first cycle at 0.00. An account already linked to a participant (one waiver per person) is left alone once that waiver has started or been forfeited; one linked at import before it was a member enrolls now, the same as an email match. Otherwise the first participant with the account’s email and no user_id gets the account’s user_id, its waiver starts (started_at now), and its review flag is cleared. After the enrollment deadline (end of January 4, 2027, US Eastern) that participant is instead unlinked and marked needs_manual_review with the account in review_user_ids, for a person to decide whether it is a cure. Failing that, the first unlinked participant with the account’s phone number gets needs_manual_review and the account added to review_user_ids.

ListSettlementReviews returns the participants with needs_manual_review (GSI4). ReviewSettlementParticipant records a person’s decision, with reviewed_by and reviewed_at, and clears the flag and review_user_ids either way. Approving sets user_id to one of the review_user_ids (an account already linked to another participant is refused), and for a current subscriber starts the waiver, now or at the cure’s attempt_at, and calls ApplySettlementWaiver; anyone else starts it by reactivating. Dismissing leaves the participant unmatched.

The subscriptions Lambda records a participant’s membership ending: on cancel-successful or account-closed for a user matched to a participant, it sets cancelled_at, and on or after the enrollment deadline also forfeited_at, once. A forfeited participant no longer has a waiver: reactivation and activation skip them (falling back to a win-back offer), so a rejoin is billed at the standard rate. A cancellation before the deadline keeps the waiver for when they rejoin.

Source: pkg/repository/settlement.go, pkg/api/settlement.go