In addition to the recent release of Form Tools - Running a Cloud Connector via Form Processing Step, enhancements to the Eloqua Event/Webinar apps were also introduced.  Now you can Form Tools - Running a Cloud Connector via Form Processing Step, and also use a field on the contact record or a mapped Custom Data Object, as a dynamic source for the Event/Webinar ID.

 

This means that you can use the same custom object created when you registered the contact, to query for attendance and hold the returned data.

 

To see this in action, let's first configure a Form Tool to register a contact. (Note: this will also work when running the Register connector on the canvas or program builder)

 

Start by following the step from Form Tools - Running a Cloud Connector via Form Processing Step.

 

On the Configuration screen, let's choose to source the ID dynamically from a contact field.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-19_16-07-51.png

If you choose the source type of Dynamic (in a Contact Field), when the connector runs, it will look for the ID in the contact field that you specify on the Mappings page.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-20_11-26-39.png

By doing this, we can use the same connector to register contacts for different events/webinars.  So, we can put a form field containing the ID (hidden or shown) on your registration form and map it to the contact record.  When the contact submits the form, the ID will be written to their record.  Now, when the Form Tool executes for the contact, it will use the ID found in the field and register them for that Event/Webinar.

 

The other thing we'll do is save the Join URL, Event/Webinar ID (and any other returned data) to a Custom Data Object/Data Card Set.

Eloqua Cloud Connectors - Step Overview - Google Chrome_2013-02-20_10-12-16.png

When the connector executes, it will create and link a new Custom Object/Data Card to the contact, in the specified Custom Data Object/Data Card Set that contains the Event/Webinar ID.

 

Now for the really cool part...we can use this same Custom Data Object with the Query connector, and dynamically source the ID from the Custom Data Object itself.  So, we can use the same object to hold both the Register information (Join URL etc) and the Query results (minutes attended, polls answered etc.).

 

See Event / Webinar Cloud Apps - Querying Dynamically for details on how to do this.