Internal engineering case / AFK³ Solutions
Repairing an inquiry blocked by a source tag
An internal AFK³ repair: reproduce a campaign-validation error, inspect the patch, and see what the regression checks establish.
By AFK³ Solutions · Published 2 November 2026
Internal engineering case
A valid source tag could stop an inquiry.
This is an internal AFK³ website repair, not a customer case or a measured sales result. The problem involved the attribution attached to a contact inquiry. No customer records or production credentials were needed to reproduce it.
Our controlled comparison used the same browser-side serializer with two inputs. A short source name worked, but a domain-style source failed.
| Input | Before the patch | After the patch |
|---|---|---|
utm_source=chatgpt | Source serialized | Source serialized |
utm_source=chatgpt.com | Serializer threw a validation error | Source serialized as chatgpt.com |
Because the form prepares attribution before sending its request, the validation error could interrupt an otherwise valid inquiry. We have not measured how many real inquiries, if any, were affected.
Practical guidance
One format rule covered two different kinds of value.
The original code used a letters, digits, underscore and hyphen rule for both referral codes and campaign values. A dot in chatgpt.com failed that rule. The serializer then threw when it found the optional-tag error.
The repair separates the formats: campaign values may include dots within the existing 40-character limit; referral codes keep their stricter format. Invalid optional tags are omitted and explained visibly, so the inquiry can continue.
The browser and server apply the corresponding rules. Accepting a source tag does not establish referral credit or authorize arbitrary input.
Practical guidance
What we checked, and what remains unknown.
- Domain-style sources survive internal links and first-touch session storage.
- A controlled form submission includes the source in the request payload.
- Malformed and oversized campaign values are omitted without blocking the inquiry.
- The server accepts supported source formats and retains input limits.
- The no-JavaScript form path is covered separately.
Email delivery is mocked in these tests. They do not prove live inbox delivery, AI crawler access, search indexing, AI recommendations, security certification or improved conversion.
Inspect the repair commit →
Browser regression checks →
Server regression checks →
Practical guidance
Check the full task, including where the visitor came from.
A form that works when opened directly can still fail when a campaign or referral URL is used. When reviewing a contact workflow, include tagged arrival, internal navigation, submission, error handling and delivery as distinct checks.
For your app, we would agree on which of those steps are in scope, reproduce the observed failure and record any untested dependencies before proposing repairs.
Your next step
Start with one workflow.
Tell us the task that breaks, the app’s stack, its business impact and your intended deadline. A fit discussion comes first. Paid diagnosis, implementation and optional support are scoped separately.
Discuss an App Review