I was using Analytics to pull our subscription package revenue every week and all of a sudden, the numbers dropped drastically. When I try pulling the numbers from reports, I get a totally different number from a canned report and another one from a custom report. Looking for ticket price only, no facility fees included. Needing advice on the most accurate way to pull this. Perhaps my filters aren't configured in the best way in Analytics. Thanks!
Are you looking at weekly revenue or revenue to date? And do you do a lot of exchanges of package items?
Revenue to date and yes, we do a fair amount of exchanges within the subscriptions.
This is something we have issues with, which is that exchanges will cause money to evaporate out of packages sales. In the past we have done exchanges outside of the original order and into single ticket sales. Reports based on price type would work as we typically used a price type flagged as as subscription price type, but looking at the packages themselves you would see them start to shrivel after a certain date.
This year we're trying out exchanging into a purpose-built flex package: we'll still see money vanish from particular package types, but overall package figures should then remain closer and easier to report on in Analytics.
Hi Gawain,
I'm curious if in Analytics you've looked at this through the lens of Ticket Original Paid Amount: for a package, the original paid amount before any component performance tickets were returned for exchanges. This was introduced in an effort to skirt the package ticket exchanges issue, and does has a small gap on fully exchanged flex packages.
I have not and will look into it. Ticket Original Paid Amount is basically bringing in the returned status SLIs, correct? I assume it would not be able to distinguish between a ticket outright returned because a cashier, say, put it on the wrong account vs a ticket returned as part of an exchange? I'd say non-exchange returns are probably small enough that they wouldn't overly concern the people looking at these reports, but I'd definitely want to know what to expect.
Yes, the returned SLI are retained in Analytics with 0 for most values except the Original and Exchange amounts. It only does this when at least one seat (including base seat) is not returned. A fully returned package that was applied to the wrong account would not be in Analytics. The case of fully exchanged flex packages... there's no base seat that isn't returned, so Analytics errs on the side of considering it fully returned (excluded from Analytics) rather than fully exchanged.