docs(plans): AI engagement attribution design doc#612
Draft
arberx wants to merge 1 commit into
Draft
Conversation
Specifies the correlation layer that joins the post-#611 traffic channels (bulk crawl, AI user-fetch, AI referral) with the answer-visibility sweep and GA4 into one per-engine engagement funnel: indexed -> fetched-live -> cited -> referred -> converted. Phase A is a read-side reconciliation endpoint (no schema change); Phase B adds GA4 outcome attribution. Picks up the layer that server-side-ai-traffic-ingestion.md (step 8) and ai-attribution-research.md (steps 2C/2D) gestured at but never specified, and respects their findings (no T0 anchoring, volume floor). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
plans/ai-engagement-attribution.md— design doc only, no code.indexed → fetched-live → cited → referred → converted.GET .../traffic/engagement), no schema change, ~500–700 LOC follow-up.convertednullable from day one).Context
PR #611 made the three traffic channels clean, but nothing joins them — they are five numbers on three or four separate screens. This doc specifies the reconciliation layer that
server-side-ai-traffic-ingestion.md(rollout step 8 — "Intelligence correlations") andai-attribution-research.md(Steps 2C/2D) both gestured at but never specified.It respects the earlier findings rather than re-litigating them: no T0-anchored lift model, the ~3k-sessions/month volume floor for the conversion tail, and Gemini's domain-only citations.
Also records a follow-up surfaced in the #611 review:
report.tsbuildServerActivitydoes not readai_user_fetch_events_hourly, so the report will undercount server activity after migration 64 unless fixed.Status
Draft — open for review of the design before any implementation. Depends on #611 (in review) and #598 (merged).
Test plan
🤖 Generated with Claude Code