Tracking Cookies

FunnelBud uses a "tracking cookie" to uniquely identify devices and browsers. Every time someone visits a website with the tracking code, a cookie is stored in their browser.

The cookie along identifies visitors and stores information about their activity on the site. Once the visitor is a "tracked contact", their site activity is automatically added to their contact record in FunnelBud

Are cookies the same as "tracking"?

A "tracked" visitor has their activity saved on their FunnelBud contact profile. A visitor is "tracked" only if they either:

The cookie is simply used to identify a web device and hence save the web activity from the device. Once the contact is "tracked", their device is associated with a contact record in FunnelBud and all the previous web activity is displayed there.

When is a cookie issued?

Whenever a visitor loads your site, if they do not have an existing cookie, the FunnelBud tracking code saves a cookie in their browser. All activity from the first, and all subsequent visits, from the device are saved, and once the visitor is "tracked", the activity is saved to their Contact record.

What if the cookie is deleted?

Are cookies reissued?

Yes, a new cookie is saved when a visitor who deleted cookies returns to your site.

If the visitor is "tracked" again, all activity from the device with the new cookie is added to the same contact record in FunnelBud.

Do you use 1st or 3rd party cookies?

Third party cookies are those that are set by another site than the one that you're currently on, and they allow the information in the cookie to be read across multiple sites. First party cookies can only be set and read by the site that actually sets them.

FunnelBud uses 1st party cookies. Except for Ads tracking, which today uses 3rd party cookies. This will be updated once Google releases their new and more secure methodology for advertising providers.

Can we change how long the _ss_tk saves information?

No, it will store information for 25 years. But you can delete the lead itself from FunnelBud, by for example setting a custom lead deletion process/automation for inactive leads or leads that should not be tracked after a certain time.

If you delete a lead from FunnelBud, the cookie would not tie information about that browser's activity with a lead in FunnelBud. However, if a person (with a deleted lead) ends up opting back in (complete form, etc.), the tracked activity would be tied to a newly created lead. The previous history from that deleted, original lead will not get connected to the new lead, as that data (in Life of the Lead) is lost upon deleting the lead.

What does the _ss_tk cookie do?

This is our main tracking cookie. It tracks visitors and form submissions and allows browser visits to be tied to the lead with the same cookie regardless of session or referrer.

Is it possible to remove the _ss_tk cookie?

No. Furthermore, this is what enables the core tracking functionality of the system so removing it would mean that the core functionality would be lost. (You can of course use FunnelBud without tracking, but this would limit many of the useful features you likely need in order to communicate more effectively with your clients.)

What information does the cookie collect before we create a lead in FunnelBud?

The cookie gathers the following information:

The pages the user has visited, in what sequence, and for how long. The type of device (mobile vs. desktop, operating system), the web browser being used, and IP address.

The cookie does not know any specific identifiers of a person otherwise (such a name). It would only connect the recorded activity to an identifiable lead if the person fills out a form / chatbot / shopping cart / API, or clicks a link in an email you send from FunnelBud.

Is it possible to implement consent banners on our website so that the cookie doesn't gather information about a lead until the visitor provides explicit consent?

Yes, please talk to FunnelBud to get help on implementing such a banner.

Related pages

Internal info:
More info on cookies