How do Default Account, Track Anonymous Visitor, and Allow Inferred Account function on ABM Pages?

While configuring a new ABM Page or an existing one, under the Configure tab there are three options mentioned: Default Account, Track Anonymous Visitor, and Allow Inferred Accounts. Among the three options, the Default Account takes precedence. 

How do Default Account, Allow Anonymous Visitor, and Allow Inferred Account function on ABM Pages?

1. User accessing an ABM Page Base URL:
   • When none of the three options (Default Account, Track Anonymous Visitor, or Allow Inferred Account) are selected, No Guest Visitor is created.
   • When an ABM Page is configured with a Default Account, a guest visitor is created and automatically associated with the specified Default Account. 
   • When an ABM Page is configured with an Inferred Account based on your Data provider, a guest visitor is created with an Account based on the IP Address. In case a Data Provider is not configured, then the Guest Visitor is not created.
   •  When the Track Anonymous Visitor option is enabled on an ABM Page, any visitor accessing the base URL is tracked as a guest visitor. These guest visitors are initially associated with an "Unknown" account.
   • When the ABM Page is configured with both Track Anonymous Visitor and Default Account enabled, a Guest Visitor is created and automatically associated with the Default Account.
   • When an ABM Page is configured with both Track Anonymous Visitor and Inferred Account enabled:
     • If the Data Provider is available, a guest visitor is created with an Account based on the IP Address. 
     • If the Data Provider is not available, Guest Visitor is created under Unknown Account.
       
       
2. The user accesses an ABM Page Base URL and Submits an SNLP Form with an Email address whose Domain has an Account in the system.
   • When none of the three options (Default Account, Track Anonymous Visitor, or Allow Inferred Account) are selected, No Guest Visitor is created. On Form Submission a Lead is created and Enriched.
   • When an ABM Page is set up with a Default Account, a Guest Visitor is created and linked to the Default Account. On Form Submission, the Visitor's First and Last Name and Email are updated, but the Account stays as the Default Account.
   • When an ABM Page is configured with an Inferred Account:
     • If a Data Provider is available, a Guest Visitor is created under the Account provided by the Data Provider. On Form Submission the Name and Email are updated but not the Account.
     • If a Data Provider is not available, No Guest Visitor is created. On Form Submission a Lead is created and Enriched.
   • When an ABM Page is configured with the Track Anonymous Visitor option enabled, a Guest Visitor is created with the Account initially set to Unknown. On Form Submission, the Visitor's First and Last Name, Email, and Account are updated based on the email details submitted.
   • When an ABM Page is configured with Track Anonymous Visitor (TAV) and the Default Account enabled, a Guest Visitor is created and immediately associated with the Default Account. On Form Submission, the Visitor's First and Last Name and Email are updated, but the Account stays as the Default Account.  
   • When an ABM Page is configured with both Track Anonymous Visitor and Inferred Account enabled:
     •  If the Data Provider is available, a Guest Visitor is created and an Account is created based on the Data Provider.  On Form Submission, the First and Last Name and Email are updated but not the Account.
       
     • If the Data Provider is not available, a Guest Visitor is created with the Account as Unknown. On Form Submission, the First and Last Name, Email, and Account are updated based on the email details submitted. 
       
       
3. The user accesses an ABM Page Base URL and Submits an SNLP Form with an email address whose domain does not have an Account in the system.
   • When none of the three options (Default Account, Track Anonymous Visitor, or Allow Inferred Account) are selected, no guest user is created in the system. On Form Submission a Lead is created and Enriched but not a Guest Visitor.
   • When an ABM Page is configured with a Default Account, a Guest Visitor is created and automatically associated with the Default Account.
   • When an ABM Page is configured with an Inferred Account, a Guest Visitor is not created. On Form Submission a Lead is created and Enriched but not a Guest Visitor.
   • When an ABM Page is configured with the Track Anonymous Visitor option enabled, a Guest Visitor is created initially with the Account set to Unknown. On Form Submission the Guest Visitor Account, First Name, Last Name, and Email gets updated.
   • When an ABM Page is configured with Track Anonymous Visitor (TAV) and the Default Account enabled, a Guest Visitor is initially created and associated with the Default Account. Upon Form Submission, the visitor's First Name, Last Name, and Email are updated in the system; however, the Account remains unchanged and continues to be linked to the Default Account.
   • When an ABM Page is configured with both Tracked Anonymous Visitor and Inferred Account enabled:
     • If a Data provider is available, a Guest Visitor is initially created and associated with the Account provided by the Data Provider, and on Form Submission, the First and Last Name and email will get updated but not the Account.
     • if a Data provider is not available, a Guest Visitor is initially created with the Account as Unknow and on Form Submission, the Guest Visitor's First and Last Name, Email, and Account get updated based on the email provided by the Visitor.
       
       
4. User accessing an ABM Page Base URL and Submit an SNLP Form with an existing Visitor's Email address [glincoln.user1@volvo.com]
   • When none of the three options (Default Account, Track Anonymous Visitor, or Allow Inferred Account) are selected, no Guest Visitor is created in the system. On Form Submission a Lead is created and Enriched.
   • When an ABM Page is configured with a Default Account, Guest Visitor is created under Default Account. On Submitting the Form a Lead is created but the Visitor's FirstName, LastName, and Email are not updated
   • When an ABM Page is configured with an Inferred Account: 
     • If the Data Provider is not available, a Guest Visitor is not created. On Form Submission, the lead is created and enriched.
     • If the Data Provider is available, a Guest Visitor is created. On Form Submission, the First and Last Name, and Email is updated.
   • When an ABM Page is set up with the Track Anonymous Visitor option enabled, a Guest Visitor is initially created with the Account labeled as Unknown. After Form Submission, the Guest Visitor is replaced with the submitted information and no longer appears as "guest64904" in the Account visitor listing page.

   • When an ABM Page is configured with Track Anonymous Visitor (TAV) and the Default Account enabled, a Guest Visitor is created with the Default Account. On Form Submission, the Account remains the Default Account, and the Account Visitor is not updated with the submitted Email details.

   • When an ABM Page is configured with  Track Anonymous Visitor and Inferred Account enabled, a Guest Visitor is created and an Account is created based on the Data Provider. Even though the form submission happens the details will get updated to the existing Visitor.
     • If a Data provider is available, a Guest Visitor is initially created and associated with the Account provided by the Data Provider, and on Form Submission, the First and Last Name and email will get updated but not the Account.
     • if a Data provider is not available, a Guest Visitor is initially created with the Account labeled as Unknown. After Form Submission, the Guest Visitor is replaced with the submitted information and no longer appears as "guest64904" in the Account visitor listing page. 
       
       
5. The user accesses an ABM Page URL with a parameter [eg; acc=acme.com] and the Account exists in the system.
   • When none of the three options (Default Account, Track Anonymous Visitor, or Allow Inferred Account) is selected, a Guest Visitor is created in the system under the given Account [acme.com].
   • When an ABM Page is configured with a Default Account, a Guest Visitor is created under the Account passed in the URL Parameter [acc=acme.com].
   • When an ABM Page is configured with an Inferred Account, a Guest Visitor is created under the Account passed in the URL Parameter [acc=acme.com].
   • When an ABM Page is configured with the Track Anonymous Visitor, a Guest Visitor is created under the Account passed in the URL Parameter [acc=acme.com].
   • When an ABM Page is configured with Track Anonymous Visitor (TAV) and the Default Account enabled, a Guest Visitor is created under the Account passed in the URL Parameter [acc=acme.com].
   • When an ABM Page is configured with both Track Anonymous Visitor and Inferred Account enabled, a Guest Visitor is created under the Account passed in the URL Parameter [acc=acme.com].
     
     
6. The user accesses an ABM Page URL with a parameter [eg; acc=nokia.com] and the Account doesn't exist in the system. 
   • When none of the three options (Default Account, Track Anonymous Visitor, or Allow Inferred Account) is selected, no Guest Visitor is created in the system. 
   • When an ABM Page is configured with a Default Account, no Guest Visitor is created in the system. 
   • When an ABM Page is configured with an Inferred Account, no Guest Visitor is created in the system. 
   • When an ABM Page is configured with the Track Anonymous Visitor, no Guest Visitor is created in the system.
   • When an ABM Page is configured with Track Anonymous Visitor (TAV) and the Default Account enabled, no Guest Visitor is created in the system.
   • When an ABM Page is configured with  Track Anonymous Visitor and Inferred Account enabled, no Guest Visitor is created in the system.