Tracking, Attribution & Exclusion Management Admin Manual¶
Module: Tracking & Attribution (M4)¶
Product: ebosAi AMP
Classification: Internal — Confidential
Version: 2.0
1. Overview¶
The Tracking & Attribution Engine is the core transaction routing layer of the platform. It intercepts referral clicks, maintains 30-day first-party cookies, captures UTM parameters, and classifies incoming signup events into attributed partner conversions or excluded organic/marketplace traffic.
2. Auditing Signup Events (/admin/signup-events)¶
Administrators can inspect every raw signup event logged in the system:
| Column | Description | Notes |
|---|---|---|
| Event Time | UTC timestamp of customer registration. | Precise transaction log. |
| Customer Identifier | Anonymized user ID / customer email. | PII-compliant identifier. |
| Source Type | partner, organic, marketplace, or direct. |
Classification result. |
| Attributed Partner | Partner name if source_type = partner. |
Clickable to partner profile. |
| Referral Slug | The /ref/{slug} string that drove the click. |
Attribution evidence. |
| UTM Parameters | utm_source, utm_medium, utm_campaign. |
Marketing tracking data. |
| Actions | Manual source override button. | Adjust attribution if necessary. |
3. Manual Attribution Overrides¶
In rare customer support scenarios (such as when a customer confirms they were referred by an affiliate but experienced cookie-blocking issues during registration):
- Locate the signup event in
/admin/signup-events. - Click Override Attribution.
- In the modal:
- Select the correct partner from the dropdown list.
- Enter an audit reason (e.g., "Customer support ticket #4521 — confirmed referral").
- Click Apply Override.
- The system immediately:
- Reclassifies the signup event to
partner. - Triggers the commission calculation workflow to generate a new pending commission note.
- Logs the action in the immutable tenant audit log with the administrator's user ID.
4. Known Marketplaces & Exclusion Lists¶
Under Settings ➡️ Known Marketplaces, administrators can configure UTM source rules that identify third-party marketplace discount traffic (e.g., AppSumo, DealMirror):
- Adding a marketplace name (e.g. appsumo) ensures that any incoming checkout with utm_source=appsumo is automatically categorized as source_type = marketplace.
- Marketplace traffic is safely excluded from affiliate commissions, protecting merchants from paying duplicate affiliate bounties on pre-discounted third-party deals.