Introduction

 

  1. We all Experience on a daily basis while shopping online, we go to the website, select a product, check into the cart and get a filled form along with product and your details and simply make payment.
  2. My recent project requires to do the same thing with our promotional emails. As we are in the software business So should do this for better customer experience and My company also introduces an eCommerce website to make the payment method easy.
  3. Information in the Externally hosted form contains Products details and Customer profile information.
  4. Product details are stored in a CDO So, we choose to do this with the help of Field merges of Contact and Custom Object (CDO).

 

Challenge

 

The Promotional email will be having a CTA button with a link which consists of some set of parameters(External Form fields name) of the Externally hosted form to retrieve those value from Eloqua. We needed to get those values for specific customers from Eloqua contact Object and Custom Object and pass it to the variable(External Form fields name) in URL.

 

Solution

 

I suggested using field merges directly in the URL. Eloqua Values will be stored in a Field Merge and then we can use those field merges in External form field placeholder in the URL.

Ex:

External Form Field name = Prod (Supposed to contain Product value Like Prod = Product Code from Eloqua)

 

This field is looking for a product value from Eloqua So, we need to create a field merge. Eloqua CDO/Contact field merge will be having product value and we need to place it in URL.

This provides a quick, easy and simple solution for email deployment. In the example below, you’ll find a way to do this.

 

Field Merges

 

For each data point about the event necessary in the URL, a field merge was created from CDO/Contact(Product name, Product description, date, contact address, etc.). This field merge used the last created information, so the contact will receive their registration confirmation email with the most up to date information from their latest form submission.

 

Prod.png

The Email  CTA LINK

 

It is important to know the Field Merge syntax and code used to achieve personalization of URL.

Eg. Below span tag is the field merge code for Product. (The same is obtained by dragging and dropping a field merge field on the email)

<span class="eloquaemail" >Product12</span>.     Here Product12 is the Eloqua Internal field Name.

 

Create the span tag of all field merged which you want to use in URL and place in place holders of link. So, the CTA link finally will be:

Link: https://www.example.com/us/en/webstore/commerce.html?prod=<span class="eloquaemail" >Product12</span>&ctry=<span class="eloquaemail" >CountryCode1</span>&email=<span class="eloquaemail" >EmailAddress</span>

Here, Prod,ctry and email are the fields name of form where this URL will be redirected.

 

Note: The External form field variable in the URL query string must be exact same as what is in External form if the wrong variable placed in URL then it will not populate data in Non-Eloqua Form.

 

Non-Eloqua Form

A script to read the values from URL Query string is implemented on Non-Eloqua form

After the above configuration, URL consists of the field merge value in the URL query string as below.

Converted URL:

https://www.example.com/us/en/webstore/commerce.html?elq_cid=54529&prod=W2130UU-1XY&ctry=US&email=xxx.gupta@xxxxt.com

Below form fields will read data from the above URL query string and populate in the form and Customer can review and go ahead.

InkedPicture1_LI.jpg

 

Note: For this project, the most helpful Eloqua courses for understanding the related functionalities to implement this solution were Creating field Merge with contact and CDO, Email fundamentals and Field merge with Query String helped me a lot in order to implement this.It was also important to have Eloqua Help Center to research Creating custom objects and Creating field merges with custom objects.

 

Results:

 

With Field merge feature of Eloqua, Customers who are redirecting to Non-Eloqua form start getting a pre-filled form to purchase the product. That reduced a couple of steps for a customer to fill the form and we could keep using Non-Eloqua forms with no changes applied in any of the interfaces, all leads running in the new infrastructure. This was required by the stakeholder.