Note: This feature is available as a Professional Service if you have purchased the Personalization module.
To request this solution, send the Eloqua blind form link to professional-services@turtl.co and our Professional Services team will add an extension to your account. Please ensure this extension is turned on in your Doc settings.
1. Introduction
Among other methods, Turtl Docs can be personalized using a public personalization form, which visitors fill in. Their input data is stored in Turtl’s database and used to personalize their Doc.
This document describes how that data can be pushed into a 3rd party CRM, Eloqua, using blind form submissions. It does so by syncing tokens within the Turtl Doc with form fields from an Eloqua form. It does that automatically when the names of tokens and form fields are an exact match.
Requirements:
Turtl Doc with a public Personalization form and the "Sync Personalization data with Eloqua" extension turned on (found under "Settings" → “Extensions").
Tokens in a Turtl form need to match the name of Eloqua form fields.
The public Personalization form needs to have two invisible, pre-filled tokens called "elqSiteID" and "elqFormName" which should contain your Eloqua Site ID and your form name values, respectively. These values are required to sync the data.
2. Setting up an Eloqua form
Create an Eloqua form like you normally would with form fields you wish to capture from Turtl’s public Personalization form. Your Eloqua form should contain the same form fields, or fewer fields compared to the form on a Turtl Doc.
For each form field, make sure you know its name, not its label. For example, the name of the "Email Address" field is called "emailAddress" (letter case is important here). If you wish to sync the email addresses that you are collecting with Turtl’s public personalization form, make sure that the token in Turtl is also called "emailAddress". The same principle applies to all other form fields (in Eloqua) and token names (in Turtl).
You will also need to find your Eloqua Site ID and Eloqua Form Name that makes the blind form URL, e.g.
http://s[elqSiteID].t.eloqua.com/e/f2.aspx?elqFormName=[elqFormName]&elqSiteID=[elqSiteID]&emailAddress=…
Turtl will use those two values to generate the complete blind form submit URL. You will need this in the next step.
3. Setting up a public personalized form
Design your public Personalization form like you normally would, but keep in mind that tokens need to be named exactly as Eloqua form fields you wish that data to flow to.
In addition to that, please add two new "Single line" fields to the form and name them tokens "elqSiteID" and "elqFormName". Enter your Eloqua Site ID and Eloqua Form Name into the "Prefill value" fields.
Mark those two form fields as invisible under the "Advanced" settings. This would ensure that the visitors of your Doc don’t see it, but its values are passed on to the extension that syncs the data with that Eloqua form.
4. That’s it!
Once your forms are set up, you can test the functionality by filling out a public personalization form in a Turtl Doc. This should generate your personalized Doc and automatically send the submitted data to Eloqua.