Skip navigation

At times you may need to pull together a bunch of contacts for a very targeted email campaign. This is easy to do in Eloqua in general but in Eloqua10 our developers made it even easier to build and visualize. Here's a great example: I need to create a list of contacts (or a "Segment" in Eloqua10 lingo) that includes contacts from the US or Canada that have opened at least 2 emails in the last month. Here's how to do it:

 

  • Choose your criteria
  • To group criteria together, select them and select the subsequent items hitting SHIFT. When you have the items selected, hit the Group button at the bottom.
  • Change the ANDs/ORs and move the items around if needed

 

Here's a quick video showing how easy this is (sorry for the bad quality).

 

Here's a quick pic on how this looks:

2-18-2011 9-59-37 AM.png

 

Have fun and happy marketing.

In a hurry and need to find that email in under 1 click? Easy. Immediately after logging into Eloqua, note the search bar on your home page. Drop down to change to the asset you're looking for, i.e. Emails, Landing Pages, Forms, etc., and type in the name and click Search!

 

Not sure EXACTLY the name, but you have a great naming convention? Equally simple. Use boolean search terms like ? to represent any AlphaNumeric character, or * as a wildcard for all characters before or after your search terms. Example: *eloqua* would return any asset with the word "eloqua" in it, while *eloqua would return only assets that end with the word Eloqua.

 

ELQSearch.png http://topliners.eloqua.com/servlet/JiveServlet/showImage/38-1147-1471/7-11-2011+6-13-37+PM.png

[These instructions refer to Eloqua 10. For Eloqua9 instructions go here.]

 

Sometimes when a user clicks a link in one of your emails you’d like to be able to do more than simply track the click-thru. The method below describes a ‘trick’ so that you can do just that! The basic premise is that you will build a form within Eloqua (that you can use again and  again). In your email message you will insert a specially created URL that points to this form. When the user clicks this link in your email, they are actually submitting an Eloqua form – although they don’t know it and it’s seamless to them (which is where the term “blind form submit” comes from). You can then use Form Processing Steps to perform many actions, such as associate them to a campaign, change their campaign status, add them to a group, notify a salesperson, etc. All of  the normal Form Processing Steps are available to you as options. An example of this might be an RSVP link in an email. You could have two separate links “No, I cannot attend” and “Yes, I’ll be there”. Each one of these links can point to the same form. But in the “rsvp” variable we can pass along a No or a Yes. Then, with conditional processing steps on the form, we can add these people to one of two contact groups.

 

 

Create Your Form


Go to Assets > Forms New  > Choose "blank form"


In the Settings area set the Form Name to “Click Thru Tracking” or whatever makes sense for your organization. This form name will appear in your CRM activity history section when this form is submitted (if you have an integration between Eloqua and your CRM, and if you have Form Submission activity turned on).

 

You can then click on "Generate" to create a unique HTML Name or type this in yourself. Make sure you take note of this HTML Name as you'll need it later on

 

2-11-2011 2-51-47 PM.png

 

Open Notepad and begin pasting the information you see in these two boxes like this:

 

secure.eloqua.com/e/f2.aspx?elqFormName=clickThruTracking-1297453884557&elqSiteID=1542

 

In case you want the details, here is an explanation of what we have so far:

  • Everyone who uses this process will have the same beginning part of the URL. All Eloqua forms are processed through this URL: now.eloqua.com/e/f2.aspx
  • The ? is the beginning of the first query string. (Query strings are a way of passing along additional information with a URL. The first one always begins with a question mark and subsequent query strings are joined by adding an ampersand [&]. )
  • The first query string is the elqFormName. Everyone will have this same parameter, but the value (the part after the equal sign) will be unique to you. For example, if you named your form something other than ‘click’ that name will appear here. In this case, it's clickThruTracking-1297453884557
  • The & is the beginning of the next query string.
  • The second query string is the elqSiteID. Again, everyone will have this parameter, but your Site ID value is unique to you.

Note: This first part of the URL (up through the SiteID value) will always be the same every time you use this feature.

 

 

To see the SiteID, go to View Form HTML > Integration Details:

2-11-2011 3-03-45 PM.png

 

Add More Fields To The Form


Just drag and drop the fields you want. There are two fields you MUST add, then additional fields are optional.

 

Email Address:

Set the HTML name to “e” (this will help keep our URL shorter).

2-11-2011 3-06-22 PM.png

 

retURL:

Similar to above, set the HTML name to "url"

 

Additional fields you may want:

Campaign ID (recommend “cid” as the HTML name)

Campaign Status (recommend “status” as the HTML name)

RSVP – if you intend to use this similar to the example at the beginning of this document

 

 

Finish Building the URL
Now continue building your URL. At a minimum it will now look like this:

 

secure.eloqua.com/e/f2.aspx?elqFormName=clickThruTracking-1297453884557&elqSiteID=1542&e=<span class=eloquaemail>EmailAddress</span>&url=http://www.company.com/landingpage.html

 

It may even look like this:

secure.eloqua.com/e/f2.aspx?elqFormName=clickThruTracking-1297453884557&elqSiteID=1542&e=<span class=eloquaemail>EmailAddress</span>&url=http://www.company.com/landingpage.html&status=responded&cid=701000000000csR&rsvp=yes

 

You can add as many fields as you like – simply connect each of the fields/query string with an ampersand.

 

NOTE: That the recipient’s email address will be inserted correctly into the link when the Batch or QuickSend is sent to them.

 

NOTE: The Destination URL that you enter must be a fully-qualified URL. (That means it must begin with http:// or https://) This is the location that you want the person to end up after they have clicked the link in the email.

 

 

Building the Form Processing Steps


The number of Processing Steps you have will depend on your needs for this  functionality. You will probably use some conditional Processing Steps as you begin to use this form more and more. For example, if you want to use the RSVP functionality example, you may have two “Add to Shared Contact List” steps – one for “yes” and one for “no”.

 

At a minimum, you must have the step called Redirect to URL. Change the properties from Constant to Form Field (as shown below) and then point to the field that you created called “retURL.”

2-11-2011 3-43-03 PM.png

If you are passing through Campaign ID or Campaign Status, you’ll also want to add the step called “Update Contacts With Form Data” and save those fields to the appropriate Contact Fields in Eloqua. You will also need to add the “Add to Program” step and choose the Update CRM program so that the person’s Campaign Status/ID can be updated in your CRM.

 

Inserting the Link into an Email

 

In your email, highlight the text that you want to make clickable and insert a hyperlink. Choose “Webpage” as the link type and paste your link code into the Webpage field as shown below. Ensure that there is now "http://" before the now.eloqua.com.... In addition, do not click “Insert as Redirect Link”.

2-11-2011 3-25-58 PM.png

[above image should be secure.eloqua.com/e/....]

 

A few things to consider:

  • Email Address Considerations
    It is important to note that because the email address is being passed  directly in the link, the email click and form submission will be associated with that specific email address.
    For example, if we use the RSVP example: If Bob Customer receives the email and clicks the link  to RSVP “yes”, then he forwards it to his friend Joe who clicks the “no” link, it will look like Bob submitted two forms – one with a yes, one with a no. For simple things like RSVP tracking this is usually okay  – you’re just trying to get a general idea of raw numbers. But there may be times that this might cause you a problem. In those cases you might add verbiage that says ‘This is your private link, do not forward’ or something like that.
  • Re-Use the Form
    You can continue to use this same form over and over by simply adding more fields as needed. It’s perfectly okay to have multiple fields within the Eloqua form but then only use two or three of them in the URL. Just use what you need at that time. And remember that conditional Processing Steps can be very helpful to you.
  • Click-Thru Tracking
    Download the Word file attached to this post for more information about tracking the click-thru in the email stats report in Eloqua.
<span class=eloquaemail>

If you're an Eloqua customer who uses Adobe Connect to run your online meetings, you're going to love our newest addition to the Cloud Connector family! I've created this step-by-step document to help you set up your event and measure attendance. Please try it out and post any feedback here (comment on this blog post) and I'll answer and/or update the document as needed.

 

(NOTE: I was a bit intimidated to start the process of using a Cloud Connector -- I was worried it was going to be too technical for me -- but I'm very happy to report that it was EASY! If I can do it, you can do it...trust me.)

 

Here’s the overview of how the Adobe Connect Cloud Connector works:

 

  1. You send an email invitation or otherwise drive traffic to a registration form for your event, which is an Eloqua-based form.
  2. When the user submits the form, they’re added to a Program (via a Form Processing Step).
  3. The Program uses a Cloud Connector step to register the user with Adobe Connect then sends them a confirmation email.
  4. When the event begins, the user logs in with their email address and password (which were configured in the Cloud Connector step and sent in the confirmation email).
  5. The Program then holds the user until a date/time you specify after the event, then it uses another Cloud Connector step to check in with Adobe and see if the person attended. You can then send “thank you” or “we missed you” follow-up emails as desired.

 

Let’s walk through this step by step!

 

1. Getting Started: Eloqua

 

You must have an account on the platform where the Cloud Connectors are hosted (https://cloudconnectors.eloqua.com), and your Eloqua user account must have API access. Cloud Connectors: Step by Step Installation Instructions if this is your first time using the Cloud Connector.

 

Eloqua elements you’ll need:

 

  • Emails: Invitation, confirmation and follow-ups (we recommend adding a calendar ICS file to the confirmation email so people can easily add the event to their personal calendar)
  • Registration Form on a landing page     
    • Minimum required fields by Adobe: First name, last name and email address
    • Form Processing Steps: in addition to the usual “Save to Contact Table” and “Update Existing Record or Data Object”, you’ll also need “Add to Step in Program Builder”
  • Contact Fields:     
    • Adobe Connect Meeting URL Holder (text field) [OPTIONAL] – this holds the Adobe Connect meeting URL that gets returned by Adobe
    • Number of Minutes Attended (numeric field)
    • Number of Questions Asked (numeric field)
  • Program Builder program – explained more below

 

2. Getting Started: Adobe Connect

You must use an Adobe Connect account with Administrator rights.

 

Create your meeting and make note of the URL and telephone connection information to use in your confirmation email and ICS file.

 

3. Building the Program in Eloqua

 

Here’s an overview of what your program will look like in Program Builder:

Adobe1.jpg

 

 

First Adobe Connect Cloud Connector Step – Register Users

 

The first Cloud Connector step (“00. Send to Adobe”) registers the user with the Adobe Connect system. To configure the step, choose “Cloud Connector” for the action and then “Adobe Connect Register Attendee.” Click the Configure button to get started.

adobe2.jpg

  • On the Credentials tab, enter your Cloud Connector credentials
  • On the Configuration tab, enter your company’s Acrobat.com domain and your username and password (remember: you must have Administrator access or be using an account that has Administrator access).
  • Enter a generic password that all new users will use (note: their username will be their email address, you cannot edit this).

 

TIP: If someone registers for your event with an email address that’s already connected to an Adobe Connect account, Adobe will NOT overwrite their existing password. The registrant can use their existing credentials to attend your meeting and it will still be recorded.

 

At this time, you can ignore the “Send email invitations” option as Adobe Connect does not support this. We set ours to “Don’t Send” as an added future-proof precaution. Click Save Settings and your meeting options will show up in the drop-down field and you can select the correct one. Click Save Settings again.

 

adobe3.jpg

 

Next you’ll set up your field mappings:

 

  • The Contact Field mappings are required
  • The “Join Meeting URL Field” is optional. Adobe Connect does not generate unique links for each attendee, so you can simply paste the link for your event directly into your confirmation email, rather than use this field to hold the information and then dynamically insert it.

 

Click SaveSettings.

 

adobe4.jpg

 

Return to the Credentials tab when you’re finished and check the “Enable Step” checkbox in order to let this step run without any intervention from you. Click Save Settings.

 

adobe5.jpg

 

 

Wait Step

 

Be sure and build a wait step into your program that holds all contacts until at least 2 hours after your event has ended. If you begin querying Adobe too soon you may not get accurate registration information.

 

adobe6.jpg

 

 

Second Adobe Connect Cloud Connector Step – Query Attendees

 

The second Cloud Connector step in the program allows you to query the Adobe Connect system to see if someone attended your event. To configure the step, choose “Cloud Connector” for the action and then “Adobe Connect Query Attendance.” Click the Configure button to get started.

 

adobe7.jpg

 

On the Credentials tab, enter your Cloud Connector credentials again.

 

On the Configuration tab:

 

  • Enter your Adobe Connect login information and click Save Settings. Your list of meetings will then appear.
  • You can choose to store your meeting attendance information on the Contact record in Eloqua (as created in the Getting Started step above) or in Data Cards (Note: Data Cards are only      available in the Eloqua Team and Eloqua Enterprise products). Click Save Settings to proceed.

 

adobe8.jpg

 

For this example, we used the Contact Record and created two numeric contact fields that we mapped to. Click Save Settings. Go back to the Credentials tab again and check the Enable Step checkbox.

 

adobe9.jpg

 

Decision Rule

If you want to send different follow-up messages to attendees and non-attendees, you can create a decision rule to look at the number of minutes the person attended, as shown below:

adobe10.jpg

 

 

4. Setting Up the Email Confirmation

 

Make sure your confirmation email includes the log-in link and the person’s username (email address) and the password that you’ve created. Here’s a simple example:

adobe11.jpg

 

That's it!

Hi everyone - I just published a really simple Lead Nurturing Program to Eloqua's SmartXChange that you can use to properly welcome new contacts in your database. To access this template, you can download it from SmartXChange. Sure you can easily build this from scratch but why should you? It's much easier to copy what others have already perfected.

 

For some background on Welcome Programs, see Ready to Welcome Your New Leads?

 

For information on how to use SmartXChange, see: SmartXchange - Installing a Template

 

 

Chad

 

PS - consider creating more than one welcome program based on who you are targeting or using email with dynamic content to enhance your email response rates.

**UPDATE: CASL Enforcement Date Announced**

Overview

 

 

Most online marketers doing business in Canada today are already familiar with PIPEDA. But many are not aware that a new law, known in Parliament as bill C-28 was given Royal Assent on December 15, 2010. The law imposes onerous opt-in and other responsibilities on marketers doing business online in Canada. It covers items such as the sending of Commercial Electronic Messages (CEM), prohibition of installing computer programs without consent, and sending messages with false or misleading information in the content or header. Enforcement of the law is expected to commence in September 2011, which should give marketers ample time to comply.

 

CASL is effectively Canada’s first anti SPAM law, which removes the distinction of Canada being the only G8 nation without one. The provisions of PIPEDA already covered opt-in however enforcement actions were limited. Under the new law, a definitive set of requirements and enforcement actions are laid out and penalties for violation of the law can be severe. Unlike CAN SPAM, which covers only email, CASL covers CEM, which is defined as any commercial "message sent by any means of telecommunication, including a text, sound, voice or image message." Effectively, this includes:

 

  • Email
  • SMS
  • Instant Messages
  • Social Media postings such as ‘tweets’
  • Some voice communications

 

 

There are a number of requirements set forth in the law regarding CEM, most notably:

  • Express affirmative (opt in) consent
  • No false or misleading headers, including sender and subject line
  • Cannot alter transmission data
  • Must provide a conspicuous unsubscribe mechanism
  • Must include postal address of sender
  • Cannot perform address harvesting to obtain email addresses or send to harvested addresses
  • Liability for entities who knowingly allow spam to be sent on their behalf, even if the message was not directly initiated by those entities

 

Exemptions to the opt-in requirement exist under certain circumstances. Consent is deemed if there is an existing business relationship, an existing non-business relationship (such as sending to a family member), conspicuous posting of an electric address such as on a 'Contact Us' page (provided there is no statement near the address indicating that it should NOT be mailed), or where the recipient has provided the electronic address to the sender. In most cases, this implied consent is valid for two years, after which the sender must gain affirmative consent.

 

 

 

Enforcement / Liability

 

 

Computer systems located in Canada used to send or access an electronic message fall under the CASL umbrella. This means that any CEM that leaves or enters Canada is subject to the regulation. CASL is primarily enforced by the Canadian Radio-television and Telecommunications Commission (CRTC), and imposes fines of up to $1 million per violation for individuals and $10 million per violation for businesses. There is also a provision for private right of action, allowing individuals and businesses to seek actual and statutory damages.

 

Enforcement does take into account ‘honest mistakes’ and for that reason, it is important to undertake clearly defined actions to comply with the law. Willful violations are the primary focus of enforcement.

 

 

Next Steps

 

 

Businesses will need to scrub their lists and remove any covered address for which there is no affirmative opt-in to receive email and other CEM. It is expected that many email lists will be significantly reduced in size as a result. Privacy Policies and form collection on websites should be updated to ensure proper consent. In the case of forms, this includes moving from an opt-out (pre-checked) to an opt-in (not pre-checked) methodology.

 

Eloqua recommends that businesses meet with their legal, compliance, and marketing teams to determine the full scope of changes to their business practices in order to comply with the new law as there are a number of key considerations and requirements not provided in this article which may apply. We also encourage affected parties to read the full text of the law, which can be found at

http://www2.parl.gc.ca/HousePublications/Publication.aspx?Docid=4901869&file=4

 

 

Legal Disclaimer:

**Note that the purpose of this post is to provide general information about Canada’s Anti SPAM Legislation. It does not constitute legal advice and Eloqua does not accept any liability regarding its completeness, accuracy or relevance. Please consult your legal counsel for full requirements and implementation recommendations.

Filter Blog

By date: By tag: