PBLISH/Docs Open App

Why Column Mapping Matters

Every major advertising platform has its own naming convention for product attributes. The same value (for example, the product image URL) is called image_link on Facebook, sku_link on TikTok, and something else on other platforms. Without PBLISH, you would need a separate, correctly named spreadsheet for each network you target.

PBLISH solves this with a universal mapping layer. You describe what each column means (for example, image URL or price). PBLISH then maps those fields to each platform's expected names on every generation run.

One mapping, all platforms
You perform column mapping once per feed. After that, every catalog you create from that feed, whether for Facebook, TikTok, Instagram, Snapchat, or Google Ads, automatically receives the correctly named and formatted attributes. No repeated work.

The Mapping Interface

The Column Mapping step (Step 4 of the feed creation wizard) presents a two-panel interface. The left panel shows all the columns detected in your source data. For each source column, you select the corresponding PBLISH universal field from a dropdown. The right panel shows any columns you have chosen to exclude. At the bottom, the Required Items section shows exactly which fields each of your selected platforms requires and which are optional.

Column mapping interface showing source columns mapped to PBLISH fields
The Column Mapping interface: source columns on the left, PBLISH universal field selection on the right. The Required Items section at the bottom shows per-platform requirements.

Platform Attribute Reference

The table below shows how PBLISH's universal field names map to the platform-specific column names that each social network expects in the catalog feed. This translation happens automatically. You do not need to memorize these platform-specific names.

PBLISH FieldFacebookTikTokInstagramDescription
ididsku_ididUnique product identifier
titletitletitletitleProduct name or title
image_urlimage_linksku_linkimage_linkURL to the main product image
pricepricepricepriceCurrent product price
descriptiondescriptiondescriptiondescriptionProduct description text
linklinkurllinkProduct page URL
brandbrandbrandbrandBrand or manufacturer name
availabilityavailabilityavailabilityavailabilityin_stock or out_of_stock
categorygoogle_product_categoryproduct_categorygoogle_product_categoryProduct category classification
Required vs. Optional columns
Each platform defines a set of required columns (without which the catalog feed will be rejected) and optional columns (which enhance the catalog but are not mandatory). The Required Items section in the mapping interface shows this breakdown for your specific platform selection.

Required Columns by Platform

The following table summarizes the minimum required columns for each supported platform. Ensure all required fields are mapped before saving your feed.

PlatformRequired FieldsOptional (Recommended)
FacebookID, Title, Price, ImageEmail, Phone, Website, Link, Description
TikTokID, Title, Price, ImageEmail, Phone, Website, Link, Description
InstagramID, Title, Price, Image, LinkDescription, Brand, Category
SnapchatID, Title, Price, Image, LinkDescription, Brand, Availability
Google AdsID, Title, Price, Image, Link, AvailabilityDescription, Brand, Category, GTIN

Editing an Existing Mapping

You can update the column mapping of an existing feed at any time by clicking the edit icon on the feed row in the Feeds list. Changes take effect on the next scheduled generation cycle. Every catalog that uses that feed picks up the updated mapping automatically.

Mapping changes affect all catalogs
Because one feed can power multiple catalogs, any change to the column mapping will affect every catalog built from that feed. Review your changes carefully before saving, especially in production environments.

Common Mapping Issues

Missing required column error
If a required column for a platform is not mapped, the catalog generation will fail with a validation error. Check the Required Items section in the mapping interface and ensure all required fields have a source column assigned.
Products showing wrong images
This usually means the image URL column is mapped to the wrong PBLISH field. Verify that your image URL column is mapped to the image_url field, not to a description or link field.
Column not appearing in the mapping interface
PBLISH reads column headers from the first row of your sheet. If a column is missing, check that the header is in row 1 (not row 2 or below), that there are no merged cells in the header row, and that the column is not empty.