# Introduction

Spindl is a measurement and attribution platform for Web 3. \
\
What that means is we can tell you where your users came from (Twitter? Telegram? An on-chain airdrop?) and what they did on-chain while inside your dApp. In other words, did they generate revenue? Did they stick around? Did they cost too much to acquire?

(If you're a Web 2 marketer who got crypto-pilled like us, think of us like a Web 3 Branch or Adjust or AppsFlyer, with some added Web 3 magic.)

Visually, the unique views you get inside Spindl look as so: Web 2 channels like Twitter appearing, correctly attributed!, next to Web 3 ones like quests and on-chain rewards. <br>

<figure><img src="https://1560216118-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXCbRJugC9obtJ12iHKUB%2Fuploads%2FhOjpGBQKHeLuqnVbWrhP%2Fgb_1.png?alt=media&#x26;token=e9c61726-35b0-4d04-8979-19d2a76d2bbf" alt=""><figcaption></figcaption></figure>

If the wonky-sounding term 'attribution' doesn't mean anything to you, click on the link at bottom to learn more. \
\
If you just want the quick-start guide:

{% content-ref url="../techncial/start-here" %}
[start-here](https://docs.spindl.xyz/spindl/techncial/start-here)
{% endcontent-ref %}


---

# Agent Instructions: 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://docs.spindl.xyz/spindl/overview/introduction.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.