Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

User Experience:

Periodically after saving content, users will experience the following warnings which will include a list of the invalid links:

image-20240425-182820.png

Odyssey:

image-20240425-182825.png

Email Builder:

image-20240425-182831.png

Once the user clicks OK, the Tracking pleat will note the following message and the tracking will be unchecked on the links referenced in the previous warning message:

image-20240425-182836.png

For Email Builder deployments, if the invalid links are left unresolved and link tracking unchecked on those links, users will receive the following warning at the time of scheduling the deployment, which will require accepting the message or canceling the scheduling of the deployment:

image-20240425-182841.png

Common Cause:

The most common cause is the existence of trailing or leading spaces within quotes contained in the href element of the “a” tags of the HTML code. For example:

image-20240425-182846.png

Please note leading or trailing spaces used in HTML are compatible within many email clients and web browsers but they will render links untrackable in Email Builder. The solution to this issue is to find the untrackable links within your HTML code and remove any leading or Dtrailing spaces and then re-save the content. Users will want to double check in the Tracking pleat that the tracking on these links has been re-enabled.

Other Causes:

Another common cause is if your URL is missing the protocol sub-string like “http://” or “https://”. For Example:

image-20240425-182852.png

The solution is to go back into the code, include the correct protocol in all your URLs, and re-save the content. Users will want to double check in the Tracking pleat that the tracking on these links has been re-enabled.

Further Troubleshooting:

If users have link tracking issues beyond these common causes, please contact your account manager and provide the track Id of the deployment in question for help troubleshooting.

  • No labels