IBX-10688: SiteAccess-aware Raptor connector configuration documented in Dev-doc #3101

mnocon · 2026-04-02T09:55:12Z

This screenshot shows the Customer ID - is that the same at the Account number, could someone take both of these information from this single screen? That would simplify the setup a bit

mnocon · 2026-04-02T10:08:46Z

Should we document the non-siteaccess-aware settings?

I mean: https://github.com/ibexa/connector-raptor/blob/main/src/bundle/DependencyInjection/Configuration.php#L21

adriendupuis · 2026-04-02T08:43:14Z

Suggested change

description: Step-by-step configuration procedure of SiteAccess-aware Raptor connector.

description: Step-by-step configuration procedure of SiteAccess-aware Raptor connector.

edition: lts-update

month_change: true

mnocon · 2026-04-02T10:19:46Z

Suggested change

description: Step-by-step configuration procedure of SiteAccess-aware Raptor connector.

description: Step-by-step configuration procedure of the Raptor connector.

mnocon · 2026-04-02T09:58:53Z

Please add a H1 header (#), or change this one

adriendupuis · 2026-04-02T08:44:07Z

Suggested change

- `customer_id` - an identifier used to authenticate requests to the Recommendation Engine. This value is can be found as `Account number` in [Raptor Control Panel](https://controlpanel.raptorsmartadvisor.com/).

- `customer_id` - an identifier used to authenticate requests to the Recommendation Engine. This value can be found as `Account number` in [Raptor Control Panel](https://controlpanel.raptorsmartadvisor.com/).

mnocon · 2026-04-02T09:58:09Z

Suggested change

- `customer_id` - an identifier used to authenticate requests to the Recommendation Engine. This value is can be found as `Account number` in [Raptor Control Panel](https://controlpanel.raptorsmartadvisor.com/).

- `customer_id` - an identifier used to authenticate requests to the Recommendation Engine. This value can be found as `Account number` in [Raptor Control Panel](https://controlpanel.raptorsmartadvisor.com/).

mnocon · 2026-04-02T10:02:53Z

Suggested change

- `tracking_type` - defines how user events are sent to the tracking API. Possible values:

- `tracking_type` - defines how user events are sent to the tracking API. Default value: `client`. Possible values:

Of course an additional question is why client is the default one, if it's a worse alternative to the server side (relates to https://github.com/ibexa/documentation-developer/pull/3101/changes#r3026892943 )

adriendupuis · 2026-04-02T08:51:25Z

A link to #3105 and #3110 functions would be nice.
I think those two PRs should share a common page introducing both functions that could be added to https://doc.ibexa.co/en/5.0/templating/twig_function_reference/twig_function_reference/ and here.

adriendupuis · 2026-04-02T08:54:24Z

About ad blockers, it seems that this is not a side remark but the goal. Maybe:

Suggested change

- `server` - tracking is handled on the backend, with events sent directly to the tracking API. It's not affected by ad blockers.

- `server` - tracking is handled on the backend, with events sent directly to the tracking API, so, it's not affected by ad blockers.

mnocon · 2026-04-02T09:19:16Z

Is it possible to use both types of tracking at the same time, or would that be an overkill? Is there a reason to use client tracking at all, if it can get blocked by ad-blockers, what advantages does it provide?

Would be nice to have somewhere (not necessarily here) this info

mnocon · 2026-04-02T09:06:53Z

Suggested change

- `recommendations_api_url` (optional) - overrides the default Raptor SaaS address, should be left unset unless a custom endpoint is required.

- `recommendations_api_url` (optional) - overrides the default Raptor address, should be left unset unless a custom endpoint is required.

mnocon · 2026-04-02T09:16:10Z

It would be best if this was part of the Raptor help center to which we could just link - this way it would stay up to date with potential UI changes, here we risk that we fail to track Raptor UI changes and update it in time.

Let's discuss moving this part to the Help Center if possible - these sections are short, so it's not critical, but would be nice to keep the boundaries between the products.

mnocon · 2026-04-02T09:17:06Z

Same here - to avoid the risk of this getting outdated, it should be part of the Help Center (official Raptor doc)

adriendupuis · 2026-04-02T09:02:33Z

As this is a new section, maybe have this precious link again:

Suggested change

To find the value for the `recommendations_api_key`, log in to Raptor Control Panel, and look for "API key".

To find the value for the `recommendations_api_key`, log in to [Raptor Control Panel](https://controlpanel.raptorsmartadvisor.com/), and look for "API key".

mnocon · 2026-04-02T09:54:19Z

Suggested change

Click on the **Show API information** and copy the number.

Click on the **Show API information** and copy the value.

adriendupuis · 2026-04-02T08:26:08Z

Suggested change

description: Step-by-step activation procedure of setting up SiteAccess-aware Raptor connector.

page_type: landing_page

description: Step-by-step activation procedure of setting up SiteAccess-aware Raptor connector.

page_type: landing_page

edition: lts-update

month_change: true

mnocon · 2026-04-02T10:05:03Z

Suggested change

# SiteAccess-aware Raptor connector

# Raptor connector

The fact that it's siteaccess-aware is not header-worthy, it's expected - and can be mentioned later.

adriendupuis · 2026-04-02T08:33:45Z

It should be clearer that this an LTS Update. Maybe there:

Suggested change

The SiteAccess-aware [Raptor](https://www.raptorservices.com/) connector provides a seamless integration between [[= product_name =]] and Raptor Recommendation Engine.

The SiteAccess-aware [Raptor](https://www.raptorservices.com/) connector LTS Update provides a seamless integration between [[= product_name =]] and Raptor Recommendation Engine.

mnocon · 2026-04-02T10:05:10Z

Suggested change

The SiteAccess-aware [Raptor](https://www.raptorservices.com/) connector provides a seamless integration between [[= product_name =]] and Raptor Recommendation Engine.

The [Raptor](https://www.raptorservices.com/) connector provides a seamless integration between [[= product_name =]] and Raptor Recommendation Engine.

adriendupuis · 2026-04-02T08:40:51Z

Raptor Connector can be confusing to people knowing that there is already a Raptor connection in Ibexa CDP.

How does it work with ibexa/cdp? Does it need CDP to be set up? What are the scope of each? Do they interact?

Suggested change

Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement.

Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement.

It must not be confused with [Ibexa CDP](cdp_guide.md) based on Raptor. CDP does TODO while Raptor Connector focus on recommandation integration TODO…

adriendupuis · 2026-04-02T08:34:33Z

And/Or there?

Suggested change

Follow a step-by-step procedure that allows you to activate SiteAccess-aware Raptor connector.

Follow a step-by-step procedure that allows you to activate SiteAccess-aware Raptor connector LTS Update.

mnocon · 2026-04-02T10:19:19Z

Suggested change

Follow a step-by-step procedure that allows you to activate SiteAccess-aware Raptor connector.

Follow a step-by-step procedure that allows you to activate the Raptor connector.

mnocon · 2026-04-02T10:16:03Z

Suggested change

Activation includes configuration, adding tracking scripts and events, and using [Page Builder](page_builder_guide.md) blocks.

To configure the Raptor integration. follow a step-by-step procedure that allows you to activate SiteAccess-aware Raptor connector.

Activation includes configuration, adding tracking scripts and events, and using [Page Builder](page_builder_guide.md) blocks.

This sentence feels out of place right now - and a link to the install/configuration doc should be added later.

mnocon · 2026-04-02T10:06:57Z

I'd also add relevant Help Center links here, if you find good ones

mnocon · 2026-04-02T09:14:06Z

What's the reasoning behind this change?

-Original file line number
+Diff line change
@@ Expand Up / @@ -508,6 +508,9 @@ nav: @@
                 - CDP add client-side tracking: cdp/cdp_activation/cdp_add_clientside_tracking.md
             - CDP data export schedule: cdp/cdp_data_export_schedule.md
             - CDP data customization: cdp/cdp_data_customization.md
+            - Integration with Raptor:
+                - Integration with Raptor: cdp/raptor_integration/raptor_connector.md
+                - Connector configuration: cdp/raptor_integration/connector_configuration.md
         - Search:
             - Search: search/search.md
             - Search engines:
@@ Expand Down @@

-Original file line number
+Diff line change
@@ Expand Up / @@ -47,7 +47,8 @@ @@
       <li class="{{ class }}">
         <a href="{{ nav_item.url | url }}" class="md-nav__link level-{{ level }}">
           {{ nav_item.title }}
-          {% if nav_item.meta.month_change %}<span class="pill pill--new">New</span>{% endif %}
+          {% set nav_item_meta = nav_item | attr("meta") %}
+          {% if nav_item_meta is defined and nav_item_meta and nav_item_meta.get("month_change") %}<span class="pill pill--new">New</span>{% endif %}
         </a>
       </li>
     {% endif %}

IBX-10688: SiteAccess-aware Raptor connector configuration documented in Dev-doc #3101

Are you sure you want to change the base?

Uh oh!

IBX-10688: SiteAccess-aware Raptor connector configuration documented in Dev-doc #3101

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

GitHub Actions / vale

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

GitHub Actions / vale

GitHub Actions / vale

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GitHub Actions / vale

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!