Read locale/offer expectation
Synthetic Chinese creative Z17 requires offer O17 in zh-HK. Entry Z-LINK ends at page P17 EN with correct O17. EN creative E17 may use P17; Chinese route requires separately supplied P17-Z in zh-HK. Local policy does not treat correct offer as locale readiness.
| Creative | Required | Terminal |
|---|---|---|
| E17 | O17/EN | O17/EN matches |
| Z17 | O17/zh-HK | O17/EN mismatch |
Resolve observed terminal properties
- Match campaign offer identity
- Inspect terminal locale
- Retain E17 route
- Correct Z17 route to P17-Z
A translated link label cannot change the terminal page’s supplied locale.
Which of the two routes needs correction?
Show the worked answer
Z17 only. Both reach O17, but only E17’s required locale is currently satisfied.
Request the exact locale correction
| Case | Decision or result | Reason |
|---|---|---|
| Chinese label with EN page | Not ready for Z17 | Locale mismatch remains |
| Chinese route to P17-Z | Candidate matches | Offer and locale both correct |
Check actual destination page context in both locales before release. This route sheet does not certify copy review or translation quality.