Daisycon Integration

Publishers in the Daisycon network don't manually curate every product they promote — they build comparison pages, niche shopping guides, and price-alert tools that read directly from the feeds advertisers submit. If your feed is missing, outdated, or incomplete, publishers either can't list your products at all or end up displaying stale prices and out-of-stock items, which erodes the trust that drives affiliate conversions.

A well-maintained feed is effectively the product catalog your entire Daisycon publisher base works from. Keeping titles, prices, stock, and imagery synchronized directly affects how many publishers pick up your catalog and how well those listings convert.

One mechanic worth understanding before you build a feed for Daisycon: product links in your feed should point to the clean, unpacked product URL on your own site, without any affiliate or tracking parameters attached. Daisycon adds its own tracking parameters to that link automatically at the moment a shopper clicks through from a publisher's site — that's what lets Daisycon (and your affiliate reporting) attribute the resulting sale back to the correct publisher.

Submitting deeplinks that already contain tracking parameters, redirects, or session identifiers from your own analytics stack risks breaking that attribution chain, so it's a detail worth checking specifically when you first connect a feed.

Advertisers register a feed URL in the Daisycon advertiser dashboard (feed management typically sits under the account's materials/tools section), and Daisycon's system polls that URL to pull in product data. Based on Daisycon's own tooling and the third-party platforms that build feeds for it, the network is built to read either XML or a delimited CSV/TXT feed (tab-, comma-, or semicolon-separated).

Practical requirements that carry over from how affiliate networks generally consume feeds — and that are echoed across the platforms integrating with Daisycon — are that the feed needs to be hosted at a stable, publicly reachable URL (no login walls) and kept live rather than submitted as a one-off upload.

Daisycon has not published a single, universally quoted field-by-field schema, so treat the list below as the attribute set that feed-management platforms building Daisycon integrations consistently include, rather than a verbatim official specification. In practice it overlaps heavily with the fields used for Google Shopping-style feeds.

If Daisycon or your account manager has provided a specific column-mapping document for your program, follow that over this general list.

1. In Feedance, create a new data source and import your product catalog from your store platform, ERP, or an existing feed.
2. Create a dedicated Daisycon export channel and map your product fields to the attributes Daisycon expects — title, description, price, category, deeplink, image, brand, and stock at minimum.
3. Make sure the deeplink field in your mapping points to the plain product URL on your site, not a URL that already carries UTM or affiliate parameters.
4. Generate the hosted feed URL Feedance produces for that channel, and register it in your Daisycon advertiser dashboard as your product feed source.
5. Set an automatic refresh schedule in Feedance so price, stock, and availability changes propagate to Daisycon without manual re-uploads.

Daisycon has not published a fixed minimum refresh interval, but daily updates are the common baseline used by platforms that sync feeds into the network, since publishers rely on the feed for both price and stock accuracy. Feed-management tools that integrate with Daisycon typically offer sync intervals ranging from every 5–15 minutes up to daily, and it's worth increasing frequency (multiple times a day) around high-volatility periods like sales events or holiday peaks, when prices and stock levels change fastest.

At minimum, treat price and availability as fields that should never be stale by more than a day — publishers promoting an out-of-stock or mispriced item is one of the fastest ways to lose their trust in your feed.

Daisycon has not published a list of specific feed-validation error codes, so the points below are general issues that commonly cause affiliate product feeds to be rejected or under-perform, rather than confirmed Daisycon error text:

1. Deeplinks that already include tracking or session parameters, breaking attribution when Daisycon appends its own.
2. A feed URL that is slow, intermittently unreachable, or blocked for automated/bot-style requests, causing failed or partial fetches.
3. Missing core fields (price, availability, image, or category) on a subset of products, which typically excludes just those items rather than the whole feed.
4. Prices shown excluding VAT when the network or publishers expect VAT-inclusive pricing, creating a mismatch between the feed and checkout.
5. Stock or availability values that lag behind the live store, leading publishers to promote items that are actually sold out.

These are general feed-hygiene recommendations rather than Daisycon-specific requirements:

1. Write distinct, descriptive titles per product (including brand, key variant details like size or color) rather than reusing generic category names — publishers building comparison content depend on this to differentiate listings.
2. Keep category values consistent and specific, since publishers often filter or group your catalog by category when building shopping pages.
3. Populate optional identifiers like EAN/GTIN and MPN where you have them — comparison-shopping publishers use these to match your listing against competitor offers.
4. Automate the feed refresh rather than uploading manually, so price and stock changes reach publishers the same day they happen on your own site.
5. Periodically spot-check a sample of deeplinks to confirm they still resolve to a live product page and haven't picked up tracking parameters from your own site changes.

Does Daisycon require XML specifically? No — Daisycon's tooling and the platforms that integrate with it support both XML and delimited CSV/TXT feeds; XML is the more commonly used format.

Can I reuse the same feed I use for Google Merchant Center? Often yes as a starting point, since the two share many common fields (title, price, availability, image, category), but you should adjust the deeplink field so it points to a clean product URL rather than any UTM- or campaign-tagged link you use elsewhere.

Where do I submit the feed URL once it's ready? In your Daisycon advertiser account, under the section where product feeds/materials are managed — register the hosted URL there rather than uploading a static file.

How do I know if publishers are actually picking up my feed? Check performance and click/conversion reporting inside your Daisycon advertiser dashboard; a feed that publishers aren't using effectively often shows up as flat or declining click volume on affected products.