Hi Robert thanks for the response.
Changing the quotations from double to single, does indeed help but I've also found the question mark after the URL, before the <span> is key.
Once included and resaved the code updates to this, which seems like a step in the right direction.
<a href="http://www.companyurl.com?~~eloqua..type--emailfield..syntax--country..innerText--country..encodeFor--url~~&elqTrackId=x9x9x">http://www.companyurl.com?<span class="eloquaemail">country</span></a>
Unfortunately I'm still getting the same error on the test emails. Any other ideas?
The other difference I see is that our Country field merge is capitalized; not sure if that makes a difference. I tested the same syntax that you have (except with uppercase C in country) in our instance and it worked okay in a test email.
I've had a response from Oracle support which solved the problem, so here's the knowledge.
The following code will work fine in your Shared Content as long as your country field merge is called country
Ours is called country1 which you can easily find out by adding the field merge directly to the shared content rather than referencing it in the source code.
Fingers crossed that will help someone else scratching their head with the same problem in the future.
1 person found this helpful
Would suggest removing the span tag as eloqua will replace it and coding it directly.
Below is the code how it worked for me.
so, from what i've seen, this works when you are not tracking the link by "managing links". If you do track the link, however, it will break. This probably needs a feature enhancement so that the field merge is translated before the link is tracked. @