Codat - Data - Page 2 of 2

Thoughts on the world of data from the Codat team

5 things you need to know before you integrate with the QuickBooks Online API

Tips for building an integration with the QuickBooks Online API that the docs don’t tell you—from one of the Engineers who built ours. While the SMB…

Data

What is a universal API, anyway?

Learn the difference between a universal, unified, and financial data API and how to find the right solution for your business needs. At the most basic…

Guides

Integrating banking and accounting data for better SMB lending

Taking a comprehensive approach to business data helps lenders make smarter, faster, and more confident credit decisions. When it comes to underwriting financial services for SMBs,…

Data

How can we tackle data security concerns?

In this new and fast expanding world of open data, it’s time to show that data sharing is nothing to be afraid of. The new era…

Data

Who will SMEs turn to for credit in 2020?

Small businesses make up over 50% of developed economies, as banks continue to under serve, other players are stepping up to the plate. As the number…

Data

The digitisation opportunity in SME lending beyond client dashboards

Automation will not only help SME lenders automate manual processes but also remain relevant as distribution channels digitise Many lenders to small businesses think that automation…

Cookie	Duration	Description
cookielawinfo-checkbox-analytics	1 year	This cookies is set by GDPR Cookie Consent WordPress Plugin. The cookie is used to remember the user consent for the cookies under the category "Analytics".
cookielawinfo-checkbox-necessary	1 year	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
viewed_cookie_policy	1 year	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.

Cookie	Duration	Description
lpv887333	30 minutes	No description
visitor_id887333	10 years	No description
visitor_id887333-hash	10 years	No description

Cookie	Duration	Description
_ga	2 years	This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
_gat_gtag_UA_89798244_1	1 minute	Google Analytics cookies are used to collect information about how Visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of Visitors to the site, where Visitors have come to the site from, and the pages they visited.
_gid	1 day	This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
_hjAbsoluteSessionInProgress	30 minutes	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
_hjFirstSeen	30 minutes	This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
_hjid	1 year	This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_hjIncludedInPageviewSample	2 minutes	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.
_hjTLDTest	session	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
_lfa	2 years	This cookie is set by the provider Leadfeeder. This cookie is used for identifying the IP address of devices visiting the website. The cookie collects information such as IP addresses, time spent on website and page requests for the visits.This collected information is used for retargeting of multiple users routing from the same IP address.
pardot	past	The cookie is set when the visitor is logged in as a Pardot user.
vuid	2 years	This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.

Data

5 things you need to know before you integrate wit...

Data

What is a universal API, anyway?

Guides

Integrating banking and accounting data for better SMB lending

Data

How can we tackle data security concerns?

Data

Who will SMEs turn to for credit in 2020?

Data

The digitisation opportunity in SME lending beyond...

5 things you need to know before you integrate with the QuickBooks Online API

What is a universal API, anyway?

Integrating banking and accounting data for better SMB lending

How can we tackle data security concerns?

Who will SMEs turn to for credit in 2020?

The digitisation opportunity in SME lending beyond client dashboards

Want to get started?