In previous posts about building cloud components, specifically in reference to the renderInstance endpoint, we touched on the ability to receive additional parameters from the Cloud Components framework.


By adding extra query string parameters to your endpoint address, an Asset ID, Contact ID, or Visitor ID can be passed by the Eloqua platform into your application.


As an example, let's look at the following endpoint address.{Id}&assetId={AssetId}&contactId={ContactId}&visitorId={VisitorId}


Notice that, in addition to the {Id} parameter, this service is requesting values be merged into {AssetId}, {ContactId}, and {VisitorId}.  When the Eloqua landing page is rendered, and this endpoint is called, the landing page ID (AssetId), Eloqua contact ID of the page visitor (ContactId), and Eloqua visitor ID (VisitorId) will be passed to your application.  (Note: The contact ID and visitor ID will only be populated if the page visitor is a known Eloqua contact or cookied visitor)


Once your application receives these values, you can use them to "personalize" your component.  For instance, using the contact ID or visitor ID and the Eloqua API, you could look-up other information on the page visitor and use that to display targeted content.  Or, if you are a video provider, you could use this information to track viewing data, and build a Feeder to pass the data back into Eloqua.


As you can see, there are many possibilities, and I think you'll agree that this is a pretty powerful capability.


Keep this in mind when you are building your component!