Get to know your segments with Scitylana

Get to know your segments with Scitylana

 

So maybe you already heard the news, but if you havent’ we are happy to tell you that you are now able to extract the ClientID as hit-level data historically with Scitylana.

Basically this means that getting hit-level data has never been easier for you and this open up a world of opportunities.

One of the opportunities is especially interesting if you have a website where your customers login when they buy your services. If that is the case, you are now able to connect all the data you have on your customers and figure out which ads or messages they respond to, even cross device.

The problem with tracking cross device is that your customers often visit your website representing multiple cookie ID’s. But when you have hit-level data with ClientID in it, you are know able to match the customer ID from your ecommerce system with the multiple ClientID’s that each customer represents, so that you get a more complete view of the many interactions your customers has had with you.

If you tracked things properly you will be able to see which ads they responded to and how much money you have spend on that specific customers. You will be able to make much more sophitiscated attribution modeling, that can save you a lot of money, as was the case with Puori.

But what has that got to do with getting to know your segment with Scitylana you ask?

The answer to that is that if you collect demographic data on your customers in your ecommerce system, you will be able to merge that data with your Google Analytics data and create new segments, which will tell you more about which audience to target with what types of messages.

If you want to start your journey, you are 15 minutes and 10 clicks away from getting your Hit-level google analytics data with the ClientID. Just follow this simple guide and reach out to us if you want more inspiration or ideas on how to leverage the power of hit-level data

Leave a Comment

Your email address will not be published. Required fields are marked *