Dynamic Product Ads
Dynamic Product Ads — Datafeed Onboarding
This guide covers everything you need to integrate your product catalog with Appier Dynamic Product Ads. If you have any questions during setup, please reach out to [email protected].
Overview
Dynamic Product Ads allow Appier to automatically display the most relevant products to each user based on their browsing behavior and preferences. To power this personalization, Appier requires a data feed, which is a structured file containing your product catalog information.
This page explains how to prepare your feed, how to deliver it to Appier, and what to expect during the onboarding process. Once you have reviewed the guide, please refer to the Onboarding Checklist and share it with Appier to kick off the integration.
File Specifications
Supported File Formats
Appier accepts product feeds in the following formats:
CSV
.csv
Recommended for most clients
XML
.xml
Also accepted; must follow standard XML structure
TSV
.tsv
Tab-separated values
RSS
.rss
RSS 2.0 feed format
JSON
.json
Flat JSON array of product objects
File Encoding
Please use UTF-8 encoding for all feed files.
Feed Types
Full Feed
Contains your entire product catalog
Daily
Partial Feed
Contains only updated or newly added products
Hourly or as changes occur
For most clients, Appier recommends starting with a daily full feed. Once the integration is stable, you may switch to a partial feed for more frequent updates.
File Format Examples
CSV Example
XML Example
Field Descriptions
The table below lists all product fields. Fields marked as Mandatory are required for the feed to process correctly.
Important: If your field names differ from Appier's standard field names, please indicate your field name in the "Your Field Name" column and share the mapping with Appier.
id
Mandatory
A unique identifier for each product. Do not change this ID once assigned. Max 32 half-width characters. Only ASCII characters (range 0x21–0x7e) are allowed.
title
Mandatory
The product name. Max 50 full-width or 100 half-width characters. Use unique, descriptive titles for best ad performance.
image_link
Mandatory
URL of the main product image. Minimum 600×600 px recommended. Square format preferred. Provide consistent image sizes across all products.
link
Mandatory (web)
The URL of the product detail page on your website.
ios_url
Mandatory (app)
Deep link URL for iOS, redirecting users directly to the in-app product page. Required if you have an iOS app and want to support deep linking.
android_url
Mandatory (app)
Deep link URL for Android, redirecting users directly to the in-app product page. Required if you have an Android app and want to support deep linking.
price
Mandatory
The original retail price of the product, before any discount.
sale_price
Mandatory
The current selling price of the product, after any discount applied.
availability
Mandatory
Set to in stock if the product is available, or out of stock if it is not.
google_product_category
Mandatory
Product category using hierarchical format. Use > (with spaces) to separate levels. For example: Category_A > Category_B. Multiple non-hierarchical categories can be separated by commas: Category_A > Category_B , Category_X
description
Optional (strongly recommended)
A description of the product. Max 2,500 full-width or 5,000 half-width characters. Avoid using ALL CAPS. Avoid short or repetitive descriptions.
extra_image_link
Optional
Additional product image URLs. Minimum 600px recommended. Supports up to 10 URLs, separated by a vertical bar |. Example: image_link_1|image_link_2|image_link_3
keyword
Optional
Comma-separated list of keywords associated with the product.
Integration Methods
Appier supports three methods for receiving your product feed. Choose the option that best fits your technical setup.
Method A — HTTP/HTTPS Link (Recommended)
Provide a direct download URL to your feed file. This is the simplest method.
Requirements:
The URL must allow direct file download without requiring login or session authentication.
The file should be accessible at a stable, permanent URL.
If your server requires IP allowlisting, please request us to share Appier's server IP.
Supported URL examples:
Method B — FTP Pull (Appier pulls from your FTP server)
If your feed is hosted on an FTP/SFTP server, Appier can pull the file automatically on a scheduled basis.
What to provide to Appier:
FTP server address and port
Username and password (or SSH key)
File path and filename
IP Allowlisting: If your FTP server requires IP restrictions, please whitelist Appier's server IP. Contact us for the IP address.
Method C — FTP Push (You push to Appier's FTP server)
Appier can provide you with credentials to upload your feed directly to our FTP server. This is useful if your system does not support outbound HTTP requests.
What Appier will provide:
FTP server address
Your dedicated account credentials
Target file path
Guidelines:
Please use a fixed filename (e.g.,
products.csv) rather than a date-stamped filename (e.g.,products_20250101.csv). This ensures Appier's system can locate the latest file reliably.Upload the file to the designated path before the scheduled sync time.
Sync Schedule
Appier syncs your datafeed on a configurable schedule. The recommended setup is:
Full Feed
Once daily (e.g., 02:00 AM local time)
Partial Feed
Hourly, or triggered after bulk inventory updates
Appier will work with you to configure the optimal sync schedule during onboarding.
Onboarding Checklist
To get started, please share the following information with Appier before or during your onboarding session. This helps us complete your datafeed integration setup smoothly.
Data source link
The URL or FTP path where your feed file is hosted
Transfer method
HTTP/HTTPS link, FTP Pull, or FTP Push
Refresh frequency
How often you plan to update the feed (e.g., daily, hourly)
Estimated product count
Approximate number of products in your catalog
Authentication requirements
Any credentials, tokens, or IP allowlisting needed to access the feed
Field name mapping
If your field names differ from Appier's standard names, please provide the mapping
Need Help?
If you have any questions or run into issues during integration, please email us at [email protected].
Last updated