The lookup code is not the problem, if I have the Eloqua cookie from a previous submit (let's say I'm using my day to day browser) it will read it with the visitor lookup with no problems. I am only posting here because I am out of solutions and have contacted ELQ Support, and in wait for an answer I wanted to know if anyone had a similar problem.
Here is the simplest version of how I would do it :
| <script type="text/javascript" src="http://img.en25.com/Web/XXXXX/elqCfg.js"></script> | |||
| <script type="text/javascript" src="http://img.en25.com/Web/XXXXX/elqImg.js"></script> | |||
| <script type="text/javascript" src="http://img.en25.com/Web/XXXXX/elqScr.js"></script> | |||
| <script type="text/javascript"> | |||
| /* <![CDATA[ */ | |||
| var elqPPS = '50'; | |||
| var elqDLKey = escape('visitorlookuphere'); | |||
| var elqDLLookup = ''; | |||
| var elqSiteID = 'siteIDhere'; | |||
| /* ]]> */ | |||
| </script> |
| <script type="text/javascript" src="http://img.en25.com/Web/XXXXX/elqCPers.js"></script> | |
| <script type="text/javascript"> | |
| var v_Email = (typeof GetElqContentPersonalizationValue == 'function') ? GetElqContentPersonalizationValue('V_ElqEmailAddress') : ''; | |
| console.log("######### vis email alternative lookup gave " + v_Email ); | |
| </script> |
