Skip navigation
1 2 3 Previous Next

Do It

32 Posts authored by: TJ Fields-Oracle

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

Company Scoring Cloud App

 

This post will describe the Company Scoring Cloud App, and how to use it within your instance of Eloqua.

 

With the Company Scoring Cloud App, you can now score a company based on the activity of contacts associated with it.

 

In order to use the App, you must be registered at cloudconnectors.eloqua.com.  When creating your account, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Company Scoring Cloud App Components

 

The Company Scoring Cloud App consists of the following Cloud Connector:

 

    • Company Scoring- allows you to score a company based on the level of activity seen from contacts at the same company.

 

Components of the AppCloud

 

Installation and Configuration

 

To install the app in Eloqua, do the following.

 

Log into cloudconnectors.eloqua.com and click on the Apps menu.

ConnectorSelector.png

 

 

Click on Company Data, then Company Scoring, and the following screen will appear:

InstallConnector.png

Click on Install Connector.  You'll then be shown the installation screen.

InstallConnectorDetails.png

 

 

 

If you are an Eloqua administrator, you can click on Add Connector, and it will take you to the Cloud Connector Management area in your instance, with the install settings pre-populated.

You can also choose to do a Manual Install (note the settings above) and then go into the Cloud Connector Management are in your instance.  Enter the settings as shown below.

 

CloudConnectorSetup.PNG

 

CloudConnectorManagement.png

 

  Enter the following information:

 

To configure the App, do the following:

    • Add a step to your marketing automation program at any point you would like to run the company scoring connector on a Company/Account record.
      • Note: The Cloud Connector will run on any Company/Account that flows into that step, and return the result to another field within the Company/Account record.
      • Make sure that you have an account on cloudconnectors.eloqua.com.
      • Created a new step with a default action of Cloud Connector, and select Company Scoring:

PBStep.png

PBCloudStep.png

 

      • Click on the Configure button.

 

    • When the Login screen appears, enter your cloudconnectors.eloqua.com credentials and click Log In.

CC_Login.png

    • Next the first setup screen for the App will appear.

CC_Config1.png

 

    • The values for Eloqua Client Name and Program Builder Step ID will automatically populate.  Enter the remaining information, then click Go.

 

    • The Configuration page will then be displayed.

Config.png

 

On the Configuration tab, enter the following information:

      • Description (optional):  Some text about this connector instance
      • Company Scoring Approach: This is the calculation that the app will perform on the contact scoring field (chosen in the next step) for all contacts associated to the company.  Options are shown below:

ConfigScoringApproach.png

 

      • Click Save Settings.

 

    • Next, click on the Mappings tab.

Mappings.png

On the Mappings tab, choose the following:

      • Contact Score Field:  The contact field that holds score that you wish to use, along with the Company Scoring Approach, to calculate the score for the company.
      • Company Score Field:  The company field to write the calculated company score back to.
      • Click Save Settings.

 

 

You are now ready to Test the connector to make sure all is set correctly.  Click on the Test tab.

CC_Test1.png

Once your step is enabled and running, the Step Members testing tab will show you the counts of companies in your step.

 

The Run Manually testing tab will allow you to perform a Dry Run or a Full Run of your step.

CC_Test2.png

A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, actually updating Eloqua.

 

To check the history of your step execution, click on the History tab.

HistTab.png

Now that you have tested your step, it's time to enable it.  Click on the Credentials tab.

CredsTabStep.png

 

When you are ready to enable your step, click the Enable Step button. (Note: Remember to also enable your program in Eloqua)

 

As Companies/Accounts flow into the step, the app will evaluate all contacts associated with the company, perform the chosen scoring approach on the contact score field, and write the result back to the chosen company score field.

Recently, a new tool for troubleshooting and supporting Eloqua Cloud Apps was added to cloudconnectors.eloqua.com.

 

There is now a Support tab on all Cloud Connector and Feeder configuration pages, shown below:

 

NewSupportTab.png

 

If you are having an issue with your app, you can simply click on the Support tab, then copy the text within the App Details box and provide this to support when calling with an issue.  You will also find a link to a troubleshooting post here on Topliners.

 

You can access this same information for Cloud Components by clicking the Support button at the bottom of the configuration page.

 

SupportButton.png

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please install the replacement app.

 

Math Function Cloud App

 

This Document will describe the Math Function Cloud App, and how to use it within your instance of Eloqua.

 

When you begin to build a high performance revenue engine for your business, you can often run into situations where you need to do a little bit of basic math with your lead data. Perhaps it’s a lead scoring algorithm that needs to find the maximum score across a few sub criteria. Perhaps you want to find the revenue per employee for a business by dividing one number by another. Perhaps you want to analyze your leads based on an average score across 5 product lines. Perhaps you want to calculate the distance from a store location to a contact’s location by looking at their longitude/latitude. Whatever the case, having access to a completely generic set of math functions that you can run against your contact data is valuable in many ways.

 

With the Math Function Cloud App, you can now do the nurturing, analysis, and scoring that you want by creating the exact mathematical expressions that you need.

 

In order to use the App, you must be registered at cloudconnectors.eloqua.com.  When creating your account, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Math Function Cloud App Components

 

The Math Function Cloud App consists of the following Cloud Connector:

 

    • Math: Generic Function - allows you to create arbitrary math functions with up to 5 fields of data from a contact.

 

Components of the AppCloud

 

Installation and Configuration

To install the Math Function Cloud Connector in Eloqua, do the following.

 

Log into cloudconnectors.eloqua.com and click on the Apps menu.

AppsMenu.png

 

 

Click on Math Function (Contact), and the following screen will appear:

CC_Install1.png

Click on Install Connector.  You'll then be shown the installation screen.

CC_Install2.png

 

If you are an Eloqua administrator, you can click on Add Connector, and it will take you to the Cloud Connector Management area in your instance, with the install settings pre-populated.

 

You can also choose to do a Manual Install (note the settings above) and then go into the Cloud Connector Management are in your instance.  Enter the settings as shown below.

CloudConnectorSetup.PNG

CloudConnectorManagement.png

 

 

Enter the following information:

 

If you receive a confirmation similar to this, the Connector has successfully been installed:

 

https://lh3.googleusercontent.com/91isBv8m-7JNbArJn5duiZ93XEKPjPCKcLr1Jfz3gHijNKLRoYgaj6a3_pvdZ5Uqux-nqkE10McTK5RNcmhzchulZg-x95jezEo_Blu7TkzT58LBh_s

 

To configure the App, do the following:

    • Add a step to your marketing automation program at any point you would like to run a math function on a contact record.
      • Note: The Cloud Connector will run any mathematical equation you specify against the data in any contact that flows into that step and return the result to another field within the contact.
      • Make sure that you have an account on cloudconnectors.eloqua.com.
      • Drag a "Send to Cloud Connector" step onto the Canvas from the toolbar:

Canvas1.png

 

Double-click on the "Send to Cloud Connector" step, select Math: Generic Function from the list, and click on the configuration button.

Canvas2.png

 

When the Login screen appears, enter your cloudconnectors.eloqua.com credentials and click Log In.

CC_Login.png

Next the first setup screen for the App will appear.

cc_setup1.png

The values for Eloqua Client Name and Program Builder Step ID will automatically populate.  Enter the remaining information, then click Go.

 

The configuration page will then be displayed.

cc_config.png

On the Configuration tab, enter the following information:

  • Description (optional):  Some text about this connector instance
  • Math function: The math function to perform.
    • If you click the full syntax instructions link, you will see the following screen, which will help you with the available functions.

Function_Help.png

  • Click Save Settings.

 

Next, click on the Mappings tab.

CC_Mappings.png

 

On the Field Mappings tab, choose the following:

  • Email Address:  The contact field that holds the Email Address.  This is used to identify the contact record to operate on.
  • Variable A - E:  The contact field(s), referenced on the Configuration screen, that hold the numeric value(s) you wish to have your function evaluate.
  • Returned Value:  The contact field to write the result of the function back to.
  • Click Save Settings.

 

You are now ready to Test the connector to make sure all is set correctly.  Click on the Test tab.

 

Once your step is enabled and running, the Step Members testing tab will show you the counts of contacts in your step.

CC_Test1.png

 

The Run Manually testing tab will allow you to perform a Dry Run or a Full Run of your step.  A Dry Run will simulate a run, but will not actually write the data back to Eloqua.  A Full Run will perform a run of your connector, actually updating Eloqua.

CC_Test2.png

 

Use the Sample Data tab if you wish to test your setup on select contacts.  Enter their email addresses, one per line, and click Test Contacts. (Note: these contacts must already exist in your instance).

(Note: If you check the Full Run box, the data will be written to Eloqua, if left unchecked, it will simulate the connector and show you the results.)

CC_Test3.png

 

A Results screen will display after clicking Test Contacts (as well as when performing a Dry Run or Full Run).  An example of the Results screen is shown below.

cc_Test_Results.png

To check the history of your step execution, click on the History tab.

HistTab.png

 

Now that you have tested your step, it's time to enable it.  Click on the Credentials tab.

CredsTabStep.png

 

When you are ready to enable your step (remember to also enable your program in Eloqua) click the Enable Step button.

 

With the step running automatically, any contacts that flow into the step will have a generic mathematical expression run against it.

The SurveyGizmo cloud app is made up of both a Cloud Component and a Feeder.

 

The Cloud Component is used for displaying a survey on an E10 Landing Page, while the Feeder allows you to pull in leads from survey responders, along with their answers (you can track up to a total of 10 questions).

 

But what if you are an E9 user...if you cannot use the Cloud Component, can you still use the Feeder?

 

The answer is YES, and here's why:

 

The Feeder is completely independent of the component.  It looks at your SurveyGizmo account, finds the survey that you have chosen, and creates contacts in Eloqua based on people who have taken the survey.  This includes all of the possible ways that the survey taker was driven to the survey.  Whether this was through an emailed link, from a link on a web page, or in the case of the component, a survey embedded directly on an Eloqua landing page.  No matter what the source, the data will be pulled in. (Note, in order for the Feeder to create a contact in Eloqua, you MUST have a question on your survey that asks for an email address.)

 

If you are an E9 user, and you want to embed the survey on your landing page, that is also possible.  To do this, you must log into your SurveyGizmo account, create an embed link, and then copy this link and paste it into your E9 landing page.  This will perform the same function as the component, it's just a more manual process.

 

For more information on using the SurveyGizmo Cloud App, please see Installing and Using the SurveyGizmo Cloud App

When setting up Eloqua Cloud Apps, there are several configuration options that they all have in common.

 

One of these is the mapping of the Custom Data Object (CDO) Unique Code.  When you choose to store data in a CDO, the field mapping screen will ask you to map your unique code.

 

There is always a lot of confusion around this, because it is usually shown on the mapping screen as Display Name.  We call this field Display Name in the apps, because this is the name that we recommend you use for your Display Name Field on the CDO itself.  This is just a recommendation however, as you can set the Unique Code field to anything you wish.  Unless the app specifically tells you to, you will not want to set your CDO unique code to be Email Address.

 

In order to better understand why you are asked to provide a unique code, let's look at what happens when an app runs.  For this example, let's pretend that we have an app that reaches out to an event system, pulls out all attendees of an event, and pushes them into Eloqua as contact records with linked CDOs.  Here's how that would look:

 

  1. User sets up the app, providing the following:
    • Credentials for their Eloqua install
    • Credentials for the event system
    • Event to obtain attendee data from
    • Contact Group/List in which to store the returned contacts
    • CDO in which to store the returned data
    • Field mappings, to tell the App which fields to put the data in (this will include the CDO unique code)
  2. The App runs, and does the following:
    • Reaches out to the event system and grabs all the people who attended the event
    • Creates a new or updates an existing Eloqua contact record
    • Creates a new or updates an existing CDO and attaches it the contact record.
    • Adds the contact to the group specified

 

Now, in order to perform the "Creates a new or updates an existing CDO and attaches it the contact record." part in step 2, we need to have a reference point to determine what is new and what already exists.  For this, we use the unique code.  For most apps, when we create a CDO, we push a combination of Email Address + Event ID into the unique code field that you specify in the setup.  By doing this, we ensure that each contact will be able to have one CDO for each event they attend.  If we were to set up another instance of this app for a different event, we could use the same CDO, because even if the same person attended both events, the unique code will be different.

 

So, when you're setting up your CDO for use with a cloud app, be sure to keep this in mind.  Unless the app specifically tells you otherwise, create a dedicated field (other than Email Address) and set this to be the Unique Code.

The Eloqua String Manipulation Cloud Connector, paired with Regular Expressions, can do some pretty useful things.

 

Let's take a look at how we can use Regular Expression Replace to take a contact's full name, contained in a single field, and split it up into a separate first and last name fields.

 

The first step is to create a new campaign.  Since the connector can only act on one field at a time, in order to split the name into two separate fields, we will need two separate String Manipulation Cloud Connector steps.

 

Here is an example of what the campaign could look like:

 

NameSplitCampaign.png

The campaign starts out by passing in a segment of contacts, each of which contain a populated First and Last Name field.

 

Here is what the configuration for the first connector step (which will get us the first name) would look like:

 

SetupPic1.png

 

  • Start by choosing a String operation type of Regular Expression Replace.
  • Next, enter the Regular Expression to find as \s+[^\s]+
    • this will select the word immediately following the first space, which in our case is the last name.
  • Leave the Regular Expression to replace blank
    • this will take the last name that is found, and replace it with blank, which leaves us with the first name.

 

Now let's set our field mappings:

 

SetupPic2.png

We want to use First and Last Name (which is the contact field that contains the full name) as our Input String, and put the Returned Value into the First Name field.

 

Once the step is saved, we will set up our next step, which will get us the last name:

 

SetupPic1a.png

  • Start by choosing a String operation type of Regular Expression Replace.
  • Next, enter the Regular Expression to find as (\w+\s){1}
    • this will select the first word, which in our case is the first name.
  • Leave the Regular Expression to replace blank
    • this will take the first name that is found, and replace it with blank, which leaves us with the last name.

 

Now let's set our field mappings:

 

SetupPic2.png

We want to use First and Last Name (which is the contact field that contains the full name) as our Input String, and put the Returned Value into the Last Name field.

 

With the second step saved, we have now completed our program.

 

Here's what will happen when the campaign runs:

 

  1. Contacts flow through the program, and arrive in our first cloud connector step.
  2. The first cloud connector picks the contact up, looks at it's First and Last Name field, and writes the first name back to the First Name field on the contact record.
  3. The second cloud connector picks up the contact, looks at it's First and Last Name field, and writes the last name back to the Last Name field on the contact record.

 

That's it!!!  You now have the names separated into the appropriate fields on your contact record.

 

Please note, the Regular Expressions used in this example will only work if the name is in the format of First Last.  For instance, TJ Fields.  If there is a middle name, or a first or last name made up of multiple words, the results will not come back properly.

So, you're trying to use an Eloqua Cloud App, and you just can't figure out how to get it installed and configured correctly.

 

Did you know that there are actually user guides for these apps?

 

Below is a list of the guides currently available, and more are constantly being added.

 

 

Additional Information:

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

Pinterest Cloud App

 

This article will describe the individual pieces of the Pinterest Cloud App, how to have it enabled for your Eloqua instance, and configure it for display on your E10 landing page. This document assumes that the reader is an E10 user, and is familiar with using landing pages.

 

In order to use the Pinterest App, you will need to be registered at cloudconnectors.eloqua.com.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Pinterest Cloud App Components

 

The Pinterest Cloud App consists of the following Cloud Components:

  • Pinterest "Pin It" Button - allows you to add a "Pin It" button to an E10 landing page.
  • Pinterest "Follow" Button - allows you to add a "Follow" button to an E10 landing page.

 

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

How to Install the Cloud App

 

The Pinterest Cloud App is already available for use in E10, but may need to be enabled.  See here for more information.

 

Using the Components on a Landing Page

 

A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.

   

From the editor toolbar, select the "Cloud Components" button.  A select box containing all of the available Cloud Components will then be displayed.

 

Pinterest1.png

 

Drag and Drop one of the Pinterest components onto the landing page.

 

"Pin It" Button:

 

Pinterest2.png

 

"Follow" Button:

 

Pinterest3.png

 

Next, save the page, then double-click the component that you just dropped onto the page.  The following screen will appear:

 

CCLogin.PNG

 

Enter your cloudconnectors.eloqua.com credentials and click Log in

 

If you're adding a "Pin It" button, the following screen will then be displayed:

PinItConfig.png

 

On the configuration screen, enter the following:

    • Admin Email Address (this should automatically populate with your address)
    • URL of the page the pin is on: (required) - this cannot be blank, and you will need to manually type this in.
    • URL of the image to be pinned: (required)  - this cannot be blank, and you will need to manually type this in.
    • Description (optional) - if a description is not provided, the visitor who clicks your button will have to enter it before they can successfully pin.
    • Pin Count Orientation

You can Also:

      • Click Preview to see what your button will look like.
      • Click Show Source to see the button source code.
      • Click Render Image to see the image that will appear in the landing page editor.

 

Click Save Settings and close the screen.

 

If you're adding a "Follow" button, the following screen will then be displayed:

FollowConfig.png

On the configuration screen, enter the following:

    • Admin Email Address (this should automatically populate with your address)
    • Pinterest Account to "Follow": (required) - the Pinterest account that you would like your visitors to follow when they click your button.
    • Button message: (optional)
    • Button to display: you can choose from the following:
      • Follow Me
      • Pinterest
      • Large Icon
      • Small Icon

The following image shows, in order, what each button looks like:

PinterestButtons.png

 

You can Also:

      • Click Preview to see what your button will look like.
      • Click Show Source to see the button source code.
      • Click Render Image to see the image that will appear in the landing page editor.

 

Click Save Settings and close the screen.

 

When the landing page renders, your button will show on the page.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Form Population capabilities are now moved into the Oracle Eloqua Core Platform. Review this page for more info.

 

Form Population Cloud App

 

The Form Population Cloud App allows the marketer to pre-populate a form that exists on the landing page.  When dragged onto the page and configured, the Cloud Component will populate hidden or shown form fields with contact data, visitor data, static values, or query strings.  Note: In order for the Contact data or Visitor data to work, the visitor to the page must be known to Eloqua.

 

This article will describe the individual pieces of the Form Population Cloud App, how to have it enabled in your Eloqua instance, and configure it for display on your E10 landing page. This document assumes that the reader is an E10 user, and is familiar with using landing pages.

 

In order to use the App, you must be registered at cloudconnectors.eloqua.com.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Form Population Cloud App Components

 

The Form Population Cloud App consists of the following Cloud Component:

  • Form Population - allows you to auto-fill form fields with data from a visitor, contact, query strings, or static values.

 

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

How to Install the Cloud App

 

The Form Population Cloud App is already available for use in E10, but may need to be enabled.

 

See here for more information.

 

Using the Component on a Landing Page

 

     A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.

 

     From the editor toolbar, select the "Cloud Components" button.  A select box containing all of the available Cloud Components will then display.

FormPop1.png

Drag and Drop the Form Population component onto the landing page:

FormPop2.png

Next, save the page, then double-click the icon that you just dropped onto the page.  The following screen will appear:

CC_Login.png

 

Enter your cloudconnectors.eloqua.com credentials and log in.

 

A screen will appear asking for your Eloqua credentials.  These credentials will be used to make calls to the Eloqua API to retrieve Visitor Profile and Contact data.

FormPopCreds.png

 

Click Go, and the configuration screen for Form Population will then be displayed:

FormPopConfig1.png

 

On the configuration screen, select the form that you want to pre-populate (NOTE: this form must also be placed on the same Eloqua landing page as the component).

 

If you would like to map a DataCard field, you will need to select the Custom Data Object you wish to pull the field(s) from.  If an object is selected from the list, the following additional settings will be displayed:

(NOTE: this step is completely optional, and is only required if you wish to population form fields with information from Custom Data Objects)

FormPopConfig3.png

 

Due to the fact that a contact can have multiple DataCards mapped to them in a set, we will need to use a rule to determine which one to use.

 

The Selection Rule will be evaluated against to field chosen for Field to Evaluate.  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 also need to map the Email Address so that the component can look at the contact visiting the page, and find any DataCards mapped to them.

 

Now that the component knows which Custom Data Object to look in, the Email Address field for determining mapped objects, and a Selection Rule and Field to Evaluate, it is possible to pull a field from the object to pre-populate a form field.

 

Click Save Settings, and then click Map Fields.

 

The Edit Form Population Mappings screen will then display.

FormPopMappingsNew.png

 

 

  1. Start by selecting a Type.  Choices are as follows:
    • Contact Data: fields from the Eloqua contact record.
    • Visitor Data: fields from the Eloqua visitor profile.
    • Static Value: a value that you provide.
    • Query String: a value that you pass to the landing page on the query string.
    • DataCard Field: fields from an Eloqua DataCard that is linked to a contact.
    • Email Group:  email groups from Eloqua.
  2. Next, choose the Form Field that you wish to populate.
  3. For Contact Data, Visitor Data, DataCard Field, or Email Group select the appropriate field from the list provided.
  4. For Static Value, simply enter the text that you would like to put into the form field.
  5. For Query String, enter the name of the parameter that will be passed to your page, without the "=" sign.

       (NOTE: The app supports populating checkboxes from static values.  If the form field you are populating is a checkbox, enter a Data Field value of true to check the box, or false to un-check it)

 

Once your mappings are completed, click Save and the screen will close, returning you to the configuration page.

 

The count of mapped fields will be shown next to the Map Fields button.

FormPopConfig4.png

 

Note: Clicking the Preview button, with the email address of a contact that already exists in your Eloqua instance, will pop up a window that will be blank.  Since this is a non-visual component, you will need to view the page source to see the results of your setup.  The page source will show you the code that will be inserted into the landing page to fill in the form fields.

 

Now that the configuration is complete, when the landing page is rendered, the fields should be filled with the data that you set up in the mappings.

 

Things to note:

  • This is a non-visual component, meaning you do not actually see anything on the page.  (Note: If you view the page source, you will find the code returned by the component inside the CloudComponentInstance span tag).
  • The component does not actually submit the form, it simply populates the form fields with data.
  • The Contact Data and Visitor Data options will only work if the Visitor or Contact is known to Eloqua.  For DataCard Field and Email Group the Contact must be known.
  • In order to bring back a DataCard field, the contact must have a DataCard mapped to them in the chosen set.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

Lead Assignment Cloud App

 

Please note, this app is currently in BETA, so it may be buggy!

 

This article will describe the Lead Assignmenthttp://www.surveygizmo.com/Cloud App, and how to use it within your instance of Eloqua.

 

In order to use the Lead Assignment Cloud App, you must be registered at cloudconnectors.eloqua.com.  When creating your account on cloudconnectors.eloqua.com, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Lead Assignment Cloud App Components

 

The Lead Assignment Cloud App consists of the following:

 

  • Lead Assignment Cloud Connector - The Lead Assignment Cloud Connector allows an Eloqua user to configure a set of rules that map to a salesperson.  When set up as a Cloud Connector step in Program Builder, it will take a set of contacts, run them through the rules, and write the appropriate salesperson’s name into the Salesperson field on the contact record.

 

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

Installing and Configuring the Cloud App


To install the Lead Assignment Cloud Connector in Eloqua:

 

    • Have your Eloqua administrator go into the Cloud Connector Management area in your instance.


https://lh5.googleusercontent.com/wSV2eCtkyBkhDP5Y_c67zCED4lSUEwQoNupdldZQ1m1tQ-A3EiU08U0co_mAFha3rTThBaVT6bG7LS1mPL6g8A8SvQvPhv3VNb84kGivs5GK0iUolDI

 

 

 

 

 

If you receive an error similar to this, it means the Connector had been installed previously:

 

 

https://lh5.googleusercontent.com/OYRVQGqH8qzl9obXkElxfUiONR5mShxa3N_XBJrQ2q8cVe2FwVxNNOIgt1taSv_zDWegc-ffbwj2rDxgTIN2rB4pAXifPzHEr6yNiq--MtJAGwfrcq0

If you receive a confirmation similar to this, the App connector has successfully been installed:


https://lh3.googleusercontent.com/91isBv8m-7JNbArJn5duiZ93XEKPjPCKcLr1Jfz3gHijNKLRoYgaj6a3_pvdZ5Uqux-nqkE10McTK5RNcmhzchulZg-x95jezEo_Blu7TkzT58LBh_s


To configure the Lead Assignment Cloud Connector:

 

    • Make sure that you have an account on cloudconnectors.eloqua.com.
    • Create a program in Program Builder, with a Cloud Connector step.

 

https://lh4.googleusercontent.com/RyDWAPbP67y3s4Iftb-2ah12Q3OEaCZPrAQFAxbsfkI9RqAfxG1gVE-q1AIa8-3Ar-hqDOwoacWGY1KjefTwf_NO8WKD2Z8AB6CIweRuOxic-ed57ik

 

 

    • Click on the cloud icon to configure the step.
    • On the Edit Action screen, choose Contact Sales Lead Assignment, and click Configure.

https://lh4.googleusercontent.com/ii4tJQanUNf2gqL38aJAVYC7ww9ovXaRGfCzGFuT_CPMdOrNmviAeAp_DKX-URheseH4D-uiheNxiIqRSvL-NIJGEuNj6hGossadCSYBOoaXUsdwddA

 

When the Login screen appears, enter your cloudconnectors.eloqua.com credentials and click Log In.

 

https://lh5.googleusercontent.com/G9G2q8fG0DcjuMgX8KfyGMvLpHFQYEi2YVz2tsbbCboTncd-g6AqqfbZy-hNvusJilDYIdtv_A9twK_wfR_CaUx7oh-jAdVa-LOMYtEntjCmR-OQF7k

 

On the next screen, make sure your information is correct, and click Go.

 

https://lh5.googleusercontent.com/whsnAYISCc_ek10v6IgP4zKUYP2BzKvgrZed2r-b8ZW6sIXs58VcwGBYdP9L9g6rUwMAVJehLjNyMk88OLJPD-YFN3y7GlwywcU1eys3tUasj3O-iHs

 

                    The Configuration tab will then display.

 

https://lh3.googleusercontent.com/KriugyBMO446y-N4QHKWZPrTbAhZ588FQnEPt_WQrFnqINEXlKQcMjJvBoP6l07lIjqldaAx49_Rpl7-6xebiRdjI4Zpqu9bpAscPRu-lQBf4rrC8Fc

Do the following:

    • Enter a Description (optional)
    • Click on Build Rules

 

 

          The Rules Builder screen will then appear.

https://lh4.googleusercontent.com/M2sRh_SNqm_bVmL9HTmgSk5QJFaOIe83P3PQbAD5fwyDYRUk8IKQVi9F766BUnmTXPyylmRpihMx7aVLh8OUtN7PP-DQ_XMQxaKlqF2OLuwRRJ4YCMY

          Do the following:

        • Enter a salesperson’s name into the Salesperson field (this will be the value that writes to the Eloqua contact record if this set of rules are met.
        • Configure the rule by selecting the Contact Field, Operator, Value, and Logic.
        • The Contact Field is the field that you want to compare a value from.
        • The Operator is the type of comparison that you want to perform (Equals, Contains, Starts With, Greater Than, or Less Than).
        • The Value is the value that you would like to compare the Contact Field to.
        • Logic is either AND or OR.
        • Click Save to save your rules.

 

https://lh3.googleusercontent.com/ZJoZpRHhKWrxfMdI-jySE4i6pX-RC-HDJBU3rwbIR2PJJR2YrLDfKS1LAEwmU2B6Vab6u3DOGUYB5hO5EEK8tfHlSw2-v90AukhR8Rd8L53RmGv97QA

If you wish to create another rule, click the Add Rule button.  This will add a new rule to the Salesperson.

    • To delete a rule, simply click the Delete button for the appropriate rule.  Press Save.
    • If you would like to create a new Salesperson, click the Add Salesperson button.
    • Enter the new Salesperson name and press Save.

 

https://lh6.googleusercontent.com/vh_ILzWPOkOMKvFTK4B7xV8C14qZcdiZ9KxUzQ4YXJc2X1yY59uNUI1rViSly6ztUlH0kj62yxu-Ge4hbShueLKhXRp8KS_lLsaXLnqXEwF1IF2pZXE

 

If you would like to delete a Salesperson, click the Remove button next to the Salesperson.

https://lh3.googleusercontent.com/mnd7mt05u4Q62fA5s4VxuATZLXuo0buqYncLYZPuNtzALenkXCfS46SVgSmxukd2q95MfCATV6AYpZ_e3pYYuA8JUlq7OG47uyfa86dLbTx1stO1pZE

The Salesperson will then be removed.

https://lh6.googleusercontent.com/r7Yn4p-9SHITrIGVNGrRNMeXEIvMCos5TKFoMyFNsBxZVVRAaKVYJ5lhRTccjN4Wj6C_Si0dPv1Azyo_tN7dkf5Nlr0C53JDFhIElf0HCI_VIkvTLWA

 

When you have finished setting up your rules, click Save and then close the window.

 

Next, click on the Field Mappings tab.

 

https://lh5.googleusercontent.com/qo0yeT_IK9RBuq1F86oZRhHsyx0HXFID0vMtZmExlJoHEvDjXLzOO90Q7tx5WNc3fBAiu2ztYD3lzU_pxqJ1X3EcoW5y3_-4DGgl3PGY9sMR62Ayxzo

 

On the Field Mappings screen, choose the Eloqua contact field for Email Address, and Salesperson.  It is recommended that you select Salesperson from the list, but if you so choose, you can select a different contact field to hold the returned Salesperson name.

      • Save your settings and close the screen.  And click on the Credentials Tab.
      • On the Credentials tab, enable the Cloud Connector by clicking the Enable button.
      • Close the configuration screen.

 

Congratulations, your Lead Assignment Cloud Connector is now configured.  Turn on your Program and Contacts should start having a Salesperson assigned as they flow through.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

SurveyGizmo Cloud App

 

This article will describe the individual pieces of the SurveyGizmo Cloud App, and how to use them within your instance of Eloqua.

 

In order to use the SurveyGizmo Cloud App, you will need an existing account on SurveyGizmo, with surveys already created.  You must also be registered at cloudconnectors.eloqua.com.  When creating your account on cloudconnectors.eloqua.com, make sure the user whose Eloqua credentials you provide is added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

SurveyGizmo Cloud App Components

 

The SurveyGizmo Cloud App consists of the following:

 

  • SurveyGizmo Embed - this Cloud Component allows you to embed a SurveyGizmo survey or poll into an E10 landing page.

 

  • SurveyGizmo Feeder - allows you to pull into an Eloqua group, all the people who have filled out a specified survey, along with a select number of responses to questions (currently, you can track up to 10 questions).

 

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

Installing and Configuring the Cloud App

 

SurveyGizmo Embed

 

The SurveyGizmo Embed component is already available for use in E10, but may need to be enabled.  See here for more information.

 

        A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.

 

        First, from the editor toolbar, select the "Cloud Components" button.  A select box containing all of the available Cloud Components will then display.

SurveyGizmoEmbed1.png                             

Now, drag and drop the SurveyGizmo Embed component onto a landing page:

 

SurveyGizmoEmbed2.png

 

Next, save the page, then double-click the icon for the component that you just dropped onto the page.  The following screen will appear:

CC_Login.png

Enter your cloudconnectors.eloqua.com credentials and click Log in.  The configuration screen for SurveyGizmo Embed will then be displayed:

 

SurveyGizmoEmbedConfig1.png

On the configuration page, do the following:

    • Enter the Admin Email Address (your email address).
    • Enter your SurveyGizmo Username and Password.
    • Click “Save Settings”, and a list of your SurveyGizmo surveys will show in the Survey Name drop-down list.
    • Select a survey and then press Save Settings. 
    • If your credentials are accepted, a list of embed codes will display in the Embed Code drop-down (see note below).
    • Select an Embed Code
    • Select a size for your survey and click “Save Settings”. You can now close the configuration page.

 

Note: In order to see an embed code in the list, you will first need to create one in SurveyGizmo.  To do this...

      1. Log into your SurveyGizmo account, select a survey, and click on Publishing
      2. Click on IFrame Embed.

SurveyGizmoSurveySettings1.png

A screen will appear where you can name your embed and press Save.

SurveyGizmoSurveySettings2.png

 

Now, render the landing page, and you will see your Survey embedded on the page where you placed it.

 

SurveyGizmo Feeder

 

  • The SurveyGizmo Feeder does not require installation, as it is a standalone application that runs outside of Eloqua, and connects to your instance.
    • Make sure that the Eloqua user account that is being used for the feeder had Eloqua API access. 
    • Create a Contact Group in Eloqua (called a Contact List in E10), to store the Contacts created/updated by the feeder. For more information about creating a contact group, please search the knowledge base for an article named "Database Management".
    • Create a DataCardSet in Eloqua, to store the Event information returned by the feeder. For more information about creating a DataCard Sets, please search the knowledge base for an article named "Database Management".

 

     To access and configure the feeder, first visit cloudconnectors.eloqua.com and log in.

 

     Once logged in, select Products...Feeder, and choose "SurveyGizmo Feeder”.

 

Click New Step on the screen that appears:

SurveyGizmoFeeder1.png

 

The configuration screen will then appear:

SurveyGizmoFeeder2.png

Enter your Eloqua Client Name, Query Frequency (how often the feeder should run), Eloqua User Name (make sure the user has API permissions), Password, and Admin Email Address. Click Go.

 

The Setup screen will then be displayed.

Feederpage1.png

On the Configuration tab, do the following: 

    • Enter a description for the feeder (optional) and choose your.
    • Enter the Admin Email Address (your email address).
    • Enter your SurveyGizmo Username and Password.
    • Click “Save Settings”, and a list of your SurveyGizmo surveys will show in the Survey Name drop-down list.
    • Select a survey and then press Save Settings.
    • If your credentials are accepted, a list survey questions will be populated in each of the Question drop-down lists.
    • Choose the survey question that holds the Email Address (required) , First Name (optional) and Last Name (optional).
      • Note: In order for the feeder to create contacts, you MUST have a question on your survey that asks for the survey taker's email address.
    • Choose the survey questions (a maximum of 10) that you wish to track answers to.
    • Choose the existing Contact Group (E9) or Contact List (E10), in which to place the newly created contacts.
    • Choose the existing Custom Data Object in which to store the returned survey data.
    • Click on Save Settings, and then click on the Field Mappings Tab.

 

Mappings1.png

On the Mappings tab, choose which Eloqua Contact and Custom Data Object fields to map to corresponding data from the SurveyGizmo system into when the feeder runs. 

    • For the Custom Data Object, the field list selections will be populated based on the existing Custom Data Object chosen on the Configuration tab.
    • Note: for Display Name Fields (Custom Data Object) field, the field you choose MUST be set as Unique in Eloqua in order for the feeder to function properly.

 

 

On the Test tab you can test the feeder. You can choose between a “Dry Run” (no data will be changed in Eloqua) and a “Full Run” (The data will write to Eloqua – this is effectively a manual run of the feeder).

TestTab.png

The History tab shows a history of previous feeder runs.

HistTab.png

 

Once all is configured, all that is left to do is switch back to the Credentials tab and Run the feeder:

CredsTab.png

 

Now that the SurveyGizmo feeder is configured and enabled, leads will begin to flow into Eloqua based on your Surveys.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

Brainshark Cloud App

 

This article will describe the individual pieces of the Brainshark Cloud App, how to have it enabled for your Eloqua instance, and configure it for display on your E10 landing page. This document assumes that the reader is an E10 user, and is familiar with using landing pages.

In order to use the Brainshark App, you will need to have a valid Brainshark account containing presentations, and you must be registered at cloudconnectors.eloqua.com.

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Brainshark Cloud App Components

 

The Brainshark Cloud App consists of the following Cloud Component:

    • Brainshark Embed - allows you to embed an Brainshark Presentation into an E10 landing page.
    • Brainshark Feeder - allows you to import viewers of your Brainshark presentation into Eloqua.

 

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

How to Install the Cloud App

 

The Brainshark Cloud App is already available for use in E10, but may need to be enabled.

 

See here for more information.

 

Using the Component on a Landing Page

 

     A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.

 

     From the editor toolbar, select the "Cloud Components" button.  A select box containing all of the available Cloud Components will then be displayed.

BrainsharkComponent1.png

 

Drag and Drop the Brainshark Embed component onto the landing page:

BrainsharkComponent2.png

 

Next, save the page, then double-click the icon that you just dropped onto the page.  The following screen will appear:

CCLogin.PNG

Enter your cloudconnectors.eloqua.com credentials and log in.

 

Next, a page will display that will ask for your Eloqua credentials (Note: the credentials entered MUST be for an API enabled Eloqua account).

 

BrainsharkConfig1a.png

Once the details are entered, click Go, and the configuration screen for the Brainshark Embed component will then be displayed:

 

BrainsharkConfig1.png

On the configuration screen, do the following:

Enter your:

      • Brainshark Username
      • Brainshark Password
      • Brainshark Company Name

 

Click Get Presentations

 

If you have entered your Brainshark credentials correctly, your presentations will show up in the Presentation drop-down list.

BrainsharkConfig2.png

Finally, select a Presentation from the list, and choose an Embed Size.

 

Note:  you will have to play with the size of the component on the landing page to make your presentation fit

 

To help with this, here are the actual dimensions for the different size options:

 

BrainsharkSizes.png

 

Click on Save Settings and close the Configuration screen.

 

Now, render the landing page, and you will see your Brainshark Embed presentation on the page where you placed it.

 

BrainsharkComponent3.png

When a  known Eloqua contact visits the landing page and views the video, the component will pass viewer data to Brainshark.  This data will then be included in your presentation reporting in the Brainshark system.

When it comes to Cloud Connectors, one question that I am often asked, is weather or not they can be used with E10.  The answer to this question of course is yes, they can!

 

Using a Feeder, since it is hosted outside of Eloqua, requires no configuration from inside of Eloqua itself.  You simply visit the site where the app is hosted, configure it, and it feeds contacts into Eloqua regardless of the version. 

 

But what about Program Builder, wasn't that just for E9?  While it is true that step based Cloud Connectors are currently available only through Program Builder, that doesn't mean that they are just for E9.  Program Builder is in fact still available in E10!  Look for the Program Builder icon under Database in the Setup menu.

 

When configuring a connector for use with E10, one thing to keep in mind is that names and locations of certain features differ between versions.  For example, a Contact Group is now called a Contact List in E10, and Custom Data Objects (aka DataCards) are found under the Contacts menu, and are called Custom Objects.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

amiando Cloud App

 

This article will describe the individual pieces of the amiando Cloud App, and how to use them within your instance of Eloqua.

 

In order to use the amiando Cloud App, you will need to have an amiando API Key (see here for information on how to get your API Key), an existing event set up in the amiando system, and must be registered at cloudconnectors.eloqua.com.  When creating your account on cloudconnectors.eloqua.com, make sure the user whose Eloqua credentials you provide is  added to the “API Users” security group to ensure it has API access.  Your Eloqua administrator will have to do this for you.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

amiando Cloud App Components

 

The amiando App consists of the following:

  • amiando Widgets - this Cloud Component allows you to embed event-related widgets into an E10 landing page.  The following widgets are available:
    • Registration Form/Ticket Shop
    • Directions
    • Participant List
    • My Events
    • Wall
    • Photos
  • amiando Feeder - allows you to pull into an Eloqua group, all the people who registered for or attended your amiando event.

 

 

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

Installing and Configuring the Cloud App

 

amiando Widgets

 

The amiando Widgets are already available for use in E10, but may need to be enabled.  See here for more information.

 

        A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.

 

        From the editor toolbar, select the "Cloud Components" button.  A select box containing all of the available Cloud Components will then display.

                                    amiandoComponent.png

Drag and Drop the amiando Widgets component onto a landing page:

 

Next, save the page, then double-click the icon for the component that you just dropped onto the page.  The following screen will appear:

CCLogin.PNG

Enter your cloudconnectors.eloqua.com credentials and log in.  The configuration screen for amiando Widgets will then be displayed:

 

amiandoConfig.png

 

On the configuration page, do the following:

    • Enter the Admin Email Address (your email address) and your amiando API Key.
    • Click “Save Settings”, and a list of your amiando events will show in the Event drop-down list.
    • Select an Event, and then choose a Widget Type that you would like to display on the landing page.
    • Select the other optional settings to customize the Widget to the needs of your landing page, and click “Save Settings”. You can now close the configuration page.

 

Now, render the landing page, and you will see your amiando Widget on the page where you placed it.

RenderedPage.png

 

amiando Feeder

 

  • The amiando Feeder does not require installation, as it is a standalone application that runs outside of Eloqua, and connects to your instance.
  •    
  • In order to successfully configure the feeder, you must first do the following:
    • Make sure that the Eloqua user account that is being used for the feeder had Eloqua API access. 
    • Create a Contact Group in Eloqua (called a Contact List in E10), to store the Contacts created/updated by the feeder. For more information about creating a contact group, please search the knowledge base for an article named "Database Management".
    • Create a DataCardSet in Eloqua, to store the Event information returned by the feeder. For more information about creating a DataCard Sets, please search the knowledge base for an article named "Database Management".
  • To access and configure the feeder, first visit cloudconnectors.eloqua.com and log in.  Once logged in, select Products...Feeder, and choose "amiando Feeder”.

 

Click New Step on the screen that appears:

amiandoNewStep.png

The configuration screen will then appear:

amiandoConfig1.png

Enter your Eloqua Client Name, Query Frequency (how often the feeder should run), Eloqua User Name (make sure the user has API permissions), Password, and Admin Email Address. Click Go.

 

On the Configuration tab, provide a description for the feeder (optional) enter your amiando API Key, and choose your Event.  Next, choose the existing Contact Group (E9) or Contact List (E10), and Custom Data Object where your new contacts will be stored in Eloqua.

amiandoConfig2.png

On the Fields Mappings tab, choose which Eloqua Contact and Custom Data Object fields to map to corresponding data from the amiando system into when the feeder runs.  For the Custom Data Object, the field list selections will be populated based on the existing Custom Data Object chosen on the Configuration tab.

amiandoConfig4.png

On the Run Step tab you can test the feeder. You can choose between a “Dry Run” (no data will be changed in Eloqua) and a “Full Run” (The data will write to Eloqua – this is effectively a manual run of the feeder).

amiandoConfig5.png

The History tab shows a history of previous feeder runs.
amiandoConfig6.png

 

Once all is configured, all that is left to do is switch back to the Credentials tab and Enable the feeder:

amiandoEnable.png

 

Now that the amiando feeder is configured and enabled, leads will begin to flow into Eloqua based on your Events.

Important: This Cloud Connector/Component will be decommissioned  after March 31st 2017. Please review the App Replacement Cheatsheet for instructions

 

Box Cloud App

 

This article will describe the individual pieces of the Box Cloud App, how to have it enabled for your Eloqua instance, and configure it for display on your E10 landing page. This document assumes that the reader is an E10 user, and is familiar with using landing pages.

 

With the Box Cloud App, you can now share files stored in your Box account on an E10 landing page.  You can choose to either display a link to your file, embed an image, or display the Box file previewer right on your page.

 

In order to use the Box  App, you will need to have a valid Box account, and must be registered at cloudconnectors.eloqua.com.

 

What is the difference between Appcloud.eloqua.com and Cloudconnectors.eloqua.com?

 

Box Cloud App Components

 

The Box Cloud App consists of the following Cloud Component:

  • Box File Share - allows you to embed an image, document link, or document previewer into an E10 landing page.

 

ARTICLE – What is the difference between an App, a Connector, a Component and a Feeder

 

How to Install the Cloud App

 

The Box Cloud App is already available for use in E10, but may need to be enabled.

 

See here for more information.

 

Using the Component on a Landing Page

 

     A Cloud Component is inserted into a landing page via drag and drop within the landing page editor.

 

     From the editor toolbar, select the "Cloud Components" button.  A select box containing all of the available Cloud Components will then display.

CCButton.PNG

 

Drag and Drop the Box File Share component onto the landing page:

CCDrop.PNG

 

Next, save the page, then double-click the icon that you just dropped onto the page.  The following screen will appear:

CC_Login.png

 

Enter your cloudconnectors.eloqua.com credentials and log in.  The configuration screen for the Box File Share will then be displayed:

BoxConfig1.PNG

 

In order to access your Box files, you will need to grant the component access to your account.  To do this, click "Authorize Account".

BoxConfigAuthorize.PNG

The following screen will then appear:

BoxConfig2.PNG

Enter your Box credentials and click "Log In".

(NOTE: If you are using a Single Sign On (SSO) service such as Okta, enter only your Email and leave the password blank)

 

Once successful, a window will display saying "Thank you. Close this window to continue".  Close the window, you've now granted access to your files!

AuthConfirm.png

     Next, select the file you would like to share on the page.  Click on the Select File button.

     BoxConfigSelectFile.PNG

     The app will search your Box account and display the results.

     BoxConfigSelectFileList.PNG

     Your Box account contents will be displayed as a set of folders and files.  Click on a folder to see the files within it, or click on a file to select it.  You can also page through results by clicking on the numbers below the file list.

 

     Once you've selected your file, the app will check your Box account to see if the file is currently shared.  If the file is not yet shared, you will be shown the following:

     DocShareError.png

Since the app required you to share the file before displaying in on the landing page, you have a couple options.  You can choose to go to your Box account and create the share there, or the app can create it for you.  If you choose to do this through your Box  account, you simply create the share manually, then come back to the app and click Save Settings again.  The warning will then disappear.  If you choose to have the app create it for you, simply select a share type (Open, Company, or Collaborators) and click  Share.  If the share is created successfully, you will see the following:

     DocShareSuccess.png

     Your file is now shared.  The shared file will show in the File to Share field.

     BoxConfigFileSelected.PNG

    You're now ready to select your Share Type.

     BoxConfigOptionList.PNG

     You will be presented with three options for sharing.  These include:

    • Previewer - Embed the Box previewer directly in your page.
    • Image Embed - Display an image from your Box account on your page.
    • Link to File - Provide a link to a file in your page.

 

     To embed an image from your Box account, choose Image Embed.

     BoxImageEmbed.PNG

     Click on Save Settings and close the Configuration screen.

 

     Now, render the landing page, and you will see your Image Embed on the page where you placed it.

BoxImageRendered1.PNG

     If you would like to embed a link to a file in your landing page, select Link to File.

     BoxConfigFileLinkDefault.PNG

 

     For a "Link to File", you can use either the default icon, or a custom icon of your choosing.

 

     To select a custom icon, select "Custom" from the "Image to display as link" dropdown, and enter the URL to the image.

     BoxConfigFileLinkCustom.PNG

     Now, render the landing page, and you will see your file link on the page where you placed it.

BoxImageRendered2.PNG

     The third option is embedding the file previewer on your page.  Select Previewer from the option list.  The following additional settings will appear.

     BoxConfigPreviewer.PNG

     In the Previewer Settings area, you can use the following to customize the previewer for display on your page.

 

    • Permissions - Choose to either show or hide the Download, Share, or Print buttons.
    • Dimensions - Set the size of the previewer (Note: make sure that the component on the landing page is at least the dimensions that you set here to allow all of your content to display).

 

     When you have the settings the way you wish, render the landing page.  You will see the previewer displayed on the page.

     PreviewRendered.PNG

Filter Blog

By date: By tag: