FAQ

The questions people ask before booking a walkthrough, answered in one place. Where an answer rests on a figure, its source is on the facts page. If your question isn't here, book a walkthrough or email hello@grapeworks.ai.

What did this ad spend return, checked against the platform's own API rather than a self-reported screenshot?

Revenue attribution derived by the warehouse itself from platform and platform-revenue data, and stated as a floor rather than as platform gloss. The published case-study return of 6.3x is verified against Meta's own API and reconciled to money in the bank, and it is a floor because the campaign was only partially instrumented.

Where do the pixel, the platform and the booked revenue disagree, and by how much?

Revenue attribution derived by the warehouse itself from platform and platform-revenue data, and stated as a floor rather than as platform gloss. The published case-study return of 6.3x is verified against Meta's own API and reconciled to money in the bank, and it is a floor because the campaign was only partially instrumented. Every source lands raw, is cleaned per client, and is served as curated views the client owns rather than rents. Every reported number traces back to its raw source file.

Which of my own creatives won spend and clicks, and which should be cut?

Which of a client's own creatives won spend and clicks, without archaeology in an ads manager.

What is a named competitor running right now, in what formats, and for how long has each ad survived?

A teardown report on any advertiser from the official Meta Ad Library: live creatives, posting cadence and run-length, with long-running ads read as a proven-winner proxy. Standing watch-lists per client vertical.

How does organic search performance sit alongside paid, in the same governed place?

Every source lands raw, is cleaned per client, and is served as curated views the client owns rather than rents. Every reported number traces back to its raw source file. Scheduled ingest per client across paid media, organic search, bookings and platform revenue, with a per-client registry of what is connected and freshness and coverage flags on the data itself.

Where did this specific number come from, and who asked what of the warehouse?

Every question put to the warehouse is recorded, client-scoped, with its provenance and token usage. Every number can be traced to where it came from.

What should I change next, what is the forecast, and what happened when the last change ran?

Ranked recommendations for improving paid media, each carrying a forecast, the levers behind it, and the measured before-and-after result of changes that already ran. Proposed campaign changes are staged paused and never fire themselves. On the Assisted rung, the approval expires after twelve hours, so a decision you did not make stays unmade, and a budget change is capped at 1.5x per step. Both are defaults the operator chooses. The budget check fails closed: if the current budget cannot be read, the change is refused rather than applied to an assumed value. Built and merged, but not reachable by anyone outside Grapeworks. No public surface. Do not treat as callable.

Can I ask this in plain English and get a checkable answer with its provenance attached?

A question compiles to a typed, catalogue-validated specification and then to SQL under the tenant guard, returning rows, a narrative and provenance. Built and merged, but not reachable by anyone outside Grapeworks. No public surface. Do not treat as callable.