Rokt Dynamic Product Ads Data Specifications
Dynamic Product Ads use your product catalog to generate personalized ads that feature the most relevant products for each user. To ensure accuracy, performance, and consistent event matching, the product catalog must follow Rokt's Product Data Specification.
If you already maintain a Google Merchant Center or Meta product feed, you'll find the structure familiar. Rokt intentionally aligns to industry standards for faster onboarding.
A downloadable template is available here: Rokt DPA Product Feed Template
This page covers a product file you connect by URL in the Rokt Catalog app. If you manage your catalog in the Catalog Manager in One Platform, see Catalog requirements instead. The two paths accept different field limits and values.
Catalog overviewCatalog overview への直接リンク
Each row in your feed represents a product or variant. The fields below allow Rokt to display accurate product information, optimize recommendations, match user events (ViewContent, AddToCart, Purchase), and dynamically personalize creatives.
Rokt requires 9 core fields and strongly recommends additional fields for ad performance and data quality.
Required product attributesRequired product attributes への直接リンク
These fields must be present for every product.
| Field | Description | Format and requirements |
|---|---|---|
| id | Unique product identifier (SKU recommended) | ≤48 chars, case-sensitive. Must not change once assigned. Must match Product ID passed in your Rokt events. |
| item_group_id | Groups variants of a single parent product (e.g., different sizes or colors). Same value for all variants in the group, often set to the parent product ID. | Plain text, ≤48 chars. For a product with no variants, enter its own id here. Rokt skips any row where this cell is blank. |
| title | Product name | Plain text, 1–200 chars (≤65 recommended). No HTML, emojis, or promo text. |
| description | Product description | Plain text, ≤9,999 chars. Must differ from title. No HTML, URLs, or promotional text. |
| price | Price with currency | <value> <ISO 4217> (e.g., 29.99 USD). Must match landing page price exactly. |
| link | Product landing page URL | Full URL, must load with HTTP 200, must use your domain. |
| image_link | Primary product image | JPEG/PNG, ≥500×500 (1024×1024 recommended). No borders, overlays, or watermarks. |
| brand | Brand name | ≤100 characters. |
| availability | Stock status | Accepted values: in stock, out of stock. in_stock (with an underscore), preorder, and backorder are read as out of stock. |
Recommended product attributesRecommended product attributes への直接リンク
| Field | Description | Format and notes |
|---|---|---|
| product_type | Merchant-defined category or hierarchy | Plain text, ≤1,044 chars. |
| sale_price | Discounted price | Must be less than price; same format. |
| sale_price_effective_date | Sale date range | ISO 8601 range (start/end). Rokt doesn't apply this range. A sale_price applies whenever it's in the file, so remove it when the sale ends. |
| google_product_category | Google taxonomy code | Numeric ID. |
| custom_label_0–4 | Up to 5 segmentation labels | ≤100 chars each. |
| mobile_link | Mobile-optimized URL | Full URL. |
| additional_image_link | Extra product images | Direct image URLs; multiple allowed. |
| average_review_rating | Avg product rating | Decimal, 1.0–5.0. |
| number_of_ratings | Review count | Integer ≥0. |
Recommended category-specific attributes (retail)Recommended category-specific attributes (retail) への直接リンク
| Field | Description | Format and notes |
|---|---|---|
| color | Product color | ≤128 chars. |
| size | Product size | ≤128 chars. |
| gender | Gender targeting | male, female, unisex. |
| age_group | Intended age group | newborn, infant, toddler, kids, adult. |
| material | Material composition | ≤100 chars (e.g., "100% cotton"). |
| condition | Product condition | new, refurbished, used. |
Feed quality and governanceFeed quality and governance への直接リンク
Rokt automatically validates your feed for:
- Presence of required fields
- Correct formatting and accepted values
- Image accessibility and quality
- Price/availability freshness
- Product ID consistency
- Variant grouping issues
Rows that don't meet the required criteria aren't ingested into Rokt Catalog. If a required column is missing, Rokt rejects the whole file. Column names must match the field names exactly, in lower case and with no extra spaces. The file must not start with a byte-order mark, which Excel adds when you save as CSV UTF-8. Values over a field's length limit can fail to import. You must make any edits in the feed file itself.
Frequently asked questionsFrequently asked questions への直接リンク
Do sale prices and price changes update automatically?
Yes, on the next fetch. By default, Rokt fetches a URL-hosted file about once a day, at least 24 hours after the last successful fetch. A sale_price stays in effect until a fetch no longer finds it in the file.
What if my catalog contains variants?
Use item_group_id to group related products. Each variant must still have its own id, price, availability, and link.
Complete specification tableComplete specification table への直接リンク
For a full, consolidated version of fields as they appear in your CSV template, refer to the Rokt DPA Product Feed Template.