The Fredhopper Discovery platform.
Merchandising Studio
The front-end application used for managing your FHR integration.
The analytics component of the FHR platform.
Reporting Dashboard
The front-end application used for viewing the analytics provided by Insights.
The Experience Orchestrator platform.


Navigation page
A page reached via the navigation on your side, such as opening a category.
Search results page
A page with search results reached via searching on your site.
Product detail page
A page with details for a concrete product.
Lister page
A catch-all term for navigation/search results pages, i.e. a non-product detail page.
Your basket overview/checkout page.
A property used for navigation/filtering such as color.


A verb explaining the action a user performed on your site, such as: click, view etc.
Generic actions
A list of actions available by default necessary for proper tracking with our services.
Custom actions
A list of actions configured specifically for you to serve a special use case.
The target of the action such as a page, product, facet etc.
An object representing an action a shopper made on a target with all accompanying details.
A synonym for activity.


The shopper accessing your website.
User journey
A chain of actions a user performs in one visit on your webite.
An ID representing the user in our system for tracking user journeys.
session id
The default ID necessary for tracking activites. Corresponds to a user and a device.
anonymous id
An anonymous ID such as a session id.
Logged-in (known) ID
A known ID for identifying the user between journeys corresponding to an internal ID in your system, such as an ecommerce id.
Identity repository
A representation of storage for an identity type in our system.
Identity slug
An identifier/name for an identity, such as "sessionId" for a session id.

Tracker Key

A logically separated environment to be tracked i.e. a version of your website for a particular country/region
Tracker key
A unique identifier provided to you by Attraqt which corresponds to a single environment.

A/B Tests

A/B test
The entity representing all information concerning a test with two or multiple versions of a single page.
A version of a page linked to a particular A/B test.
Weight (of a variant)
The percentage of users which will be assigned to that variant.

Items API Glossary

Full (catalog) update
A full update contains the full catalog of the client. The full update is uploaded by the client and a version is assigned to it. The client may then trigger processing of this catalog version on a given environment. The client may experience this as a delete operation or cleanup of their environment and a fresh setup available with the newly uploaded catalog. A full update may supply new structural attributes compared to a previous version of a catalog, and in the data this may trigger complete reconfiguration of downstream services such as search.
Incremental (catalog) update
An incremental contains a small update to the client s catalog. The method can vary: streaming, mini-batches, a zip. The INC is always done on top of an existing FULL state or baseline, which means any structural attributes and data stay more stable, compared to how a Full update may impact the system services.
Data Version
A version is a generated or a given Id for stored data. Autogenerated versions are returned to client e.g. when the upload finishes. Clients may sometimes be able to specify under which version Id the data should be stored for purposes of grouping streaming or incremental data together for later reference in some downstream process.
Data feed
A data enrichment is data which needs to be included together with the catalog during DSP ETL processing. Enrichments are also named feeds to highlight the possibility of various sources of data not necessarily the client: data that is not catalog, or is seen as INC, or coming from partners, or coming from other places than the client itself, or coming separately from the client but not with the main catalog.
Data workflows
A data workflow is a business operation applied on client accounts and/or environments. E.g. the client wants to use git-similar workflows: branch off one environment, work on this data+config branch, then when ready schedule a merge on the live environment branch.
Data Items
Data items include not only products but also content.
A rather technical person in Attraqt who helps the customer integrate against APIs. They are our technical specialist in contact with the client.
Streaming API
Capability to ingest parallel streams of data at high rate, scalable. Capability to ingest granular updates, e.g., for product items - single attribute value update on a single product. Capability to timestamp for consistency recovery.
Batch of updates
Capability to transfer item catalog updates batched together for the purpose of balancing responsiveness with cost of network.
Capability to group together several products by a similarity. Categories typically have hierarchical relation among each other.
Product hierarchy
Capability to categorize products based on hierarchical decomposition. For example, some products can be "electronics" with further categorization in "computer" and "camera". where all cameras belong to electronics as well.
Last modified 21d ago