Product Attribute Data Is Not Synced To Klevu Indexes

problem attribute data for product records is not showing in klevu indexed data potential causes attribute is not registered with klevu if an attribute is not registered with klevu before data is sent, the request will be considered invalid and the payload will not be processed if this is a standard magento attribute, first of all ensure that the register with klevu setting is enabled in the manage attributes page ( stores > attributes > product ) next, you can check which attributes exist at the klevu side for any integrated api key by visiting the klevu information section ( stores > configuration > klevu > information > indexing > attributes > klevu attributes ) product has not been synced with klevu you can easily check the last sync activity for individual records via the magento products grid (catalog > products) in each product row, under the “select” dropdown in the action column, you will find a “klevu sync info” link clicking this link will show all recorded sync activity for that record across all integrated api keys there are a number of reasons a product may not be picked up for sync which are out of scope of this article if running entity discovery / update and triggering a sync does not send the record, please contact our support team for help product synced but rejected or dropped by klevu indexers if data is being included in the indexing api payload but doesn’t appear in the indexed data in klevu, there may be issues with the data itself, or issues with other products within the same batched payload in the entity sync information screen (shown above), you can see the status of each sync attempt which included this record if sync is not being performed successfully, please enable verbose indexing logging ( stores > configuration > klevu > developer settings > logging > indexing log level ); trigger a sync; and contact our support team with the relevant log file(s) for help product synced successfully but does not contain attribute if product records are being received successfully by klevu’s indexers, you can validate the payload sent to the api by enabling verbose indexing logging ( stores > configuration > klevu > developer settings > logging > indexing log level ); triggering a sync; and checking the resulting indexing log file (at var/log/klevu/{storecode}/klevu {storecode} indexing log) you are looking for debug lines containing the string “chunked payload”, which will contain the request payload in the context if the attribute code is not present in the payload, ensure that the pipeline configuration contains the relevant extraction stage(s) for this attribute the following command in the magento cli will generate a dump of the entire product add / update process in our example, we write the output to a file in the var directory, as pipeline configuration can contain thousands of lines $ bin/magento klevu\ indexing\ configuration dump pipeline klevu product add > var/klevu product add yml if the attribute code is present, please contact our support team for further help, including both the indexing logs and generated pipeline configuration if the attribute code is not present, or only present for a subset of products, ensure that automatic pipeline generation is enabled for this attribute via stores > attributes > product and checking the automatically generate pipeline configuration for setting you should see every product type that should contain this attribute data selected if any are missing, update the field configuration and save the attribute; and then trigger entity update and sync operations, which should now contain the missing attribute when managing attribute configuration, we need to both register the attribute with klevu so that the receiving end expects this data and knows how to process it, as well as including this data in the payload we send across we do not automatically assume you will want to sync attribute data for any product type in order to provide you with as much control over your data synchronisation as possible for example, you may explicitly not want to send data for certain product types (one use case would be excluding configurable parents to avoid potential unwanted data inheritance); alternatively, you may wish to define your own extraction; transformation; and validation stages (as detailed here changing attribute data sent to klevu indexes docid\ dzq7yw9jljr6ll1u pm3u ) if the attribute is still not present in the payload following these changes, please contact our support team for further help, including both the indexing logs and (re)generated pipeline configuration