Analytics - New To File

Hi Rachel, 

Not sure if this is helpful but the create date dimensions are specific to the cube that your dashboard is referencing. If you use the memberships cube, for instance, the create date dimension is based on membership create date, rather than a ticket related create date. However I don't think any of the create date fields are for the creation of the constituent record

One option for getting this date is to configure one of the custom date filters on the constituent dimension to pull constituent create date. These custom categories are defined in the TX_ANALYTICS_DIVISION_ELEMENT table. 

Hi Rachel, 

Not sure if this is helpful but the create date dimensions are specific to the cube that your dashboard is referencing. If you use the memberships cube, for instance, the create date dimension is based on membership create date, rather than a ticket related create date. However I don't think any of the create date fields are for the creation of the constituent record

One option for getting this date is to configure one of the custom date filters on the constituent dimension to pull constituent create date. These custom categories are defined in the TX_ANALYTICS_DIVISION_ELEMENT table. 

Amanda,

That's very helpful! Thank you. I'll have to look into configuring one of the custom date fields for this purpose.

Appreciate your response!

One other option I just thought of is to create a list with Constituent create date as your criteria with the date relative to run date of the list and use that as a filter for your fields. I believe you would have to set the list to generate each day so that updated data was captured in Analytics. 

Filtering using lists is described here: https://www.tessituranetwork.com/Tessitura_Analytics/Tessitura_Analytics.htm#Designing%20Dashboards/Filter%20by%20List.htm%3FTocPath%3DDesigning%2520and%2520Editing%2520Dashboards%7CDashboard%2520and%2520Widget%2520Filters%7C_____3

That sounds like that could work! Since analytics is refreshed nightly, I would likely have to set my list to the previous day, correct? 

Thank you so much for your help with this!

Your data would always be a day behind in Analytics but your list criteria should be set to the actual date range you want to see, if that makes sense - The data pulled into Analytics would be based on the data in the list for the last time it was generated on the night of each incremental load. So if you wanted to see constituents created the day before in Analytics you would set the list criteria to the run date of your list and then run it at the end each day before your Analytics incremental runs. 

Hi Amanda,

Setting a constituent element to pull the create date on the constituent record is one of the simplest options to configure.


Set Data Select to: MIN(create_dt)
Set Data From to: dbo.t_customer q

After your next full load of Analytics, you'll be able to report on this field.

Best,
Chris

Chris,

If I am on RAMP, do I need to do anything additional, or can I simply set this field up and expect to see it the following day in analytics?

Hi Rachel,

Configurable in RAMP. You or the appropriate person, just need log in with User Group permissions that have Administrative access to System Tables.

Best,
Chris

Great! Thank you!

Hi Chris, 

I think this actually would answer the new thread I had made recently, about having new to file, by both the first performance date, and also the constituent create date. 

While I config Tess to send this, can you share your formula for the above bar chart?

Thanks and most appreciated,

Mike

Hi Michael,

It's just:

• Production on categories
• # of unique Constituent ID as the value
• Break by Years in Custom Date 01 (configured to return the constituent record create date)

presented in a stacked column.

Cheers.

Hi Chris,

Super helpful.  This is great and I am using this now.

Thanks!

Hi. I know this thread is old, but when configuring the custom elements - is the best practice to rename them to something more user friendly, or should they remain Custom Date 01 etc?

Thanks in advance!

Hi Katie, I believe renaming TR_ANALYTICS_ELEMENT Custom Element names will break the import

https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_marketing-9/28014/setting-up-analytics-constituent-attribute-filters/76815?_ga=2.133167502.1894243030.1661135559-1697110432.1657872021