> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/integration-guides/for-brands/tracking-integrations/api-online-sale/introduction.md).

# Introduction

Online sale conversions can be tracked and reported to impact.com via a server-side API integration.

## How it works

* A visitor is redirected to your site from an impact.com partner tracking link, which appends a unique impact.com `im_ref` query string parameter to the landing page URL and populates with a unique value.
* The `im_ref` query string parameter value is captured by your site and stored in either a first-party cookie, or stored server-side. The effective lifetime of the cookie should match how long your contracts' referral window is set to — typically 30 days.
* When that visitor converts, a POST request is made to the [Conversions](https://integrations.impact.com/brand-api-reference/reference/conversions) endpoint, with a payload that includes the stored `ClickId` value for the visitor along with the associated conversion data.

{% hint style="success" %}
**Note:** This integration **requires a skilled web developer**.
{% endhint %}

## What to expect

This integration guide is simplified into two primary steps.

1. Complete the [Installation](https://integrations.impact.com/integration-guides/for-brands/tracking-integrations/api-online-sale/implementation) steps on your site — this involves developing and implementing a method to capture the `im_ref` value and make **server-side API calls** to the [Conversions](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/e-commerce/integrate-with-squarespace) endpoint of the impact.com Brand API.
2. Complete an [End-to-End Test](https://integrations.impact.com/integration-guides/end-to-end-tests) on your site — create a test partner account and complete a full test of following an impact.com tracking link, completing a test conversion, and verifying that the reported conversion data both appears in your account and is accurate.

Once the two main steps are completed, reach out to your Onboarding contact for a final *Tech Verification* from the impact.com team — we'll verify that everything looks good from our side.


---

# 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://integrations.impact.com/integration-guides/for-brands/tracking-integrations/api-online-sale/introduction.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.