Table Structure

Comments

2 comments

  • Avatar
    Todd Stoffer

    Hi Lisa Moffitt! If you are pulling data from Pendo via the aggregations API there isn't really a formal table structure to it. The API calls that you make include a source (like pageEvents, featureEvents, etc.). However, since aggregations can be written to pull from multiple sources - and transform the data in a variety of ways it is definitely possible that your data structure would be different from others using the same API to pull data. 

    However - here is a link to an ERD that Fivetran (one of our data-out partners) put together - https://docs.google.com/presentation/d/1HMUF-GiC2acnWkSflDr2M87LUdtL-F9XqjqX8lziSug/edit. This shows how they have implemented tables in their solution. You may find it helpful for your use case.

    Essentially it breaks every object in to 2 tables. So for guides you have the guide_history table that holds the data caputred when getting the guide object (who created the guide, guide ID, etc.) and the guide_events table that holds the actual events of when visitors saw the guide. The same is true for the features/featureEvents and pages/pageEvents. 

     

    0
    Comment actions Permalink
  • Avatar
    Lisa Moffitt

    Hi Todd Stoffer this is very helpful!  Thank you so much for passing this along.

    0
    Comment actions Permalink

Please sign in to leave a comment.