Story 064: UC-08 Gharart.com: Personalization and Destination Trust (edge case 4/4)
Campaign Trigger & Audience
Activate personalization and destination trust when Gharart.com schedules an audience-specific campaign burst.
Marketer Actions (UI + automation)
- Create an audience segment with clear campaign goal tags.
- Configure destination rules and preview each segment branch.
- Enable automated QA checks before go-live.
- Schedule launch window and monitor live KPI dashboard.
Expected Outcome
Gharart.com delivers trusted personalized destinations that improve campaign conversion quality.
KPI Watchlist
- guardrail_trigger_rate
- fallback_resolution_minutes
- false_positive_guardrail_rate
Tracking Setup (events, attribution tags)
- Track uc-08.configure-personalization.edge_condition_detected
- Track uc-08.configure-personalization.guardrail_applied
- Track uc-08.configure-personalization.fallback_selected
- Attach attribution tags: campaign_id, audience_id, destination_variant.
Failure Signals + Recovery
- Signal: destination domain pending verification blocks routing.
- Recovery: pause affected segment and re-run destination preview.
Rollback/Support Handoff
- Rollback: execute revert_rule.
- Support handoff: include story ID, segment ID, and event timeline.
Acceptance Checklist
- Audience segmentation reviewed.
- Destination mapping validated.
- Tracking and attribution tags verified.
- Rollback owner confirmed.
Gitagent Grounding Context
- Description: Autonomous external ChatGPT/OpenAI OAuth MCP agent for handle-scoped 10x.in workflows, connector recovery, and delegated control-plane execution
- Autonomous external ChatGPT/OpenAI OAuth MCP agent for handle-scoped 10x.in workflows, connector recovery, and delegated control-plane execution
- I am the development agent for 10x.in — a production-grade, multi-tenant link shortening and creator economy platform deployed on AWS. I understand the full stack from CDK infrastructure to CloudFront edge routing, from DynamoDB data modeling to React frontends, and from MCP tool orchestration to Temporal workflows.
- - API: Monolithic Lambda handler with 277 method-routes across handle-scoped, public, admin, and internal paths
- Key domain entities: Handles, Links, Visitors, Campaigns, Pages, Profiles, PersonalizationRules, ChainRules, TrackingTemplates, Skills, AgentRuns.
- - Deployment reliability: Follow the established deployment workflow; use IAM wrappers
- - Follow the skill-based workflow: match task to skill, read the skill file, follow the checklist
- - Use scoped commit messages:
feat:,fix:,docs:,chore: - |
/v2/handles/{handle}/*| JWT | Handle-scoped operations | - | Commerce & Growth | 8 | PersonalizationRules, Campaigns, Pages, Visitors, BillingEvents |
- ## Deployment Workflow
- ## Known Failure Patterns
- Map external end-user prompts to the canonical workflow, tool family, scope set, and rollback path.
- Use this skill when an external ChatGPT/OpenAI prompt needs to be converted into one of the canonical handle workflows.
- workflow: configure-personalization
- required_scopes: mcp.connect, tracking.personalization.read, tracking.personalization.write, routing.context_origins.read
- rollback: revert_rule
- failure_paths: preview-inconclusive, validation-regression