Skip navigation

Hello All,


I was wondering if there was a way to send a set number of emails from a PET table within a program? The only way we have found is to use an allocation switch.


For example: Using a Pet table of 50,000 would we be able to send just 10,000 within a program.


The only way we have found is using an allocation switch; we have tried a stage gate but it doesn't seem to work.



In order to create a page tags structure in Eloqua you would have to have your website fully tracked with Eloqua scripts.

Comprehensive instructions on how to do that can be found at Assets/Website setup/Tracking/Visitor Tracking/Visitor Tracking Package. Clicking the Generate button on lower right will provide and archive with the scripts and detailed instructions.


Now given that your website is tracked and you can dint it in the Eloqua Site Map, we can proceed with the tags

We have the following website structure which we want to include in our Eloqua web tagging page system.

in order to make our approach automated we will start by creating the main tags: home, services, Industries, Insights, Contact.

The base URL in the input box should be and the levels down should be set to 1.


Now we are going to create an Auto Tagging rule for second tier: Services, Industries, Insights, Contact

There will be 4 rules.

The base URL will  be different for each, for example for Industries. The tags will be created automatically for all pages under it.



Now you have your Eloqua tags all set up for a website with the above structure. The plus is that you set up Auto Tag rules, so changes within the same structure will auto tag new pages. This is alot better than selecting Create page Tag and creating one tag a time, which is a system you will have to manually support at every site map change, either by hand or excel upload (which is also by hand ).


To add a plus to reporting on tags, you can create page tags groups. I would recomment one group for each base url within the site, like Service, Industries, insights. Just manually add the page tags withn the page tag group.



The working scenario is that a contact in being forwarded and email and he clicks a link in an email and arrives to a page. It can be:

- that the page he arrives to is an unsubscribe page where he clicks a button to unsubscribe;

- the page is a prepopulated registration page;

In our case, that would be a problem because the page would pre-populate with the data of the original receiver of the email. Thus the person being forwarded the email by that office colleague could submit a form with someone else's data or unsubscribe the forwarder.


In order to prevent that we have to make some updates to the destination page. Basically we'll check if the visitor of the page has the same email address as the person who received the email. The Eloqua tracking script needs to be present on the page.


Create a Visitor Lookup in the Web Data Lookup section. Make sure the Data Lookup Type is Visitor and the data field is Cookui GUID. This will get the email adddress of the Visitor. Script is there in the Get Data Lookup Scripts section and looks like below.

<SCRIPT TYPE='text/javascript' LANGUAGE='JavaScript'><!--//

<div id="contactinfo">


function CreateRow(label, value) {

    var p = document.createElement('p');

    var b = document.createElement('b');






function SetElqContent(){

    if (this.GetElqContentPersonalizationValue){

      CreateRow('Email Address: ', GetElqContentPersonalizationValue(''));

      CreateRow('Email Address: ', GetElqContentPersonalizationValue('V_Email_Address'));

  } else {

      CreateRow('Personalization functions not found','');





From here you can check this visitor email address againt the one coming from the email link, that is if you populate with field merges.


var eloquaEmailAddress = "<span class="eloquaemail" >EmailAddress</span>";

function verifyIdentity(cookieEmailAddress) {

    if(eloquaEmailAddress == cookieEmailAddress || cookieEmailAddress == undefined || cookieEmailAddress == "") {      

        // KEEP Identity based on Eloqua ID

    } else {

        // SET Identity based on Cookie GUID

        for (var i=0;i<document.getElementsByName('emailAddress').length;i++){

            document.getElementsByName("emailAddress").value = cookieEmailAddress;





If you populate using Contact Lookups, there appears to be a new option to get this solved. Basically this Contact lookup on a page will return lookup data if there's a match with the Visitor (we didn't give a try to this one yet).

Filter Blog

By date: By tag: