# WooCommerce integration for paid acquisition

Hendrik reads WooCommerce orders, refunds, products, customers, and current inventory so you can compare advertising reports with store results.

## Questions Hendrik can help answer

- Did net order value move with the advertising report?
- Did refunds change the store result?
- Is current stock a reason to limit more demand?

## Illustrative example

### Platform value rises while store net value falls

All figures are USD for the same completed 28-day windows

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- Spend (Google Ads): US$20,000 → US$25,000
- Reported conversion value (Google Ads): US$80,000 → US$100,000
- Net order value (WooCommerce): US$100,000 → US$98,000

### What Hendrik checks

- **Check matching windows:** Use completed periods and identify whether refund recognition differs from the advertising platform.
- **Inspect refund timing:** Test whether refunds were created for earlier orders.
- **Review stock:** Check whether current low-stock items make additional demand undesirable.

### What Hendrik sees

Google Ads reported higher conversion value while WooCommerce net order value fell.

### What to do next

Do not increase spend until the team resolves the store-level discrepancy.

**Limit:** This aggregate comparison does not show that Google Ads caused the change.

## What WooCommerce contributes

Use WooCommerce with ads data to compare reported conversion value with store orders, refunds, and current stock.

## Data Hendrik reads

- **Orders:** Store order facts and order-line details.
- **Refunds:** Refund records incorporated into net order value.
- **Products:** Products, variations, SKU, quantity, and order-line value.
- **Inventory snapshot:** Current stock state, not inventory movement history.

## Setup and access

- **Setup:** Enter the store URL and approve WooCommerce application read access. Setup can request 1 to 730 days of history.
- **Permissions:** WooCommerce application authentication with read access.
- **Accounts:** One store, identified by its store, site, and home URLs.
- **History:** WooCommerce setup defaults to 90 days and accepts 1 to 730 days. Hendrik shows the actual coverage after the first sync.
- **Refresh:** Configured data streams run from hourly to every 6 hours. Hendrik shows the published freshness for each source after sync.
- **Setup timing:** WooCommerce starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- **Actions:** Connecting reads WooCommerce data. It does not change products, inventory, or orders.
- **Availability:** Your workspace shows Connect or Request access for your account.

## What you need to connect

- Confirm the exact WooCommerce store is available in the workspace.
- Use completed, comparable windows and one currency.
- Keep order and refund date definitions visible.

## Important limits

- WooCommerce attribution source, medium, campaign, and content are unavailable in the current model.
- It does not provide payment settlement, disputes, or order-level COGS history.
- Current inventory does not prove stock at the time of an order.

## Provider documentation

- [WooCommerce REST API](https://woocommerce.github.io/woocommerce-rest-api-docs/)
- [Google for WooCommerce](https://woocommerce.com/document/google-for-woocommerce/get-started/)

## Start with WooCommerce

[Create a workspace and connect WooCommerce](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=integration-woocommerce&integration=woocommerce)