LESSON 08 / 08 · 5 MIN READ
Run your network week by week
Create a practical operating routine for traffic checks, conversion reconciliation, partner communication and payout preparation.
Reviewed 20 September 2026 · MyCPANetwork team
BY THE END OF THIS LESSON
Assign an owner and cadence to the checks that keep your pilot under control.
Before you start
Keep your offer agreement, publisher brief and successful tracking test together. Know who can pause traffic and who can approve commercial changes.
This routine is a starting point. A busy or newly changed campaign may need checks more often than a mature, low-volume one. The point is to assign real responsibility rather than rely on a weekly reminder alone.
Check a live pilot daily
Review whether the intended publishers are sending traffic to the correct offer and market. Look for unexplained changes in clicks, recorded conversions, approval status or rejection reasons.
A sudden conversion-rate change is a signal to investigate, not proof of fraud or success. Compare reporting periods, sample sizes, landing-page changes and the advertiser’s own information before drawing conclusions.
Check tracking failures and unresolved partner messages. If you cannot explain a material problem, pause the affected flow under the agreed process while you investigate. Do not hide discrepancies by editing reports without a traceable reason.
Use a weekly review
| Area | Review | Record |
|---|---|---|
| Offer health | Landing page, availability, rules and agreed limits. | Changes and their effective dates. |
| Tracking | Clicks, postback outcomes and missing transactions. | Test evidence and unresolved issues. |
| Quality | Approval/rejection reasons and advertiser feedback. | Decisions supported by evidence. |
| Partners | Approved sources, questions and planned changes. | Owner and next action for each issue. |
| Payments | Statements, adjustments, due dates and receipts. | Reconciliation and payment references. |
Use consistent dates, time zones and conversion statuses when comparing reports. A report of pending events cannot be compared directly with an advertiser’s approved-and-paid statement.
A worked review
Your network shows 40 recorded subscriptions in a week. The advertiser’s statement lists 32 approved, five pending and three rejected. That does not automatically mean eight conversions are missing.
First compare transaction identifiers and the reporting window. If all 40 are accounted for, explain their statuses and the relevant approval rules to the publisher. Investigate any rejected action with the advertiser if the reason is unclear or disputed.
Now imagine the statement lists only 30 transactions in total. Match the identifiers, look for delayed reporting and inspect the postback log. Record which side will investigate each unmatched item and when you will check again.
These are illustrative counts, not normal approval rates or performance targets.
Prepare payments deliberately
Reconcile each partner’s period before preparing a payment. Confirm the applicable rates, adjustments, contractual due date and previously paid amounts. Arrange payment through your agreed method and keep its reference alongside your records.
OfferDaemon can support your payment-management workflow, but your team still owns approval and payment execution. Do not assume that marking a balance or viewing a report transfers money automatically.
Review available cash against the payment schedule, including delays already observed. If a partner raises a dispute, preserve the original record and document the resolution.
Make changes one at a time
Before changing a landing URL, rate, traffic rule or publisher integration, write down what changes and when. Tell the affected parties through your normal agreed channel. Test the changed tracking path before resuming or expanding traffic.
Do not expand to more offers merely because the first test passed. First establish that the pilot’s tracking, approval and payment processes can be reconciled and supported.
Know when to ask for help
Technical support is useful when you need help configuring OfferDaemon, diagnosing callbacks or reviewing how a report is interpreted. Our technical-care service is individually scoped around those tasks.
It does not take over advertiser acquisition, publisher recruitment, business decisions or partner payments. Agree the scope and access needed before work starts; do not send passwords in an inquiry.
Common mistakes
Watching totals without matching transactions. Aggregate numbers can conceal mismatched periods or statuses.
Changing several settings at once. Keep a change record so that you can identify what caused the result.
Treating monitoring as payout approval. Reconciliation and payment authorization are separate steps.
Your checklist
- Each daily/weekly check has an owner.
- Reporting periods and statuses are comparable.
- Discrepancies have evidence, an owner and a next action.
- Payment preparation follows the agreed terms.
- Changes are communicated, recorded and tested.
Next step
Review the launch checklist. Any unchecked essential is a concrete next task, not a reason to skip ahead. If you need assistance with the technical work, tell us about your setup.
Want a hand with this step?
Ask about your setup ↗Get practical setup help from the team behind OfferDaemon.