Nudge's traffic sources are an excellent way to split and compare different sources against each other.
To get the most out of these splits in your application, Nudge offers a couple of ways to get set up.
How things work out of the box
By default, Nudge looks for common traffic tags in order to help it decide where to route your traffic. These are:
- The common "utm_source" parameter from Google
- Social referrers, from Facebook, Instagram, Google Plus, LinkedIn, etc
If we see any of these, and you do not have any custom rules in place, these will be used to select the source. If nothing is detected, the source is deemed as direct.
Native native tags
Nudge native tags are included out of the box. If these tags are seen, they take priority over the above tags. These can be used a couple of different ways:
- If you include ndg_source AND ndg_label, we will route the traffic source to "ndg_source - ndg_label" - where the two ndg_ tags are replaced by the values you provide in the URL. Please see below for examples.
- If you include JUST ndg_source, we will the value of this as the traffic source.
Will be routed to: "Hello"
Will be routed to: Hello - Placement 1 (the %20 is converted to a space)
See https://ndg.io/admin/traffic_sources if you need further help here.
Please note: Allow values must be HTTP escaped. Please see here if you need more details.
Using custom or existing tags
Fully custom tags can also be set up for to help route your traffic. These provide the greatest flexibility, including the ability to read and understand your existing tags.
Please visit here https://ndg.io/admin/traffic_sources, and select the "Existing Tags" tab to begin working with custom or existing tags.
Some example of how this can be used:
|Key||Value||Traffic Source Name||Result|
|nudge||<blank>||<blank>||The value of the "nudge" parameter will be used|
|nudge||testing||Facebook Live Video||If we see the parameter nudge=testing, we will mark this as "Facebook Live Video"|
|<blank>||Feed||If we see the parameter "google" used anywhere, we will mark the impression as being from "Feed"|
My direct traffic seems too high
- High direct traffic to content is unlikely to occur. So if it is, it can be a red flag.
- The likely cause is a traffic source is removing the traffic parameters and referrer.
- Use the Nudge Traffic Source Builder, to create your sources and add the parameters to all inbound traffic sources.
Note: This can also be an indicator of advertising fraud. If in doubt you can request a Nudge engineer to evaluate the sources. Please lodge a ticket within the dashboard.
If a large amount of the direct traffic is mobile (simply use the dashboard filters to verify this) it could be in-app traffic. The fix is the same, to append traffic parameters to the inbound sources.
My traffic sources aren't showing up
This typically means either the parameters aren't showing up OR the Nudge code isn't on the page.
The best way to debug this, is to find an ad unit/traffic source and click on it.
- Once you arrive on the content and it has finished loading.
- Copy the URL in your browser toolbar.
- Paste it in to a text editor.
- Can you see your Nudge parameter on the URL?
- If not, neither can Nudge. You need to investigate your traffic driver setup and/or any click trackers aren't removing the parameter.
- If you can,
- Is this a custom parameter? Please check your Traffic Source Builder is configured correctly.
- If this is a regular Nudge parameter, please check your dashboard in 30 minutes
Need something more advanced? Send us a message at email@example.com.