Topliners Theme
1 3 4 5 6 7 Previous Next

Do It

494 posts
After having spent an intensive year on the platform I've collected a handful of tips & tricks from Eloqua support, colleagues, Topliners and sheer accident.


  1. Moving members around on the Campaign Canvas:
    • Once you have a campaign activated, and the audience members are located in various steps of the campaign canvas, you can manually move the members around to other steps. To do so, double click on the bubble in the top right-hand corner of the canvas element > the "View Campaign Step Members" window should pop up > now select some or all of the members > look at the bottom of the pop-up window. The "move" button should now be click-able. If not, you may need to save your campaign then return to this point > Click the "move" button > you will now see the campaign canvas with all the elements available for your move highlighted. Choose the appropriate one > Hit "move members" at the bottom of the window > done!
  2. If you have dirty data and you don't have a contact washing machine built yet, build it. Do not export your data to Excel for cleaning. Using Excel to clean data certainly works and it's comfortable, but if you force yourself to spend the extra couple of hours to setup a simple program to clean up a small data problem you can then add to that program as you encounter new data issues. And when you discover other data with the same old problems you do not have to duplicate your work.
  3. You can run validation rules against shared lists. If you are building and testing a contact washing machine or if you are doing some simple, non-repetitive data cleaning it's handy to know that you can open any shared list, hit the gear icon on the top right-hand side, select "validation rule" and then select from any existing validation rule to run against a set of contacts on the fly.
  4. If you are uploading large files (possibly for a migration) you may run into a timed-out issue when uploading from the desktop. To get around that, upload via SFTP instead of directly from your desktop. The SFTP upload option does not have a timed-out limitation.
  5. You can see the upload history of files by going to the Integration screen. To get there, go to the Eloqua setup screen, select "Integration", select the "Inbound" tab, hit the "Reporting" drop-down and select "Upload history"
  6. In addition to #5, keeping the file upload notifications that Eloqua sends provides a very simple way to keep track of data uploads. Every time data is uploaded into Eloqua a notification email goes out (or can go out) to the user. These notifications can serve to help you quickly figure out what file was uploaded for that rush segment you built 10 months ago. I recommend building a filter in your email client that stores all of your Eloqua notifications in one folder. Then when you need to find out the details of upload id #12345, just go to your email client, search for that number, and you will find the notification email that contains the upload file name and number of users successfully uploaded.
  7. If you're working with a colleague on a campaign, segment, email or landing page you can reference the ID of the item instead of the name. If they are logged in, you can even just send them the link:
    • It's also worth noting that when you are on the phone it is much easier to tell someone to check out campaign ID 12345 than to spell out a complex name
  8. Naming conventions are important. Wildcards are cool. When you are searching for a segment that begins with BLUE and ends with RED, try searching for this: "BLUE*RED" - this will return everything beginning with BLUE and ending with RED. The magic here is that this approach works across E10, including in the configuration menus in the Campaign Canvas elements


I hope this is helpful to a few of you. Please do feel free to add your own in the comments below.


Birthday Campaign Ideas

Posted by ldfarah-Oracle Feb 28, 2014

So it's my birthday today (well, technically, I was born on the 29th so this year the 28th is as close as I can get) which means I'm getting all kinds of birthday greetings via email, text and social media. Interestingly, each year I notice that get more and more well wishes through these same channels from the businesses I frequent as well. Of course I know that the businesses haven't *actually* remembered my birthday (and let's be honest, my friends and family probably wouldn't remember either without Facebook), but the truth is that it still feels nice to watch them come in throughout the day - automation notwithstanding.


Setting up a simple birthday campaign that sends a personalized greeting to your customers (or heck, even your employees - check out the how-to for that idea here: Sales & Marketing Alignment the Human Way - Part 2 of 3) is an easy way to add a lovely, non-sales centric touch to your ongoing communications strategy. If you haven't set one up yet, now is a great time to add the idea to your to-do list. Because really, why not?


Some things to consider before you begin:

  • Data: How confident are you that the birth date you have on file is correct? The last thing you want to do is get their birthday date wrong, so make sure you start with sparkling clean data (check out Benefits of Quality Data for tips, or consider sending out a birthdate verification email like this one from West Elm).
  • Timing: Are your recipients in time zones that might make your greeting arrive too early or too late? Use the handy Time Zones Across Eloqua guide to make sure your message arrives when you want it to.
  • Channel: While sending a greeting via email is a great option, nothing beats receiving a physical card in the mail (and yes, Eloqua has an app for that: The specified item was not found.). And consider social and SMS options as well if those make sense for your audience (check out our AppCloud for options that plug directly in to your Eloqua campaign).
  • Content: A birthday greeting doesn't have to be content heavy. A simple text or graphic greeting is probably sufficient - it's the personalization that makes all the difference (be sure to use Gain Your Hours Back | Personalization as a guide).
  • Call To Action: Decide if you really want or need one. Your message should be about *their* birthday, not your sales cycle. Still, if it makes sense within the context of your business to offer a gift, a special discount or something similar in honor of their big day, feel free!


Many happy returns!

Want to make an image dynamic for each recipient based on a field merge?


A big thank you Rob Sommers on this one! I hope this document makes it easy for others in the future. This is my first 'blog' and technical tip - a shame after 3+ years of being in Topliners!


We had a tradeshow in which a QR code was used for checking in. Our team wanted to keep the email in Eloqua and not use another tool to send the email. First thing that came to mind? ACD - but was I really going to upload 200+ QR codes and create 200+ rules for each individual in the ACD Rules? No way! Eloqua support had recommend this as well. Determined to find an easier, streamlined method I took to Topliners and Rob Sommers had the solution!


Use Cases:

- Append your URL with a SFDC Lead or Contact ID with the field merge

- Append a random or personalized string in the URL

- Dynamically display an image based on a field value (w/Images being hosted externally)


Be sure to post your use cases below!


Steps to Success

1. Create a new Field Merge

2. Upload images to an external FTP site

3. Create an Excel sheet mapping your image file names to each customer

4. Add your field merge to the email.

5. Test!


1. Create a new Field Merge

With the field you wish to use to store your image file names, create a field merge. Check out the guide here: The specified item was not found.


2. Upload Images to an external FTP Site

Upload all of the images into a folder on your FTP site -> make note of the entire URL until that directory. For this example, we will use - this is your Base URL


**Note: Make sure each file name is unique to each customer.


3. Create an Excel sheet mapping your image file names to each customer

The easiest way to get each file name is to keep all of the images in one directory. Use this guide to get the file names into a .txt file How to create a text file list of the contents of a folder. From there, copy the text over into an Excel file and map each file name to the right email customer.


See the attached file as an example. Once the file is ready, upload it into Eloqua and map it to the right field.


4. Add your field merge to the email

1. The first thing you want to do is place the field merge anywhere in the email - this will help us get the needed code for the field merge:

2. Next you want to right click the email text and hit Edit Source:

3. Once in the edit source, you will find the code for your field merge, it will look something like this: <span class="eloquaemail">QR_Code1</span>

4. Now we want to place this code into the code of your image source For this, take your base URL and append your field merge to the end - should look like this:

<img src="<span class="eloquaemail">QR_Code1</span>">

Final Step: remove the quotations around the "eloquaemail" to leave you with the code below:

<img src="<span class=eloquaemail>QR_Code1</span>">


That's it! Place the image where you need it in the email and it will look like a little square - since it's dynamically pulling it in, don't worry!

5. Test!

Simply hit the settings gear and hit 'Preview'. in the preview pane, choose a contact which you know should have the image and hit preview:

Boom there it is! and you are done! To be on the safe side and as a sanity check, randomly check a handful of contacts to make sure the image is rendering.



A similar approach of taking off the quotations can be used for simple URLs instead of an image as well.

If you have any questions please feel free to post them. Any comments or recommendations on guide would be great!

hey i am getting an error..ERROR

The remote name could not be resolved: 'https' on CRM system fields..when trying to integrate eloqua and crm on demand

Our Winter'14 Release will be rolled out to our Eloqua Production Instances between February and March, 2014.

Find out when you will receive the Winter'14 Release

  1. Log into Eloqua as you normally do
  2. Look at the browser URL once you are logged in
  3. Use this chart to determine when you'll receive the Winter'14 Release in your Eloqua Install


BROWSER URL WHEN LOGGED INTO ELOQUA  RELEASE DATE, Feb 4, 2014:  11:00 pm - 5:00 am on EST Wed, Feb 5

Sunday, Feb 23, 2014:  5:00 am - 11:00 am EST    (note:  no number included in URL)

Sunday, Mar 16, 2014:  5:00 am - 11:00 am EDT


For more information on the Winter'14 Release, please visit the Release Resource Center (Eloqua Insiders Area)

Every now and then I get emails that I feel compelled to share. As marketers we're always looking for ways to engage our audiences, and Welcome Campaigns are just one of them. When I think of a Welcome Campaign, I feel that one of the main purposes is to clearly state how you will be communicating with your contacts, and to let them set their own preferences (if they choose). This is also a fantastic place to note your social channels, if you have any, so that they have alternate options of communicating.


After entering a contest through another company, I received this email from one of the contest sponsors:




I love how this email clearly states the communication timeline, and gives a chance to change those settings. I also love the invites to the social media channels, and their SmartPhone application.


No need to be fancy - email campaigns can be simple and to the point!

When our company began using Eloqua 10 we found that we needed a way to reserve segments to be used for future dates. The idea here is that by reserving a segment you could then suppress those users from similar emails going out in the same time frame. By using a combination of a shared list, a segment and the campaign canvas I was able to approximate this functionality. This is not a perfect solution and it requires a bit of work (you end up building a campaign for each week of the year), but it does ensure that our audience is not inundated with a wave of similar emails on the same day or week. Additionally, if we provide a quote to a client or salesperson for a set number of emails, by reserving the segment we know that we have that same number of users available to be targeted on the day requested.


A simple alternative to the method I describe below involves building a shared filter: Build a shared filter that filters for users who have received at least one email from the email group you are interested in within the past day, week or whatever time range you like. Add that shared filter to your campaign as a decision step. Users that get caught in the filter can either drop off of the campaign or you can put them in a wait step and run them through the decision step at a later time. This approach works well if you do not need to guarantee a certain number of emails going out on a certain day.



In the end you will be scheduling and suppressing users contained in segments based on the type of email group they are going to be emailed. In this case, we are using an email group "Press Release" as an example.


The workflow:

  • A marketer informs you that they need a set of names that meet a certain criteria for a press release email for a new product announcement happening next month.
  • You build the query in Eloqua, save the segment and you report back to the marketer letting them know the number of names you have available for them.
  • The marker replies happily with: "Excellent - I want to target all those names. We must email all of these users on 02/05/2014. I'll get you the HTML a few days before then."
  • You now need to reserve the names in this segment because you know that there are going to be a series of other press releases going out that same week and you don't want to hit the same audience with a multiple emails that look the same a muddle your messaging.
  • When the next marketer requests a similar mailing for this same week, as you build the segment you will exclude the names that are already reserved. The count that you provide for this second request will reflect what is actually available.


Built it:

  • Create a new shared list called 02-03-2014 Fatigue Press Release (note that 02/03 is the Monday, the first day of the week for the week of our scheduled email)
  • Create a new segment called 02-03-2014 Fatigue Press Release
  • You only need to add one criteria to this segment: "Sent Emails from Email Groups" - set the email group to the type you are concerned with and set the date range as "within 2/03/2014 - 02/07/2014"
    • Why bother with this step if we only care about segments scheduled in the future? Because adding this segment means that if we accidentally forget to schedule our segments, at least they will get added to our system once they deploy.
  • Build a campaign called 02-03-2014 Fatigue Press Release
  • Now, add the segment and shared list we built and add one wait step. Set the wait step to hold for 90 days.
  • Connect the elements as in the image below:




  • Now, right-click on the segment and select "configure" and chose the selection for "add members hourly until campaign is deactivated"
    • Note: only make this setting for this one segment. The other segments should have standard configuration.


You are now at a key point in the process.  If you stop adding items to this campaign and go ahead and activate it, you will have a built a sort of collector campaign . It will will add anyone who gets sent an email of the type you specified in the 2/03/2014 - 02/07/2014 date range to the shared list.


  • To make the magic happen, you need to add the segment that you want to have reserved to this campaign, then activate the campaign. Like so:


  • Activate the campaign now. Users will flow from the "segment that I want to reserve" into the shared list. And now that those users are in a shared list you can suppress them from any segment or campaign.
  • When you need to schedule another segment for this same week, just deactivate this campaign, add it to the campaign, and reactivate it.


Rinse and Repeat:

  • The ugly side of this process is that you have to create a new shared list, segment and campaign for each week. But you can speed up this build process by building all these elements in big chunks of time. Once you are comfortable you should be able to build a few months worth in just an hour.



  • What if you forget to add segments to the reservation campaign? If that happens, some users may get a few extra emails, but by adding that first segment to the campaign those users will still get added to the shared list once they get sent an email. So if you are building segments later on during the week, at least the users who got an email on Monday are going to be included in the shared list.
  • Before you jump into this, consider how many segments you would be adding to one of these campaigns and how often a segments gets rescheduled.
  • You can, of course, include multiple email groups in this one setup. You would just need to add those email groups to the filter criteria of the one segment that you build for each week.


Please let me know if I can clarify anything or if you have suggestions for a better approach.

When adding custom fields to a form, there can be some confusion regarding what values are saved when a form is submitted. The custom field that often inspires the most debate is arguably the single checkbox. Here's an inside peak into what IS saved, and what isn't.


If someone selects or 'checks' a single checkbox, the value that is saved to Eloqua is "on". This can be found by navigating to the submitted form and then clicking on the action gear drop-down and selecting View Submission Data:


Single Checkbox selected.JPG.jpg arrow.JPG.jpg   on.JPG.jpg


If someone does NOT select a single checkbox, or leaves the checkbox 'unchecked', there is no value saved to Eloqua:

Single Checkbox.JPG.jpg        arrow.JPG.jpg   blank.JPG.jpg


So, if you are making a processing step conditional, based on someone selecting or not selecting a checkbox, you'd configure it as "on" for any conditions dependent on it being checked...


processing on.JPG.jpg

and you have TWO options for configuring a condition dependent on a single checkbox NOT being checked:


1. not exactly "on":




2. exactly "blank" (the text field is left empty):

processing blank.JPG.jpg

I keep a gmail account that I use for testing client emails. I'm not sure how, but this account has been running on the newer Gmail platform (with Gmail tabs) ever since I opened it, even while my personal gmail does not. When I logged into this account this morning, I saw some interesting news.


The first was this survey question. Of course we can only speculate at this point, but it looks like they may start sorting emails somewhat differently depending on the way you're using the account.

Screen Shot 2013-12-19 at 9.43.52 AM.png

Secondly, and I take this as great news!, Gmail is now auto showing images. This was always one of my biggest gripes, especially as an email marketer. For B2B senders, this isn't usually as big of a deal, as most emails are more text heavy than content heavy, but for B2C senders, whose emails are primarily comprised of images, this is awesome!


Screen Shot 2013-12-19 at 9.44.17 AM.png

Anyone have any other speculations?

It has been a while since I wrote a post to Topliners (and truthfully, my Topliners points are craving my return to the top 100!) so I pondered about a topic that is very important but may not get all the credit it deserves. Your subscription management strategy should be just as important as your creative lead generation campaigns, but many companies still have limited to no options on how contacts are communicated to and their ability to determine their preferences. Hopefully this post has you review your current subscription strategy and opens the door for a review or optimization of your existing process.


This immediately got me thinking - what are some great resources, examples that I have shared with clients to help them along this path! I can not take all the credit as there have been folks before me that have talked in length about this so I figured I would share some of these awesome resources. To end, I will share my secret sauce to subscription management success.


I start with my colleague, crowds2crowds from who boldly demonstrated in a great blog two great examples of Email Subscription Centers that allow the end user to determine how they want to be communicated with. His examples though very different still provide a good resource to get your company thinking!


I found this blog post from HAVAS DISCOVERY which immediately connected with me as the purpose of a subscription center is to allow the contact to "Opt-Down and no Globally Opt-Out" by providing options that clearly speak to your companies areas of interest and determine communication frequency levels.


When thinking subscription management here are my top 5  items to consider:


  1. How easy is it for someone to determine how often they would like to be communicated to?
  2. How user friendly is your subscription center?
  3. Are you giving your contacts several things to unsubscribe from or are they only given a global opt out? (there is no magic number here, you just need to find the 'sweet spot' between cumbersome and clunky and non-existent)
  4. Is there an opportunity for the contact to update their existing profile?
  5. Are you currently marketing to countries in Europe? If yes, is your subscription management compliant with European laws?


I'd love to hear your feedback and thoughts on what your organizations are doing. If you have pages you'd like to share, myself and I trust the community would appreciate it!


Thanks -


Jason Pemberton

Director, Key Accounts


Yes we all know that progressive profiling is pretty cool and we all want to implement it.

Couple if months back I jumped into this adventure too. Here is some background of we I wanted to it.



Our Trial download form had 15 fields, 3 of them helped lead routing in SFDC (Country, State and No. of employees )

Others were profile or contact info product of interest etc... Once the forms is submitted the user were sent a trial key and a URL to download the .exe file.


Once the user download the trial and start the installation process we asked for Name, Email and product key. In-case if anything was different a duplicate record was created and this lead to lot of issues.



Many system for involved, like Website form passed to Elqoua and a Key Gen service. The info passed to SFDC.



1.Simplified form with 4 fields with product of interest selected from whichever page the form gets accessed form.

2. Created a web services that links the email to the Key Generated.

3. When the user put the key in the installer we did a web service call and pulled the email back. which meant we did not ask for email, name, company etc...

4. Made Country, State and No. of employees pick list so room for error.

5. Lastly created a survey at end of trial finish profiling.



No more duplicates.

Clean data, higher form completion.

Increase in Trial activation result to Higher close rate.


If need more detail please contact me.

That’s right, folks. Nearly three years after receiving Royal Assent and going through a seemingly endless set of delays, comment periods, and guidance changes it appears that Canada’s Anti Spam Legislation (CASL) is finally coming into force. Canada’s Minister of Industry James Moore announced today that CASL will come into force on July 1 2014. Eloqua’s Dennis Dayman posted about the announcement here.


We wrote about CASL at length here but as a quick reference, these are a few of the main points of the law:


  • CASL requires express consent. This means NO pre-checked boxes.


  • CASL is not just an email law.
    • It covers installation of computer programs without the end user’s consent
    • It covers any Commercial Electronic Message (CEM). A CEM is defined as any electronic message that encourages participation in a commercial activity. A CEM could for example be:
      • Email
      • SMS
      • Instant message
      • Some social media messages


  • It covers any CEM sent TO or FROM Canada. The CRTC will work with international regulatory bodies such as the FTC to ensure compliance by parties based outside of Canada’s borders.


  • Prescribed information is to be included in every CEM as well as any request for consent. Requests for consent are also covered by the law, which means that they cannot be sent without first obtaining express consent.


  • Existing contacts cannot be ‘grandfathered’ in most cases and will therefore require marketers to gain affirmative consent from their Canadian contacts before the law comes into force. Addresses who have already opted in under PIPEDA may however be permitted.


  • Fines are steep, up to 10 million dollars per violation and private rights of action are permitted.


What’s next?


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

Often you may encounter a situation where a salesperson needs to change the email address on a contact record in your CRM.  Since Eloqua uses email address as the unique identifier, the auto-synch will run and try to find a match using the new email address. However, since this change has only been made in the CRM, it will not find a match in Eloqua and therefore create a new record instead of modifying the existing contact.  Ideally you will want to configure your integration to update existing contacts in cases such as this in order to avoid sending duplicate communications a two addresses owned by the same contact, or sending emails to an inactive address.


There are two ways to change the email address on an existing contact:


  1. Perform and upload with the purpose of “Change Email Address”.  This will allow you to upload a file containing a list of old email addresses and new email address, and Eloqua will make the updates.  Jordo’s Playbook outlines a solution using this method for CRM systems track contact field history (such as Salesforce)
  2. Perform a contact upload using a field other than email address as the unique identifier for the purpose of the upload.  This is the method we will be using in this solution.


In order to automate email address changes using a unique identifier other than email address, we need to find a field that exists and is unique for all contacts in Eloqua; for this purpose we will be using the Eloqua Contact ID field.  This is a system generated ID which is assigned to an Eloqua contact upon creation.

We also need to ensure that this same unique identifier is available on any leads or contacts in your CRM system.  This is easy for leads created by Eloqua (just map Eloqua Contact ID in your Create Lead external call), but can be a bit trickier for leads created directly in your CRM.  We can account for both kinds of records using the following process:


Standard Integrations

  1. Create a field in your CRM system called “Eloqua Contact ID”
  2. Update your Create Lead, Update Lead and Create Contact External Calls so the Eloqua “Eloqua Contact ID” field is mapped to the corresponding field in the CRM.  This will ensure that all leads originating from Eloqua will have an Eloqua Contact ID.  To handle contacts and leads who originate from the CRM, we will need to make changes to our auotsynchs.
  3. Create a new Get Leads autosynch and a new Get Contacts Autosynch (Jordo's Playbook contains step by step instructions for creating autosynchs), and add a filter to the syncs so that they only retrieve leads/contacts who have an Eloqua Contact ID in the CRM.  Both of these synchs should use Eloqua Contact ID as their unique key.  This will ensure when any lead or contact in your CRM who has an Eloqua contact ID changes their email address, Eloqua will update their existing Eloqua contact record instead of creating a new record.
  4. Create a new Integration rule collection called Update Eloqua Contact IDs.  This collection should contain 2 rules:
    - If a contact has a CRM Contact ID, run the Update Contact external call- If a contact has a CRM Lead ID, run the Update Lead external call
  5. Create a second Get Leads autosynch and a new Get Contacts autosynch (Call them Get Leads (Email) and Get Contacts (Email) to keep things straight).  Add a filter to these syncs so that they only retrieve leads/contacts that do not have an Eloqua Contact ID in the CRM. Both of these synchs should use Email Address as the unique identifier
  6. Modify the Upload action on the Get Leads (Email) and Get Contacts (Email) autosynchs, and configure it to run the Update Eloqua Contact IDs integration rule collection.  This will ensure that any time a record without an Eloqua contact ID is brought over from your CRM, Eloqua will immediately update the CRM record with the Eloqua contact ID.  This means that a contact will never come through the email autosynchs more than once.

to recap, in total you should have 4 autosynchs:


Get Leads (Eloqua Contact ID) – Will run on all leads with an Eloqua contact ID.  Matches Eloqua contacts using Eloqua Contact ID as the unique identifier

Get Contacts (Eloqua Contact ID) – Will run on all leads with an Eloqua contact ID.  Matches Eloqua contacts using Eloqua Contact ID as the unique identifier

Get Leads (Email) – Will run on all leads without an Eloqua contact ID.  Matches Eloqua contacts using Email address as the unique identifier, and executes the Update Eloqua Contact IDs integration rule collection to write Eloqua Contact IDs to your CRM

Get Contacts (Email) – Will run on all leads without an Eloqua contact ID.  Matches Eloqua contacts using Email Address as the unique identifier, and executes the Update Eloqua Contact IDs integration rule collection to write Eloqua Contact IDs to your CRM

Custom Integrations


For custom integrations using the Data Export and Import area of the application, the steps are a little different since Data Imports do not have upload actions which can be used write contact IDs back to your CRM.  If you have a data import/export based integration, your solution will look like  this:

  1. In Eloqua, create a new checkbox contact field called “Sync Contact ID”
  2. On your CRM side, create two files for import into Eloqua, one should contain all contacts to be synced over from your CRM which have an Eloqua Contact ID, and one should contain all contacts to be imported that do not have an Eloqua Contact ID
  3. Set up an import to pull in the contacts that already have Eloqua contact IDs, this should use Eloqua Contact ID as the key field.
  4. Set up an import to pull in the contacts that do not have Eloqua contact IDs.  This import should use Email address as the unique key.  Every record in this import should also write a value of TRUE to the “Sync Contact ID” field
  5. Create a new segment called “Contact IDs to be synced”.  This segment should contain one filter which looks for any contacts that have a value of TRUE in the “Sync Contact ID” field.  Share this filter and save the segment
  6. Create a new export to push contact IDs to your CRM system.  This export push all of the members of the “Contact IDs to be synced” segment to your CRM and should be scheduled to run 1 hour after your imports.
  7. Create a new program in program builder with three steps:
    i. Wait two hoursii. Run Update Rule – Set “Contact IDs to be Synced” to FALSEiii. Remove from program
  8. Set up a feeder on this program to feed the members of your “Contact IDs to be Synced” filter to the program after your imports run.  This program will ensure that contacts are removed from the “Contact IDs to be Synced” segment after they are pushed to the CRM system



To recap, in the custom integration solution you will have:


Two imports

  • One to bring in records with an Eloqua Contact ID using Eloqua Contact ID as the key field
  • One to bring in records without an Eloqua Contact ID using Email Address as the key field, and writing a value of TRUE to the “Sync Contact ID” field

One Export

  • This Export will push all contacts with a value of TRUE in the “Sync Contact ID” field to your CRM

One Program

  • This program will clear the “Sync Contact ID” flag after contacts’ IDs have been exported.

Sharing problem.

Posted by masoud.banbersta Nov 25, 2013

I can't share content with my network. Whenever I try to share the following message appears.

Your content could not be saved due to an error. You may have been logged out. If this problem persists please contact your system administrator. Click here to refresh this page.

I refresh the page and make sure that I´m Logged in and still receive the same message. Who knows what the problem is? Thank you in advance!

In using the campaign object we ran into a challenge. The standard fields for a campaign are simply sent and responded. We wanted to expand the options for some campaigns to other statuses as well. For example email with landing page we wanted (sent, email opened, form fill). We wanted to standardize this so that the fields are the same every time a marketer chose it. This is not possible directly in SFDC.


Fullcircle CRM has an appexchange program that is very reasonable that allows you to do just that. You can setup standard or custom member status values by campaign type and then they are always standardized. Not sure if anyone else has tried to solve this one, but wanted to share.


The Easy Campaign Member Status Manager from Full Circle CRM enables you to define standard or custom member status values by campaign type. Set up your default values, and never have to worry about them again!


Easy Campaign Member Status - Full Circle CRM - AppExchange

Filter Blog

By date:
By tag: