# Tracker Conversion Test Site A tiny static website for testing a Stallion Tracker click and conversion postback. It has no build step, server code, database, or external dependency. Upload the files in this folder to any basic hosting account. ## Quick use 1. Upload `index.html`, `styles.css`, `app.js`, and this README to a folder on your hosting account. 2. Open the site and enter your tracker base URL, campaign key/URL, test network key, test network secret, goal, payout, currency, and status. 3. Click **Open campaign**. Configure the campaign’s final destination as this page, or use **Open test offer** to open the page directly. 4. When this page receives a URL containing `click_id`, it captures the click ID automatically. You can also paste it manually. 5. Click **Send GET**, **Send form POST**, or **Send JSON POST**. 6. Confirm the conversion in the tracker’s conversion, event, or log screens. The page stores setup and the current test click in this browser’s local storage only. Use **Clear saved test** for a clean run. ## Current tracker format This kit follows the current upstream tracker integration guide for release **1.1.8**: ```text https://TRACKER/postback/NETWORK_KEY/NETWORK_SECRET ?click_id=CLICK_ID &transaction_id=TRANSACTION_ID &goal=lead &status=approved &payout=10.00 ¤cy=EUR ``` The tracker accepts GET, form POST, and JSON POST. Parameter/status mappings can be changed in the tracker, so use the names configured for your test network. The idempotency key is network + transaction ID + goal; the **New transaction ID** button makes repeat tests easy. ## Optional Direct mode The optional section generates and can load the current v2 direct-mode helper: ```html Continue to the offer ``` Use this only after registering/verifying the landing hostname and adding the full page URL in the tracker’s Landers configuration. The tracker guide says `s.v2.js` is canonical for Direct mode; `/s.js` is the v1 helper and `/tracker.js` is the legacy compatibility route. ## Important safety notes - Use a dedicated test network key and secret. Do not publish a real production postback secret in a public page. - A static page cannot securely keep secrets or verify a postback response server-side. This kit is for disposable testing. - The browser may block the JSON POST or prevent the page from reading a cross-origin response. That does not prove the request was not sent; verify inside the tracker. Form POST and Open URL are useful fallbacks. - Never place real customer email, phone, or other personal data in the extra-parameters field.