Free attribution tool

MMP Tracking Link Checker

Check AppsFlyer, Adjust, Branch, Singular, Kochava, Airbridge or another attribution URL. See every error, its reason and the exact fix before sending paid traffic.

Paste complete tracking link

Processed only in your browser. The link is not opened, followed or saved.

Step-by-step guide

How to check and fix your link

Copy from MMP

Copy the complete attribution link from your MMP campaign or partner setup.

Insert ADJODO macros

Map the click identifier to {click_id}; AppsFlyer commonly uses af_sub1={click_id}.

Paste and check

Fix every red error first, then review amber warnings and the parameter table.

Fix at the source

Edit the MMP/network template, copy the updated URL and check it again.

Run a real test click

Use a test device and verify that the click appears inside your MMP.

Verify conversion/postback

Complete the intended event and confirm SDK attribution plus the S2S postback.

Important: This checks URL structure only. It cannot confirm that the SDK is installed, tracker token is active, postback secret is correct or a conversion will be approved.

Need integration help?

A valid URL can still fail when the SDK, event mapping or S2S postback is incorrect.

Tracking docs Contact support

Read a tracking-link report before spending on traffic

Start with the actual campaign template

Paste the complete link that publishers are expected to use, including its query parameters. A shortened screenshot or a domain copied from an email cannot show the same template problems as the original address. This checker inspects the URL you provide and identifies familiar attribution-provider hosts.

Its findings concern the visible structure of that link. They do not establish ownership of the campaign, verify an SDK installation or contact a provider account. Keep the original version separately so you can compare the suggested change with the link that was supplied by your campaign manager.

Understand placeholders and real identifiers

A template can contain placeholders that are replaced when a click is generated. Seeing a placeholder in the editor is therefore different from seeing it unchanged after a real click. Check the parameter table to understand which values look like macros and which values are ordinary text.

The click identifier needs to travel through the agreed mapping so a later conversion can be associated with the correct visit. Do not replace every placeholder with a made-up value merely to remove a warning. Confirm the expected mapping with the system that expands the link and the system that receives it.

Prioritize errors without turning warnings into guarantees

An invalid address or an unsuitable scheme deserves attention before a campaign is distributed. Warnings can point to incomplete mappings or settings that need human review, but the right fix depends on the provider and the campaign design. Read the finding and its explanation together instead of using the score as an approval certificate.

A link can pass structural checks and still point to an inactive tracker. Conversely, a provider-specific setup may require context that a local URL inspection cannot infer. Resolve each finding against your actual integration rather than optimizing only the displayed number.

Edit the source and inspect the result again

Correct the template in the place where it is maintained, then copy the revised version into the checker. Editing a temporary copy without updating the campaign leaves publishers using the older address. Compare the domain, destination-related parameters and click mapping after the edit.

Watch for accidental spaces, doubled separators or values that became encoded twice during copying. Preserve case where a provider treats a parameter value as case sensitive. If several people distribute links, label the approved version clearly so an earlier attachment does not quietly become the active template again.

Finish with an observed test journey

A structural report is one step in validation. Use an authorized test journey to observe the generated click and the intended destination, then check the attribution and conversion path in the relevant systems. Match identifiers across that journey before concluding that the integration is complete.

Avoid submitting fabricated production conversions simply to obtain a successful response. Share the finding titles and a redacted example when asking for help; provider secrets and personal device identifiers are not needed in a public message. Repeat the inspection whenever the template, attribution provider or payable event changes.