The Bucket Overwrite Loop Solution

We've received some questions about a specific use of BTBuckets upon overwriting buckets.
This situation occurs when you have a bucket A and bucket B and when you enter on bucket A you don't want to belong to B and vice versa. The natural thinking is to configure A overwriting B and B overwriting A. However, we cannot have 2 buckets overwriting each other (because the system will not allow users to be placed in buckets if they already are in another bucket that overwrites the new one).
BTBuckets works with the pyramid overwrite feature, which means that you can implement someting like Gold, Silver and Bronze buckets (gold overwrites silver and silver overwrites bronze).
To solve that overwrite loop problem, you can follow these simple steps:
1. Configure a bucket A with the behavior desired and include a OR condition with the event "create_a" in one time. You can use the parenthesis to isolate the expression;
2. Configure a bucket B with the behavior desired and overwriting bucfket A;
3. Create a new bucket C with the same behavior of bucket A. This is going to be your control bucket to garantee that you can overwrite the bucket B when you have the A behavior.
4. On bucket A setup, configure to overwrite bucket C. The table below resumes the buckets configuration.

Bucket	Behavior	Buckets to overwrite
A	(your desired behavior A) OR Event name: Viewed: create_a	C
B	your desired behavior B	A
C	your desired behavior A	B

5. The last step: on TARGETING menu, create a new targeting with the name "create a". Select the bucket C to execute the target. On Client-side Targeting Callback Code, include the follow code to execute on all pages:

<script>$BTB.trackEvent("create_a");</script>

Now, when you enter on bucket B overwriting A, and perform the A behavior, bucket C will be created overwriting B and will create bucket A which overwrites bucket C. You're going to have the A / B bucket switch as you perform A and B behaviors.
Although this solution works very well, we also think that it's not quite simple as we want to be. We already included in our release planning and soon we're going to launch as a feature.