Read common questions with the relevant account workflow in mind
Use an FAQ answer to identify the next check
A frequently asked question can explain a common product step, but it cannot display the actual state of every account. Begin by identifying whether the question concerns advertising, publishing, tracking or account access. Read the answer as guidance about the supported workflow and then compare it with the status shown in your own account. A general explanation of campaign approval does not establish that your specific campaign has already been approved.
Likewise, a payout overview does not identify the amount available for a particular request. The FAQ page helps reduce confusion about recurring questions, while private records and exceptional cases remain part of the authorized account and support process. Keeping that distinction clear makes the answer more useful without implying facts that the public page cannot know.
Understand prerequisites before expecting the final action
Many product questions concern the stage after a prerequisite has been completed. An advertiser may need account verification and a funded wallet before proceeding through the campaign sequence. A publisher may need source review and campaign eligibility before a useful link can be used. Check the current stage instead of jumping to the last action mentioned in an answer.
If the interface displays a specific error, preserve that message and the step that produced it. The same broad question can have different causes for different accounts. A concise FAQ answer points to the normal sequence, but it should not be used to bypass the sequence or to assume that a previously completed setup applies unchanged to a new campaign or integration.
Keep model definitions and recorded outcomes separate
Terms such as click, install, lead and action describe different objectives and different records. When an answer discusses pricing or reporting, identify which model it refers to and which stage of an event is being counted. A raw callback is not automatically a reviewed payable outcome, and a destination visit is not the same as a completed lead. Compare the answer with the model and event definition configured for the relevant campaign.
For a discrepancy, use a campaign reference and a defined time period rather than an unlabeled screenshot of a total. Tracking and API documentation provide more detail when the issue concerns identifiers or callbacks. An FAQ can clarify a concept, while a technical or account-specific investigation still needs the evidence that belongs to the actual setup.
Escalate when the question depends on a private decision
If an answer does not resolve the issue, identify which part of it differs from the behavior you observed. Contact the authorized team with the role, page, reference and error needed for that review. Avoid sending passwords or integration secrets in an attempt to make the conversation faster. Keep several separate questions distinguishable so a support reply can address the right one.
If the issue is a new commercial requirement rather than a product error, use the enquiry route suitable for that discussion. The FAQ is not a substitute for an approval decision or a guarantee of a specific service outcome. Its purpose is to make the normal product steps understandable enough that a visitor can take an informed next action or explain precisely where further help is needed.
Check the scope of a saved answer before reusing it
An answer copied into a team note should retain the question it addresses. A sentence about one campaign model can become misleading if reused as a statement about all models. Keep links to the relevant product page with the note and review the current account requirements when applying it to a new setup. This prevents a useful short explanation from becoming an unsupported blanket promise in another conversation.