ADJODO is a product of SEO Markit — performance marketing made simpler.

Help center

Find the right workflow without guessing.

Use guides for verification, campaign launch, publisher onboarding, tracking and payments.

Account and OTP help
Campaign setup
Publisher verification
Tracking and postbacks
Wallet funding
Withdrawals
01

Advertiser guide

Verify email, fund the wallet, validate a destination, create a campaign and monitor approval.

02

Publisher guide

Submit traffic details, await verification, choose campaigns and generate unique links.

03

Measurement guide

Use ADJODO tracking or configure AppsFlyer/Adjust and test callbacks.

Find the next product step from the problem you are facing

Identify the workflow before searching for an answer

A helpful starting point is the action you were trying to complete, not only the error message that appeared at the end. Decide whether the issue belongs to account access, advertiser campaign setup, publisher onboarding, tracking or a payment-related request. Each workflow has different prerequisites and records. A campaign cannot be investigated effectively from a screenshot that omits which campaign was involved, while a login problem does not need a conversion payload.

Use the page and role you were actually working with to choose the relevant guide. ADJODO's help route organizes this product context so you can reach a more specific explanation. It is different from the support channel where an authorized person investigates a particular account record or request.

Follow the advertiser sequence with the current status in view

For an advertiser setup question, check account verification and the wallet state before looking at campaign configuration. Confirm the intended destination and selected platform, then review the objective, geography, bid and supported budget controls. Tracking details should match that campaign rather than a remembered template from another account. After submission, read the displayed review state before expecting publisher distribution.

If one step fails, note the field or message and keep the submitted value private where necessary. Do not skip a prerequisite simply because another campaign once used a similar setting. The guide sequence helps locate the stage that needs attention, while the account's actual records establish whether that stage is complete for this particular setup.

Use the publisher path for traffic and link questions

A publisher question often starts with the declared traffic source, its review status and the eligible campaign being considered. Confirm those details before comparing click or earnings counts. A unique tracking link is associated with a campaign and publisher relationship, so another person's link is not a substitute for your own setup. Keep source and sub-identifier information meaningful when it is part of the supported workflow.

For a missing result, identify whether the issue concerns link generation, a visit, a reported event or a reviewed earning. Those stages require different evidence. The public help page can explain the sequence, but private account information should be checked through the authenticated publisher area or shared only with authorized support handling the relevant request.

Escalate with a concise, reproducible description

When a guide does not resolve the issue, use the appropriate contact or support route and describe the steps you took. Include the role, relevant campaign or request reference, time of the issue and the specific message displayed. Explain what you expected to happen and what actually happened. Screenshots can be useful when they omit passwords, tokens and unrelated personal data.

Avoid opening several unrelated conversations for the same request without preserving its reference, because that can scatter the evidence needed for review. Product guidance is not a guarantee that every account state can be changed automatically. A well-scoped description lets the support team decide which authorized workflow should investigate the issue and which additional non-sensitive details are needed next.