> For the complete documentation index, see [llms.txt](https://learn.fueled.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.fueled.io/how-fueled-works/use-cases.md).
# Use Cases
> 🔥 *As eCommerce merchants learn to utilize* [*first-party and zero-party customer data*](https://learn.fueled.io/304d900b35964db58155e982a62c3edc)*, the possibilities presented by CDPs and 1st-party data tracking tools like Fueled continue to expand.*
## Customer Journey Analytics
If you’ve ever looked at a report in Google Analytics, you’ve used a ***customer journey analytics platform***. Journey analytics tools allow merchants to track and analyze how customers interact with a website and/or other customer engagement channels.
Typical journey analytics reports include funnel reports, customer flow visualizations, and cohort retention charts.
To fully leverage a journey analytics tool (from commonplace tools like Google Analytics to more feature-rich platforms like MixPanel and Amplitude), merchants need to be able to collect and organize customer events, to provide a “stitched together” view of how each customer interacts with the brand’s website, email marketing, paid ads, and so forth.
Fueled provides a single approach to collecting, organizing, and cleaning this data for more complete analysis in customer journey analytics tools.
This sort of product analysis allows merchants to make better merchandizing decisions — both in-store and on their website storefronts.
## Personalization
The most talked about use case for CDPs and 1st-party attribution tools like Fueled is for personalization of website experiences, as well as other sales/marketing channel experiences like email and SMS.
Because Fueled captures all of a customer’s interactions with a brand, Fueled can power personalization tools placed on a storefront, or marketing automations that personalize email and SMS content experiences.
## Precise Ad Targeting
Similar to personalization strategies, CDPs and 1st-party attribution tools like Fueled provide merchants with a comprehensive view of customers’ interactions with a brand and its product catalog. This data allows merchants to create more precise *segments*, or lists of customers, which they can used for paid ad targeting, as well as the creation of “look-a-like” audiences in Facebook and Google.
## Contextualized Customer Support
While not commonly talked about (yet!), CDPs and 1st-party attribution tools like Fueled can push customer events into customer service platforms, such as Gorgias, Zendesk, and Kustomer.com. This provides a cost-effective way for merchants to provide customer service reps with the full history/context of a customer when addressing support issues.
More personalized, contextualized customer support experiences lead to happy customers with higher customer lifetime value.
## Merchandizing Decisions
Many eCommerce brands have started piping all of their customer behavioral events, most importantly purchase-related events, into a data warehouse. From there, they can use a BI tool (like Tableau or Power BI) to analyze what products are selling best and what discounting strategies might be better performing.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://learn.fueled.io/how-fueled-works/use-cases.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.