Dialogtrail Integration

Dialogtrail's product guides and recommendations are only as good as the data behind them. A feed that is complete, accurate, and kept up to date lets Dialogtrail's guides reliably show in-stock items, current prices, and the right images, and lets store teams build richer guides using extra attributes pulled straight from the feed instead of re-entering product details manually.

Feedance can generate and maintain a Dialogtrail-compatible feed from your existing product data, so updates made in your shop or PIM propagate through automatically instead of requiring a manual re-export every time your catalog changes.

Dialogtrail's own documentation describes two feed types that work together. A full feed contains the complete product dataset (all fields, all products) and is expected less frequently — the first feed uploaded for an account must be a full feed. A partial feed contains only a subset of attributes that change often, such as price or availability, and can be sent more frequently.

The two are linked by identifiers: every product in a partial feed must use the same id (and group_id, where used) as the matching product in the full feed, or Dialogtrail cannot reconcile the update against the right product. The same id-matching rule applies to secondary-language feeds, which should contain translated values only, not structural changes.

According to Dialogtrail's documentation, the platform accepts product feeds in several formats:

1. JSON (a product array)
2. NDJSON / JSONL (newline-delimited JSON)
3. XML (RSS or Atom style)
4. CSV (with common separator characters)

Feedance can export your catalog into any of these formats, which gives flexibility if you later change how the feed is delivered or need to match a specific structure Dialogtrail's importer expects.

Dialogtrail documents a small set of required fields plus several commonly used optional ones. Field names can be renamed or remapped during import, and the documentation notes it is generally better to include as much additional attribute data as possible, since extra fields become usable when building product guides.

Beyond these, any other attribute present in your feed (color, size, material, etc.) can be imported and used when building product guides.

Dialogtrail's public documentation does not publish the exact delivery mechanism (hosted feed URL, manual upload, or API) it expects from every merchant, so treat the steps below as the general Feedance pattern rather than a confirmed Dialogtrail-specific wizard, and confirm the delivery method with Dialogtrail support during setup:

1. In Feedance, create a new feed export and map your product data to Dialogtrail's required and optional fields (id, name, image_link, link, price, plus any attributes you want available in your product guides).
2. Choose an output format Dialogtrail accepts — JSON, NDJSON, XML, or CSV.
3. Generate the feed and confirm with Dialogtrail whether they will pull it from a hosted URL Feedance provides or whether it needs to be submitted another way.
4. Upload or register the first feed as a full feed, since Dialogtrail requires the initial submission to contain the complete catalog.
5. If you plan to push frequent price/availability updates, set up a second, partial feed export using the same id/group_id values as the full feed.

Dialogtrail's documentation frames update frequency around the full-feed/partial-feed split rather than a fixed schedule: full feeds (the entire catalog) are expected to change less often, while partial feeds carrying volatile fields like price and stock are meant to be sent more frequently. Dialogtrail does not publish a specific numeric cadence (e.g. hourly or daily) in its public docs, so agree on a refresh schedule with Dialogtrail support and set Feedance's export schedule to match — daily for a full feed and a shorter interval for partial price/availability updates is a reasonable general starting point.

Dialogtrail's formatting guide calls out specific rules that, if broken, will cause import problems rather than a clean feed:

1. Duplicate id values across products — the documentation states two products cannot share the same id.
2. Prices formatted with a comma decimal separator or thousands separators (e.g. "1.999,99") instead of a plain dot (e.g. "1999.99").
3. Mixed units or formats within the same attribute (e.g. shoe sizes and shirt sizes in one "size" field) instead of separate, consistently formatted fields.
4. Partial or secondary-language feed rows whose id (and group_id) don't match the corresponding row in the full feed, breaking the link between updates.

Dialogtrail's public documentation does not list verbatim error messages shown in its dashboard, so if you see an import failure not covered above, check with Dialogtrail support for the specific cause.

General best practices for a Dialogtrail feed, based on the platform's own guidance to include rich attribute data:

1. Include more attributes than the minimum required set — Dialogtrail's docs note that extra fields (color, material, use case, etc.) become usable when building product guides and advisor questions.
2. Keep each attribute single-purpose and consistently formatted (one field per unit/category) rather than mixing value types in one column.
3. Use group_id consistently across variants so guides can present a single product with size/color options instead of duplicate listings.
4. Validate your full feed against Dialogtrail's required fields before switching to frequent partial-feed updates, since partial feeds depend on ids already established by the full feed.

Is Dialogtrail a Dutch company? No. Public company records place Dialogtrail AB in Gothenburg, Sweden. It was acquired by the chatbot company Hello Ebbot in 2022; the Dialogtrail product and documentation site continue to operate under the Dialogtrail name.

Is Dialogtrail a chatbot tool or a product feed platform? Both, depending on the era of information you find: older company profiles describe an early Messenger-based conversational commerce product, while its current public documentation describes a guided-selling / product-advice platform driven by a structured product feed.

What feed formats does Dialogtrail accept? JSON, NDJSON/JSONL, XML (RSS/Atom), and CSV, per its official documentation.

Do I need every optional field? No — only id, name, image_link, link, and price are documented as required. Optional fields like group_id, description, sale_price, and brand, plus any custom attributes, are recommended but not mandatory.

How do I confirm the exact delivery method and update schedule? These details are not published in Dialogtrail's public docs, so confirm them directly with Dialogtrail support when setting up your integration.