10%

Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(3)

Customer Journey(12)

Design(32)

Solar Industry(4)

User Experience(53)

Edtech(9)

Events(34)

HR Tech(2)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(15)

Testing(9)

Android(47)

Backend(29)

Dev Ops(4)

Enterprise Solution(23)

Frontend(28)

iOS(43)

Javascript(15)

AI in Insurance(33)

Insurtech(61)

Product Innovation(44)

Solutions(18)

E-health(7)

HealthTech(18)

mHealth(4)

Telehealth Care(2)

Telemedicine(3)

Artificial Intelligence(124)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(16)

FinTech(47)

Banking(4)

Intelligent Automation(26)

Machine Learning(46)

Natural Language Processing(13)

expand Menu Filters

“User Tracking Code” for Secure Lead Attribution

There are various insurance aggregators in the industry which frequently compare various insurance plans.

Often, a user might check out the details of a policy from the aggregator, but might not buy it from there.

There is a good chance that he goes to the actual insurance site and buys the policy from there.

In this case, both the aggregator and the insurance company agrees that the Lead has legitimately come from the Aggregator website.N000011en-zanox-Tracking-Process-3760x1400 copy

The question is, how do you understand the same?

This problem of attributing the source of a lead is solved by some third party tools. Both the websites keep a java-script code. So, if a user goes to the insurance detail page of the aggregator website, this executes a code and the third party sets a cookie on the browser.

Now, if the user visits the insurance site to