Customer support

Get help from guidance or the ADJODO team.

Ask the assistant for product guidance or your own account status, and send a request when human review is needed.

Open support chat Send a request

Public how-to answers

Private account help

Human escalation

Admin-reviewed replies

Privacy controls

Conversation history

Ask

Describe the workflow and affected campaign—never send passwords, OTPs or payment secrets.

Troubleshoot

Get help with verification, campaigns, tracking, wallets, payouts and fraud review.

Escalate

Unresolved questions can enter the support queue or contact workflow.

Prepare a support request that can be investigated

Choose account support when the issue needs a private record

Some questions can be answered from a public guide, while others require an authorized review of an account or campaign. Use support when the issue depends on a specific status, transaction, link or submitted request. Begin by identifying your role and the workflow affected. A publisher earning question and an advertiser funding question can involve different records even when both are described as a payment issue.

The public support page helps you choose the appropriate channel and prepare the information needed for that review. It does not expose another account's records or authorize a change simply because a message has been sent. Keep private details in the account-specific channel appropriate to the issue rather than posting them in a public discussion or an unrelated contact message.

Describe a reproducible issue instead of only its symptom

Write the action you attempted, the page where you attempted it and the result shown by the interface. Include the relevant campaign or request reference if you have one, along with the approximate time of the problem. A clear expected result helps distinguish a failed operation from a misunderstanding of the current workflow. If the issue appeared after a configuration change, mention what changed without exposing its secret values.

A screenshot can show an error state, but a screenshot alone may omit the step that produced it. Keep the description focused on one issue so the investigation has a clear scope. This preparation allows the support team to decide which records and permissions are relevant before asking for additional context.

Share evidence without sharing access to the account

Do not include passwords, OTPs, access tokens or private integration secrets in a conversation. An authorized investigation can use references and appropriately scoped logs without receiving your full credentials in a chat. Remove unrelated personal details from screenshots and confirm that copied URLs do not contain secret values. For a tracking issue, provide the campaign and test reference through the relevant support workflow rather than broadly publishing a raw callback.

For an account-access issue, describe the displayed message and the recovery step attempted. The type of evidence should match the question. Keeping that distinction clear avoids sending a large collection of confidential material that does not actually help identify the cause of the problem.

Keep the conversation and next action connected

Retain the request reference and continue the discussion where the relevant evidence has already been collected. If you need to add information, explain how it relates to the original issue instead of starting a separate account of the same problem. Read any requested next step carefully and verify that it uses the official product workflow. A support message is not a guarantee of immediate approval, payout or a configuration override.

The team may need an authorized review, an integration check or another dependency to resolve the issue. A concise record of the problem, evidence and next action makes the status easier to understand. Use Help for general product sequences and Contact for a broader enquiry, while reserving account support for the specific private record that needs investigation.