---
title: "Separate catalog data from customer segments"
url: https://www.datawebot.com/blog/klaviyo-scraped-data-segmentation
description: "A manual handoff recipe to adapt in your own environment. Public extraction does not provide customer identity, consent or campaign execution."
updated: 2026-09-14
author: datawebot team
---

Extraction guide

# Separate catalog data from customer segments

A manual handoff recipe to adapt in your own environment.

Updated September 14, 2026 · datawebot team

[← All guides](https://www.datawebot.com/blog)Field map ↓Try the workflow ↗

01 / INPUT**Product records + authorized customer data**

02 / YOUR WORKFLOW**Map fields → inspect → hand off**

03 / OUTPUT**A reviewed segmentation input**

## Keep the right fields.

Manual data handoff

| Field / step | Input | Rule |
| --- | --- | --- |
| Source record | Product and variant identifiers | Keep identity as strings. |
| Identity | Your merchant catalog mapping | Do not join customers on product titles. |
| Evidence | source_url + retrieved_at | Keep the original observation attached. |

Synthetic catalog data · not a retrieval result

01 / Example record Fictional product

### Cotton Crewneck T-Shirt

`No source URL`

Products

1

Variants

4

Record origin

Synthetic

Page visits

Not applicable

[Field definitions](https://www.datawebot.com/docs/data)

02 / Inspect the example

| Variant | SKU | Example price | Example availability |
| --- | --- | --- | --- |
| Small / Navy | `DEMO-TEE-S-NV` | USD 32.00 | Example: available |
| Medium / Navy | `DEMO-TEE-M-NV` | USD 32.00 | Example: available |
| Medium / Sand | `DEMO-TEE-M-SD` | USD 34.00 | Example: unavailable |
| Large / Navy | `DEMO-TEE-L-NV` | USD 32.00 | Example: unknown |

All names, identifiers, prices and availability values are fictional. They do not describe a merchant’s catalog or inventory.

Illustrative schema · synthetic records

[Example CSV](https://www.datawebot.com/samples/catalogue-example.csv) · [Example JSON](https://www.datawebot.com/samples/catalogue-example.json) · [Use with an agent](https://www.datawebot.com/docs/agents)

## Before you use the output

Public extraction does not provide customer identity, consent or campaign execution.

## Check one record first.

Start with the smallest useful scope. Compare the returned record with its source, confirm variant identity and inspect missing fields before applying the mapping to a larger dataset.

Keep extraction warnings and the retrieval timestamp with downstream output. When a required field is missing, leave it unresolved or return to the source; do not fill it from an assumption.

Working references [Product and variant schema ↗](https://www.datawebot.com/docs/data) · [Supported endpoints ↗](https://www.datawebot.com/scraper) · [Incomplete or unavailable results ↗](https://www.datawebot.com/docs/troubleshooting)

[Continue this workflow](https://www.datawebot.com/solutions/product-catalog-enrichment)