Skip to content

Commit

Permalink
apply suggestions from github actions
Browse files Browse the repository at this point in the history
  • Loading branch information
reithor committed Sep 20, 2024
1 parent f816580 commit 741ad46
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/personalization/enable_personalization.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,12 +162,12 @@ Place the following code snippet in the `<head>` section of your header template
You can verify the import controller of the bundle by calling the local API.
As the API uses token based authorization you first need a valid bearer token.

When you publish a Content Item a bearer token will be created and saved to the ibexa_token db table.
When you publish a content item a bearer token is created and saved to the `ibexa_token` db table.

Additionally a POST request is send to the Personalization Engine, containing the token
and the Rest URL where the Personalization Engine can fetch the changed Content.

The BEARER_TOKEN will be the newest one in `ibexa_token` table having `type=1` and `identifier=update`. The token will by default be valid for 1 day.
The BEARER_TOKEN is the newest one in `ibexa_token` table having `type=1` and `identifier=update`. The token has a default lifetime of one day.

You can use this token to check what is provided to the Personalization Engine:

Expand Down Expand Up @@ -237,13 +237,13 @@ To get recommendations you must first export the item information to the Persona
After you [define item types to be tracked and recommended](#set-up-item-type-tracking),
start the full export.

You need to run the `ibexa:personalization:run-export command per SiteAccesses that you want to use together with Personalization. Please note that you need different customer IDs for different SiteAccesses.
You need to run the `ibexa:personalization:run-export command per SiteAccesses that you want to use together with Personalization. You need different customer IDs for different SiteAccesses.

``` bash
php bin/console ibexa:personalization:run-export
--item-type-identifier-list=<item_type>,<item_type>
--siteaccess=<site_access_name>
--customer-id=<customer_id>
-- =<customer_id>
--license-key=<license_key>
--languages=<language>,<language>
```
Expand Down

0 comments on commit 741ad46

Please sign in to comment.