For those using INBOX25 landing pages, this article is important to understanding how record data is managed across multiple lists (either CRM or Marketing Lists). It is not an uncommon scenario to create a landing page mapped to (ex.) SugarCRM leads, but have a SugarCRM contact land on and fill out the page. In any default scenario INBOX25 will detect the existence of the SugarCRM contact and will not create that record as a new lead. The contact's profile would mark the conversion as having occurred on both the form results and INBOX25 Timeline Report.
Below is a landing page currently mapped to the SugarCRM leads module to keep our above example consistent.
When is this option helpful?
While the default method of scanning for duplicate records upon a landing page conversion is recommended, there may be certain situations in which a user would want to create a new record if the converted record does not exist on the list the landing page is mapped to.
For those using exclusively marketing lists, or a combination of CRM lists and marketing lists, you may want to keep the data between the two lists separate. It will all depend on your data structure and the organization behind it.
Selecting "No, don't check and create a new record" will disable INBOX25's check upon conversion and create a new record even if that record may exist within another list.
Note*- No matter which option is chosen, the system will always check if a converted record exists within the list the landing page is mapped to. INBOX25 will never create duplicate records across the same list.