Affiliate Attribution & Campaign Tracking Infrastructure

## Overview

LeadStorefront should support end-to-end attribution and affiliate tracking workflows for paid traffic, localized storefronts, lead generation, and affiliate conversion campaigns.

The platform will act as the conversion and storefront layer between advertising platforms, affiliate providers, lead workflows, and localized commerce content.

---

## Goals

- Capture inbound advertising attribution parameters
- Persist visitor attribution sessions
- Support affiliate and travel partner link workflows
- Enable localized affiliate routing
- Track storefront conversion performance
- Support lead scoring and conversion analytics

---

## Supported Traffic Sources

The platform should automatically ingest and persist common traffic attribution parameters from:

### Social / Ad Platforms

- Facebook / Instagram → fbclid
- Google Ads / YouTube → gclid
- Microsoft Ads → msclkid
- TikTok → ttclid
- LinkedIn → li_fat_id
- Twitter / X → twclid
- Pinterest → epik
- Reddit Ads → rdt_cid

### Standard UTM Parameters

- utm_source
- utm_medium
- utm_campaign
- utm_content
- utm_term

---

## Affiliate & Travel Tracking Support

Support common affiliate and partner tracking parameters:

- affid
- aid
- partner_id
- partner
- subid
- sub_id
- clickid
- click_ref
- campaign_id
- ref
- source
- cid

Travel-specific support:

- market
- locale
- currency
- destination
- hotel_id
- offer_id
- checkin
- checkout
- adults
- children

---

## Core Requirements

### Attribution Persistence

Persist attribution state via:
- cookies
- local storage
- server session
- lead records

Track:
- first-touch attribution
- latest-touch attribution
- campaign source
- market source
- affiliate source

---

## Outbound Affiliate Routing

Support outbound affiliate link generation with:
- affiliate IDs
- sub IDs
- click references
- market-aware partner routing
- dynamic retailer selection

Example:

txt booking.com/?aid=uk_partner

or

txt booking.com/?aid=de_partner

based on storefront market context.

---

## Storefront Conversion Workflow

Expected flow:

txt Traffic Source (Facebook / Google / TikTok) ↓ LeadStorefront (captures UTMs + click IDs) ↓ Localized storefront page ↓ Lead form / offer page / comparison ↓ Affiliate redirect (Booking.com / Agoda / operator) ↓ Commission or qualified lead

---

## Future Enhancements

- Affiliate link rotators
- EPC optimization
- Dynamic offer ranking
- Conversion scoring
- Multi-market attribution reporting
- Retailer performance analytics
- A/B retailer routing
- Conversion event webhooks
- CRM integrations
- Partner analytics dashboards

---

## Positioning

LeadStorefront should function as:
- hosted storefront infrastructure
- conversion infrastructure
- attribution infrastructure
- affiliate operations tooling
- localized commerce delivery platform

rather than only a storefront builder.

The issue names no files, tests, or entry points; begin by locating the existing attribution, storefront, lead, and affiliate-routing areas in the Go repository. Define the smallest agreed scope and acceptance checks before implementation, noting that linked PR #60 indicates work has already moved.

Written by the indexing model from the issue text.