This article will show you how to solve common pre-population issues. Please note that the first section only applies to Eloqua.
If your gate script is present and rendering correctly but no pre-population is occurring, you need to identify which pre-population method is not working. Formulayt uses two types of pre-population to ensure the best user experience.
Troubleshooting marketing automation platform (MAP) pre-Population
Eloqua
To verify if the Eloqua script is running properly:
Open the browser console
Type _elq directly into the console (not the search or filter) and press Enter
Do the same for _elqQ
Check for error messages
If you see a red error message like the one below, the Eloqua tracking script is missing and needs to be added:
If the script is on the page correctly, you should see a message like this:
Additionally, alongside the Eloqua tracking script, the current user's Cookie ID must be known for pre-population to occur.
Troubleshooting Formulayt's built-in browser cache
Formulayt stores a snapshot of submission data in an encrypted storage key within the browser every time a form is submitted. This allows pre-population of subsequent forms without relying on up-to-date Eloqua contact records. Occasionally, this caching layer can affect testing of MAP pre-population, and you may need to clear it.
To clear the browser storage:
Open developer tools
Go to Applications tab
Expand Local Storage
Click on the item that matches the current page's domain
Locate the GCDCApp key
Delete the key using the X button
Repeat the same steps for Session Storage
Hard refresh the page
You can hard refresh by right-clicking the refresh button while the developer tools window is open.
After following these steps, any pre-population data must be coming from the MAP, as you've cleared the local browser cache.