• Replies 3 replies
  • Subscribers 961 subscribers
  • Views 96 views
  • Users 0 members are here
Related

Tracking Subscription sales revenue

Hilary Leierer
$organization

Hi all,

I have a widget in my Subscriptions dashboard that tracks a daily running total for each of our subscription packages. The problem I'm encountering is that the data rarely matches or even comes close to other reports that we use daily. Some of our smaller packages, Jazz for example, are usually pretty close but our Broadway season is always way off. Wondering if it's not counting package fees or something else that I'm not considering. This is the formula I'm currently using for revenue:   RSUM([Total Ticket Original Value])

I've tried a few different ticket value metrics, wondering if there is another piece that I am missing. 

Thanks for any advice!

Parents
  • $organization

    Hi Hilary,

    From Cube Field Definitions > Seats and Tickets Cube

    Ticket Original Paid Amount For a package, the original paid amount before any component performance tickets were returned for exchanges. Flex packages where all performance have been exchanged can not be discriminated from flex packages that have been returned, and as such, neither are included in Analytics. This field has no practical use for individual performances.

    All tickets in Analytics have a Ticket Original Paid Amount regardless of whether they are part of a package. If the scope of your widget is not limited to packages, for example, includes tickets from all price types in the Subscription price type category, then the single tickets resulting from exchanges will be included. This will double count the paid amount from the original sale of the package and by including the value of the exchanged-into ticket.

    I recommend either:

    • Use [Ticket Original Paid Amount] and filter on [Is Package Flag] = Y to limit the scope to only packages and exclude the single tickets they may have exchanged into, which will show the money on the original package and performances.
    • Use [Ticket Paid Amount] or [Ticket Paid/Reserved Amount] and filter on [Price Type Category] to show the money on the exchanged into performances and not on the original packages and performances in those packages.
Reply
  • $organization

    Hi Hilary,

    From Cube Field Definitions > Seats and Tickets Cube

    Ticket Original Paid Amount For a package, the original paid amount before any component performance tickets were returned for exchanges. Flex packages where all performance have been exchanged can not be discriminated from flex packages that have been returned, and as such, neither are included in Analytics. This field has no practical use for individual performances.

    All tickets in Analytics have a Ticket Original Paid Amount regardless of whether they are part of a package. If the scope of your widget is not limited to packages, for example, includes tickets from all price types in the Subscription price type category, then the single tickets resulting from exchanges will be included. This will double count the paid amount from the original sale of the package and by including the value of the exchanged-into ticket.

    I recommend either:

    • Use [Ticket Original Paid Amount] and filter on [Is Package Flag] = Y to limit the scope to only packages and exclude the single tickets they may have exchanged into, which will show the money on the original package and performances.
    • Use [Ticket Paid Amount] or [Ticket Paid/Reserved Amount] and filter on [Price Type Category] to show the money on the exchanged into performances and not on the original packages and performances in those packages.
Children
No Data