Basic Information
A REST API integration directly adds contacts in a specified Act-On list. Visitors will see a form you built in ion (and data is saved to your ion console), and then behind the scenes we pass designated data to your Act-On list. Maintenance for this method can be complex, as it requires updates to custom scripting should you want to change or expand the exported fields in the future. You will not be able to trigger automation in Act-On based on form completion, since there was no Act-On form submitted.
A Post to Web Form integration is what it sounds like: data collected in ion is re-posted to a form you've published in Act-On. While the visitor sees a form you built in ion (and data is saved to your ion console), Act-On treats it like someone completed the Act-On form directly. Future updates or expansion of your integration typically require changes to both your ion integration and your Act-On form(s).
A Post to Web Form integration is what it sounds like: data collected in ion is re-posted to a form you've published in Eloqua. While the customer sees a form you built in ion (and data is saved to your ion console), Eloqua treats it like someone completed the Eloqua form directly. This method often requires more effort to update or expand your integration in the future, as any changes must be made to both your ion integration and your Eloqua form(s). The benefits of this method are the ability to trigger automation in Eloqua based on form completion, as well as the ability to pass data to a custom data object (via form processing steps on your Eloqua form).
A Post to Web Form integration is what it sounds like: data collected in Ion is posted to a form you've published in HubSpot. While the customer sees a form you built in Ion (and data is saved to your Ion console), HubSpot treats it like someone completed the HubSpot form directly. This method often requires more effort to update or expand your integration in the future, as any changes must be made to both your ion integration and your HubSpot form(s). The benefits of this method are the ability to trigger automation in HubSpot based on form completion.
Your Marketo form code is used to build a reusable widget in the ion platform. Once the widget is built, you can insert any Marketo form and alter the "thank you" page destination using variables in ion's Creative Studio. This method requires custom scripting to pass data that isn't collected directly via form fill (things like IP address or the results of an interactive assessment) to hidden fields on your Marketo form. The benefits of this method are the ability to use form completion as a Smart List trigger/filter and the ability to leverage progressive profiling built in Marketo. This can also be a good solution for companies with strict data security policies who do not want lead form data stored in ion for any period of time.
Your Pardot form code is used to build a reusable widget in the ion platform. Once the widget is built, you can insert any Pardot form using variables in ion's creative studio. This method requires custom scripting or other specialized setup to pass data that isn't collected directly via form fill (things like IP address or the results of an interactive assessment) to hidden fields on your Pardot form, or if you wish to use the embedded form as a gate for interior ion pages. The primary benefit of this method is the ability to leverage progressive profiling built in Pardot. This can also be a good solution for companies with strict data security policies who do not want lead form data stored in ion for any period of time.
There are few items you'll need to roundup from RD Station prior to setting up the integration, listed below:
A private app needs to be created in RD Station in order to generate the REST API details.
Please find steps below to generate these details within RD Station. Should you need additional guidance with the steps below, please reach out to RD Station support.
Log into RD Station App Store
Click “Create App” button
Give your app a name, select a category and check the boxes for the languages you would like to support.
For the callback URL, use the below, but replace the bold part of the URL with your Ion console’s URL. Please note that the actual client ID value will replace the xxxxx placeholder in step 8.
https://yourcompany.postclickmarketing.com/Admin/Integration/RDStationAccounts/HandleCallback?clientid=xxxxx
Click “Save and next” button
The next screen will show you your app’s Client ID, Client Secret and the Callback URL. Copy both the Client ID and Client Secret values from this screen and save them in a separate document for later.
Edit your app’s information and replace the placeholder clientID value (xxxxx) with the Client ID value that you copied.
Save
You have two integration methods to select from when exporting data from ion to your Salesforce instance (also known as an "Add Lead" integration): the SFDC API method and the Web-to-Lead Form Post method. Both methods can work with your ion creatives. The best method for you will depend on whether you have support from your Salesforce admin and how many leads you anticipate collecting on a daily basis.
Note: Both integration methods can only create new Lead records. They cannot update existing Lead records or interact with other Salesforce objects.
A Form Post integration is what it sounds like: data collected by an ion form is re-posted to a Salesforce Web-to-Lead Form. Salesforce imposes a limit of 500 leads per day created via Web-to-Lead. If you are using the Web-to-Lead method for other integrations and/or anticipate collecting a large volume of leads via your ion creatives, this method may not be for you. The primary benefit of this method is the ease of implementation, as many Salesforce users have appropriate permissions to generate the Web-to-Lead Form.