Fix URLs in Field Merges
Currently, Eloqua doesn't officially support using full URL field merges in <a> tags. According to Eloqua Support, URL-based field merges can only be used as text (e.g. <p><field merge containing a URL></p>) or as query string parameters of a static URL (e.g. www.example.com?p=<field merge>).
While you can still use a URL-based field merge as a link, this is unsupported and can cause all sorts of issues. For example, if the URL has a query string in it, this will break Eloqua's system tracking parameters because Eloqua doesn't recognize the existing parameters and appends a 2nd ? to the URL. For example, if the original URL in the field merge is www.example.com?p=sneakers, Eloqua will change this to www.example.com?p=sneakers?elq=12344&elqaid=5566&elqcampaign=89898. This also happens with Eloqua's external tracking.
The current support for text or query string parameters is very limiting, especially if you're integrating with a 3rd-party system, such as eCommerce engines or site optimization platforms, to send emails that drive people to personalized pages such as abandon cart. These systems typically use complex query-string based URLs to dynamically assemble pages.