-online-total visitors-clicks
Read public placement evidence ↓

The evidence room behind the marketplace.

Buyer reports, open research questions and traceable sources. Fresh launches live on the homepage; this page tests whether the market claims hold up.

11
public sources
5
placement results
1
research clusters
Public placement evidence

What people report after placements go live.

Every card separates the public claim from what it does not prove, then links to the exact original post.

This week

Joffrey IO logo
Joffrey IO@joffreyio · Joffrey IO
Earned result

After an unpaid badge feature on Outbid, Joffrey reported 1,413 outbound clicks, 938 visitors and 43 signups in 31 hours.

CaveatEarned feature, not a paid bid; the result may not transfer to another placement.

X
Not paid1,413 clicks938 visitors
Open
Outbid logo
Jonathan Wilke@jonathan_wilke · Outbid
Founder report

One week after launch, Outbid's founder reported 1.36M visitors, $221K total revenue, a $17K top bid and more than 300 clones.

CaveatFirst-party founder report. The traffic and revenue figures are public claims, not independently audited totals.

MyEmpire logo
Rahul Rajput@r2hu1 · MyEmpire
Operator view

The MyEmpire founder reported 7,000 views in four hours, thousands of clicks, eight countries acquired and two outbids after launch.

CaveatSeller-reported platform activity. It does not show a named advertiser's conversions or collected revenue.

X
7K / 4hThousands2
Open
Stop the Cap logo
Walid B.@WalidBou07 · Stop the Cap
Pending

Walid publicly reported spending more than $1,000 for the #1 Agencies & Services position and promised to publish clicks, leads, meetings and revenue.

CaveatNo outcome follow-up was found as of Aug 27. The open loop is shown so an initial purchase is not mistaken for a successful result.

CrowdReply logo
CrowdReply@Crowdreply_io · CrowdReply
Paid result

After paying $12,700 for Outbid's #1 spot, CrowdReply reported 7,300+ clicks, 1,900+ signups and 55+ demos within 72 hours.

CaveatPipeline is not collected revenue; every figure comes from CrowdReply's own updates.

X
$12,7007,300+ clicks55+ demos
Open
Outrank logo
Tibo@tibo_maker · Outrank
Paid result

A $12,000 placement produced 113 trials across three days. Tibo estimated that 53 of them were above Outrank's normal baseline.

CaveatIncremental trials are derived from a self-reported baseline; resulting customers were not published.

X
$12,000Not reported53 above baseline
Open
1 Million Pixels logo
MakerThrive@MakerThrive · 1 Million Pixels
Paid result

MakerThrive attributed one $1,000 sale to a $42 Outbid placement. A later $24,000 project total is shown separately, not attributed entirely to the ad.

CaveatOnly the $1,000 sale was directly attributed; the later $24,000 total is contextual.

X
$42Not reported$24k later
Open
Comp AI logo
Lewis Carhart@lewiscarhart · Comp AI
Paid result

Comp AI reported 9,391 visits from a $10,000 placement. Its founder said one closed demo would cover the ad through customer lifetime value.

CaveatThe LTV claim is self-reported; closed customers and collected cash were not shown.

X
$10,0009,391 visitsAd covered
Open
Accelevents logo
Jonathan KazarianCEO, Accelevents · Accelevents
Operator view

Here’s the reality. No one trusts ‘event influenced revenue’.

CaveatThe comments include both confirming examples and a direct warning about attribution across repeated event touches.

LinkedIn
AttributionDistrustPublic
Open
Jodi Whitehead logo
Long-form evidenceJodi WhiteheadBizzabo

Sponsor Playbook: Using Onsite Data to Prove Event ROI

Fragmented systems create attribution blind spots. Registration lives in one tool. Badge scans in another. CRM records somewhere else.

Registration, badge scans and CRM records often live in separate systems, creating blind spots between engagement, pipeline and revenue.

Vendelux logo
Long-form evidenceVendeluxEvent intelligence operator

Event Sponsorship: The B2B Pipeline Playbook

Every conversation is logged in CRM same-day with the sponsorship tagged.

Event sponsorship outcomes often lag the event; meetings and opportunities need the sponsorship tagged in CRM and revisited over longer windows.

Sponsorship attributionCorroborated signal · not validated

Sponsors struggle to connect sponsorship activity with conversations, follow-ups, pipeline and eventual revenue.

  1. Sponsorship spend
  2. Meaningful conversation
  3. Follow-up
  4. Pipeline
  5. Revenue

Exact pain

The event report closes before the commercial outcome becomes visible. Impressions and scans are easy to count, while the conversation that changes a deal may only become valuable weeks or months later.

Existing workaround

Teams tag meetings and opportunities to an event in their CRM, then revisit the account over a longer attribution window. Some compare exposed opportunities with similar opportunities that had no event interaction.

What reports miss

Traditional reports prove exposure and activity. They rarely preserve the path from a specific conversation to follow-up, opportunity movement and closed-won revenue.

Sponsor.it implication

Sponsor.it should preserve the source event and conversation context, then let teams append follow-ups, pipeline movement and revenue over time instead of freezing the record at the event date.

What other people confirm

A practitioner in the public discussion described a trade-show conversation that moved a dormant opportunity to a signed contract, while first-touch attribution gave the event no credit.

Another practitioner said repeated third-party event touches make attribution difficult even when the commercial influence is clear.

What could challenge it

Event-influenced revenue is not automatically trustworthy: many other touches can affect the same opportunity.

A useful model needs a declared attribution rule and comparison baseline; merely attaching revenue to an event would repeat the same problem.

Next research question

Ask for the attribution method, not agreement.

Event reports count impressions and badge scans. But some of the best sponsor conversations only become valuable weeks later. How are teams actually attributing those outcomes back to the event?

Test this signal on X ↗