How Attribloom researches, tests, and updates its documentation

Attribloom documentation is written by Attribloom Engineering and reviewed by Attribloom Product. These are internal teams, not individual bylined authors, so pages carry an organization-level byline rather than a personal one.

The same people who build the attribution runtime write the guides that describe it. When a guide and the product disagree, the product is the source of truth and the guide is corrected.

Every implementation claim traces to a primary source. For iOS that means Apple's StoreKit 2, App Store Server API, and App Store Server Notifications v2 documentation. For Shopify that means Shopify's Admin API and webhook documentation. For our own runtime that means the public OpenAPI contract at api.attribloom.com/openapi.json.

We prefer primary documentation and the live API over secondary write-ups. Where a page cites a source, it links the exact page and records the date we last checked it.

Code shapes and request and response examples are checked against the public OpenAPI contract and, for platform behavior, against the current Apple and Shopify documentation. We distinguish behavior we have observed directly from behavior we derive from a vendor's documentation, and we do not present one as the other.

The attribution methodology page explains that boundary in detail for the iOS and Shopify surfaces.

Every content page shows a published date and a last-reviewed date. The last-reviewed date changes when we re-check the page against its sources, not only when we change wording.

We revisit a page when the platform it documents changes, when the runtime contract changes, or on a periodic review pass. The sitemap carries the same last-modified dates so crawlers see current freshness signals.

If a page is wrong, we fix the page rather than leave a caveat. Material corrections move the last-reviewed date forward. If you find an error, email [email protected] and we will check it against the primary source and correct it.

We do not publish fabricated metrics, invented customer counts, review scores, or ratings. Numbers on the site read from a real, verifiable source. We do not document a feature that is not shipped, and pages mark a surface as coming soon rather than describing it as available.