Use click reports to check when your app link gets traffic, which destinations it sends visitors to, and which devices they use. Country and referrer data can add context, though those fields may be missing.
01 Start with the destination and the click context
In AppRoute's click analytics, choose the link and reporting period before interpreting its clicks. Read the destination alongside the available context: the same total can prompt different checks depending on when traffic arrived, which devices visitors used and how the source was identified.
| Context | What to check next |
|---|---|
| Timestamp and link | Confirm that you're reviewing the intended link and period. Use the same timezone when comparing reports. |
| Destination | Check that the recorded destination matches the store listing or website you intended visitors to reach. |
| Device and browser | Look for traffic patterns that warrant checking the destination on that device or browser. |
| Source and referrer | Check campaign tags and available source information before assigning traffic to a placement. |
| Country | Compare known countries with the audience you intended to reach. Keep unknown locations separate. |
Source labels need care. AppRoute can infer a source from campaign tags, platform click IDs, in-app browser signals or the referrer. Those signals can be incomplete. A missing referrer may appear as “direct,” but that doesn't establish that someone typed or bookmarked your URL.
A click total also isn't a count of unique people. Before treating a change as an audience trend, note your team's test clicks and check how bot and link-preview traffic is filtered.
02 Compare one placement at a time
Give each placement a consistent label before you compare its clicks. For TikTok and Instagram profile links, keep the campaign, medium and content values the same and change only the source. That gives you a specific comparison: traffic through each profile link during the period you choose.
In this hypothetical app-launch setup, add these query values to your app's smart link:
| Campaign parameter | TikTok profile | Instagram profile |
|---|---|---|
utm_source | tiktok | instagram |
utm_medium | organic-social | organic-social |
utm_campaign | app-launch | app-launch |
utm_content | profile | profile |
AppRoute reads these campaign values from the incoming smart link URL into click events. The labels describe your setup; choosing organic-social doesn't prove that every click came from organic reach. Use the UTM cheat sheet to build the URLs, then compare them as follows:
- Check the labels before collecting a comparison period. Put the TikTok-tagged URL in your TikTok profile and the Instagram-tagged URL in your Instagram profile. Open each once and verify that its campaign values appear in the click report. Record those test clicks so you can account for them when reviewing traffic.
- Match the reporting windows. Choose the same start and end dates for both placements, using one timezone. If you're comparing one week with another, use windows of equal length. Avoid comparing a partial day with a full day.
- Keep the report definitions consistent. Use the same app link, campaign, medium and content values, with source as the comparison variable. Apply the same filters to both sets of clicks. Note how team tests, bots and link previews are handled; don't assume every unwanted click has been removed.
- Describe the difference at the level you measured. Compare clicks through the two tagged profile links. A higher click total doesn't establish a larger unique audience or greater organic reach. If the labels, windows or filters differ, fix that mismatch before using the comparison to decide which placement deserves attention.
03 Keep imported revenue beside the click report
On Pro and Team, you can import overall revenue from Stripe and RevenueCat to review alongside link traffic. Those totals don't tell you which link produced a purchase: revenue attribution from individual link clicks is coming soon. If clicks and revenue rise during the same period, that gives you a pattern to investigate, not evidence that those clicks caused the sales.
Before comparing imported revenue across periods, check the provider, date range, metric definition and how refunds are handled. Keep each currency separate; AppRoute doesn't convert currencies or combine them into one total. With those definitions aligned, you can describe how traffic and revenue changed over the same period without assigning revenue to a particular placement.
04 Leave the next person a useful note
Record what you found and what you want someone to check next. A useful note gives a teammate enough context to repeat the comparison without treating your interpretation as a measured result.
Copy this blank decision worksheet and fill it with your own findings:
| Field | Your notes |
|---|---|
| Period and timezone | |
| Link or campaign reviewed | |
| Traffic pattern or finding | |
| Checks completed and questions still open | |
| Next action and who will take it |
For example, if Android traffic records an unexpected destination, assign a teammate to open the tagged link on Android and inspect its routing settings.
Keep customer emails, names and secret tokens out of public campaign URLs. Before sharing a click export, review which data it contains, who needs access and how long it should be kept. Hashing a value does not guarantee anonymity. Read the AppRoute privacy policy when reviewing how the service handles data.
Choose one open question from your worksheet and assign the next check.