Content:

• Overview and Key Notes
• Configure Your Eloqua Form
  • • Add a Hidden Field to Capture the Log ID
• Add the BookIt Script to Your Form Page
• Add the BookIt Script to Your Thank You Page
• Configure Your Trigger Node
  • • Set Your Trigger Node Name
    • Add Your Field Mappings
    • Configure the Rest of Your Routing Graph

 

Overview and Key Notes

This guide walks you through how to display a calendar as a pop-up on a thank you page, triggered after a user submits an Eloqua form and is redirected to that page.

 

Configure Your Eloqua Form

Add a Hidden Field to Capture the Log ID

First, make sure your Eloqua form includes a hidden field to store the BookIt Log ID. If you haven't already done this, follow our guide on Adding a Hidden Field in Eloqua. This value will later be used to update the associated Lead or Contact in Salesforce.

 

Add the BookIt Script to Your Form Page

Add the following BookIt script to the page containing your form.

You will need to update the placeholder values (highlighted in yellow) in the LDBookItV2.initialize() function. 

Replace the placeholders with your values:

• <Org ID> — Your 18-digit Salesforce Org ID. This should match the org where your live BookIt router graph resides (or the sandbox you’re testing in).

• <Trigger Node Name> — The name of the trigger node in your BookIt router graph. Use something descriptive like "Demo Request". You’ll configure this in a later step.

• <Hidden Field Name> — The value you specified for the HTML Name of the hidden field you created in an earlier step ("ldBookItLogID" in our example)

<script>
  var _ld_scriptEl = document.createElement('script');
  _ld_scriptEl.src = 'https://cdn.leandata.com/js-snippet/ld-book-v2.js';;
  _ld_scriptEl.addEventListener('load', function () {
    LDBookItV2.initialize('<Org Id>', '<Trigger Node Name>', '<Hidden Field Name>');
    LDBookItV2.setFormProvider('eloqua');
  });

  document.body.appendChild(_ld_scriptEl);
</script>

 

Add the BookIt Script to Your Thank You Page

First, make sure your form is configured to redirect to a thank you page on the same domain as the form page.

Add the following BookIt Script to that page. The script will load the LeanData BookIt library and trigger the calendar once the page loads.

Be sure to replace the highlighted placeholder values in the LDBookItV2.initialize() function:

• <Org ID> — Your 18-digit Salesforce Org ID. This should match the org where your live BookIt router graph resides (or the sandbox you’re testing in).

• <Trigger Node Name> — The name of the trigger node in your BookIt router graph. Use something descriptive like "Demo Request". You’ll configure this in a later step.

<script>
  var _ld_scriptEl = document.createElement('script');
  _ld_scriptEl.src = 'https://cdn.leandata.com/js-snippet/ld-book-v2.js';;
  _ld_scriptEl.addEventListener('load', function () {
    LDBookItV2.initialize('<Org Id>', '<Trigger Node Name>', true);
    LDBookItV2.submit();
  });

  document.body.appendChild(_ld_scriptEl);
</script>

 

Configure Your Trigger Node

Set Your Trigger Node Name

In your LeanData BookIt for Forms routing graph:

• Double-click on the Trigger Node to open the editor

• Update the Node Name to match the <Trigger Node Name> you defined earlier in your embed script.

Add Your Field Mappings

You can define field mappings directly in the Trigger Node. This allows you to pass values from your form into variables that can be used in your graph’s routing logic.

When specifying Form Field API Names, you'll use the HTML Name attributes/values for each field on your form.

When adding field mappings in your Trigger Node:

• If available, select from the list of default variable options.

• Otherwise, define your own variable name and specify its type (e.g., string, email, phone).

 

Configure the Rest of Your Routing Graph

Now that your trigger node and form field mappings are in place, you can continue building and customizing your routing logic.

Need help? Our LeanData Professional Services team is happy to assist with advanced configuration, best practices, or validation of your setup.