Monday, February 28, 2011

On24 and Eloqua Integration


For those who use On24 as your system for webinars or virtual events, you have probably quickly realized the need for deep integration between On24 as virtual event software, and Eloqua as marketing automation software, to market those events and follow up with registrants and attendees accordingly. The insight to be gained from understanding what a prospect did at a webinar is tremendous, as webinars generally show a wide range of attendance stats among those who register. Large percentages of people who register do not attend at all - often between 40 and 60% of registrants. Among those who do, some may drop off after 5 minutes while others may stay for the full hour. Knowing about this attendance difference is crucial in understanding how to follow up and how to score leads.

A prospect who registered but did not attend should be sent a “sorry we missed you” rather than a “thanks for attending” email, while a prospect who dropped off after only 5 minutes might respond well to a follow-up proposing a different set of topics that might be more appealing. Similarly, lengthy attendance combined with engagement such as asking and answering a number of questions is a great indicator of high interest and likely purchase intent.

Working with this insight, however, requires it to be present within Eloqua's marketing automation system. Only when it is, can lead nurturing and scoring can take advantage of it. Bringing this data in manually would require a tedious continual effort, which would test the patience of most marketers. Eloqua now has a cloud connector to enable this integration and bring the best digital body language insights from On24 into Eloqua. The On24 cloud connector allows three main usage scenarios (each can be used as individual steps within a marketing automation program as you design the promotion, reminder, and follow-up campaigns around your webinars):

- Register Attendee: Registers a contact who is in that step of a program with a specific event in On24.

- Query Attendance: Looks at each contact in that step of the program and queries On24to see if they attended the live or archived events and for how long, how many poll questions or surveys they answered, and how many questions they asked. All very interesting info for subsequent lead scoring or follow-up.

- All Attendees: Automatically pulls a list of all people who attended a particular On24 webinar and feeds them in to Eloqua as contacts and places them into a group (where of course they can be fed automatically into a program for follow-up nurturing). Again, for each attendee, the information captured is if they attended the live or archived events and for how long, how many poll questions or surveys they answered, and how many questions they asked.

To get started, you’ll need the Cloud Connector installed in your Eloqua instance. This is very easy to do, see the recent post on Cloud Connector Installation instructions for how to add a new Cloud Connector to your install. The Cloud Connector we’ll be looking at here is available on our repository of interesting connectors. Go to cloudconnectors.eloqua.com and create an account. Under Communication, you'll find On24: Register and On24: Query Attendance, while under Feeder, you’ll find On24: All Viewers – those are the connectors we’ll be working with, and the ones to install.

Once you have them installed, you can begin using them within your webinar invitation and management program. The cloud connector steps for On24 integration can be plugged into your marketing automation program at whatever points make sense, so be sure to whiteboard what you want to have happen and use the steps accordingly.

Likely, you’ll want to use a On24: Register step when the buyer has indicated that they are interested in attending, perhaps by clicking a link or submitting a form.

You’ll want to run the On24: Query step after the event has taken place to see who attended and for how long. That data can be used to guide prospects down unique follow-up paths depending on their behavior.


Now, for each step, you’ll need to configure the Cloud Connector to do what you need. Each connector is roughly the same, but with slightly different options, but once you have one figured out the rest will be simple. For the sake of simplicity, we’ll walk through the On24: Query step. Choose Cloud Connector as a step type, and pick On24 Query from the drop-down below (if you have installed the connector in your Eloqua instance as we discussed earlier). Click the Configure button to launch the configuration UI.

The connector will need to be configured with your On24 credentials, including the Event ID, Session ID, Client ID, and Key. These credentials must be obtained from On24 team when you ask them to enable the Eloqua integration feed on your On24 account.

A final setting is where you want to store the returned information, in the contact record or in a custom data object (data card). If you're running many events, you'll want to use custom data objects to keep a full history of attendance.

With that configured and saved, move to the field mappings tab, and choose the contact fields or custom data object fields that you want to read data from or write data to. Each data point returned (minutes attended live or archived, poll or survey questions answered, and questions asked) can be mapped to an individual field or left blank if you're not interested.

That's all that's needed to have full integration between your On24 webinars and your Eloqua marketing automation. You can go over to the Run Step tab to run the integration manually a few times to make sure it's all working. This shows you the results you will be pulling back into Eloqua or lets you manually run the step to check that it's all configured correctly.



When you're happy with the results, just go to the Credentials tab to click "Enable Step" to enable it to run automatically.


We'd love to hear your feedback on this connector, what can be improved, and what else you need it to do.

Tuesday, January 4, 2011

WebEx and Eloqua Integration - Webinars as source of Digital Body Language


Webinars are as much of a core element of most B2B marketer's day to day tactics as anything. They form a great vehicle for educating prospects on a deeper topic than might otherwise be possible, they allow a richer interaction with presenters, and they provide a great interim point to guide prospects towards that is less of a commitment than a purchase.

However, webinars generally show a wide range of attendance stats among those who register. Large percentages of people who register do not attend at all - often between 40 and 60% of registrants. Among those who do, some may drop off after 5 minutes while others may stay for the full hour. Knowing about this attendance difference is crucial in understanding how to follow up and how to score leads.

A prospect who registered but did not attend should be sent a “sorry we missed you” rather than a “thanks for attending” email, while a prospect who dropped off after only 5 minutes might respond well to a follow-up proposing a different set of topics that might be more appealing. Similarly, attendance for the majority of the webinar is indicative of very high engagement, and may be a good factor in lead scoring.

Historically, this has been difficult as this data would have to be brought in manually. Eloqua now has a cloud connector to change that – making us the first marketing automation platform with a seamless integration into WebEx. The WebEx cloud connector allows four main usage scenarios (each can be used as individual steps within a marketing automation program as you design the promotion, reminder, and follow-up campaigns around your webinars):

- Register Attendee: Registers a contact who is in that step of a program with a specific event in WebEx meeting center, training center, event center, or sales center.

- Unregister Attendee: Unregisters a contact who is in that step of a program from a specific event in WebEx meeting center, training center, event center, or sales center.

- Query Attendance: Looks at each contact in that step of the program and queries WebEx to see if they attended and for how long

- All Attendees: Automatically pulls a list of all people who attended a particular WebEx webinar and feeds them in to Eloqua as contacts and places them into a group (where of course they can be fed automatically into a program for follow-up nurturing)

To get started, you’ll need the Cloud Connector installed in your Eloqua instance. This is very easy to do, see the recent post on Cloud Connector Installation instructions for how to add a new Cloud Connector to your install. The Cloud Connector we’ll be looking at here is available on Black Starfish, our repository of interesting connectors. Go to cloudconnectors.eloqua.com and create an account. Under Communication, you'll find WebEx: Register, WebEx: Unregister, and WebEx: Query Attendance, while under Feeder, you’ll find WebEx: All Viewers – those are the connectors we’ll be working with, and the ones to install.



Once you have them installed, you can begin using them within your webinar invitation and management program. The cloud connector steps for WebEx integration can be plugged into your marketing automation program at whatever points make sense, so be sure to whiteboard what you want to have happen and use the steps accordingly.

Likely, you’ll want to use a WebEx: Register step when the buyer has indicated that they are interested in attending, perhaps by clicking a link or submitting a form.


You’ll want to run the WebEx: Query step after the event has taken place to see who attended and for how long. That data can be used to guide prospects down unique follow-up paths depending on their behavior.



Now, for each step, you’ll need to configure the Cloud Connector to do what you need. Each connector is roughly the same, but with slightly different options, but once you have one figured out the rest will be simple. For the sake of simplicity, we’ll walk through the WebEx: Query step. Choose Cloud Connector as a step type, and pick WebEx Query from the drop-down below (if you have installed the connector in your Eloqua instance as we discussed earlier). Click the Configure button to launch the configuration UI.



The connector will need to be configured with your WebEx credentials, the type of WebEx event (ie Meeting Center, Event Center, etc), and the Session ID (from the event details page in WebEx). You can also configure the Session ID to be pulled dynamically from the contact record if you're running a large number of events and want to manage this dynamically.

A final setting is where you want to store the returned information, in the contact record or in a custom data object (data card). If you're running many events, you'll want to use custom data objects to keep a full history of attendance.



With that configured and saved, move to the field mappings tab, and choose the contact fields or custom data object fields that you want to read data from or write data to.


That's all that's needed to have full integration between your WebEx webinars and your Eloqua marketing automation. You can go over to the Run Step tab to run the integration manually a few times to make sure it's all working, or just go to the Credentials tab to click "Enable Step" to enable it to run automatically.



We'd love to hear your feedback on this connector, what can be improved, and what else you need it to do.

Monday, December 20, 2010

Junk Scan - look for bad form data


Anyone who has put up a web form has suffered from bad form data. We all know what it looks like, "aaaaa", "test@test.com", "1@1.com", "asdf", "mickey mouse", "donald duck", "555-1212", the list goes on.

Sure, one option is to only provide access to an asset after sending a person a link, in order to ensure that the email address is valid, but there are many situations where you don't want to (or can't) add in this secondary step. Generally, these are real people submitting the form, so the various tools to prevent bots and spammers are of no use either.

However, having this data in your marketing database does no good either. With it there, your analytics will show incorrect results, segments might pull in bad data, and any of this data that gets passed to sales will immediately decrease marketing's credibility.

Now, to solve this problem, we have a Cloud Connector that does a "junk scan" on your data to look for the typical problems that are seen. It scans first name, full name, email address, and phone number looking for data that is known to be bad or looks suspect, and flags the record in your Eloqua marketing database.

To get started, you’ll need the Cloud Connector installed in your Eloqua instance. This is very easy to do, see the recent post on Cloud Connector Installation instructions for how to add a new Cloud Connector to your install. The Cloud Connector we’ll be looking at here is available on Black Starfish, our repository of interesting connectors. Go to cloudconnectors.eloqua.com and create an account. Under Contact Data, you'll find Name Analyzer - that's the connector to install.



With the name analyzer cloud connector installed, all you need to do is create a step in your marketing automation program - after a web form is submitted, as part of your contact washing machine, or when you analyze your contact data and detect data quality issues. This step will take in contacts, and then the cloud connector will flag them as valid, invalid, or unknown (in a specific field in the contact data), and will also, as a bonus, flag their gender (useful for geographies like Germany where gender is important in building a salutation).



For the step, select "Cloud Connector" as your step type, and you will see a drop-down list of options below. You'll see the "Name Analyzer" cloud connector you just installed via the setup interface in this list. Choose that, and click the "Configure" button to begin setting up the step.



The popup window gives you your configuration options, the majority of which are how you want to flag the contact. You can choose what text you want to mark each contact with for a) gender, and b) validity. For gender, remember that there is an option for first names that could be either gender (ie, "Chris" or "Pat").



Click save on that screen and move to the field mapping tab. As inputs, it will take first name, last name, email address, and phone number, and as outputs, it will write the text you just selected to fields for gender and validity.



You're now ready to go. The validity analyzer looks at the following to figure out whether a person's contact information is valid:

- First Name: to understand if the name is known to exist (by cross-referencing against a database of known names

- Full Name: looking for known bad names ("mickey mouse" or "donald duck" where the first name may be valid itself ("mickey" or "donald")

- Email Domain: looking for @test.com or @1.com

- Email Name: looking for aaa@ or 111@ as invalid email names

- Phone Number: looking for numbers that are too short, all the same number (11111, 22222), or known to be bad (555-1212)

On the "Run Step" tab, you can run the step manually to pull in a few members from the step, and see what the results are, or, if you go to the "Credentials" tab, you can check off "Enable Step" and have the step run automatically.



And that's it, you're done. Now, the contacts that flow through the step will be marked with validity and gender.



Looking forward to your feedback on this. Is this catching and flagging the right garbage names that are input? What other factors do you look for when you're looking at your names manually?

Tuesday, December 14, 2010

Eloqua and Jigsaw Integration for Better Marketing Data


If there is one common challenge that is faced by every marketer who thinks about marketing automation, it is access to up-to-date, complete, clean, and comprehensive data. Asking for data on web forms is tricky in that the more you ask for, the more visitors tend to abandon forms. Similarly, data collected via web forms generally suffers from being less clean and standardized than marketers might like.

For anyone who joined us at Dreamforce last week, you may have seen our Jigsaw integration and realized that it makes some significant strides in solving this challenge. Salesforce.com’s Data-as-a-Service solution, Jigsaw, has one of the best and most accessible stores of crowd-sourced data that is kept up to date and clean. Now, in an easily configurable way, you can access this data source directly from your marketing automation programs in Eloqua.

The Cloud Connectors for Eloqua/Jigsaw integration accomplish three separate integration tasks, but all are set up in roughly the same manner, so the instructions should be easily translatable between the three different connection options.

Contact Search – When you have companies that you’re interested in, whether you want to flesh out the list of the key people at an account that has shown some interest, or to proactively target a territory or a list of named accounts, this connector allows you to find the contacts at those companies who are in key roles. Simply by specifying the role (ie, marketing, sales, finance), level (ie manager, director, vice president), and geography, you can retrieve as many contacts as you specify at each company that flows through a given program builder step

Company Info – When the information on companies in your database goes little farther than a name, you will be very limited in your ability to market to them. This is a common problem when the information comes in via web forms though as company questions like revenue, industry, number of employees, or stock ticker tend to bulk up forms and drive visitors away. With the Company Info cloud connector, you can quickly append and correct this type of information directly from the Jigsaw company database.

Contact Refresh – when a contact enters your database, its information begins to go out of date immediately. Titles change, phone numbers are updated, and new information may be gathered that you don’t yet have. The Eloqua/Jigsaw Cloud Connector allows a contact refresh to append and update any information that Jigsaw has on any contact that flows through a step in your marketing automation program.

To get started, you’ll need whichever of the three Cloud Connectors you are interested in installed in your Eloqua instance. This is very easy to do, see the recent post on Cloud Connector Installation instructions for how to add a new Cloud Connector to your install. The Cloud Connectors we’ll be looking at here are available on Black Starfish, our repository of interesting connectors. Go to cloudconnectors.eloqua.com and create an account. Under Contact Data, you'll find Contact Search (by Company) and Contact Refresh, and under Company Data, you’ll find Jigsaw Company Info. Those are the connectors you’ll need, and the instructions for each one will be relatively similar from here on.

With an account set up and the connector installed into your Eloqua instance, you're now ready to quickly add in data from Salesforce.com's Jigsaw service into any program.


Add a step to your program, in this case we'll look at retrieving contacts at a specific company. The program step, in this case, will contain the companies, and we'll feed the contacts back into a contact group (obviously, if we want to process those contacts, we can just feed that contact group right into a program, but that's another topic).

For the step definition, choose "Cloud Connector", and you should have a drop down of options appear below. If the Jigsaw Contact Search option is not in that list, make sure you added the cloud connector definition to your Eloqua instance as we looked at earlier.



Click on the "Configure" button to pop open the configuration window. This connector will need your credentials for Eloqua (must be API-enabled), and for Jigsaw (it uses whatever license you have with Jigsaw so you will be charged for data accordingly).

In the configuration screen, choose what roles, levels, and geographies you are interested in, how many contacts per company you would like to retrieve. Hit save on this page to save your selections.


On the next tab, field mappings, pick the contact field you would like to save the data in. Jigsaw returns a lot of great information, but if you don't want any particular field, just leave that blank.



When you're ready, you can either go to the "Run Step" tab to run a few trial runs and see what data you'll get back, or just go right to the "Credentials" tab, check off "Enable Step", and click "Save" in order to have the step running automatically.


That's all that's needed. With that enabled, you'll have Jigsaw returning data on the right contacts at the companies you're interested in. The two other Jigsaw connectors, for company information, and for contact refresh, work in a very similar manner. Enjoy, and please don't hesitate to provide any feedback on what's working for you and what's not.

Monday, December 6, 2010

Generic Web Forms from Program Builder


As your marketing automation programs become increasingly advanced, there is sometimes a need to tie into remote systems from half way through a program. Perhaps a lead needs to be created in an proprietary, custom CRM system, or a demo account needs to be registered if a person reaches a certain threshold.

With Eloqua, you can now accomplish this by triggering a generic form submit from any step in Program Builder. Whether the step contains contacts, companies, or prospects, the data on those individuals can be packaged up and submitted as a web form (http Get or Post). Simply create a step in your program, and choose "Cloud Connector" as your step type to access Cloud Connector functionality.



The Cloud Connector step type we'll use for this is Form Submit Contact. If you haven't done this before in your install, you won't see that connector in the drop down list. That's okay, it's really simple to add them. See the recent post on Cloud Connector Installation instructions for how to add a new Cloud Connector to your install.

To find the Cloud Connector for submitting a form, go to cloudconnectors.eloqua.com and create an account. Under Contact Data, you'll find Form Submit (Contact). That's the connector you need, and follow the instructions to install it. (similar connectors are available for Prospects and Companies).



With that installed, you now can select it, and you will see a "Configure" button beside the dropdown that allows you to access the configuration screen.



The first thing to configure is the destination form. Input the form URL on the site you are targeting. (note, that to perform some interesting creative scenarios, you can also point this right back at Eloqua web forms...).

Choose whether you want http Post or Get as your method, and then add any form variables that are submitted with every form regardless of the person.



Then, to configure the set of fields that are submitted from each contact, prospect, or company, click the Edit Fields button. You will see a simple UI that allows you to choose the fields you are interested in, and then provide the HTML name for those fields in the web form you want to submit.



Click the "Set Values" button, and don't forget to hit save on the configuration screen to save these values, and you're all set. Use the "Run Step" tab to do a test or two to make sure that you've set everything up as intended. You'll be able to see what the forms that are being submitted will look like and what data is retrieved for each contact in the step.



When you're ready to go, go back to the "Credentials" tab and check off the "Enabled" checkbox to have this step run automatically.



Now as anyone flows into that step within Program Builder, a form is automatically sent on their behalf exactly as you specified.

Hopefully this capability is useful for you, don't be shy about feedback, we look forward to hearing from you. For those of you who are inspired to do so, please find the instructions to build your own Cloud Connector here. We look forward to seeing what you create.

Monday, November 15, 2010

Creating Reports from Eloqua Discover for Salesforce.com


(guest post from Ben McPhee)

As you may know, we recently launched a new sales tool called Eloqua Discover for Salesforce.com. This application, written entirely on the Force.com platform, provides sales reps both individual and account-level activity insights paired with flexible tracking tools so that they are able to understand which prospects they should be engaging, with what content they should be engaging them and when engagement would be most effective.

But the question comes up:

How can management and executives get the same information? What about the management and executive level folks that do not directly own or engage all sales opportunities but want to leverage the insights provided by Discover to keep track of general activity within territories and understand who the hottest accounts are?


Because of the way Eloqua Discover for Salesforce.com is designed, you can easily generate rollup activity reports right in Salesforce.com based on rep & region and know exactly which Accounts in which regions are most likely to buy. Here’s what it can look like:

The graph below illustrates which regions have the greatest purchase interest at the Account level, broken down by which reps own those Accounts



The graph below illustrates which Accounts are showing the most buying interest, by region. Hovers allow you to quickly see exactly which Accounts are exhibiting the highest engagement



How do you do this? It’s actually pretty straight forward.

In short, you just make a report in SFDC that references a few extra fields that Discover has added to your Account object. You could also do it based on fields added to the Contact and Lead objects (the same fields are added to all), but for illustration purposes, we’ll focus on the Account rollup reporting here.

Once Eloqua is up and running with activity synchs to SFDC and you have installed and configured Eloqua Discover for Salesforce.com, you can go to create a new report.

To create the reports shown above, you will want to create a Accounts & Contacts report, then base it on Accounts.



Select the type of report you want (e.g., Summary) and then when you get to the Standard Summary Fields interface, scroll down and you will note additional fields that have been added to the Account object by the Discover application:



Opt to Sum any of the fields on which you want to report – in this case, we have used Total Buy Signals and Total Open Opportunities (we are using Total Open Opps so that we can filter out Accounts that do not have at least one open opportunity).

Depending on how you want to group the data (e.g., You are interested in seeing, by region, WHICH ACCOUNTS have the most Buy Signals), select the appropriate metrics. For the second graph above, we use the following grouping logic:



Then make sure that in your Columns selection, from the Account: Custom Info area, you choose the 2 new fields – Total Open Opportunities and Total Buy Signals:




Then, make sure you apply a filter that weeds out:
• Accounts linked to no open opportunities
• Accounts that aren’t showing a relatively significant amount of activity



Depending how your regions are broken out, you may also want to generate several different reports only covering certain regions or certain reps (as we have done in this example), so the filters are entirely up to you and will simply dictate the breadth of data you want to cover in each overview report.

Now, you just have to put the finishing touches on your Chart. The below outlines the basic setup for the Hottest Accounts by Region report:



And you’re done!

Now that you can quickly whip up overview reports of your hottest Accounts, Leads and Contacts, Eloqua Discover for Salesforce.com quickly becomes an invaluable tool for not only providing your sales reps with close power but also for providing your sales management and executive team with high-level insight into which regions, reps and accounts are seeing and generating the most interest in your products.

If you’d like some general info on Eloqua Discover for Salesforce.com, please get a hold of your Customer Success Manager and/or check out http://eloquaforsales.eloqua.com/.

A question out to the readers and users – will this type of reporting prove valuable? Why? If not, what are the additional metrics and perspectives that would really drive this over the fence?

Tuesday, November 9, 2010

Cloud Connector Installation, Step by Step


(guest post by Dave Seaton)

An exciting new capability within Eloqua that you may have heard mention of a couple of times is the Cloud Connector concept. Essentially, Cloud Connectors allow anyone in the Eloqua community to build their own steps within Program Builder. If you're interested, the instructions for building Cloud Connectors are here, but for now, we'll focus on installing one that's already built.

Here's a step by step guide to getting your first Cloud Connector installed and ready to go.

1) Enable Account

First you need to have your account set up correctly. Please ensure that your company is enabled for API usage and that the user account you plan on using is enabled as an API user. To confirm your company has the API enabled please contact an Eloqua Product Specialist at 1 866 327 8764. If you are a customer administrator for Eloqua you can go to the user management tab and ensure that the user has the API User role enabled as well as one of Advanced User - Marketing or Basic User - Marketing User Role. Please feel free to contact an Eloqua Product Specialist if you require assistance setting up an account.




2) Find A Connector

With an API-enabled, account, you're now ready to set up a connector. If you have built one already, or have a third party you're working with, great. For this example, we'll use one of the connector prototypes that Eloqua has built, available at cloudconnectors.eloqua.com, but the same sequence of steps is used for whatever connector you're looking to install.

Each connector is identified by a unique code, and a URL. These should either be displayed in the connector's setup screen, or provided to you by your Cloud Connector provider. You will need to copy the Unique Code and Configuration URL into Eloqua.




3) Install Connector In Eloqua

To install this Cloud Connector in Eloqua go to System Management and you will see the Cloud Connector Manager on the left side. (Setup -> Management -> System Management -> Cloud Connector Manager)

Name your Cloud Connector in the service name field, copy the Configuration URL from cloudconnectors.eloqua.com into the service URL field and copy the Unique Code from the provider into the Unique ID field. Click add - you have now created a Cloud Connector!



4) Implement Connector

With this Cloud Connector installed, it will now be an available option within a step in Program Builder. You can use it once, twice, or as many times as you like, as you would a normal Program Builder step. To implement the connector go to the Program Builder module in Eloqua. In a program you need only create a new step and set the default action to Cloud Connector. Then use the drop down menu to select the Cloud Connector you have created.



5) Configure Connector

While editing the default action of your cloud connector step you will need to configure the external program that the Cloud Connector connects to. Simply click on the configure button, login and a window will open that connects you to the login for the Cloud Connector's configuration screen.



You have now installed and configured your first Cloud Connector!

Monday, October 4, 2010

Follow Drake to San Francisco for Eloqua Experience



Hi Eloqua friends - Drake here, your Eloqua Customer Success Tour Ambassador. Today I’m beginning my cross-country trip to Eloqua Experience 2010 where I will be working at the Eloqua University booth. I’m starting from the east coast of the US and making my way by plane and car to San Francisco, arriving on October 17. Why am I telling you this? Because you can follow me along the way, guess my route, and potentially win a $100 iTunes or Amazon gift card. Here’s how:


  • Every weekday I will be posting a clue about where I am on my Facebook wall (www.facebook.com/EloquaDrake) and via Twitter (@EloquaDrake).

  • You can post your guess about my location (name of the city) in the comments on my Facebook wall, then after two more moves I’ll reveal where I was.

  • I’ll be keeping a tally of who has the most correct guesses and that person will win the gift card.

  • Tip: You don’t have to be going to Eloqua Experience to participate, but if you are going to be there, I’ll also throw in an extra gift onsite at the event as well.

Here are a few more pieces of information about the locations I’ll be visiting:



  • They’re all US cities with populations over 100,000

  • When I fly, I’ll be flying on Continental non-stop

  • When I drive, it will be somewhere that I can get to within 8 hours in a car (which will really only take me 6 hours, heh heh) – in other words about 500 miles.

  • I won't ever backtrack - my movement will always be in the direction of San Francisco

Visit me on Facebook today for my first clue about my starting point city.

Tuesday, August 31, 2010

Win a Free Ticket to Eloqua Experience!


(guest post from Adrian Chang)

Are you Eloqua's biggest fan? Share why on our Facebook Fan page and you can win a free ticket to this year's Eloqua Experience in San Francisco from October 18-20.

We are looking for you to share 10 Reasons why you are Eloqua's biggest fan. Be creative

- write a poem, create a YouTube video, or use photos to craft your submission. You will post your entry on our Eloqua's Facebook Page - www.facebook.com/eloqua.

Rules
· One entry per Eloqua Fan - make it count!
· You must be a fan of Eloqua on Facebook (Go to www.facebook.com/eloqua and "Like" our page)
· This contest is for Eloqua customers only
· You may use Twitter to promote your entry and link to our fan page - please use #1EloquaFan for the contest.

Also, if you want to make mention of this year's Eloqua Experience, please use #EE10SF.

Judging

The winner will be selected by a committee of Eloqua employees. The committee will review entries based on creativity and response from the Eloqua community (Likes, Comments).

Duration

Starts September 1st through the 15th (ending at 11:59pm PT). Winner will be announced on September 17th.

Prize
One (1) free ticket to Eloqua Experience. Current registrants may still apply - you will be reimbursed in the event that you are selected as the winner. Also, the winning entry will be featured during the conference.

Eloqua Employees, Customers and Partners – How can you participate?

1. If you are a Facebook User, please ensure that you are a Fan of Eloqua. Go to www.facebook.com/eloqua and
"Like" our page

2. Highlight the entries that you like by commenting or click on the "Like" button for any entries

3. For general guidelines as to how you can participate in Social Media - http://blog.eloqua.com/eloqua-socialplaybook

Any questions? Please contact me Adrian Chang at 416.642.7586 or at adrian.chang@eloqua.com