> For the complete documentation index, see [llms.txt](https://purchasely.gitbook.io/purchasely/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://purchasely.gitbook.io/purchasely/quick-start-1/sdk-configuration.md).

# SDK configurations

With SDK v3, Purchasely moves from a monolith to a modular system composed of 3 modules:

* Transaction processor: Cross-platform management of subscriptions and one-time purchases
* Subscriber Data Hub: Real-time subscription lifecycle events used to fuel our dashboards and integrations like [Firebase analytics](https://firebase.google.com/docs/analytics), [Amplitude](https://amplitude.com), [Airship](https://www.airship.com/fr?), [Braze](https://www.braze.com), [Batch](https://batch.com), [Segment](https://segment.com), …
* User Journey Optimizer: Our Paywall CMS to create and optimize native subscription screens

That way Purchasely can be used in many ways to:

* Perform purchases
* Analyse purchases that were made with your own IAP system (aka *observer mode*)
* Display paywalls
* Use everything offered by Purchasely without changing your own transactional system

And of course everything listed above.

To reflect these compositions, you have to select a `runningMode` when you initialize Purchasely:

* `transactionOnly`
* `observer`
* `paywallObserver`
* `full`

### Running modes comparison

{% tabs %}
{% tab title="paywallObserver" %}
![](https://github.com/Purchasely/gitbook_v4/blob/main/.gitbook/assets/paywall%20+%20observer%20mode.png)
{% endtab %}

{% tab title="Full" %}
![](https://github.com/Purchasely/gitbook_v4/blob/main/.gitbook/assets/full%20mode.png)
{% endtab %}
{% endtabs %}

### Running modes

<table><thead><tr><th width="213.63814712584755"></th><th width="298.93536682393926">Description</th><th>Modules</th></tr></thead><tbody><tr><td><code>paywallObserver</code></td><td><p>Same as <code>paywallOnly</code> but Purchasely also observes transactions made by your system to fuel its dashboards and Webhook.</p><p><a href="/pages/XWM2OgJ9iCytXmFM9isp">Details</a>.</p></td><td><p>Paywall Builder</p><p>Subscriber Data Hub</p></td></tr><tr><td><code>full</code> <em>(default)</em></td><td><p>Purchasely handles everything from paywall to transactions including data and Webhooks.</p><p><a href="/pages/ywmIW3W2C9IPyTKw9cg9">Details</a>.</p></td><td>Transaction Processor<br>Subscriber Data Hub<br>Paywall Builder</td></tr></tbody></table>


---

# 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://purchasely.gitbook.io/purchasely/quick-start-1/sdk-configuration.md?ask=<question>&goal=<endgoal>
```

`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.