Is Revcontent traffic real? How to check Revcontent traffic quality
widget / site in RevcontentValidVisit flags the bad widget / site; block them in Revcontent's targeting blacklist.
Revcontent operates as a cost-per-click native recommendation network, placing sponsored content widgets across a broad publisher base that ranges from large editorial properties to long-tail content sites. The supply-side economics create a structural tension: individual publishers are paid per outbound click generated by the recommendation widget they embed, giving lower-quality properties a direct incentive to send volume rather than intent. That volume does not distribute evenly — it clusters in specific `{widget_id}` values tied to specific publisher placements, which means campaign-level metrics can look tolerable while a handful of widgets quietly consume a disproportionate share of budget against visits that never engage. ValidVisit captures Revcontent's tracking tokens on every click — `{widget_id}`, `{boost_id}`, and `{conversion_uuid}` — so IVT scoring happens at the sub-source level where the problem actually lives, not averaged across the entire boost.
https://yoursite.com/landing?utm_source=revcontent&utm_medium=native&vv_campaign_id={boost_id}&vv_creative_id={content_id}&vv_publisher_id={widget_id}&vv_placement_id={adv_targets}&vv_click_id={conversion_uuid}How invalid traffic shows up on Revcontent
On Revcontent, the clearest early signal of degraded inventory is a disconnect between click volume and any downstream engagement: sessions that arrive without scroll, without dwell, and without any interaction with on-page elements. That pattern is not random — it tends to be sharply concentrated in a small number of `{widget_id}` values, and those widgets almost always map to publisher domains whose editorial model depends on driving outbound traffic at high volume rather than retaining readers.
A second pressure point specific to native recommendation inventory is proxy and residential-proxy traffic. Recommendation widgets are embedded on content sites that attract privacy-tool users, but the risk profile differs: a genuine privacy-conscious reader carries low IVT risk, while a rotating residential proxy cycling through sponsored cards to generate clicks carries high risk. ValidVisit tells these cases apart by weighing each click against 100+ independent data points — covering where the click came from, the device behind it, and how the visitor actually behaves on the page — so a real browser running a VPN reads very differently from an automated proxy stack, even when both resolve to a residential IP range.
A third pattern is server-farm click volume that mimics organic content discovery behavior at the surface level — a sponsored card receives a click, the advertiser landing page loads, and the session ends immediately with no further signal. Those origin and network characteristics are part of the same 100+ data points ValidVisit folds into a single 0-100 quality score per click, and every score is tagged with the `{widget_id}` and `{boost_id}` so you can see which sub-sources are disproportionately associated with these hollow sessions. The tracking script fires asynchronously and does not alter or delay the landing page load path in any way.
What to watch on Revcontent
Sort your ValidVisit publisher report by `{widget_id}` and compare each widget's IVT rate against your campaign-wide baseline. Widgets running well above that baseline — especially those accounting for a disproportionate share of total clicks — are strong exclusion candidates. Add those widget IDs to Revcontent's widget blacklist manually inside the network dashboard.
A boost that opens with reasonable traffic quality and degrades over a multi-week window is a sign that lower-quality publisher placements are being added to the distribution as the boost scales. Monitor per-`{boost_id}` IVT rate on a rolling basis; a sustained upward trend warrants reviewing which new widgets have entered that boost's inventory.
Cross-reference ValidVisit's per-click scores against on-site engagement signals — scroll depth, session duration, CTA interaction. Clicks with elevated IVT scores that also show zero engagement corroborate automated or incentivized traffic. Use `{conversion_uuid}` to join ValidVisit data with your analytics platform or CRM at the individual click level, giving you an auditable record per session.
Use the `{adv_targets}` parameter to segment IVT rates across different content-category or audience targeting selections. If a specific targeting segment consistently over-delivers clicks at elevated IVT rates, the publisher placements serving that segment likely include lower-quality sites that warrant either exclusion or reduced bid weighting.
How ValidVisit attributes Revcontent traffic
Each Revcontent macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | Revcontent macro | Maps to | Identifies |
|---|---|---|---|
| Campaign (Boost) ID | {boost_id} | campaign_id | campaign |
| Content (Creative) ID | {content_id} | creative_id | creative |
| Widget ID | {widget_id} | publisher_id | publisher |
| Advertiser Targets | {adv_targets} | placement_id | placement |
| Click ID (rc_uuid) | {conversion_uuid} | click_id | click |
- Revcontent macro
{boost_id}- Maps to
- campaign_id
- Identifies
- campaign
- Revcontent macro
{content_id}- Maps to
- creative_id
- Identifies
- creative
- Revcontent macro
{widget_id}- Maps to
- publisher_id
- Identifies
- publisher
- Revcontent macro
{adv_targets}- Maps to
- placement_id
- Identifies
- placement
- Revcontent macro
{conversion_uuid}- Maps to
- click_id
- Identifies
- click
Pinpoint the bot publishers & placements in Revcontent
Revcontentitself isn’t the problem — bots and invalid traffic concentrate in a handful of its sub-sources: the publisher, site or zone, and the placement or widget within it. So we roll the score up by those Revcontent tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — Revcontent traffic scored 0–100 per sub-source, worst first.
See your own Revcontent sub-sources scored this way.
Bot / invalid-traffic score broken down by:
- Widget ID
{widget_id}Numerical identifier of the publisher widget/placement where the click occurred. Recommended by Revcontent for utm_medium to track the publisher placement.
Bot / invalid-traffic score broken down by:
- Advertiser Targets
{adv_targets}Traffic type / topic the creative was serving based on (where the click came from).
Per-click id: Revcontent passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every click.
Compare bot & invalid-traffic breakdown across every ad network →How the detection works
Data points → one score
Every click is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Many angles, combined
Each data point is combined rather than checked in isolation, so a genuine human almost never trips enough of them to be flagged — and bots that beat one rarely beat the rest.
Proprietary, not a black box
The detection model is ours and stays that way. What you get is a clear verdict on every click — not a single brittle rule you can game, and not an unexplained number you can't act on.
Pinned to the source
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
Revcontent traffic quality — FAQ
How do I act on ValidVisit's findings inside Revcontent?+
ValidVisit scores every click and attributes each score to the originating `{widget_id}`, `{boost_id}`, and `{conversion_uuid}`. Your ValidVisit dashboard lets you sort and filter by widget to identify the placements driving elevated IVT rates. From there, you export that list of widget IDs and paste them into Revcontent's widget blacklist manually — the exclusion happens inside the Revcontent interface, not inside ValidVisit. ValidVisit's role is to give you the scored, ranked list of sub-sources; Revcontent's own tools are where the exclusion is executed.
Why does click quality need monitoring per widget rather than per boost?+
A boost is a campaign-level container — it aggregates performance across every publisher widget in Revcontent's inventory that matches your targeting. IVT almost never distributes uniformly: a boost can show an acceptable average quality score while a small number of widgets within it are responsible for the bulk of low-quality sessions. Boost-level metrics average out the problem; widget-level scoring surfaces it. That is why `{widget_id}` is the most diagnostic dimension for Revcontent — it maps one-to-one with individual publisher placements, which is where the incentive structure that drives click inflation actually operates.
Does ValidVisit work with Revcontent's direct-link click delivery?+
Yes. Revcontent delivers clicks via a direct destination URL rather than an extra-hop chain, which means there is no in-transit signal to intercept — all scoring happens once the click lands on your page. ValidVisit's tracking script fires asynchronously on the landing page and reads how each visit arrives and behaves without adding any latency to page load. The `{conversion_uuid}` macro (passed as `rc_uuid` in your URL) ties each tracked event back to the exact Revcontent click record, enabling click-level attribution in your reports.
Catch the fake clicks on Revcontent.
See which campaigns and publishers send real, converting traffic vs bots — every click scored 0–100.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis