> 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/sports-and-outdoor/activity.md).

# Activity

&#x20; OVERVIEW &#x20;

The Activity field captures the specific sport, outdoor pursuit, or physical activity a product is designed and optimised for. It is the primary discovery mechanism for outdoor and sports products: customers do not browse for 'gloves' — they browse for 'skiing gloves', 'climbing gloves', or 'cycling gloves'. Without structured Activity data, these searches surface nothing.

Activity is not the same as product category. A hydration pack could serve hiking, trail running, cycling, or mountain biking. Each activity has different hydration volume needs, fit requirements, and feature expectations. Activity data enables a single product to be discovered across all relevant use cases, or to be precisely positioned for one.

&#x20; BUSINESS VALUE &#x20;

Why this field matters

* Activity is the dominant search term in outdoor and sports retail — customers lead with sport, not product type
* Structured activity data powers sport-specific collection pages and navigation menus without manual curation
* Multi-activity products can be surfaced across all relevant activity searches with one listing and one structured field
* AI recommendation engines use activity to suggest complementary gear ('other items for trail running')
* Seasonal campaigns (ski season, cycling season, trail running season) rely on activity tags to pull the right products automatically
* Specialty retailers and sporting goods marketplaces require activity classification for catalogue integration

&#x20; ACF SETUP &#x20;

How to configure this field in Accentuate Custom Fields

| Where       | ACF dashboard → Templates tab → Product scope → Add new field |
| ----------- | ------------------------------------------------------------- |
| Label       | Activity                                                      |
| Name / Key  | activity                                                      |
| Namespace   | accentuate (default)                                          |
| Field type  | Shopify >> Single-line text (List)                            |
| Multi-value | Yes — many outdoor products serve multiple activities         |

<br>

| Note: Multi-value is essential. A base layer top may suit hiking, skiing, trail running, and mountaineering simultaneously. A single-value field would force an artificial choice and cause the product to be missed in most relevant searches. |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

&#x20; STEP-BY-STEP IN ACF &#x20;

* Open ACF, go to Templates tab and select the Product scope
* Click 'Add new field'
* Label: 'Activity' — Key auto-fills as 'activity'
* Namespace: leave as 'accentuate'
* Field type: Shopify >> Single-line text (List)
* Enable 'Allow multiple selections' — multi-sport products are the norm in outdoor retail
* Click Done, then Save
* Populate each product with every activity it is genuinely designed and tested for

| Shopify admin (optional pinning): Settings → Custom data → Products. Namespace: 'accentuate', Key: 'activity'. Pinning is strongly recommended — Activity is the most frequently queried field in outdoor product data entry. |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

&#x20; REFERENCE VALUES &#x20;

Example values — use the activity names your customers search for

| Value                 | When to use                                                                             |
| --------------------- | --------------------------------------------------------------------------------------- |
| Hiking                | Day hikes and multi-day treks on trail or off-trail terrain                             |
| Trail running         | Off-road running on natural surfaces — technical footwear, vests, poles                 |
| Cycling               | Road cycling — road bikes, helmets, jerseys, clipless shoes, accessories                |
| Mountain biking       | Off-road cycling — MTB-specific helmets, gloves, pads, tyres, apparel                   |
| Skiing                | Downhill and resort skiing — skis, boots, bindings, ski-specific apparel and protection |
| Snowboarding          | Snowboard-specific gear — boards, bindings, boots, snowboard outerwear                  |
| Climbing              | Rock climbing and bouldering — harnesses, shoes, chalk, protection, ropes               |
| Kayaking / Paddling   | Kayaks, paddles, PFDs, dry bags, paddle-specific apparel                                |
| Camping               | Overnight outdoor stays — tents, sleeping bags, mats, camp kitchen, camp lighting       |
| Mountaineering        | High-altitude and technical alpine climbing — crampons, ice axes, mountaineering boots  |
| Running               | Road and track running — road shoes, performance apparel, GPS watches, hydration        |
| Swimming / Open water | Pool and open water — swimwear, wetsuits, goggles, swim caps, buoys                     |

&#x20; BEST PRACTICES &#x20;

* Assign activities the product is designed and optimised for — not every activity it could theoretically be used for
* Distinguish related activities: 'Cycling' and 'Mountain biking' are separate activities with different gear requirements
* Use the activity names your target customers type into search — 'Trail running' not 'Off-road running'
* Review activity assignments when a product is repositioned for a different customer segment or sport
* If a product is genuinely universal (a base layer top worn for almost any activity), limit to the 4–5 most relevant activities to avoid diluting search precision

&#x20; COMMON MISTAKES &#x20;

* Assigning every possible activity to maximise visibility — this destroys collection precision and frustrates focused buyers
* Confusing 'Cycling' and 'Mountain biking' — these are distinct disciplines with different product specifications
* Using 'Outdoor' as an activity value — Outdoor is an environment, not an activity; use specific activity names
* Not distinguishing 'Skiing' from 'Ski touring' — alpine resort skiing and backcountry touring have very different product requirements
* Leaving activity blank on multi-sport products — the field supports multiple values precisely for this case

&#x20; IN CONTEXT &#x20;

| Trail Running Hydration Vest — 8L | <p><br></p>                             |
| --------------------------------- | --------------------------------------- |
| Activity                          | Trail running, Hiking, Mountain running |
| Skill level                       | Intermediate, Advanced                  |
| Terrain                           | Trail, Mountain, Technical off-trail    |
| Weather suitability               | All conditions                          |

&#x20; DEVELOPER IMPLEMENTATION &#x20;

| Liquid note: Shopify >> List — use .value for the array. Link each activity tag to its dedicated sport collection — this is a high-converting cross-navigation pattern in outdoor retail. |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Liquid — Storefront Rendering

\| <p>{% comment %}</p><p>Activity — Shopify >> Single-line text (List)</p><p>Namespace: accentuate | Key: activity</p><p>Link tags to sport-specific collection pages</p><p>{% endcomment %}</p><p>{% assign activities = product.metafields.accentuate.activity.value %}</p><p>{% if activities != blank %}</p><p>  \<div class="activity-tags"></p><p>    {% for act in activities %}</p><p>      \<a href="/collections/{{ act | handleize }}" class="activity-tag"></p><p>        {{ act }}</p><p>      \</a></p><p>    {% endfor %}</p><p>  \</div></p><p>{% endif %}</p> |
\| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

<br>

| Pro tip: Use activity values to power seasonal campaign automation. Filter by activity = 'Skiing' to build your winter ski launch collection — products appear automatically as you tag them, with zero manual collection management. |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

&#x20; SEE ALSO &#x20;

* Skill level — activity context determines which skill levels are relevant
* Terrain — different activities are performed on different terrains; the combination drives precise discovery
* Weather suitability — activity + weather suitability defines the conditions a product is built for

| Full ACF documentation: help.accentuate.io \| Metafield Definitions → Fields → Field data type → Shopify field types |
| -------------------------------------------------------------------------------------------------------------------- |

<br>


---

# 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:

```
GET https://help.accentuate.io/use-case-guides/sports-and-outdoor/activity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
