Read route and terminal expectation
Synthetic creative expects terminal page COURSE-A. Entry SHORT1 maps to HUB, HUB maps to COURSE-B. COURSE-B is terminal. Local readiness compares the terminal identity, not whether the entry opened.
| Hop | From→to | State |
|---|---|---|
| 1 | SHORT1→HUB | Continue |
| 2 | HUB→COURSE-B | Terminal B |
| Expected | COURSE-A | Mismatch |
Follow every supplied hop
- Start at SHORT1
- Follow HUB mapping
- Resolve terminal COURSE-B
- Request route correction to COURSE-A
A repeated route identity indicates an unresolved loop, not a terminal page.
How many hops lead to the wrong terminal?
Show the worked answer
Two hops. The terminal is COURSE-B, so the campaign destination is not ready for COURSE-A.
Correct a wrong terminal
| Case | Decision or result | Reason |
|---|---|---|
| Only test SHORT1 opens | Incomplete | Terminal not checked |
| Trace to COURSE-B | Hold campaign link | Wrong course identity |
Retain the full route trace with the correction request so the responsible maintainer can fix the relevant hop.