Filter Dimention Attribution: Repeating (default), Instance, Non-Repeating Instance

Hi,

In the screenshot you attached (pasted here for reference, so that no one has to download it)

"Event 4" isn't recorded as an instance because the value is persisted...  and no, renaming "Instance" to "Non-consecutive Instance" doesn't make sense, because that isn't the behaviour here... that is already covered by "Non-repeating Instance".

So, let's break this down:

• Event 1
  • Page Name is set to "Women"
    • Since the value is being explicitly set, this will count against the default (repeating) attribution, as well as the instance (because the value is explicitly being set)
    • The Non-Repeating Instance will also appear here, because there is no previous value (and therefore no consecutive value)
• Event 2
  • Page Name is set to "Met"
    • Since we are looking for "women", this won't apply
• Event 3
  • Page Name is set to "Women"
    • Since the value is being explicitly set, this will count against the default (repeating) attribution, as well as the instance (because the value is explicitly being set)
    • Here I think the documentation is wrong, I think the non-repeating instance would count here, since the previous value was "men" (this is how it works in AA)... also the later example when the value changes from Checkout (Event 5) to Women (Event 6) shows it counting...  I would assume that this is a mistake that should be fixed...
• Event 4
  • Page Name is not set, the value "Women" persists due to the attribution on the value
    • The Repeating (default) attribution counts here, because there is an occurrence, and the value is "Women" through the persistence
    • The Instance will not count, because the value was not explicitly set... therefore it is not an instance
    • The Non-Repeating Instance would not count because again this isn't an instance (repeating or not) - I will add another example below to account for this scenario (which hasn't been properly shown in this example)
• Event 5
  • Page Name is set to "Checkout"
    • Since we are looking for "women", this won't apply
• Event 6
  • Page Name is set to "Women"
    • Since the value is being explicitly set, this will count against the default (repeating) attribution, as well as the instance (because the value is explicitly being set)
    • Here is the exact same scenario as "Men" before, but this time shows the correct behaviour... the non-repeating instance would count because the previous value was "Checkout"
• Event 7
  • Page Name is set to "Home"
    • Since we are looking for "women", this won't apply

Now, to properly cover the "non-repeating instance" scenario....

• Event 1
  • Page Name is set to "Women"
  • Since the value is being explicitly set, this will count against the default (repeating) attribution, as well as the instance (because the value is explicitly being set)
  • The Non-Repeating Instance will also appear here, because there is no previous value (and therefore no consecutive value)
• Event 2
  • Page Name is set to "Women"
  • Since the value is being explicitly set, this will count against the default (repeating) attribution, as well as the instance (because the value is explicitly being set)
  • The Non-Repeating Instance will be excluded, because even though this is an instance (i.e. the value is being explicitly set), it value is repeated from the last event and therefore will be excluded.

That is the difference between Instance and Non-Repeating Instance; even if the value is explicitly set, the consecutive (or repeating values) are excluded.