> For the complete documentation index, see [llms.txt](https://help.accentuate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.accentuate.io/use-case-guides/other-mixed-catalog/target-audience.md).
# Target Audience
A product without a defined audience is a product for no one. Target Audience is not a demographic assumption — it is a structured signal that tells every system, from search to AI, who this product is for.
OVERVIEW
The Target Audience field captures the intended user group or demographic a product is designed and marketed for. It enables filtering, recommendation, and curation by audience — surfacing the right product to the right customer without relying on product names or description text alone. It is applicable across all product categories: children's products, senior-focused items, gender-specific gear, professional-grade tools, and more.
Target Audience does not replace age range, skill level, or gender as individual fields. Where those fields exist and are populated, they provide greater precision. Target Audience operates at a higher level — answering who is this product for in a single, scannable value that can be filtered, badged, and surfaced across the storefront without complex logic.
BUSINESS VALUE
Why this field matters
* Target audience is a primary gift-purchase filter — buyers shopping for others need to know immediately whether a product is right for the recipient
* Structured audience data powers 'Shop for...' navigation hubs — 'For kids', 'For her', 'For the serious cyclist' — without manual collection building
* AI recommendation engines use audience to avoid surfacing products to inappropriate segments — a professional-grade product shown to a casual buyer creates confusion and erodes trust
* Audience data enables personalised homepage and collection merchandising based on a customer's stated or inferred profile
* Wholesale and trade buyers — schools, sports clubs, outdoor centres — procure by audience segment; structured data supports B2B catalogue browsing
* Lifecycle marketing (email, retargeting) uses audience data to segment product recommendations by customer profile
ACF SETUP
How to configure this field in Accentuate Custom Fields
| Where | ACF dashboard → Templates tab → Product scope → Add new field |
| ----------- | ------------------------------------------------------------- |
| Label | Target Audience |
| Name / Key | target\_audience |
| Namespace | accentuate (default) |
| Field type | Shopify >> Single-line text (List) |
| Multi-value | Yes — a product can be designed for multiple audience groups |
| Note: Target Audience coexists with, but does not replace, more granular audience fields such as Age Range, Gender, or Skill Level. Use those fields for precise filtering. Use Target Audience for high-level navigation, gift guidance, and audience-based collection logic. |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
STEP-BY-STEP IN ACF
* Open ACF, go to Templates tab and select the Product scope
* Click 'Add new field'
* Label: 'Target Audience' — Key auto-fills as 'target\_audience'
* Namespace: leave as 'accentuate'
* Field type: Shopify >> Single-line text (List)
* Enable 'Allow multiple selections' — family products and unisex products span multiple audience groups
* Click Done, then Save
* Assign audience values based on who the product is designed for and how it is positioned, not who could theoretically use it
| Shopify admin (optional pinning): Settings → Custom data → Products. Namespace: 'accentuate', Key: 'target\_audience'. Pinning is recommended — target audience is assigned during initial product setup and reviewed whenever a product is repositioned. |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
REFERENCE VALUES
Example values — use the audience language your customers recognise and identify with
| Value | When to use |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Men | Products designed or sized for men — menswear, male-specific gear, male-targeted lifestyle products |
| Women | Products designed or sized for women — womenswear, female-specific gear, female-targeted lifestyle products |
| Unisex / Gender neutral | Products designed without gender-specific sizing or positioning — universal fit, gender-inclusive styling |
| Children | Products designed for children generally — for age-specific products, pair with a dedicated Age Range field |
| Toddlers (1–3 years) | Products for the toddler developmental stage — motor skill development, safety-first design, supervised play |
| Kids (4–12 years) | School-age children — active play, learning, growing independence; not yet teen-positioned |
| Teens / Youth | Adolescents — bridging children's and adult product design; often sport- or lifestyle-specific |
| Adults | Standard adult positioning — no specific demographic qualifier; broadest adult audience |
| Seniors / 60+ | Products designed with older adult needs in mind — ease of use, comfort, accessibility, joint support |
| Beginners | Audience defined by experience level — newcomers to a sport, hobby, or activity; pair with Skill Level field |
| Professionals | Products designed for commercial, trade, or expert use — higher specification, durability, or compliance requirements |
| Families | Products designed to be used together by adults and children — family camping, family games, multi-user equipment |
BEST PRACTICES
* Assign audience based on design intent and positioning — not on who could theoretically use the product
* Use 'Unisex / Gender neutral' deliberately — do not default to it to avoid making an audience decision
* Pair Target Audience with more precise fields (Age Range, Skill Level, Gender) wherever those fields exist — Target Audience provides the high-level filter; the specific fields provide depth
* Avoid over-segmenting: a product for 'Adults' does not need separate 'Men' and 'Women' values unless the product is genuinely gender-specific in design or sizing
* Review audience assignments when a product is repositioned — a product originally designed for professionals may be rebranded for enthusiast consumers
COMMON MISTAKES
* Assigning every audience value to maximise reach — a product cannot be meaningfully designed for toddlers AND professionals simultaneously
* Confusing target audience with product category: 'Running shoes' is a category; 'Women' or 'Men' or 'Unisex' is the audience
* Using 'Adults' as a catch-all when the product is genuinely targeted at a specific adult demographic (seniors, professionals)
* Omitting audience on children's products — 'Children', 'Toddlers', 'Kids' and 'Teens' are distinct audiences with different safety, sizing, and design requirements
* Not updating audience when a product line is extended: a women's running shoe that adds a men's version needs separate audience assignments per variant
IN CONTEXT
| Junior Trail Running Shoe |
|
| ------------------------- | -------------------------------- |
| Target audience | Kids (4–12 years), Teens / Youth |
| Activity | Trail running, Hiking |
| Skill level | Beginner, Intermediate |
| Terrain | Trail, Mud / Wet terrain |
DEVELOPER IMPLEMENTATION
| Liquid note: Shopify >> List — use .value for the array. Target audience values are ideal for 'Shop for...' gift navigation and for personalised homepage recommendation slots. |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Liquid — Storefront Rendering
\| {% comment %}
Target Audience — Shopify >> Single-line text (List)
Namespace: accentuate | Key: target\_audience
Use for gift navigation and audience-based collection logic
{% endcomment %}
{% assign audiences = product.metafields.accentuate.target\_audience.value %}
{% if audiences != blank %}
\
{% endif %}
|
\| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pro tip: Build 'Gifts for...' collection pages filtered by target\_audience. A 'Gifts for Him', 'Gifts for Kids', and 'Gifts for the Outdoor Enthusiast' range — each powered by a single collection condition — is one of the highest-converting gift season merchandising patterns in outdoor and lifestyle retail. |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
SEE ALSO
* Skill level — experience-based audience segmentation within a specific activity
* Activity — activity context determines which audience segments are most relevant
* Tags (controlled) — target audience values can be mirrored as tags for Shopify's native filtering
| Full ACF documentation: help.accentuate.io \| Metafield Definitions → Fields → Field data type → Shopify field types |
| -------------------------------------------------------------------------------------------------------------------- |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.accentuate.io/use-case-guides/other-mixed-catalog/target-audience.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.