Test your tracking and postback
Follow one test visitor from a publisher link to a recorded result, using real dashboard screenshots.
Reviewed 24 September 2026 · MyCPANetwork team
Check that one test click and result belong to the right offer and publisher, with the right amounts.
Before you start
You have an offer and a link. Now check that one visit leads to a result for the right publisher. Complete lesson 7 first. Keep the offer name, publisher, rates and test label beside you.
The screenshots show a real controlled test in Demo Network, in light mode, on 22 September 2026. We sent the visitor to MyCPANetwork, then simulated the advertiser’s callback. This verifies the demo’s tracking path; it does not prove that an external advertiser stores the click ID or sends postbacks correctly. You must also run that advertiser’s permitted test before launch.
For a real integration, agree how to trigger a test and exclude it from billing. Do not make unauthorized purchases, invent customer details or approve test commissions for payment. Open screenshots at full size when you need to read a field.
Understand the three parts
The path is simple: open the publisher link → record the visit → receive the advertiser's result → check the publisher's record. The automatic message reporting the result is called a postback. Lesson 9 explains it in more detail.
| Part | Direction | What it proves |
|---|---|---|
| Click | Publisher link → OfferDaemon → destination | The visit is recorded and reaches the right page. |
| Advertiser postback | Advertiser → your network | The reported action can be matched to the original click. |
| Publisher postback, if needed | Your network → publisher’s tracker | The publisher’s own system receives the result. |
A click ID identifies one visit. A transaction ID identifies one sale or other action in the advertiser's records. Write down both; they do different jobs.
Step 1: Open one generated tracking link
- Confirm your test offer is Active and the test publisher is Approved.
- Copy the URL from the publisher’s Tracking Link Generator, including your
sub1test label. - Note the time and open the link once in a new tab.
- Confirm that it reaches the intended destination.
- Check that
{click_id}has been replaced by a real value in the destination parameter. In our example the parameter isnetwork_click.
For a real advertiser, ask them to confirm the exact value they received and stored. The value in their system must match yours; their own internal visit ID is not a substitute.
If this step fails: check the offer activity, partner status, generated domain and destination URL first. Do not continue to conversion testing while the redirect is wrong.
Step 2: Find the same click in OfferDaemon
- Return to the admin dashboard and open Clicks in the sidebar.
- In Search (ID, IP, ISP, referrer, sub1-5), enter your test label, such as
pilot-test-20260922, and click Filter. - If you use From and To, make sure the range includes the test. A date filter can hide a valid click.
- Open Columns. For a focused view, select Offer, Publisher, Sub1 and Click ID, then Apply Columns. Keep Date/Time too when comparing multiple visits; scroll the table horizontally if needed.
- Compare the offer, publisher and click ID in this row with your notes and the ID in the destination URL.
You should now have: a click record whose ID matches the value sent to the destination. This proves the first half of the journey.
Step 3: Copy the address that receives results
- Open Settings → Postback URL.
- Under Your postback URL, click Copy.
- Give the advertiser this receiving address, called an endpoint. Ask which value in their system holds your original click ID.
- Their system must replace example placeholders with real values when sending the result. A completed test message must not contain the literal text
{click_id},{amount}or{event}.
The current panel also supports separate postback domains. Keep the working default for this first test. A DNS verification by itself does not prove that a new custom endpoint has working hosting and HTTPS.
Step 4: Agree the values the advertiser will send
For our CPA Fixed example, the message needs the original click ID, what happened, and a unique transaction reference. Here is the shape of the URL:
https://YOUR_NETWORK.offerdaemon.net/postback?click_id=ORIGINAL_CLICK_ID&event=sale&tx_id=UNIQUE_TEST_TRANSACTION¤cy=USD
Use the address shown in your own panel, not YOUR_NETWORK above. Replace ORIGINAL_CLICK_ID with your test click's ID. Give each new sale its own transaction reference. If you resend the same sale, keep the same reference.
| Parameter | What to send for this example |
|---|---|
click_id |
The exact value originally passed to the destination. |
event |
sale, because the example’s qualifying action is a paid subscription. |
tx_id |
A stable reference for this one test transaction. We used mycpanetwork-tutorial-20260922-01. |
currency |
USD, matching the example. |
amount |
Omitted in this fixed-rate test; its $20 revenue and $14 payout come from the offer configuration. |
If your offer uses CPA Fixed, continue to Step 5. Other rate models need different values; a short note about them appears after the test result below.
For a real integration: ask the advertiser to trigger the permitted test event through their system. They should send the completed request from their server or tracker.
For a practice network only: you can fill the URL with your test click ID and open it once in a browser. This sends the same kind of web request, called HTTP GET, and creates a test result. It checks whether your network receives the message; it does not test the advertiser's system. If the browser shows no answer, check Postback Log before trying again. The first request may already have arrived.
Step 5: Read the postback result
- Open Postback Log in the sidebar.
- Paste the test click ID or transaction ID into Click ID, TX ID, Offer or Publisher and click Filter.
- Open Columns and include Time, Result, HTTP, Event, Click ID and Response.
- Read Result and Response, not only the HTTP status.
In this demo, recurring postbacks were off. The first callback was accepted; repeating the same transaction produced duplicate. Do not change the transaction ID merely to make a retry appear new.
| Result or symptom | First thing to check |
|---|---|
| No matching log entry | Endpoint, date/search filters and whether the advertiser actually sent the request. |
click_not_found / Click Not Found |
Compare the returned ID with the original click. Check that you are using the right network. |
missing_params / Missing Params |
Check that the required identifiers have real values. |
duplicate / Duplicate |
Find the original accepted event. A retry may already have been processed. |
| Accepted, but the report looks empty | Check conversion filters and beneficiary type, then match the click or transaction ID. |
Other models and enabled restrictions can produce other outcomes. Use the log’s explanation before changing rates or resending requests.
Step 6: Compare the conversion with your agreement
- Open Conversions.
- Search for your offer in Offer and select the result.
- Set Beneficiary Type to Publisher, then click Filter. This shows the publisher's payment record instead of any separate merchant or referral payment.
- Use Columns to show Offer, Event, Payout, Revenue, Status and Beneficiary Email.
- Compare the row with your test brief. Add Click ID or Transaction ID in Columns when you need to match one result among several.
For this example, the expected result is:
| Check | Expected result |
|---|---|
| Offer | MyCPANetwork tutorial — Freelancer software |
| Publisher | Atlas Content (atlas@example.com) |
| Event | sale |
| Publisher payout | $14 |
| Advertiser revenue | $20 |
| Status | pending, because Auto-approve conversions was off |
| Duplicate retry | No second publisher conversion for the same transaction |
Accepted and approved mean different things. Accepted means the callback was processed. Pending means the conversion still awaits approval under the chosen workflow. A correct pending result is not a tracking failure, and approving it is not required just to prove the test worked.
The $6 difference in this example is before any additional commissions, fees, reversals or operating costs. It is not a profit promise.
If your offer uses a different rate model
RevShare uses a percentage, so the advertiser normally needs to send a positive amount. With CPA Dynamic, the message can supply the advertiser's revenue for that result. In an incoming advertiser message, payout is another name for amount; it does not directly change the publisher's payout. Check the postback parameter reference before testing either model.
Step 7: Finish the handoff and save evidence
If your publisher needs a callback to their own tracker, agree their receiving URL, required identifiers and expected value, then test that outbound path separately. A conversion in OfferDaemon does not prove that another system received its callback. This walkthrough does not demonstrate publisher callback delivery.
Keep a short test record:
- Test time, network, offer and publisher.
- Generated tracking link and test label.
- Original click ID and transaction ID.
- Postback result and conversion status, revenue and payout.
- Advertiser confirmation, any required publisher callback evidence and the agreed treatment of test billing.
Pause a practice-only offer after you finish: in Offers, find its exact name or slug and use Deactivate. Our demo tutorial offer was deactivated after these captures. Keep test records identifiable and out of normal payout approval.
Ready for a real pilot means: the advertiser has also confirmed their side of the test, your records agree, and any required publisher callback has been checked. A successful sandbox simulation is a useful milestone on the way there.
Check what you learned
Try to explain each idea in your own words, then tick to see a one-sentence reminder.
A test click shows that the publisher link reaches the approved destination and creates a click record for the right offer and publisher.
OfferDaemon uses the same click ID sent to the advertiser to match the reported action to the earlier visit.
The log shows whether an incoming result was accepted, treated as a duplicate or could not be matched.
The conversion should show the intended publisher and offer, the agreed amounts and the correct approval status.
A network conversion does not prove publisher callback delivery or settle how test results are excluded from normal billing.
0 of 5 ideas reviewed
Your progress stays in this browser.Next step
Read Understanding postbacks to see why the advertiser-to-network and network-to-publisher messages are separate. Then use the weekly operating routine to keep tracking and commercial records aligned after launch.
Want a hand with this step?
Get practical setup help from the team behind OfferDaemon.