Choose a traffic source for your connected channel

Routy could not tell which of your traffic sources one of your connected channels belongs to. Until that is settled, the channel's numbers are not credited to any of your sites, so it looks as if it earned nothing.

What it means

Some channels tell us where their traffic lands: a Search Console property reports its web address, a Voluum workspace its landing pages, an AppsFlyer app its store pages. Routy compares those addresses with the website addresses on your traffic sources and links the channel to the one that matches. This time there was no single clear match, and we do not guess, because crediting one site's earnings to another looks completely normal on a report.

The channel keeps syncing and nothing is lost. The numbers are just not attributed to a site yet.

Why it happens

The message tells you which case you are in:

• Several of your traffic sources match. Usually the same site was added twice, for example once as example.com and once as www.example.com. Both look identical to us.
• None of your traffic sources match. Either the channel sends traffic to a site you have not added as a traffic source, or the traffic source's website address is not stored as a full address. example.com on its own cannot be matched; https://example.com can.

What you can do

1. Open Traffic sources and find the site the channel belongs to. See Traffic sources.
2. If the site is missing, add it as a traffic source with its full address, starting with https://.
3. If its website address is not a full address, correct it to one.
4. If the same site is there twice, delete the duplicate you do not use. Check first that none of your live tracking links belong to it, because they stop working when it is deleted.
5. Wait for the channel's next sync, which runs about every hour. The link is then made automatically.

If the channel genuinely belongs to a traffic source whose address does not match (for example, a tracker that sends traffic to several sites), contact support and tell us which traffic source it is.

When it clears

When the traffic source is chosen for the connection, the issue closes straight away and the channel's history is re-credited in the background, going back as far as we hold that channel's data (90 days for most).

If you fix it by correcting your traffic sources instead, the channel is linked on its next sync, but this issue does not close at that moment. It closes by itself 30 days after it was last raised. While the problem is still there, each sync raises it again and keeps it open.