Customerlabs CDP Documentation
Form submission tracking
Watch this video to track the form submit.
No Code Tracker- Form Submission Tracking
- Introduction
- Lead event
- Create User
- Steps
Introduction:
The No code event tracker enables the marketers/customer/agency owners to track and analyze the website events in real-time without developer support
Lead Event:
In layman’s terms, a lead event refers to an event in which someone is interested in your service or product. For example, when someone registers for a webinar, it shows they are interested in your webinar event, or if someone schedules a demo call for your SaaS product. These examples are considered Lead events, and they vary from business to business.
How to Capture the Lead Event?
To capture the lead event, please follow the steps below given in the documentation
Step 1: Sign In to your CustomerLabs account and update the tracking code on your website.
To update the tracking code, follow the steps given below:
- If you are using a Shopify platform for your website, please refer to the documentation for reference.
- If you are using a Woocommerce platform for your website, please refer to the documentation for reference.
- If you are using a Big Commerce platform for your website, please refer to the documentation for reference.
- If you are using JS platform for your website, please refer to the documentation for reference.
Step 2: To launch the No Code Tracker/Action Recorder, click on the icon.
You can access the action recorder from the home and event manager pages.
Step 3: You will be redirected to your website, where the action recorder/no code tracker panel will open.
Step 4: Click on Record Action:
Step 5: Select the event name from the dropdown as โLeadโ or you can choose the custom action name and name the event as per your needs while naming the events to make sure you name the event in a small case (eg: lead, lead_demo,lead_register)
Step 6:
Case-1:
After naming the event, select the element picker (pick the button) and enable the pick the common selector (the common selector helps you track all similar actions or items on your website without having to set up tracking for each item one by one
Case-2:
Else If you are using different forms on different pages on the website, select the element picker and choose the specific selector for that element. This will ensure that tracking is set up only for that particular form or action on the page.
Step 6: Verify the selector.
After selecting the selector, verify the selector before proceeding with the next steps
To verify the selector, click on the pencil icon. Youโll receive a “selector verified” message if itโs correct; otherwise, it will show “selector does not match.”
Note: Steps to be followed while selecting the selector
Step 7: Data collected on your page
Skip the data collected on your page and choose the next post action trigger
Why are we not collecting the user information in the Lead event?
As per the ad platform standards, user information must be hashed before being sent to the ad platforms. If you collect user information in the Lead event, it will be treated as an event attribute.
ย For each user, the system generates a unique user ID, which is used to stitch the journey together.
If you collect user information in the ‘Create User’ event, the system can identify the user based on the details collected.
The user information will be hashed and sent to the ad platforms.
Step 8: Post Action Trigger:
If your forms have any successful scenarios, you can add the paths and save the success scenario, then click the ‘Next Tracking Rule’ button.
Here, the success scenario means that after the user fills out the form, they are redirected to a โconfirmation pageโ or โthankyou page”
Here, the trigger path means where the forms are located on your website
An example of a form with a success scenario screenshot is attached below for reference.
Step 9: Tracking page
If you want to track your form submissions the page where the form is located will be your tracking page where the tracking will happen and the thank you or confirmation page will serve as your success page.
Step 10: Create a create user event
Similarly, follow the steps followed for creating the lead event.
Step 11: Creation of create user event
Choose the Create user event from the dropdown choose the action button and follow the steps given below
Step 12: Search and assign the external ID
Select ‘identify_by_email’ from the attribute dropdown and use the element picker to capture the email section.
Step 13: Data collected on your page
While setting up the create or update user event, the form fields that give more information about the user must be added as user traits. In this example, fields such as name, and mail should be added as user traits and it helps in the enrichment of the data.
Choose the custom attribute and name it in the form as email, first_name, last_name, or phone_number as required in the form
If your form collects both the phone number and email, follow these steps
choose the custom attribute, name it as ‘identify_by_phone’, enable the ‘external ID’ radio button, and save.
Similarly, verify the selector and proceed further with the next steps
An example of a create user event is given below,
Step 14: Post Action Trigger:
If your forms have any successful scenarios, you can add the paths and save the success scenario, then click the ‘Next Tracking Rule’ button.
Here, the success scenario means that after the user fills out the form, they are redirected to a โconfirmation pageโ or โthankyou page”
Here, the trigger path means where the forms are located on your website
An example of a form with a success scenario screenshot is attached below for reference.
Step 15: Tracking page
If you want to track your form submissions the page where the form is located will be your tracking page where the tracking will happen and the thank you or confirmation page will serve as your success page.
