Overview

We are now introducing a flexible system that allows you to capture registration attempts based on your needs. This update ensures all lead inflows are accurately tracked and managed according to your business processes. Users can customize tracking behaviors for different lead inflows, aligning the system with your lead nurturing process.

With this flexibility, you can customize the registration attempt settings to better fit your workflows, ensuring the system supports your unique business needs.

Benefits

Customizable Tracking:
With the ability to configure registration attempts based on origin and action, you can customize the tracking to match your unique business processes. This flexibility ensures that the CRM aligns with how you manage leads, providing more relevant data and insights.

Improved Lead Tracking:
Configuring registration attempts allows you to capture every interaction a lead has with your system, whether it's a add quick lead, update via an API, or updating via Widget. This ensures that no interaction goes unnoticed, giving you a complete picture of lead behavior.

How to Configure Registration Attempts?

1. Access the Registration Attempt Configuration:
   
1. Navigate to the Settings menu in your CRM.
2. Select Registration Attempts configuration under the Lead Flow section.
   
   
2. Set the attempt type for each Lead Inflow:
   For each origin, decide when a registration attempt should be recorded:
1. Lead Create Only: Registration Attempt count increases only when a lead is created using this origin.
   
2. Lead Create or Update: Registration Attempt count increases both when a lead is created or updated, even if no significant changes are made.
   
3. Never: Registration Attempt never increases when a lead is created.
   
   This can be configured based on your business requirements.
   
   
3. Save and Implement:
   
1. Once you’ve configured the settings to your satisfaction, click Save to implement the changes.
2. The registration attempts will now be captured as per your configuration.
   
   
4. Monitor and Adjust:
   
1. Make adjustments as necessary to refine your lead tracking and ensure it supports your evolving business needs.
   

Registration Attempt Configuration Table:

The table below outlines the various scenarios under which a registration attempt is logged. The values highlighted in blue represent the default settings. If no changes are made to the configuration, the registration attempt will follow these default behaviors.

FAQs

How registration attempts are captured for APIs?

Users can use a registration attempt field key to pass on a registration attempt when sending hits via API. This ensures accurate tracking and updating of registration attempts across systems and processes. Use the key field_registration_attempt in your API payloads:

• If the field_registration_attempt is present, its value will increment the registration attempt count.
• If not present, the system will follow existing logic (e.g. Count on Creation, Count on Creation and Update, Never).

Values passed here: Yes | No. This field is optional and maintains backward compatibility.

How registration attempts are captured using the Bulk Offline Upload/ Upload Bulk Application?

Use the "Field Registration Attempt" key to pass a registration attempt during Bulk Offline Upload/ Upload Bulk Application. 

     • If the "Field Registration Attempt" has a value of "Yes", this would increase the registration attempt count for the lead by 1.
     • If the "Field Registration Attempt" has a value of "No", then the registration attempt will not be updated.
     • If the "Field Registration Attempt" is absent, the system will not update the registration attempt for the lead.
     Values passed here: Yes | No. This field is optional.

How registration attempts are captured using the Widget?

You can configure each widget to a registration attempt type, which gives you the ability to capture the registration attempts from the specified widgets.

By default, the new widgets will fall into the “On Create and Update” category.
If any widget is unselected, then by default it would work as “On Create and Update”.