Lookups publishes any Lens table as a key/value API your website, tag manager or app can call in single-digit milliseconds. One table, one key, one answer. No engineering project.
Requires Lens. 14-day free trial, no credit card.
Your product catalogue, your store list, your price bands, your loyalty tiers. All of it is sitting in a reporting table nobody can query from a web page. So the site gets a hardcoded copy that goes stale, or a ticket goes into an engineering backlog.
A warehouse table is built for dashboards. Pointing a live web page at it means either a slow query or a nightly export somebody has to maintain.
A JSON blob pasted into a tag or a page ships once and then quietly diverges from the source. Nobody notices until a price or a store address is wrong.
Standing up an endpoint means a service, a deployment, keys, monitoring and someone to own it. That is a lot of ceremony for one table.
Any table Lens already maintains. It might come from a CSV you upload, a REST feed, BigQuery, your Echo event stream or a join across several sources. If Lens can build it, Lookups can publish it.
Choose the columns that identify a row: a SKU, a store number, a postcode, a customer tier. Those columns become the key you call the API with.
Publishing mirrors the table into a low-latency key/value store behind its own endpoint. Each lookup gets its own access key, and you can restrict which sites are allowed to call it with an origin allowlist.
A tag in GTM, a script on the page, a mobile app, a server. Pass the key, get the row back. Requests are metered so you can see exactly what is being asked for.
Anything shaped like "give me this key, tell me about it" fits.
Look up a SKU and get back name, category, margin band or whatever else the table holds. Useful for enriching a tag payload without asking the site to carry the whole catalogue.
Store number in, address and opening hours out. The list stays maintained in Lens where the rest of the business already keeps it.
Region, tier or quantity in, price out. One table, one key, and no pricing logic duplicated into front-end code.
Resolve a customer identifier to a tier or segment at page load, so personalization and tagging can act on it straight away.
The published table is mirrored into a key/value store built for point reads, not scans. It answers fast enough to sit in a page load without anyone noticing it.
Every lookup is published with its own key, separate from your TagPipes login and from every other lookup. Revoking one does not touch anything else.
Restrict a lookup to the sites you name. Calls from anywhere else are refused, so a public key does not mean a public free-for-all.
Every call is counted, so you can see which lookups are actually being used and what they cost before you scale them up.
A lookup can be keyed on more than one column. Region plus tier, store plus day, brand plus SKU. The combination is the key.
CSV uploads, REST feeds, BigQuery, Search Console, Adobe, Olo, your own S3 bucket, Echo events, or a join across several of them. The lookup does not care where the rows came from.
Metered on lookup API requests per month. Annual billing pays for ten months and covers twelve. One-time setup fee applies.
Lookups requires a Lens subscription. Add-ons available for request overage, hourly mirror refresh and additional mirrored rows. Questions about limits? .
Publish the table you already maintain and let the site read it live.