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

[Rafael_Sahagun]

Hi All happy '25,

I need clarification of the types of attribution on the box before last at bottom of page here (also attached to this post):

https://experienceleague.adobe.com/en/docs/analytics-platform/using/cja-components/cja-filters/filte...

I'm going to assume Events in the box are not 'metrics' in a traditional Adobe Analytics (as in event1 means form completion etc) way but a sequence of actions taken in a session, such as step 1, 2, etc.

Repeating (default), first row:

All events (steps) look fine except Event 4, why does it need to use persistence when Page Name equals Women is being hit at that moment?

Instance, second row:

Why isn't Event 4 being recorded? I'm thinking it is a page reload and instances are only counted when there are other pages (or different dimension values) between in the journey? if so perhaps adding that in the explanation to the documentation will make it easier to comprehend.

Non-repeating instance, third row:

I'd think is only recorded in the first step and never again, why is being repeated in Event 6?

Thanks!

Rafael Sahagun

[Rafael_Sahagun]

perhaps 'Instance' could be renamed 'Non-consecutive Instance'

[Jennifer_Dungan · Accepted solution]

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.

[Rafael_Sahagun]

Thanks @Jennifer_Dungan!

The explanation table from Adobe Analytics below doesn't have Event 2 and the why Event 3 is not part of the Non-repeating instance segment.

Since CJA's table has Event 2 (which is not Page Name equals Women), then Event 3 should be part of the filter as you mentioned.

I would find it useful if your explanation was added to the documentation.

Part of my confusion was to think each step was a page view and didn't make sense a value was being persisted on a page, and as someone else pointed out an example would be a link click, which looking at the journey could be 'add to cart', all kind of unrelated to the point of the table which seems to mark weather each data point in the journey would be part of a segment (filter) based on each attribution method.

[Rafael_Sahagun]

Edit: 'The explanation table from Adobe Analytics below doesn't have a different value in Event 2 and the why Event 3 is not part of the Non-repeating instance segment.'

[Jennifer_Dungan]

I am going to reach out to an Adobe person who works on documentation and ask him to update that... I don't want other people to get confused by it!

[Rafael_Sahagun]

Great!

Although they are different in explanation (and now that I'm clear more so), I would have found useful to if there was a brief alert in the docs double confirming something along the lines of 'forget for now last click, first, linear, etc, and add these 3 new attribution methods specific for filters to you repertoire' or so if that makes sense, as I was a bit inclined to fit those other methods first when trying to reason the situation. Thanks again!