Before You Build
Web AppShut Down

Lookery

Lookery was a social ad targeting and analytics company built around Facebook application and social-network data.

View original story

Product snapshot

What it was

Lookery sold social ad targeting, analytics, and ad network services around Facebook applications and other social-network inventory.

Who it was for

advertisersad networksFacebook app developerssocial app publishers

Problem / value

Help advertisers and app publishers monetize and target social-network audiences.

Core workflow

  • target ads using social data
  • monetize Facebook app traffic
  • analyze social app audiences
  • sell or buy social-network ad inventory

Product form

ad networkanalytics servicesocial ad targeting platform

Pricing model

Public sources describe an ad network and data business; exact pricing is not public.

What happened

Summary

Lookery’s ad network business was sold to Adknowledge, making it a low-confidence but useful platform-dependency signal for products built close to social-platform data and inventory.

Outcome

The ad network business was folded into Adknowledge; the standalone company’s later public shutdown evidence is limited.

Demand signal

Public sources show Lookery operated close to Facebook app advertising and later sold its ad network business, but they do not provide a full founder postmortem or quantified shutdown reason.

Distribution issue

Lookery’s early opportunity depended on Facebook applications, social-network ad inventory, and data surfaces controlled by larger platforms.

Timeline

  • 2007: Wired covered Lookery as part of the emerging Facebook widget ad network market.
  • 2008: VentureBeat and Adweek reported Lookery sold its ad network business to Adknowledge.
  • 2009: Failory lists Lookery as shut down, but detailed shutdown mechanics are not public in the sources used.

Before you build

Why it matters

Many small tools now sit on top of social graphs, ad platforms, app stores, search APIs, or browser ecosystems where the platform can change access or absorb the feature.

Primary check

Prove you can keep access, differentiation, and buyer value if the platform changes data access or absorbs the ad product.

Checklist

  • Can the product work if the platform changes API or ad-targeting rules?
  • Does the company own any defensible dataset or workflow outside the platform?
  • Would customers keep paying if the platform shipped the same targeting feature?
  • Identify which data, audience, and inventory are controlled by the platform.
  • Test whether buyers still value the product without exclusive platform access.
  • Build an export, owned-data, or cross-platform path early.
  • Avoid strong claims when only acquisition and directory evidence is public.

Relevant if

  • You are building with platform-owned data
  • Your product depends on one social or ad ecosystem
  • A platform-native feature could replace your workflow

Less relevant if

  • You own the underlying customer data
  • The product works across several platforms with independent value

Pre-build tests

  • Run a buyer interview focused on what happens if platform data access changes.
  • Build a cross-platform proof before relying on one ecosystem.
  • Test whether owned first-party data improves outcomes beyond platform-native tools.

Transferable lessons

  • Treat platform access as borrowed, not owned.
  • Build value that survives if the platform changes data access or ad products.
  • Avoid making all distribution and data come from the same platform owner.

If you build this today

Start with owned data or a cross-platform workflow before building an analytics or ad product around one platform’s audience graph.