SEAL tracks in aggregated way what is happening in your website, basically SEAL counts page views. When a page view triggers a “lead-microconversion”, for example, a “thank you page”; SEAL pixel hash’s the email directly from the customer’s website and sends to SEALmetrics the information hashed! We don’t see, store or land in our servers any personal data. All it’s happening in our customers’ site

This hashed data is counted, it’s NOT related to a journey because as we said before, we don’t work analyzing customer journey or any kind of individual tracking.

So we have page views + leads, all on an aggregated basis.

The next step is when this lead becomes conversion, because, for example, our customer’s contact center closed this lead.

When our customer closes this deal, send us via API or Zapier (coming soon), the information about this lead now is client, then our API hashed all the information.

SEAL counts this offline conversion.

So, we have page views + leads + conversions, all on aggregated basis.

I’m going to explain in bullets for making easier the explanation:

Aggregated basis: We don’t track individually
Leads are hashed from customer’s site. (anonimous)
Conversions are hashed when they are sent to us. (anonimous)
SEAL can’t match a hashed info to an individual journey.

then we can track offline conversions being completely GDPR and ePrivacy compliant.