# Conversion Tracking Event

Goals;

* Easily identify and define a conversion event
  * Page visits, e.g. /success page
  * Form submissions
    * Via Basin 
* Capture all relevant source data 
  * Referer
  * UTMs
  * etc. 
* Capture relevant conversion data
  * Transaction ID
    * From querystring, etc. 
  * Conversion type
  * Conversion item
* Clean data
  * Via transaction ID 
  * SPAM-free, e.g. Basin 
* Configure it for;
  * Custom logging URL 

## Conversion Event Config

Conversion events are configured in an [SA5 Configuration Block](/overview/configuration-blocks.md) 

e.g. a typical Basin Contact Us form 

```html
<script type="application/sa5+json">
{
  "@context": "https://attr.sygnal.com",
  "@type": "ConversionEvent",
  "@version": "0.1",
  "url": "https://conversion-tracker-url.com", 
  "transactionIdType": "query", 
  "transactionId": "transactionId",
  "type": "contact",
  "item": ""  
}
</script>
```

* Data pulled in from session var&#x20;
* Overridden with data here
* TransactionID created / set&#x20;

## Placement&#x20;

These can be placed in a webpate

<img src="/files/889CMtAHrEe1WK5cZd8e" alt="" class="gitbook-drawing">

e.g. a typical Basin Contact Us form&#x20;

```html
<script type="application/sa5+json">
{
  "@context": "https://attr.sygnal.com",
  "@type": "ConversionEvent",
  "@version": "0.1",
  "url": "https://conversion-tracker-url.com", 
  "transactionIdType": "query", 
  "transactionId": "transactionId",
  "type": "contact",
  "item": ""  
}
</script>
```

* Data pulled in from session var&#x20;
* Overridden with data here
* TransactionID created / set&#x20;

## Configuration Settings&#x20;

### url

Specifies the conversion event logger URL base, without querystring params

### type & item&#x20;

Describe the type of conversion for data processing purposes, since different conversions

### class ( FUTURE ) &#x20;

* Purchase - payment captured
* Booking - reservation, but no money captured
* Enquiry -&#x20;
* Enrollment - good lifetime value, no immediate purchase&#x20;

### value ( FUTURE )&#x20;

### transactionIdType & transactionId

Indicates the type of the transaction ID&#x20;

| transactionIdType | transactionId                                  | Notes                                                                                                                         |
| ----------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| `query`           | querystring param name                         | Retrieves the transactionId from the querystring via the named param                                                          |
| `auto`            | <p>querystring param name <br>( optional )</p> | <p>Auto-generates a transactionId from crypto.<br>Automatically adds it to the redirect as the given param, if specified.</p> |

## Future

### transactionId

* Push onto redirect URL in Webflow Forms&#x20;
  * Allow ?param to be specified

unknown utm\_source for unknown referers

* First pass in lib
* Fallback to generic hostname tracking&#x20;

configurable param on redirect&#x20;

### Single-send

When a conversion is registered, avoid re-sending the same conversion Id&#x20;

Check in session, etc.&#x20;

ConversionLogged yes&#x20;


---

# 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://attr.sygnal.com/sa5-cro/conversion-tracking-event.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.