Testing Integration

Before going live, verify each layer in order to confirm that your identifiers, metadata, and revenue path line up correctly:

1. click tracking
2. signup/lead tracking
3. sale tracking

The easy way — Run verification

You don't need to manually test each layer. Once your tracking code is live on your public site, Affitor detects it automatically (no debug mode required), and on the Share Program step the dashboard shows a Run verification button.

Run verification fires a synthetic click → signup → sale through Affitor's real attribution + commission pipeline — no real customer, no real money — and shows you a per-step verdict. When the synthetic sale is attributed, your integration is verified and Go Live unlocks.

This is the same check the agent runs with affitor test (and the MCP affitor_run_verification tool), so humans and agents verify the exact same way.

The manual, per-layer checks below are optional — useful when you want to confirm a specific layer is firing in the browser.

1. Test Click Tracking (optional, manual)

Tracker debug mode

Enable debug mode in your tracker install.

Script tag:

<script
  src="https://api.affitor.com/js/affitor-tracker.js"
  data-affitor-program-id="YOUR_PROGRAM_ID"
  data-affitor-debug="true">
</script>

What to verify

• the tracker script loads successfully
• the page can set/read Affitor cookies
• click/pageview-related requests are visible in the browser
• your dashboard shows test/debug activity for the pageview step

2. Test Lead Tracking

Browser-side signup test

After a successful signup in a tracked browser session, call:

await window.affitor.signup('user_123', 'user@example.com');

Verify that:

• the same internal ID you passed as customerKey is the one you plan to reuse later
• the tracker emits the expected network/debug activity
• the dashboard/test-event view reflects lead test activity where applicable

Server-side lead API test

curl -X POST https://api.affitor.com/api/v1/track/lead \
  -H "Content-Type: application/json" \
  -d '{
    "click_id": "test_lead_001",
    "customer_key": "test_customer",
    "additional_data": {
      "test_mode": true,
      "program_id": "YOUR_PROGRAM_ID"
    }
  }'

Expected response:

{
  "success": true,
  "message": "Test lead event tracked successfully",
  "data": {
    "eventId": 456,
    "programId": 1,
    "test_mode": true
  }
}

What test mode means for leads

• creates a test lead event only
• does not create a production lead/customer progression
• helps verify that your program ID and endpoint wiring are correct

3. Test Sale Tracking

You can test sale tracking in two different ways depending on your implementation: server-side tracking vs Stripe integration.

Option A — Test Server-side tracking

curl -X POST https://api.affitor.com/api/v1/track/sale \
  -H "Authorization: Bearer YOUR_PROGRAM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "additional_data": { "test_mode": true },
    "amount_cents": 9999,
    "currency": "USD",
    "sale_type": "payment"
  }'

Expected response:

{
  "success": true,
  "message": "Test sale event tracked successfully",
  "data": {
    "eventId": 789,
    "programId": 1,
    "test_mode": true
  }
}

What test mode means for sales

• still requires the Bearer token
• creates a test sale event only
• does not create commissions
• does not create platform fees
• does not update production metrics

Option B — Test Stripe integration

If you use Stripe Checkout:

1. switch Stripe to test mode
2. complete a test checkout
3. verify webhook delivery in Stripe
4. inspect the metadata on the checkout/payment objects

Check that metadata includes:

• program_id
• affitor_click_id
• affitor_customer_key

For subscriptions, also confirm the same values exist in subscription_data.metadata.

4. Verify Test Events Were Received

After sending test events, query the test-event checker to confirm they were received.

curl -X POST https://api.affitor.com/api/tracking/check-test-events \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "YOUR_PROGRAM_ID"
  }'

You can also filter by step:

• pageview
• referrals
• payments

5. Recommended Real-World Test Scenarios

Scenario A — Full tracked funnel

1. open a fresh browser session
2. land through an affiliate link
3. sign up
4. complete payment
5. verify click → lead → sale linkage

Scenario B — Server-side tracking path

1. complete a backend-controlled purchase
2. send POST /api/v1/track/sale
3. verify the response contains sale_id and commission_id
4. confirm no duplicate retries reuse the same transaction_id

Scenario C — Stripe subscription path

1. create a Stripe Checkout subscription in test mode
2. ensure both metadata and subscription_data.metadata are present
3. verify the initial invoice/webhook delivery
4. confirm your renewal setup will preserve those identifiers

Common Failure Modes

Lead works but sales do not attribute

Usually caused by one of these:

• customerKey at signup does not match the later payment identifier
• Stripe metadata uses the wrong customer key
• transaction_id is duplicated or missing in the server-side tracking path
• no tracked click/customer relationship exists for the customer

One-time Stripe works but renewals do not

Usually caused by:

• missing subscription_data.metadata
• relying only on initial checkout metadata
• mismatched customer key between signup and Stripe metadata

Dashboard status is confusing

The dashboard combines:

• test event presence for click/lead verification
• Stripe connection/configuration state for payment setup
• real sale events for broader integration completeness

Treat dashboard status, test-event checks, and Stripe webhook delivery logs as complementary signals — no single source is the full picture.

Before You Go Live

Confirm all of the following:

• tracker installed on all landing pages
• signup tracking sends a stable internal customer ID
• Server-side tracking or Stripe integration path is fully implemented
• Stripe subscription metadata is duplicated correctly when relevant
• one end-to-end test has succeeded with the exact path you will use in production

Related guides:

• 3-Step Integration Guide
• Lead Tracking
• Payment Tracking