Hello,
We are wondering if anyone is using constituencies to track new to file patrons. Ideally we would like to have this managed nightly with rules for adding and removing the constituency based on transaction history. If anyone is doing this, it would be great to find out best practices!Many Thanks,
Christopher S. Adriance
Marketing and Loyalty Campaigns Manager
Pacific Symphony
Hey Christopher,
We use attributes rather than constituency, and we add them manually.
At the moment we do a post-prod season analysis of New to File for each show, which involves deduping/merging, then using t-stats and extractions to narrow it down to all truly-new accounts; we then tag all accounts with an Attribute called "New Customer First Show" where the Value is the Production name. We also use pivot tables connected to T-stats so we can dynamically track what those customers bought subsequently, and we built a list criteria for the Attribute so we can easily pull a list of everyone who was new for a particular show.
But we are looking at automating part of the process, to add the attribute to an account whenever the first order is made. But it does create some issues with merges down the line when a supposedly New account is found to be a dupe.
Cheers,
Meg