Start by identifying what is actually disputed
A commission concern can describe several different problems: a click that appears not to have been recorded, a conversion that is absent, a conversion that is present but not approved, or an approved amount that differs from an expected amount. These are not interchangeable. The next useful check depends on which state the records show. Before opening a support ticket, write a one-sentence description of the discrepancy and identify the report fields that support it.
Avoid treating a visitor’s claim that they completed an action as proof that the program owes a commission. The program may define qualifying events, exclusions, attribution rules, validation periods, and adjustment reasons. Your evidence file should make it possible to compare what the dashboard recorded with those written rules, without collecting unnecessary personal information about visitors.
- Classify the issue as missing click, missing conversion, pending conversion, declined conversion, or amount mismatch.
- Note the date range and time zone used by both your own records and the program report.
- Use campaign or sub-ID references where available, rather than including visitor-identifying details.
Preserve records before dashboard data changes
Reports can be revised, filtered, or displayed differently as a program processes events. Save an original export when possible, along with the report name, selected date range, filters, and retrieval time. If the dashboard does not provide an export, make a dated screenshot that includes enough context to identify the report and selected filters. Keep the original files unchanged and make working copies for notes.
For a focused dispute, assemble only the records relevant to the question. A useful set may include the applicable program terms, the report rows for the period, your own click or campaign logs, and a short chronology of the issue. Do not paste credentials, full payment details, or sensitive visitor data into a ticket. Store the evidence in a restricted business location and follow your organization’s retention practices.
| Record | What to capture | Why it helps |
|---|---|---|
| Program report | Period, filters, event status, campaign identifier, export date | Shows what the program currently reports |
| Program terms | Relevant qualification, validation, or adjustment language and version/date | Establishes the rule you are asking the program to apply |
| Site-side records | Aggregate click counts or campaign logs for the same period | Can help identify whether the concern is tracking or later processing |
| Support history | Ticket reference, submission date, response, and follow-up | Preserves the escalation timeline |
Compare records without assuming they should match
Your website’s click totals and a program’s conversion totals measure different events. They may also use different time zones, attribution rules, filters, or event definitions. A click count is not a conversion count, and an apparent difference alone does not establish a tracking failure. First align the reporting period and identify the exact event or status being compared.
If a conversion appears in the report but is pending, declined, or adjusted, look for the status definition and any reason code the program provides. Compare that explanation with the applicable written terms. If the conversion is absent, state that clearly and provide the narrowest relevant time window and campaign reference. Do not infer a reason that the report does not show; ask the program to clarify the recorded status or applicable rule.
- Check time zone and date boundaries before comparing totals.
- Compare like with like: clicks to clicks, conversions to conversions, and approved amounts to approved amounts.
- Record any filters, status definitions, or reporting delays described by the program.
- Mark assumptions separately from facts visible in records.
Write a support request that can be investigated
A useful inquiry includes the account or property reference the program requests, the relevant period, the campaign identifier, the event status, and a concise description of the discrepancy. Attach a small, legible evidence set rather than a large unfiltered archive. Ask one or two answerable questions, such as whether a specific recorded status reflects a stated qualification rule or whether an event was received for the cited campaign and period.
Keep the tone factual and avoid presenting an expected commission as guaranteed unless the program’s terms and records establish that conclusion. Request clarification of the report field or rule, not access to another person’s account data. If support asks for more information, provide only what is needed through the program’s designated channel and retain a copy of what you sent.
| Ticket element | Example of useful content |
|---|---|
| Issue | “The report shows a conversion as pending for the cited period; I am asking what status definition applies.” |
| Scope | A specific date range, time zone, campaign reference, and report name |
| Evidence | Relevant report row, terms excerpt, and dated site-side record if applicable |
| Question | “Can you confirm the recorded status or point me to the applicable qualification rule?” |
| Requested outcome | Clarification, review, or correction if the program confirms a reporting error |
Track the outcome and improve future operations
Log the submission date, ticket reference, response date, and any promised next step. If the first response does not answer the question, follow up by summarizing what remains unresolved and referring to the original evidence. Avoid repeatedly opening duplicate tickets unless the program directs you to a different channel. If the program has a stated review or appeal process, follow its instructions and deadlines rather than assuming an informal message replaces them.
After resolution, note the reason in your internal program record. A finding that a conversion did not qualify may point to a need to understand a rule more clearly; a confirmed reporting issue may call for a monitoring check. Keep the record neutral and avoid turning one case into a broad performance claim. Over time, consistent documentation helps you spot recurring operational questions and decide what should be checked before relying on a program.
- Close the case with the final status and the source of that information.
- Update internal guidance if a written term or reporting definition was clarified.
- Do not alter original exports; attach later versions as separately dated records.
- Reassess whether the program’s reporting and support processes meet your operational needs.
Common questions
Does a difference between my click log and a program report prove tracking failed?
No. Clicks and conversions are different events, and reports may use different periods, time zones, attribution rules, or status definitions. Align the records and identify the specific event missing or disputed before drawing a conclusion.
What should I include in a commission dispute ticket?
Include the relevant period, time zone, campaign reference, report status, a concise description, and only the records needed to explain the discrepancy. Ask a specific question about the event or rule. Do not include passwords, full payment details, or unnecessary visitor information.
Should I wait for a conversion to be approved before asking about it?
Check the program’s stated validation and inquiry process. If the status is unclear or a deadline may apply, ask the program how pending events are handled rather than assuming that pending means either approved or declined.
How long should I keep dispute records?
There is no universal retention period that fits every business or jurisdiction. Follow your organization’s recordkeeping rules and applicable requirements, and keep only records you have a legitimate reason to retain.