Test Custom Events and Payments

​

Choose the right method

​

Usually send as a custom event

• Product view, search, add to cart, and checkout started
• Content view, level completion, and referral
• Purchase initiated when it only marks the start of checkout
• Payment failure shown for product analytics when you do not need a payment record

​

Usually send with capturePayment

• Completed purchase
• First or second payment
• One-time or recurring payment
• Subscription creation or renewal with a charge
• Wallet top-up or funds withdrawal
• A failed or cancelled transaction when you need it recorded with PAYMENT_FAILED or PAYMENT_CANCELLED

​

Before you test

• Complete the click → install → signup flow so the test user is attributed.
• Use the same user_id that your app registered through signup.
• Generate a fresh payment_id for each real transaction.
• Send amount as a number in one reporting currency.
• Pick one source for each payment, either the app SDK or your backend.
• For server-side tests, generate a server key from Settings → Data APIs.

​

Test flow

1

Create traceable test values

Use values that you can find in the Events Log:

user_id: your attributed test user
payment_id: lr_test_payment_001
amount: a small test amount
type: DEFAULT
status: PAYMENT_COMPLETED

Use a new payment_id every time you test a new transaction.

2

Send a custom event control

Send a non-payment action such as checkout_started through your SDK’s trackEvent method or the Event Capture API.

curl -X POST https://api.linkrunner.io/api/v1/capture-event \
  -H "Content-Type: application/json" \
  -H "linkrunner-key: YOUR-SERVER-KEY" \
  -d '{
    "event_name": "checkout_started",
    "event_data": { "test_run": "lr_payment_flow_001" },
    "user_id": "YOUR_ATTRIBUTED_USER_ID",
    "event_id": "lr_test_event_001"
  }'

A successful API request returns a captured-event response.

3

Send a completed payment

Send the actual transaction through your SDK’s capturePayment method or the Revenue Tracking API.

curl -X POST https://api.linkrunner.io/api/v1/capture-payment \
  -H "Content-Type: application/json" \
  -H "linkrunner-key: YOUR-SERVER-KEY" \
  -d '{
    "user_id": "YOUR_ATTRIBUTED_USER_ID",
    "payment_id": "lr_test_payment_001",
    "amount": 1,
    "type": "DEFAULT",
    "status": "PAYMENT_COMPLETED"
  }'

A successful API request returns HTTP 201.

4

Verify both records in Linkrunner

Open Events → Events Log, then filter by your test user or event name.

• checkout_started appears as a custom event.
• The transaction appears as a payment event.
• The payment row contains the expected Amount, Payment ID, and Payment Status.

5

Verify payment deduplication

Send the same payment again with the same type and payment_id.Expected result: the Events Log still contains one payment for that combination. Linkrunner records the first request and ignores later duplicates.

6

Verify a new transaction

Send another completed payment with a new payment_id, such as lr_test_payment_002.Expected result: the Events Log contains a second payment. If it does not, confirm that the new transaction did not reuse the previous payment_id.

​

Expected classification

​

Test Meta Purchase forwarding

1. In Linkrunner, map the payment type you send, such as DEFAULT or FIRST_PAYMENT, to Meta’s standard Purchase event.
2. Include the required event_data fields for Purchase, including product IDs, contents, content_type, value, currency, num_items, and order_id.
3. Send a new payment with a new payment_id.
4. Check Meta Commerce Manager → Events. The real-time hit should appear within about 15 minutes. Full reporting can take a few days.

​

Test payment removal

curl -X POST https://api.linkrunner.io/api/v1/remove-payment \
  -H "Content-Type: application/json" \
  -H "linkrunner-key: YOUR-SERVER-KEY" \
  -d '{ "payment_id": "lr_test_payment_001" }'

​

Troubleshooting