Quick Answer
When a redirect link fails, do not only ask whether it opens on one device. Check the entry status, destination URL, DNS or routing state, HTTPS behavior, tracking parameters, recent changes, and access logs. A good troubleshooting workflow connects the user report to the exact entry and its change history.
When a campaign link breaks, the first message is usually vague:
“The link does not work.”
That can mean many things: DNS issue, wrong destination, 404 page, redirect loop, blocked path, missing HTTPS, or a page that works only for logged-in users.
Decision Table
| Symptom | First check | Next check |
|---|---|---|
| 404 or wrong page | Entry status and destination | Recent changes and fallback page. |
| Works for one person, not another | Region, device, cache, and network | Logs and status-code distribution. |
| Tracking missing | UTM preservation | Redirect chain and analytics setup. |
The Short Answer
To troubleshoot a broken campaign entry, check the hostname, entry status, destination URL, redirect chain, final status code, UTM behavior, recent changes, and access logs. Do not guess from the first error screen.
Step 1: Confirm the Entry Exists
Check whether the hostname is managed and active.
Ask:
- Is the hostname spelled correctly?
- Is the entry active?
- Was it paused or retired?
- Is it the right environment?
Many “broken links” are actually old or inactive entries.
Step 2: Check the Destination
Open the stored destination.
Look for:
- Typos.
- Staging links.
- Deleted pages.
- Login-only pages.
- Region-specific pages.
- Query parameters that break the page.
If the destination itself returns 404, the redirect layer may not be the problem.
Step 3: Follow the Redirect Chain
A campaign entry may pass through more than one redirect.
Check:
- Does it reach the final page?
- How many redirects occur?
- Is there a loop?
- Does HTTP become HTTPS?
- Do parameters remain intact?
Long chains make debugging harder.
Step 4: Read the Status Code
Common codes:
200: Page loaded.301: Permanent redirect.302: Temporary redirect.404: Page not found.500: Server error.503: Service unavailable.
The final status code matters more than the first hop.
Step 5: Check Recent Changes
Ask:
- Who changed the destination?
- When did it change?
- Did traffic drop after that?
- Was a page migration happening?
- Was a campaign paused?
Trace logs make this much faster.
Step 6: Decide the Fix
Depending on the cause, the fix may be:
- Correct the destination.
- Restore the missing page.
- Replace with a fallback page.
- Pause the entry.
- Update campaign materials.
- Retire the old entry.
Final Thought
Troubleshooting broken campaign entries is easier when entries have status, destination, access statistics, and change history in one place.
The less context you have, the more every 404 feels like a mystery.
FAQ
What should I check first when a link does not open?
Check whether the forwarding entry is active and whether the current destination URL is still reachable.
Why are trace logs useful?
Trace logs help teams connect a user report with recent changes, routing behavior, status codes, and operational context.
How does PushUlink help troubleshooting?
PushUlink combines managed entries, access statistics, operation logs, and traceable changes in one workflow.
