Why place Factors's SDK on your website?
Tracks website analytics metrics like pageviews, sessions, time spent/session duration, bounces, exit and page scroll %.
Tracks website analytics dimensions like UTMs, page URLs, referral URLs, channel (organic search, direct, paid etc), geography (pincode, city, country, continent), device type, device brand and OS.
Tracks form submit events automatically with form name, form id, page URL on which form was submitted, timestamp of form submit, form fields (email, name, etc). More details around form submission capture here.
Auto excludes bot traffic.
Uses proprietary rules engine to identify same users across devices (if they identify using form fill) and maps a website visitor to a Lead/Contact/Opportunity/Deal from your CRM. Hence serves as an easy way to do end-to-end customer journey analytics and attribution.
Thus, Factors's SDK solves for website analytics, customer journey analytics and multi-touch attribution.
How is Factors's SDK better than Google Analytics's SDK/tag?
Unlike GA, Factors's SDK captures page time spent and avg. session duration metric accurately. Factors's SDK looks for active engagement on the webpage like cursor movements to track time spent and hence doesn't consider idle time on the web page as part of time spent.
Unlike GA, Factors's doesn't sample data in any way for higher data volume. Hence you have access to the accurate nos inside Factors.
Where to place Factors's SDK?
On any webpage (owned by your organisation) where your prospects interact with your brand and content or fills out a form:
Blogs, webinar, case studies or any other resource pages including the ones hosted on 3rd party CMS like WordPress, Hubspot Blogs, etc.
Sign up or login pages including the one hosted on the product app. Below is an example of sign-up page of Hubspot hosted on the app. Note that the SDK is to be placed only on the sign or login page but not the entire app or product URLs.
Pages where lead gen, content forms, and any type of inbound forms are hosted.
Landing pages including the ones hosted on 3rd party CMS like WordPress, Hubspot Blogs, etc or landing page builders like Instapage, Wix, Leadpages, etc.
Where NOT to place Factors's SDK?
Inside the app or product
Pages where you don't want to track website engagement or activity like help docs, careers page, etc for marketing/sales purposes.
[IMPORTANT] How to place Factors's SDK the right way?
There are two ways to place the SDK. Either ways you MUST ensure that the SDK is placed in the <head> section of the every web page. Firstly, let us understand why is it essential to place the SDK in <head> section, and generally why is it not advised to place marketing tags in the <head> section but why Factors's SDK trumps the usual marketing tags.
Why is it advised to NOT place marketing tags in the <head> section? To decrease the load time of the page and thus improve page performance (also has an impact on SEO efforts). E.g., if marketing tags are placed in the head section and they take time to load, it leads to delay in the loading of content (text, images, GIFs, etc) of the page causing poor web experience.
How is Factors's SDK different than the usual marketing tags?
Unlike other marketing tags, Factors's SDK is asynchronous. It means that the SDK doesn't impact the loading of other content or tags on the website. Hence it doesn't affect page load time or performance in any way.
Size of SDK is just 22Kbs. This is one of the lightest marketing tags you would ever come across.
Load time of Factors's SDK is less than 10ms for the first time load, and less than 5ms for consecutive loads.
Factors's Engg team has done the performance analysis for a few of our enterprise clients that have millions of website visitors per month. The results of the analyses have consistently proved that the SDK doesn't impact website performance, load time or SEO in any way.
Now that we've established that there is no harm at all in placing Factors's SDK in the <head> section of your website, let us understand why to place it in the <head> section and the impact of NOT doing so:
The SDK takes a few seconds (even upto 7-8 seconds in a few cases) to load due to other async marketing tags
Missing out on website visitors and users, and associated UTM parameters leading to incomplete tracking.
Upto 10% of total form fills not getting captured causing less no of leads/contacts getting attributed to the online channels.
In conclusion- it will impact end to end customer journey analytics and attribution reporting. We have seen this happening with a few our early customers and the problems were fixed as soon as the SDK was placed in the <head> section.
If you or your web-dev/IT team still needs more convincing on this, please write to us at firstname.lastname@example.org / email@example.com or just raise a concern with your Customer Success Manager at Factors.
Let us look at the 2 ways to place Factors's SDK on your website:
A.] Using a tag manager or container like Google Tag Manager (GTM): This method is preferred as it doesn't require any developer help. Below are the steps which will take maximum 2 mins to complete once you have publisher access to your GTM. Here is the link to the doc that contains steps to place the SDK using GTM. This takes upto 2 mins of your time. Note that the GTM has to be placed in the <head> in order to use this option. Else, go with the second option.
B.] This option requires help from your web developer or IT team. Just share the SDK code with your web developer and ask them to place in the <head> and </head> tags.