feat: UTM digest tracking + AE last-viewed roster#51
Closed
m1lestones wants to merge 1 commit into
Closed
Conversation
DigestTracker now captures ae_id from URL params (?utm_source=digest&ae_id=xxx)
instead of using a hardcoded ID. Views stored in Supabase digest_views table
and forwarded to backend endpoint. DigestRoster shows Danielle each AE's
last digest open time on the home page admin view.
Requires Joel to:
1. CREATE TABLE digest_views (ae_id uuid PRIMARY KEY, digest_id text, viewed_at timestamptz DEFAULT now());
2. Append ?utm_source=digest&digest_id={id}&ae_id={ae_id} to all digest links
Collaborator
Author
|
Closing — merged into feat/mobile-polish instead to keep everything together before Demo Day. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Closes the loop on whether AEs are actually opening the Monday digest.
ae_idfrom URL params instead of hardcoding Danielle's ID. Fires on?utm_source=digest&ae_id=<uuid>&digest_id=<uuid>./api/digest-view— new Next.js route. Stores views in Supabasedigest_viewstable (upsert byae_id) and also forwards to your/api/v1/digest-viewsendpoint silently.What Joel needs to do
1. Run this in Supabase:
2. In
format_weekly_digest(), append UTM params to every dashboard link:That's it — frontend handles everything else. The Supabase write works independently of your endpoint, so this is safe to merge before your digest endpoint is live.
No dependencies on feat/mobile-polish
This PR is based off
mainand can be merged in any order.🤖 Generated with Claude Code