Segment for page with specific tags

As I understand, because article tag tracking began in April’26,  AA cannot retroactively identify recipe-tagged content before that date using the “tags” variable alone. To analyze jan–may traffic, you need to segment recipe articles using an existing historical dimension such as page URL, article ID or a retroactive classification as applicable.

so use a visit level segment based on any applicable existing dimension that had historical data:

like:

• URL contains /recipe/
• pageName
• article ID

Hit = only tagged hits
But visit = all visits to recipe pages

so if you need Jan–may:

use URL/page/ID or Classification (retroactive on existing dimensions).

since AA can’t backfill new eVars/props from before implementation.
Switch from Hit: Tag=Recipe To Visit: Page/URL/ID = Recipe.

As ​@SumitK4 said, if you weren’t tracking the “recipe” tag at the beginning of the year, you cannot retroactively pull a report based on “tag = recipe”. You can only pull based on the available information at the time of the tracking request.

You can try to use other data that you did have available to pull that information… such as the URL or Page Name.

If you don’t have any common or easy to identify values, you might have to use a Classification Set. Basically, you would need to create a data mapping between your Article Identifiers, for the articles that are tagged as “recipe”. Consider it a temporary backfill of data.

If you need other tags beside recipe, you may need to get a list of ALL articles, and map each tag…

If your articles have multiple tags (such as “recipe” and “dinner” and “carrots”, etc) then classification sets may not work, as you would need to create multiple layers… as only a single value can be set into a classification set….