- Documentation >
- Recommendations >
- Integration with Raptor >
- Tracking with PHP API
Tracking with PHP API
You can interact directly with the Raptor connector's service using the PHP API for advanced tracking usage.
Advanced usage – direct interaction with the service
EventMapper's method
The recommended method, providing full control over event tracking, is EventMapperInterface::map() method.
It allows to interact directly with the service, supporting advanced use cases not covered by default implementation.
Check the following example:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22 | <php>
use Ibexa\Contracts\ConnectorRaptor\Tracking\EventMapperInterface;
use Ibexa\Contracts\ConnectorRaptor\Tracking\ServerSideTrackingDispatcherInterface;
use Ibexa\Contracts\ConnectorRaptor\Tracking\EventType;
class MyCustomService
{
public function __construct(
private readonly EventMapperInterface $eventMapper,
private ServerSideTrackingDispatcherInterface $trackingDispatcher,
) {}
public function trackProductView(ProductInterface $product, string $url): void
{
// Map product to VisitEventData automatically
$eventData = $this->eventMapper->map(EventType::VISIT, $product);
// Send tracking event
$this->trackingDispatcher->dispatch($eventData);
}
}
</php>
|
Manual EventData creation
Manual creation of EventData allows precise control over the events sent to the service.
It enables to define custom event parameters, track specific user interactions, and tailor data collection to advanced use cases.
Check the following example:
1
2
3
4
5
6
7
8
9
10
11
12
13 | <php>
use Ibexa\Contracts\ConnectorRaptor\Tracking\Event\VisitEventData;
$eventData = new VisitEventData(
productId: $product->getCode(),
productName: $product->getName(),
categoryPath: '25#Electronics;26#Smartphones', // Build manually
currency: 'USD',
itemPrice: '999.99'
);
$this->trackingDispatcher->dispatch($eventData);
</php>
|
For more information, see available events in the tracking event namespace
Example - event subscriber
If you need to track events automatically based on application events, you can use Event Subscriber.
It reacts to specific events in the application and triggers tracking logic without the need to add it manually in templates.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39 | <php>
use Ibexa\Contracts\ConnectorRaptor\Tracking\EventMapperInterface;
use Ibexa\Contracts\ConnectorRaptor\Tracking\ServerSideTrackingDispatcherInterface;
use Ibexa\Contracts\ConnectorRaptor\Tracking\EventType;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
use Symfony\Component\HttpKernel\Event\ResponseEvent;
use Symfony\Component\HttpKernel\KernelEvents;
class ProductViewTrackingSubscriber implements EventSubscriberInterface
{
public function __construct(
private readonly EventMapperInterface $eventMapper,
private ServerSideTrackingDispatcherInterface $trackingDispatcher,
) {}
public static function getSubscribedEvents(): array
{
return [KernelEvents::RESPONSE => ['onResponse', -10]];
}
public function onResponse(ResponseEvent $event): void
{
if (!$event->isMainRequest()) {
return;
}
$request = $event->getRequest();
// Example: track only if request has specific attribute
$product = $request->attributes->get('product');
if (!$product) {
return;
}
$eventData = $this->eventMapper->map(EventType::VISIT, $product);
$this->trackingDispatcher->dispatch($eventData);
}
}
</php>
|