Brokers...am I right??????

Hey friends,

I am wondering if any of you amazing people have built a dashboard (or custom report) that can find accounts that a total ticket count for a show that is higher (or equal to) your published ticket limits. We are trying to find an easy way to find accounts who have either: A) purchased to the ticket limit (or over somehow) on web orders and/or B) accounts that have placed multiple orders that bring them to a total ticket amount that is equal to or more than your ticket limit.

We have been getting slammed by chargebacks and we need to find every way possible to find these accounts as soon as possible to return those tickets before a chargeback would happen.

Any and all advice is appreciated.

Chris

Parents
  • I've written a sql query just because it was easier for me, but I feel as though some of these criteria could be duplicated in Analytics.

    1. Out of state address or out of state area code. (I uploaded a custom table that can associate phone area codes to their US states/cities, so probably can't be duplicated in analytics. You could use Geo Area as Evan suggested, depending on your normal out of state attendance.)
    2. Multiple orders to the same production season in a single day or consecutive days.
    3. Purchases over $500 worth of tickets.
    4. Purchases usually no more than 7 and no less than 2 days out from performance date, enough time to resell but not too far out that the chargeback shows up before the show.
    5. Shows with lots of ticket inventory, so multiple performances, almost always Broadway
    6. Customer account create date was same day or day before order. (I don't think account create date is in Analytics, but this proved to be a very important criteria in our search)

    We calculated these criteria by analyzing what amounted thousands of dollars worth of chargebacks from 2 spring Broadway and another earlier this fall. We diligently ran this query through our run of another Broadway show first weekend of October. The most recent Broadway show was more family oriented, so it might not have been as desirable a target for credit card scammers, but normally we would start receiving chargebacks within a week and a half after the show ends, but we have yet to see a single chargeback after we cancelled nearly a dozen orders for that show.

Reply
  • I've written a sql query just because it was easier for me, but I feel as though some of these criteria could be duplicated in Analytics.

    1. Out of state address or out of state area code. (I uploaded a custom table that can associate phone area codes to their US states/cities, so probably can't be duplicated in analytics. You could use Geo Area as Evan suggested, depending on your normal out of state attendance.)
    2. Multiple orders to the same production season in a single day or consecutive days.
    3. Purchases over $500 worth of tickets.
    4. Purchases usually no more than 7 and no less than 2 days out from performance date, enough time to resell but not too far out that the chargeback shows up before the show.
    5. Shows with lots of ticket inventory, so multiple performances, almost always Broadway
    6. Customer account create date was same day or day before order. (I don't think account create date is in Analytics, but this proved to be a very important criteria in our search)

    We calculated these criteria by analyzing what amounted thousands of dollars worth of chargebacks from 2 spring Broadway and another earlier this fall. We diligently ran this query through our run of another Broadway show first weekend of October. The most recent Broadway show was more family oriented, so it might not have been as desirable a target for credit card scammers, but normally we would start receiving chargebacks within a week and a half after the show ends, but we have yet to see a single chargeback after we cancelled nearly a dozen orders for that show.

Children
No Data