Skip to main content
JoseSe6
Level 2
Jul 20, 2023 3:11 PM UTC
Question

404s on Emails

Hello everyone,

 

We have been experiencing 404s on URLs added to our Marketo emails for a while.

The issue is not with all the urls, it just happens randomly.

If we change the url and try to open it another browser then the link works.

 

This is an example of a link that doesn't work: 

visit.company.com/OTQ1LUNYRC0wNjIAAAGNDJ5NgrAXyub4LVHxPikNibAHxgxrr_vPFdA_NvusCXBklPxJWmXYNMrTA5aDEqntV_f9HW4=

 

Has anyone experience anything like this?

 

Cheers,

Pepe

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

SanfordWhiteman
User Group Leader
SanfordWhitemanUser Group Leader
User Group Leader
Jul 20, 2023 4:59 PM UTC

Change the URL in what way? The click tracking IDs aren't something you can just guess.

Also please don't use somebody else's domain in your examples. You may use example.com, which is standardized for this purpose.

Translate
JoseSe6Author
Level 2
Jul 21, 2023 6:52 AM UTC

Thanks for the reply.

 

I didn't mean to say change sorry, my bad.

What I meant is that if we open the link that is giving us a 404 in a different browser, the link works

The url is not real, I used company.com instead of example.com

 

 

Translate
SanfordWhiteman
User Group Leader
SanfordWhitemanUser Group Leader
User Group Leader
Jul 21, 2023 7:17 AM UTC

I didn't mean to say change sorry, my bad.

What I meant is that if we open the link that is giving us a 404 in a different browser, the link works

The url is not real, I used company.com instead of example.com

But company.com is somebody else’s domain. It’s not a placeholder. You should use example.com, both to avoid confusion and to avoid inadvertently sending people to that domain.

 

The behavior you’re describing is consistent with the negative response being cached in the first browser. (Note it’s not actually an HTTP 404, it’s an HTTP 200 with an internal error message that looks like a 404.) But this response should not be cacheable, per its explicit cache-control HTTP header. I think you should supply an actual link that gave a 404 so we can inspect the response.

Translate
Terms & ConditionsAccessibility statement

Loading footer...