Skip to content

Feature: writing Algolia / Search ObjectID back to Saleor #1718

@JannikZed

Description

@JannikZed

Currently, the Algolia app is handling just one-way sync from Saleor to Algolia. For deep integration between these two systems, like for user event tracking purposes, we need the ObjectId from Algolia oftentimes.
For example: Algolia can dynamically rank items differently based on popularity and other factors, even on the granularity of user level. To make that work, we need extensive user tracking on several places. Shop systems are often build on a combination of Saleor directly fetching and fetching from Algolia. This mixture makes it sometimes difficult in the event tracking, as you need to have the Algolia ObjectID available on every event. Having the Algolia objectId in the metadata of an item would be really handy, as this would allow us to query for it in the storefront.

This idea should be easy to implement, with not many side-effects, as every webhook update shows us, if we have a metadata entry for AlgoliaObjectId already there and just update it, if it is not there or different to the one we get returned from Algolia.

This change would allow us later also to add an optional new feature, that would send all purchase (order create) event to the Algolia recommend API, to allow server-side event tracking.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions