> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/~/changes/1390/readme.md).

# Welcome to Intelligems

### **What is Intelligems?**

Intelligems is the ultimate profit optimization tool. We provide data-driven solutions and help maximize profits for Shopify merchants wanting to optimize their content, prices, discounts, and shipping rates, along with their checkout and post-purchase upsells.

Our mission is simple: we want to help e-commerce entrepreneurs improve their businesses and make more money, by helping you use data to manage your websites and profitability more effectively. We aim to provide independent e-commerce stores access to the same revenue optimization tools that power the growth and profitability of companies like Amazon and Uber.

### **Why Intelligems?**

Our founders and several team members met at Via Transportation, a ridesharing company based in NYC. Over the course of five years, we gradually built out the tools, data, algorithms, and systems to compete with the rapidly evolving rideshare market.

The most powerful tool we built was a dynamic pricing engine underpinned by robust A/B testing. Any question or hypothesis we had, we could simply run a test to get the (statistically significant) answer.

Now, as Intelligems, we are bringing our learning, mindset, and toolkit to e-commerce operators, especially Shopify store owners.

{% hint style="info" %}
Looking for developer docs? You're in the right place, you can get started [here](/~/changes/1390/developer-resources/javascript-api.md)!
{% endhint %}

### **What can you build with Intelligems?**

Everything you build in Intelligems is an **experience**: a change to your store that you show to a portion of your visitors or all of them.

You build the change once, then choose how it runs. Run it as a **test** to split your traffic and let the data tell you which version wins. Run it as a **personalization** to show it to a specific audience, always on.

#### The six experience modules

Experiences are grouped into six modules, matching the sections in your Intelligems left nav. Which modules you have access to depends on your plan.

| Module        | What it's for                                                                                                                                  |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Content       | Test imagery, copy, landing pages, themes, and templates to find the version that converts.                                                    |
| Merchandising | Use discounts, volume pricing, and free gifts to lift AOV without giving away margin.                                                          |
| Pricing       | Take the guesswork out of your product prices and find the ones that drive profit, revenue, and conversion.                                    |
| Shipping      | Find rates and thresholds that work for you and your customers, so you can boost profits or maximize conversion without sacrificing on margin. |
| Checkout      | Add upsells, trust badges, and progress bars to convert more of the shoppers who reach checkout.                                               |
| Post-purchase | Offer one-click upsells after checkout to add revenue to orders you've already won.                                                            |

If you don't see what you're looking for, or aren't sure of the best way to set up a specific experience you have in mind, reach out to our support team [here](https://portal.usepylon.com/intelligems/forms/intelligems-support-request).


---

# 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://docs.intelligems.io/~/changes/1390/readme.md?ask=<question>&goal=<user_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.