Segmentar Integração

Segmentify's own documentation is explicit that behavioural tracking alone is not enough: it also needs a product feed to know details that only the merchant's systems hold, such as current price, stock level and promotional badges. Segmentify's FAQ states that updated information is highly important, especially for product stocks, prices and product badges, because a recommendation engine that suggests an out-of-stock product, or shows the wrong price, damages trust and conversion rather than helping it.

A properly connected feed also supports Segmentify's other personalised channels beyond on-site recommendation widgets, including personalised search results and product-based email and push campaigns, so the accuracy of the catalogue affects more than just the recommendations shown on product pages.

Segmentify's FAQ states that the Google Merchant Center standard format is its preferred format for the product feed, supplied as an XML file. If a merchant does not already have a product feed in this format, Segmentify notes that its own team can build a custom integration, but says this would take up to two days of additional development -- a delay Feedance's automated feed generation is designed to avoid, since it can produce a compatible feed directly from a store connection or existing product data.

Segmentify's developer documentation also describes a complementary, event-based integration: a JavaScript SDK (or iOS/Android SDKs for apps) that reports live page views, product views and basket activity as shoppers browse. According to Segmentify, certain product attributes can be sent either through this JS integration or through a dedicated params node inside the XML feed, so the catalogue feed and the on-site tracking script work together rather than as alternatives.

Segmentify's own FAQ, in the section it calls "XML tags definition," lists the specific tags it expects in the product catalogue file. The table below reproduces that list. Segmentify's public documentation does not label most of these as strictly required or optional -- the only two tags it explicitly marks as optional in its own example are sizes and colors. Treat the rest as the fields Segmentify itself documents for the feed, even where their necessity is not spelled out field by field.

Segmentify's public documentation does not publish a character-limit or strict data-type specification for these fields (for example, maximum title length or decimal precision on price). Where that level of detail matters for a catalogue, Segmentify recommends coordinating directly with its integration team.

Feedance handles the feed-building side of this connection so a merchant does not need to hand-format an XML file. Connecting Segmentify through Feedance follows the same general pattern as Feedance's other integrations:

1. Add a product data source in Feedance -- a store platform connection or an existing product file -- so Feedance can read the catalogue.
2. Feedance maps the product data onto the fields Segmentify's own documentation expects (productid, title, URL, image, price, currency, categories, inStock, and the optional attributes above), and generates a hosted feed URL in the Google Merchant Center-style XML format Segmentify's FAQ says it prefers.
3. Set an update schedule in Feedance so the hosted feed, and in particular price and stock, stays current, then share the feed URL with the Segmentify integration contact so it can be connected on Segmentify's side.

Segmentify separately requires its JavaScript (or mobile) SDK to be installed on the site for behavioural tracking -- the feed and the tracking script are complementary, not substitutes for one another.

Segmentify does not publish a fixed required update frequency for the product feed. What its own FAQ does say is that updated information is highly important, especially for product stocks, prices and product badges -- meaning the practical risk of an infrequently updated feed is that Segmentify recommends a product that is already sold out, or displays a price that no longer matches the site, which Segmentify explicitly treats as an error.

Given that guidance, and standard e-commerce feed practice, refreshing the feed at least daily, and more frequently if stock or pricing changes intraday, is a reasonable general target. Feedance can schedule automatic refreshes so the feed stays aligned with the live catalogue without manual re-uploading.

Segmentify's own FAQ calls out a small number of specific, documented feed problems:

1. Price mismatch. Segmentify states the price in the feed and the price on the website must be exactly the same, and gives its own example: a website price of "15.00" against a feed price of "14.99" is not correct. Any discrepancy, even a small one, is treated as an error.
2. Inconsistent stock reporting. Segmentify accepts either a stock count or a stock status and says one is enough -- sending neither, or sending conflicting values across the two, is the underlying issue this guidance is meant to prevent.
3. Non-standard category formatting. Segmentify's documentation recommends separating category levels with ">" (e.g. "Woman > Jeans"); category strings that do not follow a consistent hierarchy are harder for its recommendation logic to use.

Beyond these documented points, Segmentify does not publish a broader public list of feed error codes or validation messages. As general good practice, it is still worth checking for the usual feed-hygiene issues that affect any recommendation or personalisation feed, such as missing product images, dead product URLs, and duplicate product IDs, even though these are not specifically called out in Segmentify's own materials.

The following are general feed-optimisation practices worth following for a Segmentify feed, based on standard e-commerce feed management rather than Segmentify-specific documentation:

1. Keep price and stock fields perfectly in sync with what is live on the site -- Segmentify treats even small price discrepancies as an error.
2. Use a consistent, well-structured category hierarchy with the ">" separator Segmentify's documentation recommends, rather than flat or inconsistent category labels.
3. Fill in optional attributes like brand, gender, sizes and colours where available -- richer attribute data gives a personalisation engine more signals to match products to shoppers.
4. Make sure every product has a working image URL and a canonical product URL, since broken links or missing images undermine any recommendation widget regardless of platform.
5. Refresh the feed on a schedule that matches how often prices and stock actually change, rather than leaving it static.

What feed format does Segmentify need?
Segmentify's own FAQ states it prefers the Google Merchant Center standard XML format for the product catalogue.

What if I don't already have a product feed?
Segmentify says its team can build a custom integration, though this can take up to two days. Feedance avoids that wait by generating a compatible feed directly from a store connection or existing product data.

Does the price in my feed have to match my website exactly?
Yes. Segmentify's documentation is explicit that any mismatch, even a one-cent difference in its own example, is treated as an error.

Do I need to send both a stock count and a stock status?
No. Segmentify's FAQ says either one is sufficient.

Can I send custom product attributes that aren't in the standard field list?
Yes -- Segmentify's documentation describes a params node in the XML feed for custom attributes, as an alternative to sending them through the JavaScript integration.

How often should I update my Segmentify feed?
Segmentify does not publish a fixed required cadence, but its own guidance stresses that stock, price and badge data must stay current. Daily or more frequent updates are a reasonable general target, and Feedance can automate this on a schedule.