Data Quality Throughout Warmly

Why am I seeing different data in Slack vs Warm Visitors?

You might notice that the notifications coming through Slack sometimes might not match what you see in Warm Accounts and Warm Visitors, but why?

• Remember, the purpose of the Slack integration is to get live notifications when someone is on your site so your team can "Warm Call" them and chat live to book a meeting.

• Warmly sends off Slack notifications as quickly as possible to allow your team to catch the visitor before they leave the site.

• However, some of Warmly's identification methods take 15-45 minutes, so in some cases, visitors are only identified after leaving the site.

• Slack notifications will also not send if Warmly is still processing the visitor (if it goes through enrichment, CRM/segment check). If the visitor left the site before full identification then Warmly will not send a notification at all. The only place to see these visitors are through Warm Accounts/Warm Visitors.

• If Warmly initially identifies a visitor as Alan, but on their next visit a different data vendor identifies them as Ryan, Warmly will update the visitor information to reflect Ryan as a separate person.

Consider the following example:

• Someone visits your website (anonymous)

• Slack is not fired because this anonymous visitor doesn't match the segments applied to your Slack channels

• Chat is not fired because this anonymous visitor doesn't match the segments on the Chat workflow

• 45 minutes later we identify this person as [email protected]

Why am I seeing different data in Warmly vs Google Analytics?

This is normal and there are a handful of reasons why you'll see different data across Warmly and Google Analytics:

• Warmly filters out bot traffic

• Warmly begins to identify someone once they take an action on your site (scrolling, clicking, typing)

Warmly does a lot of filtering to remove bot traffic and provides roughly 65% company-level and 15-20% individual-level identification. This is why Warmly is delivering the best, hottest leads (no bots!) though we're not able to get all of them based on how we identify.

Bot Traffic Filtering and Lead Credits

How does Warmly handle bot traffic, and does it count toward my credits?

Warmly's approach to bot traffic is to balance lead quality with comprehensive visitor capture:

• Obvious bot traffic is always filtered out - This traffic never consumes your lead credits and represents clear non-human visitors

• All other traffic is counted - We capture all visitor traffic except obvious bots. This ensures we don't miss legitimate leads who may not immediately interact with your site

• Approximately 5% of credits may go to sophisticated bots - While we filter obvious bot traffic, some advanced bots may still consume credits. This trade-off ensures we capture all genuine high-intent visitors

Managing Traffic Quality with the Data Quality Slider

The Data Quality Slider Feature gives you control over this balance:

• Higher quality setting: Filters out more potential bot traffic but may exclude some legitimate visitors

• Lower quality setting: Captures more comprehensive traffic including edge cases that might be valuable leads

This flexibility allows you to optimize based on your specific needs - whether you prioritize lead volume or lead precision.

Note: When viewing your credit usage, the count reflects all identified traffic excluding obvious bots. The Data Quality Slider helps you further refine what appears in your Warm Accounts and Warm Visitors views, but doesn't affect credit consumption.

This article was written by the Customer Success team at Warmly. Please feel free to reach out to your CSM directly or [email protected]