Add a data source
- Go to Catalogs
- Click Get Started
- Click Add data source
- Make sure you have appropriately prepared your data source before ingestion
- You must have a claimed domain to add a data source
- Input your data source URL
- A data source URL is a link to the location from where Pinterest will be able to fetch your data source
- This URL must begin with http://, https://, ftp://, or sftp://, and include the full filepath, and no credentials in the URL)
- We don't accept compressed files at this time
- Select the file format (CSV, TSV, or XML)
- Select “My data source is password-protected” if your data source requires credentials
- If necessary, input your credentials
- Select the currency
- Click Create Pins
After you click Create Pins, you'll land back at the main Data Source page. Your feed is being processed - wait for a confirmation email from Pinterest for the status of your data source submission.
More about data sources
- Update daily. We ingest your data source once every 24 hours. Make your updated full data source available daily to keep your product details up-to-date. We don't support scheduling or on-demand ingestion.
- Host your data source. Host your own data source on an FTP/SFTP server or with an HTTP/HTTPS direct-download link. This needs to be accessible by a user-agent, and can't require IP or SSH key whitelisting. If you're using a direct download link, there can't be any extra navigation required for Pinterest to access the file. We don't provide data source hosting.
- Max 5 million products. We can process up to 5 million products per account. If your data source has more than 5 million products, we'll process the first 5 million rows.
- One data source per business account.
Data source error messages
We use unique messages to let you know if something went wrong with product Pin creation or if we have a recommendation for you. There are three different message types you can expect.
- File-level error: your entire data source may fail ingestion if your data source has any of the file-level errors listed below.
- Product-level error: if your product has failing errors, it will not be able to create product Pins.
- Product-level alert: products with alerts will still create product Pins, but we recommend you adjust the product data to avoid warnings.
Your entire data source may fail ingestion if your data source has any of the file-level errors listed below. If your product has failing errors, it will not be able to create product Pins. Products with alerts will still create product Pins, but we recommend you adjust the product data to avoid warnings.
Look for the error message below for tips on how to update your data source.
Error code | Error message | Error type | What to do |
---|---|---|---|
100 | Your data source can't be accessed. | File-level failure | Review your data source credentials and filepath. Ensure that your file name hasn’t changed on the location (for ftp/sftp). Ensure that your hosting location isn’t timing out. Ensure that you did not include the username/password in the file URL. |
101 | Your data source uses an unsupported encoding format. | File-level failure | Re-encode your file to UTF-8 or Latin1. |
102 | Your data source contains formatting errors. | File-level failure | Make sure your file is delimited in either comma (double quote-wrapping recommended) or tab form. Make sure there are no additional or missing delimiters in each row. |
103 | Your data source is missing some required column headers. | File-level failure | Make sure you are sending all required column headers. Review the required data source specifications. |
104 | Some image links are formatted incorrectly. | Row-level failure | Make sure your image link begins with http:// or https:// and is a valid URL. |
105 | Some items are missing an item ID in product metadata, so these items will not be published. | Row-level failure | ID is a required field. Make sure you are sending item ID for all rows in your data source. Remove any items with no IDs. |
106 | Some items are missing a title in product metadata, so those items will not be published. | Row-level failure | Title is a required field. Make sure you are sending a product title for all rows in your data source. Remove any items with no titles. |
107 | Some items are missing a description in product metadata, so those items will not be published. | Row-level failure | Description is a required field. Make sure you are sending a description for all rows in your data source. Remove any items with no description. |
108 | Missing required attribute: Google product category – your products are missing Google product category values in the required Google product category attribute. | Row-level failure | Send google_product_category following the right taxonomy. We currently only accept en-US taxonomy. |
109 | Invalid formatting required attribute: Google product category – your products do not include a valid Google product category. | Row-level failure | Make sure you are following the correct taxonomy. We currently only accept en-US taxonomy. |
110 | Some items are missing a link URL in product metadata, so those items will not be published. | Row-level failure | Link is a required field. Make sure you are sending a product landing page. |
111 | Some items are missing an image link URL in product metadata, so those items will not be published. | Row-level failure | Image_link is a required field. Make sure you are sending an image link for your product. |
112 | Some items are missing an availability value in product metadata, so those items will not be published. | Row-level failure | Availability is a required field. Make sure you are sending one of: in stock, out of stock or preorder. |
113 | Some items have price value formatting errors in product metadata, so those items will not be published. | Row-level failure | The Price field must be formatted as 'number' 'currency', e.g. 1.00 USD, 1 USD or 1.00USD. |
114 | Your title for this item is truncated because it contains too many characters. | Row-level warning | We truncate the title if it is longer than 128 characters. To ensure that your title does not get trimmed, please send product titles that are less than 128 characters. |
115 | Your description for this item is truncated because it contains too many characters. | Row-level warning | We truncate the description if it is longer than 500 characters. To ensure that your product description does not get trimmed, please send descriptions that are less than 500 characters. |
116 | Some items are missing a condition value or their condition value is formatted incorrectly, so some products will be published without a condition listed. | Row-level warning | The accepted condition values for your product are: new, used or refurbished. Ensure that you are not sending any other values for the Condition column. |
117 | Some gender values are formatted incorrectly, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | Gender must be one of the following: male, female or unisex. Any other strings will be stripped from your product data and will impact relevancy for your product. |
118 | Some age group values are formatted incorrectly, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | The age_group must be one of the following: newborn, infant, toddler, kids or adult. Any other strings will be stripped from your product data and will impact relevancy for your product. |
119 | Some size type values are formatted incorrectly, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | The size_type must be one of the following: regular, petite, plus, big_and_tall or maternity. Any other strings will be stripped from your product data and will impact relevancy for your product. |
120 | Your data source contains formatting errors for some items. | Row-level failure | Your data source contains formatting errors causing upload failure for one or more lines, which can also affect upload for your entire product feed. Check and correct any formatting errors before your next update to try again. |
121 | Invalid formatting required attribute: link – your product links contain UTM tracking parameters. | Row-level warning | Check the UTM parameters are following our tracking guidelines and set up specifically for Pinterest. |
122 | Some links are formatted incorrectly. | Row-level failure | Make sure your link begins with http:// or https:// and is a valid URL. |
123 | Your product feed contains duplicate items. | Row-level warning | The current row has a warning because the data source already contains an item with the same product ID. Do not send duplicates of your product. |
125 | Some items have sale prices listed that are higher than the original price of the item. | Row-level warning | The Sale price field must be formatted as 'number' 'currency', e.g. 1.00 USD, 1 USD or 1.00USD. Sale price cannot be higher or the same as the Price column. |
126 | Some items only have 1 or 2 levels of Google product categories listed, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | We recommend sending the full specific Google Product Category. More granular categories will help us better understand the product. |
127 | Some Adwords_redirect URLs are duplicates of the link URLs for that item. | Row-level warning | Confirm that the ad_link column is sending the right tracking parameters for Pinterest. We recommend sending organic links in the link column, and any URLs with tracking in ad_link. |
129 | Your data source contains duplicate headers. | File-level warning | Your data source contains duplicate column names. Remove duplicate columns and send unique columns only. We will only accept the first column of the duplicate column if duplicates occur. |
130 | Your tax values for some items are formatted incorrectly. | Row-level warning | Make sure your tax column is following the correct setup. All colons are required, even for blank attributes e.g. US::0.13: |
131 | Your shipping values for some items are formatted incorrectly. | Row-level warning | Make sure your Shipping column is following the correct setup. All colons are required, even for blank attributes e.g. US:::0.00 |
132 | Some items have invalid shipping weights. | Row-level warning | The current line failed validation because the Shipping weight field is not in the following format: '3kg' or '3 kg'. The string must contain a numeric value first then a valid weight unit type (one of 'lb', 'oz' or 'kg'). |
133 | Some items have invalid multi-pack values. | Row-level warning | Multipack value must be numeric. Any other strings will be stripped from your product data. |
134 | Some Adwords_redirect links are formatted incorrectly. | Row-level failure | Make sure your ad_link link begins with http:// or https:// and is a valid URL. |
135 | Some Adwords_redirect links contain too many characters. | Row-level failure | Make sure your ad_link link is shorter than 511 characters and is a valid URL. |
136 | Your image link is formatted incorrectly, so this item will be published without an image. | Row-level warning | Check for any issues with your image link's URL formatting or your hosting site and correct them before your next update. |
137 | Some image links are formatted incorrectly and will not be published with your item. | Row-level warning | We will strip any additional_image_links that are not formatted correctly. Please ensure these are valid URLs. |
138 | Your data source contains too many items, so some items will not be published. | File-level warning | We only accept 5 million rows at the moment. Only the first 5 million products will be processed. Any additional products will be ignored. Send fewer than 5 million products to ensure that all of the products you want to be processed are accepted. |
139 | Your product links don't match the verified domain associated with this account. | File-level failure | Your link URLs must match the verified domain for your account. Make sure you are not sending any redirects or other domains in the Link column of your data source. |
140 | Your merchant domain needs to be claimed. | File-level failure | You must have a verified domain in order to ingest your data source. Verify your domain and try again. |
141 | Some items have invalid adult values. | Row-level failure | If you are including an 'Adult' column and have a value for the column, make sure it is one of: true, false, yes or no. |
142 | Your product link for this item wasn't published because it contains too many characters. | Row-level failure | Check your product link and make sure it is no longer than 511 characters before your next update. |
143 | Your data source couldn't be validated because your .xml file is formatted incorrectly. | File-level failure | Check for any formatting errors in your .xml file (missing end tags, invalid characters, etc.) and correct them before your next update. |
144 | Your expiry date is formatted incorrectly, so this item will be published without an expiry date. | Row-level warning | Make sure your expiry date column entry is formatted numerically, and correct any other formatting before your next update. |
145 | Your availability date is formatted incorrectly, so this item will be published without an availability date. | Row-level warning | Make sure your availability date column entry is formatted numerically, and correct any other formatting before your next update. |
146 | Your sale date is formatted incorrectly, so this item will be published without a sale date. | Row-level warning | Make sure your sale date column entry is formatted numerically, and correct any other formatting before your next update. |
147 | Your weight unit is formatted incorrectly, so this item will be published without a weight unit. | Row-level warning | Make sure your weight unit column entry is formatted as lb, oz or kg, and correct any other formatting before your next update. |
148 | Your bundle column entry is formatted incorrectly, so this item will be published without being bundled with other products. | Row-level warning | Make sure your bundle column entry is formatted as yes, no, true or false, and correct any other formatting before your next update. |
149 | Your updated time column is formatted incorrectly, so this item will be published without an updated time. | Row-level warning | Make sure your updated time column entry is formatted numerically, and correct any other formatting before your next update. |
150 | Your data source couldn't be downloaded due to URL redirect issues. | File-level failure | Check for any issues with your data source URL's formatting or your hosting site and correct them before your next update. Your data source URL may have exceeded 10 redirects, changed protocols during a redirect, or may be completely invalid. |
151 | This item will not be published because price information is required. | Row-level failure | Enter correct price information in the price column before your next update. |
152 | Your data source couldn't be validated because your file doesn't contain the minimum number of lines required for a valid data source. | File-level failure | Make sure your data source contains at least two or more lines (a header line and one or more product lines) before your next update. |
153 | Your custom label is too long, so this item will be published without a custom label. | Row-level warning | Make sure your custom label is no longer than 100 characters before your next update. |
154 | Your product type is too long, so this item will be published without a product type. | Row-level warning | Make sure your product type is no longer than 750 characters before your next update. |
155 | Your catalogue couldn't be validated because there are no products in your Shopify store to ingest. | File-level failure | Check your product listings in your Shopify store and confirm that you have items for sale before your next update. |
156 | Your additional image links exceed the limit for additional images, so this item will be published without some of your images. | Row-level warning | Limit entries in the additional links column to 10 or less. |
157 | Some Google product category values are missing, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | Check your Google product category values and make sure they are formatted with values from the US-EN GPC taxonomy for any items with associated Google product category values before your next update. |
158 | Some Google product category values are formatted incorrectly, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | Check your Google product category values and make sure they are formatted with values from the US-EN GPC taxonomy for any items with associated Google product category values before your next update. |
159 | Some condition values are missing, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | Check your condition values and make sure they are formatted as new, used or refurbished for any items with associated condition values before your next update. |
160 | Some condition values are formatted incorrectly, which may limit visibility in recommendations, search results and shopping experiences. | Row-level warning | Check your condition values and make sure they are formatted as new, used or refurbished for any items with associated condition values before your next update. |
163 | Some availability values were formatted incorrectly and have been automatically corrected. | Row-level warning | Enter availability values for all items or delete items that are missing availability values before your next update. |
164 | Some condition values were formatted incorrectly and have been automatically corrected. | Row-level warning | Enter condition values for all items or delete items that are missing condition values before your next update. Condition values have to be formatted as new, used or refurbished. |
165 | Some gender values were formatted incorrectly and have been automatically corrected. | Row-level warning | Check that your gender value entries are formatted as male, female or unisex before your next update. |
166 | Some age_group values were formatted incorrectly and have been automatically corrected. | Row-level warning | Check that your age_group value entries are formatted as newborn, infant, toddler, kids or adult before your next update. |
167 | Some size_type values were formatted incorrectly and have been automatically corrected. | Row-level warning | Check that your size_type value entries are formatted as regular, petite, plus, big_and_tall or maternity before your next update. |
168 | Some of your utm_source values were formatted incorrectly. Those values have been automatically corrected to `pinterest` in order to ensure accurate UTM attribution. | Row-level warning | Review your utm_source values and make sure they are entered as ‘Pinterest’ to ensure accurate UTM source attribution. |
1001 | Some images can't be found. | Row-level failure | Make sure your image link is a link to an image file and can be downloaded by a user-agent. |
1007 | Some images have unacceptable formats. | Row-level failure | Send valid image URLs with image files in the destination. |
1012 | This item will not be published because the maximum number of items in this group has been exceeded. | Row-level failure | Reduce the number of items listed for this group to 350 or less. |
4028 | Some main images can't be found. | Row-level failure | Check for any issues with your main image's URL formatting or your hosting site before your next update. |
4029 | Some additional images can't be found. | Row-level warning | Check for any issues with your additional images' URL formatting or your hosting site before your next update. |
What's the next step?
Was your data source ingested successfully? It may take a day or so to find out.
- Yes! Great, read our guide to learn how to promote your product groups.
- Nope, it had some errors. That's okay, it may take a few tries to get it right. Use our error message troubleshooting guide to iron out those errors.