---
title: "Connect module: attribution"
description: How the affiliate tag captures attribution parameters at landing, and how a recorded click makes the attribution module conformant.
---

For the operator's engineer adding affiliate attribution to the landing and registration pages.

# attribution

The attribution module makes sure affiliate tracking parameters survive from a player's first landing to their registration, so affiliate vendors can attribute the player. In v1 it is the OneHazel Affiliate Tag on your site.

## Who calls whom

The player's browser calls OneHazel. You add one script tag to your landing and registration pages:

```html
<script src="https://app.onehazel.com/tag/v1/oh.js" data-operator-id="<your_operator_id>"></script>
```

The tag stores the attribution parameters in a first-party cookie so your own registration payload can include them. Install details, framework recipes and the full privacy notes are on [Affiliate Tag](/connectors/attribution-tag).

## Headers

None to build. The operator id in `data-operator-id` is a public identifier, not a secret. No API key ever goes in the browser.

## How it becomes conformant

The attribution module has no conformance run. Its state is derived from a recorded click: it becomes `conformant` once OneHazel has recorded at least one attribution click for your operator. Clicks are recorded only when the tag runs with server sync on, so add `data-server-sync="true"` to the tag (described on the [Affiliate Tag](/connectors/attribution-tag) page). Until a click is recorded, `connect_status` shows it `not_started` with the reason "install the affiliate tag". Its `evidence` is always `derived`.

## Conformance

None. Open your own landing page with a tracking parameter in the URL and the recorded click is the check.

## Samples

There is no server sample: the tag is the whole implementation.