Run your network week by week
Use a simple daily and weekly routine to check visits, results, partner questions and payments.
Reviewed 24 September 2026 · MyCPANetwork team
Decide who checks each part of the campaign and when they will do it.
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 is a starting routine. A new or busy campaign may need more frequent checks. Give each check to a named person so a problem does not wait for the next reminder.
Check a live pilot daily
Check that approved publishers are sending visitors to the right offer and country. Look for unexpected changes in visits, recorded results, approval status or rejection reasons.
If the share of visitors who complete the agreed action suddenly changes, investigate. Check the dates, number of visitors, destination page and the advertiser's own records before deciding why it happened.
Check broken links and unanswered partner questions. If a serious problem remains unexplained, pause the affected part of the campaign using the agreed process. Keep the original records and note what you changed.
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. |
When you compare reports, use the same dates, time zone and approval status. A list of results waiting for review will not match a statement containing only approved and paid results.
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 each sale's ID and the dates covered. If all 40 sales are present, explain which are approved, pending or rejected. Ask the advertiser about any rejection you cannot explain.
Now imagine the advertiser's statement lists only 30 sales in total. Match the IDs one by one, allow for reports arriving late and check Postback Log. Write down who will investigate each missing item and when you will follow up.
These are illustrative counts, not normal approval rates or performance targets.
Prepare payments deliberately
Before preparing a payment, compare your records with the advertiser's and publisher's records for the same period. Check the agreed rate, any changes, the due date and anything already paid. Pay through your agreed method and keep the payment reference.
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.
One successful test is only a start. Before adding more offers, make sure you can reliably track visits, explain approvals and match the payment records for this first campaign.
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.
Check what you learned
Try to explain each idea in your own words, then tick to see a one-sentence reminder.
Daily checks watch traffic, results, links and questions; weekly reviews compare offer health, tracking, quality, partners and payments.
Totals are comparable only when the reports cover the same dates, timezone and approval states.
Match individual transaction IDs, keep the evidence and give an owner a next action before changing totals.
Amounts due depend on agreed rates, approved results, adjustments, due dates and payments already made.
Recording and communicating one change at a time makes later results easier to explain, while a fresh test checks the tracking path.
0 of 5 ideas reviewed
Your progress stays in this browser.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?
Get practical setup help from the team behind OfferDaemon.