Journey Analytics - licensing costs & how to assume number of rows | Community
Skip to main content
Michael_Soprano
Level 10
October 9, 2024
Question

Journey Analytics - licensing costs & how to assume number of rows

  • October 9, 2024
  • 1 reply
  • 600 views

Assuming that customer has 50 millions page views per month. Additionally there can be some additional events connected with search, add to cart, transactions and lead generation events.

If I have lookback period of 30 days there might be 60 millions rows. 

How you determine such an assumption? Do you have any hints & shortcuts? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SSampsa
Level 4
October 11, 2024

This is a tough one, since as you said, it really depends on two main factors:

  1. Amount of page loads (traditional or virtual)
  2. Amount of custom non-pageview events (such as download or exit links, button clicks and so on)

If we have the page view amount assumed, my personal method is something like this (this assumes we don't have Analytics already setup, if we do, it's easier to be accurate):

  1. Take amount of current (average per month for 6 months or so if possible) pageviews
  2. If the site has downloads and there is an estimate how many are triggered per month
  3. Exit links is a bit more difficult, depends a lot. Often times if this is not common for the content to link to outside sources, I usually skip this
  4. If there are custom in-page events (so events tracked as non-pageviews), such as button clicks, I get the amount of these actions triggered

After all this I usually add 20% to account for growth and changes in requirements. Note that if there is growth expectations, we can increase the estimated growth %.