diff --git a/docs/api/php_api/php_api_reference/classes/Ibexa-Contracts-ConnectorRaptor-Tracking-EventMapperInterface.html b/docs/api/php_api/php_api_reference/classes/Ibexa-Contracts-ConnectorRaptor-Tracking-EventMapperInterface.html new file mode 100644 index 0000000000..9d7f16df04 --- /dev/null +++ b/docs/api/php_api/php_api_reference/classes/Ibexa-Contracts-ConnectorRaptor-Tracking-EventMapperInterface.html @@ -0,0 +1,420 @@ + + + + + EventMapperInterface | PHP API Reference (Ibexa Documentation) + + + + + + + + + + + + + + + + +
Copied!
+ + + +
+ +
+ +
+
+
+ + + + + + + + +
+
+
+ + + +
+
+ + +
+
+

+ EventMapperInterface

+ +
+ EventMapperInterface.php + : + 17 + +
+
Interface
+ +
+

Maps domain objects to tracking event data using registered strategies.

+ + + + + + + + + + + + + +

+ Methods +

+ +
+

+ publicmap() + +

+
+ EventMapperInterface.php + : + 24 + +
+
+ +
+ + + + + + + +
+
+
+
+ 		+
+ 
public map(EventType $eventType, mixed $data[, array<string, mixed> $context = [] ]) : EventDataInterface
+
+
+
+
+
+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDefault valueDescription
+ $eventType + + EventType + + - + + - +
+ $data + + mixed + + - + + - +
+ $context + + array<string, mixed> + + [] + + - +
+

Return values

+

EventDataInterface

+ +
+ Tags + + +
+
+
+ Throws +
+
+ InvalidArgumentException + +
+
+ +
+
+
+ +
+
+
+ +
+
+
+
+
+
+ + + + + + + + + + + diff --git a/docs/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking-event.html b/docs/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking-event.html new file mode 100644 index 0000000000..2fefef146f --- /dev/null +++ b/docs/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking-event.html @@ -0,0 +1,325 @@ + + + + + Event | PHP API Reference (Ibexa Documentation) + + + + + + + + + + + + + + +
Copied!
+ + + +
+ +
+ +
+
+
+ + + + + + + + +
+
+
+ + + +
+
+ + +
+
+

+ Event +

+ +
+ + + + +

+ Interfaces, classes, traits, and enums +

+ + +
+
+
+ +
+
+
+ +
+
+
+
+
+
+ + + + + + + + + + + diff --git a/docs/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking.html b/docs/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking.html new file mode 100644 index 0000000000..7ff734605e --- /dev/null +++ b/docs/api/php_api/php_api_reference/namespaces/ibexa-contracts-connectorraptor-tracking.html @@ -0,0 +1,355 @@ + + + + + Tracking | PHP API Reference (Ibexa Documentation) + + + + + + + + + + + + + + +
Copied!
+ + + +
+ +
+ +
+
+
+ + + + + + + + +
+
+
+ + + +
+
+ + +
+
+

+ Tracking +

+ +
+ + +

+ Namespaces +

+ + + +

+ Interfaces, classes, traits, and enums +

+ + +
+
+
+ +
+
+
+ +
+
+
+
+
+
+ + + + + + + + + + + diff --git a/docs/recommendations/raptor_integration/raptor_connector_guide.md b/docs/recommendations/raptor_integration/raptor_connector_guide.md index efab81153c..d838ca78ff 100644 --- a/docs/recommendations/raptor_integration/raptor_connector_guide.md +++ b/docs/recommendations/raptor_integration/raptor_connector_guide.md @@ -32,7 +32,7 @@ Recommendation blocks provided in Page Builder, are available in [[= product_nam ## How does Raptor tracking work -To start [tracking]((https://content.raptorservices.com/help-center/introduction-to-tracking-documentation)) user interactions, the tracking script needs to be added to the website’s layout. +To start [tracking](https://content.raptorservices.com/help-center/introduction-to-tracking-documentation) user interactions, the tracking script needs to be added to the website’s layout. Tracking can be set up either on the client-side or server-side, depending on how you want to capture and process the events. The tracking works differently depending on the mode you choose. diff --git a/docs/templating/twig_function_reference/recommendations_twig_functions.md b/docs/templating/twig_function_reference/recommendations_twig_functions.md index 37f7c4c850..410913ac29 100644 --- a/docs/templating/twig_function_reference/recommendations_twig_functions.md +++ b/docs/templating/twig_function_reference/recommendations_twig_functions.md @@ -69,7 +69,7 @@ ibexa_tracking_track_event( ``` - **eventType** - type: string, defines the type of tracking event to be sent, for example, `visit`, `contentvisit`, `buy`, `basket`, `itemclick` -- **data** (optional) - type: mixed, accepts the primary object associated with the event, such as a Product or Content, can be null if not required. For more information, check [tracking event examples](tracking_php_api.md#tracking-events). +- **data** (optional) - type: mixed, accepts the primary object associated with the event, such as a Product or Content, can be null if not required. For more information, check [tracking event examples](#tracking-events). - **context** (optional)- type: array, additional event data, such as quantity, basket details, or custom parameters. For more information, see [example usage](#context-parameter-example-usage). - **template** (optional) - type: string, path to a custom Twig template used to render the tracking event, allows overriding the default tracking output @@ -150,7 +150,7 @@ In this case, `context` parameter allows to override the product category by pas {% endblock %} ``` -For another example of `context` parameter usage, see [Basket event](tracking_php_api.md#basket-event). +For another example of `context` parameter usage, see [Basket event](#basket-event). ### Custom Templates