Now that we've looked at Event / Webinar Cloud Apps - Registering Dynamically, let's look at how to dynamically query for attendance.


There is a new capability within the Event/Webinar cloud apps (WebEx, Adobe, Citrix GTW) that allows you to dynamically source the ID from either a contact record, or a custom data object.


In the previous post, we registered the contact for an event, sourcing the ID from the contact record.  When we did that, the connector created a Custom Object/Data Card, mapped to each contact record, that contained the Event/Webinar ID.  We want to use the ID contained in that same Custom Object / Data Card to query for attendance.  When the attendee is found, we also want to write the attendance data back to the same Custom Object / Data Card.


Let's start by setting up a Query connector.  On the Configuration page, choose to source the ID from a Custom Data Object Field.



If you choose the source type of Dynamic (in a Custom Data Object Field), when the connector runs, it will look at the contact and find all of their mapped Custom Objects/Data Cards in the chosen Custom Data Object/Data Card Set.


Now let's set up a rule to handle the case where multiple custom objects are returned for a given contact.  In the Dynamic Event Source Configuration section, choose your Selection Rule.  Based on your choice, the section will be displayed as follows:

Eloqua Cloud Connectors - Step Details - Google Chrome_2013-02-15_15-45-30.png


Eloqua Cloud Connectors - Step Details - Google Chrome_2013-02-15_15-45-43.png

The Selection Rule will be evaluated against to field chosen for Field to Evaluate on the Mappings page.  The choices are as follows:

  • Latest of Date Values - Returns the object with the field containing the latest (most recent) of date values.
  • Earliest of Date Values - Returns the object with the field containing with the earliest (oldest) of date values.
  • Field Contains Value - Returns the object with the field containing the Comparison Value.
  • Field Equals Value - Returns the object with the field exactly matching the Comparison Value.


We now have our rule for matching, but we'll need to chose the Field to Evaluate, as well as the Custom Data Object field that contains the Event/Webinar ID to use for the query.



When the connector runs, if multiple records are found, it will apply the Selection Rule to the Field to Evaluate and return the matching record.  It will then and retrieve the Event/Webinar ID from the chosen field in the Custom Object, and use that to query for attendance.  The attendance data will be written back to the same object that acts as the source.


By using these new dynamic ID source capabilities, you can streamline your Event/Webinar management.