url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment/Recurring_Payments#checkoutcontroller.php | CheckoutController.php
public function paymentAction(Request $request): Response
{
$factory = \Pimcore\Bundle\EcommerceFrameworkBundle\Factory::getInstance();
$checkoutManager = $factory->getCheckoutManager($this->cart);
$user = $this->getUser();
// open payment or submit recurring payment
... | CheckoutController.php | [
-0.20961272716522217,
-0.25539639592170715,
-0.21604979038238525,
0.1083059161901474,
0.25634050369262695,
-0.3222557306289673,
-0.03433043882250786,
0.2556443214416504,
-0.21878744661808014,
0.20720036327838898,
0.010368679650127888,
0.2588939964771271,
0.2905644178390503,
0.2295922040939... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment/Recurring_Payments#payment.html.php | payment.html.php
?>
<form method="post" action="{{ pimcore_url({action: 'confirm'}, 'checkout', true) }}">
{% if sourceOrders is not empty %}
<h4>{{ 'checkout.use-recurring-payment'|trans }}</h4>
{% for paymentMethod in paymentMethods %}
{% if ... | payment.html.php | [
-0.17675870656967163,
-0.350945383310318,
-0.22531282901763916,
0.01807303912937641,
0.1597261279821396,
-0.3590776026248932,
-0.06300870329141617,
0.1157674565911293,
-0.22653324902057648,
0.2736651301383972,
0.06582244485616684,
0.2329821139574051,
0.3007194399833679,
0.40964585542678833... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment/Recurring_Payments#ecommerce.yaml | ecommerce.yaml
payment_manager:
providers:
qpay:
profiles:
sandbox:
secret: 'CHCSH7UGHVVX2P7EHDHSY4T2S4CGYK4QBE4M5YUUG2ND5BEZWNRZW5EJYVJQ'
customer: 'D200411'
toolkit_password: 'XXXXXXX' # necessary for recurPayment operation
optional_payment_p... | ecommerce.yaml | [
0.055304303765296936,
-0.34960082173347473,
-0.1440303474664688,
-0.06438323855400085,
0.4633118808269501,
-0.00029284044285304844,
0.13930848240852356,
0.0353650227189064,
-0.11042230576276779,
0.1855389028787613,
0.19796356558799744,
0.3366948962211609,
0.30106398463249207,
0.53787839412... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment#payment-manager | Payment Manager
The Payment Manager is responsible for all aspects concerning payment. The main aspect is the implementation
of different Payment Provider to integrate them into the framework. | Payment Manager | [
0.303640753030777,
-0.08120577782392502,
-0.21910792589187622,
0.10663879662752151,
0.27328377962112427,
0.2864247262477875,
0.018443014472723007,
-0.2183404266834259,
-0.2642452120780945,
0.1799493134021759,
0.0899769738316536,
0.3487623631954193,
0.2398536503314972,
0.02584376372396946,
... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment#basic-workflow | Basic workflow
[SHOP] Init payment provider ($payment->initPayment()).
[SHOP] User click pay button and is redirected to the payment provider page.
[PAYMENT PROVIDER] User fill up payment information and is redirected back to the shop.
[SHOP] Check if the payment is authorised ($payment->handleResponse()). At th... | Basic workflow | [
-0.1175411120057106,
-0.22267304360866547,
-0.11220881342887878,
-0.09478562325239182,
-0.048474155366420746,
-0.12807868421077728,
-0.009162435308098793,
-0.042988371104002,
0.05742587149143219,
0.15717117488384247,
0.19309072196483612,
0.36937105655670166,
0.4272211194038391,
0.408160150... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment#configuration | Configuration
Configuration of Payment Manager takes place in the pimcore_ecommerce_config.payment_manager config section:
pimcore_ecommerce_config:
payment_manager:
# service ID of payment manager implementation - following value is default value an can be omitted
payment_manager_id: Pimcore\Bundle... | Configuration | [
-0.2014421820640564,
0.054983627051115036,
-0.1612374186515808,
-0.06733142584562302,
0.32928788661956787,
-0.056953832507133484,
0.3168441653251648,
-0.11350847035646439,
-0.22007417678833008,
0.37416452169418335,
-0.09443936496973038,
0.3844357132911682,
0.3475753664970398,
0.40407174825... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment#payment-providers | Payment Providers
Following Payment Providers are available as a dedicated bundle to be integrated into the E-commerce framework:
Datatrans
PayPalSmartButton
Klarna
OGone
MPay24
PayU
Unzer (former Heidelpay)
Hobex
| Payment Providers | [
0.14856331050395966,
-0.2090834230184555,
-0.22168496251106262,
-0.05529056489467621,
0.45794403553009033,
-0.09458930790424347,
0.30280980467796326,
-0.10023678094148636,
0.08323439210653305,
-0.03341590613126755,
-0.06653426587581635,
0.24040184915065765,
0.4410749673843384,
0.6458852887... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment#third-party-payment-provider-integrations | Third-party Payment Provider Integrations
BS PAYONE
| Third-party Payment Provider Integrations | [
0.005719139240682125,
-0.2167021781206131,
-0.2467198520898819,
0.04801454395055771,
0.1441388875246048,
-0.08265210688114166,
0.15003767609596252,
-0.1647254377603531,
0.1318853497505188,
0.175121009349823,
-0.028918199241161346,
0.35374945402145386,
0.31868383288383484,
0.786803901195526... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Payment#further-payment-aspects | Further Payment Aspects
Recurring Payments
| Further Payment Aspects | [
0.0017682734178379178,
-0.30342182517051697,
-0.3317888081073761,
0.12735480070114136,
0.13571612536907196,
-0.09804452210664749,
-0.0957883968949318,
-0.053906600922346115,
-0.12458286434412003,
0.16403824090957642,
0.17383794486522675,
0.23327811062335968,
0.046464256942272186,
0.4619434... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#working-with-order-lists | Working with Order Lists
The Order List are a one stop API for filtering and listing order objects. Of course default Pimcore object lists also
can be used for listing order objects. But Order Lists provide additional functionality in terms of predefined filters etc. | Working with Order Lists | [
0.09248863160610199,
-0.23498262465000153,
-0.2922159433364868,
-0.12541386485099792,
-0.0240242350846529,
-0.3366754353046417,
-0.010122548788785934,
-0.1600092649459839,
0.05229899659752846,
0.08550886064767838,
-0.3082849979400635,
0.20073702931404114,
0.0029414549935609102,
0.229822784... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#basic---get-newest-orders | Basic - Get Newest Orders
<?php
// create new order list
$orderManager = Factory::getInstance()->getOrderManager();
$orderList = $orderManager->createOrderList();
// get the newest 10 orders
$orderList->setOrder( 'order.orderDate desc' );
$orderList->setLimit( 10, 0 );
// iterate
/** @var \Pimcore\Bun... | Basic - Get Newest Orders | [
-0.17802655696868896,
-0.3993169069290161,
-0.32826751470565796,
0.23524221777915955,
-0.20260649919509888,
-0.11024826765060425,
-0.0710098147392273,
0.16315455734729767,
-0.06233614310622215,
0.2120048552751541,
-0.1953551173210144,
0.13083390891551971,
0.02419682778418064,
-0.0292567871... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#basic---using-filter | Basic - Using Filter
<?php
// create new order list
$orderManager = Factory::getInstance()->getOrderManager();
$orderList = $orderManager->createOrderList();
// create date time filter
$filterDate = new \Pimcore\Bundle\EcommerceFrameworkBundle\OrderManager\Order\Listing\Filter\OrderDateTime();
$filterDate-&... | Basic - Using Filter | [
-0.23907281458377838,
-0.044114984571933746,
-0.3743092119693756,
0.022509541362524033,
-0.04338918626308441,
-0.3026867210865021,
0.08291692286729813,
0.10845574736595154,
0.04289843142032623,
0.19156184792518616,
-0.1326192319393158,
0.06318192183971405,
-0.04506805166602135,
0.061690524... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#basic---list-order-items | Basic - list Order Items
<?php
// create new order list
$orderManager = Factory::getInstance()->getOrderManager();
$orderList = $orderManager->createOrderList();
// get only orders that are committed
$orderList->setListType( $orderList::LIST_TYPE_ORDER_ITEM );
$orderList->setOrderState( AbstractOrder:... | Basic - list Order Items | [
-0.10227534174919128,
-0.1163405030965805,
-0.3024778366088867,
0.2427925318479538,
-0.04222758486866951,
-0.16071869432926178,
0.0743742510676384,
0.2467617243528366,
0.15147705376148224,
0.2347809374332428,
-0.04525287449359894,
-0.11949512362480164,
-0.21449458599090576,
-0.055170677602... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#advanced---custom-condition | Advanced - Custom Condition
<?php
// create new order list
$orderManager = Factory::getInstance()->getOrderManager();
$orderList = $orderManager->createOrderList();
// e.g. - search for a specify order number
$query = $orderList->getQuery();
$query->where('order.ordernumber = ?', 'ord_554b425dcae53');... | Advanced - Custom Condition | [
0.245825856924057,
-0.007925914600491524,
-0.3227282166481018,
0.36438432335853577,
-0.1774275153875351,
-0.32293644547462463,
0.03676171228289604,
0.36207568645477295,
0.24222585558891296,
0.09372499585151672,
-0.15460841357707977,
-0.16840538382530212,
-0.2569458484649658,
-0.35738009214... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#expert---high-performance | Expert - High Performance
avoid loading of Pimcore object's for higher performance
<?php
// create new order list
$orderManager = Factory::getInstance()->getOrderManager();
$orderList = $orderManager->createOrderList();
// add all required fields to the select
$orderList->addSelectField(['OrderNumber' ... | Expert - High Performance | [
-0.47021523118019104,
-0.11348089575767517,
-0.2697696387767792,
0.44111838936805725,
-0.020350655540823936,
-0.17547687888145447,
-0.14258117973804474,
0.20251235365867615,
0.08953017741441727,
0.36458978056907654,
-0.09146622568368912,
0.4695468842983246,
0.040254145860672,
0.27896717190... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#expert---extended-conditions-via-joins | Expert - Extended Conditions via Joins
<?php
// e.g. get all orderings for a customer
$orderList->joinCustomer( \Pimcore\Model\DataObject\Customer::classId() );
$orderList->getQuery()->where('customer.id = ?', 12345);
// e.g. filter product number
$orderList->joinProduct( \Pimcore\Model\DataObject\Pro... | Expert - Extended Conditions via Joins | [
-0.17861396074295044,
0.0032224112655967474,
-0.3007747232913971,
0.32056567072868347,
-0.155612513422966,
-0.4617794156074524,
0.03040534071624279,
0.24591590464115143,
0.12302477657794952,
-0.0039758626371622086,
-0.31198811531066895,
0.20851701498031616,
-0.16426505148410797,
0.14066031... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Lists#generic-filter | Generic Filter
Namespace: \Pimcore\Bundle\EcommerceFrameworkBundle\OrderManager\Order\Listing\Filter
Filter
Description
OrderDateTime
Date Range Filter
OrderSearch
Search order for a specified keyword
Payment
Filter by payment state (ok or fail)
Product
Filter by product and its variants
ProductType
Fi... | Generic Filter | [
-0.01227140799164772,
-0.15925028920173645,
-0.24734903872013092,
-0.003019525669515133,
0.10765239596366882,
-0.18467193841934204,
-0.15800915658473969,
0.2668392062187195,
0.09419749677181244,
-0.13139384984970093,
-0.36168599128723145,
-0.015969576314091682,
-0.07508416473865509,
0.2836... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Agent#working-with-order-agent | Working with Order Agent
The Order Agent is a one stop API for working with orders, e.g. changing state of orders, modifying quantity of items, etc.
and keeps track of these changes in a change log.
See following examples for how Order Agent can be used: | Working with Order Agent | [
0.3905736207962036,
-0.08010922372341156,
-0.21773667633533478,
-0.0779993087053299,
-0.11431849747896194,
-0.17365585267543793,
0.1919330656528473,
-0.23711343109607697,
0.24029158055782318,
0.03900519013404846,
0.14650914072990417,
0.2030913233757019,
-0.0422854982316494,
0.3879175782203... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Agent#change-item-quantity | Change item quantity
<?php
// load order item
$orderItem = DataObject\OnlineShopOrderItem::getById($this->getParam('id'));
$order = $orderItem->getOrder();
// create new order agent
$orderManager = Factory::getInstance()->getOrderManager();
$orderAgent = $orderManager->createOrderAgent($order);
// cha... | Change item quantity | [
-0.006381919141858816,
-0.13481660187244415,
-0.2943364679813385,
0.23469802737236023,
0.19000180065631866,
-0.2930213212966919,
0.3959769606590271,
-0.21637673676013947,
-0.12575754523277283,
0.4139012098312378,
-0.10432231426239014,
0.2068529725074768,
0.14279507100582123,
0.266901403665... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager/Working_with_Order_Agent#changelog-usage | Changelog Usage
<?php
// load order
$order = DataObject\OnlineShopOrder::getById($this->getParam('id'));
// create new order agent
$orderManager = Factory::getInstance()->getOrderManager();
$orderAgent = $orderManager->createOrderAgent($order);
// get changelog
/** @var \Pimcore\Model\Element\Note $log *... | Changelog Usage | [
-0.20330128073692322,
-0.04791616275906563,
-0.14435645937919617,
0.2142622321844101,
0.05174560472369194,
-0.22458505630493164,
0.45225876569747925,
0.07960844784975052,
0.028333768248558044,
0.12176722288131714,
0.01784844882786274,
0.22265496850013733,
-0.07021117210388184,
0.2017583101... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager#order-manager | Order Manager
The Order Manager is responsible for all aspects of working with orders except committing them (which is the
responsibility of the Commit Order Processor). These aspects contain among other things:
Creating orders based on carts
Order Storage (by default as Pimcore objects)
Loading orders
Loading order l... | Order Manager | [
0.33883097767829895,
-0.007745718117803335,
-0.1556173413991928,
-0.030158860608935356,
0.04738813266158104,
0.13763710856437683,
0.14546619355678558,
-0.3946700394153595,
-0.062061045318841934,
0.17050008475780487,
0.028650909662246704,
0.12037994712591171,
0.0626540333032608,
0.017737409... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Order_Manager#configuration | Configuration
The configuration takes place in the pimcore_ecommerce_framework.order_manager config section and is tenant aware.
pimcore_ecommerce_framework:
order_manager:
tenants:
_defaults:
# service ID of order manager implementation
order_manager_id: Pimcore\... | Configuration | [
-0.044209036976099014,
-0.06493769586086273,
-0.17683908343315125,
0.09829571843147278,
0.2696461081504822,
-0.24434423446655273,
0.21570131182670593,
-0.19617697596549988,
-0.11482156813144684,
0.2016373723745346,
-0.12660683691501617,
0.2414843887090683,
-0.01662443019449711,
0.065385796... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#tracking-manager | Tracking Manager
The Tracking Manager enables e-commerce transaction tracking for e-commerce websites built with the framework. Due to
different tracker implementations, it supports different tracking services.
Current implementations of trackers are
Google Tag Manager (GTM): \\Pimcore\Bundle\EcommerceFrameworkBundle... | Tracking Manager | [
-0.258571594953537,
-0.3199867308139801,
-0.12445652484893799,
0.1269034445285797,
0.14868773519992828,
0.10817886888980865,
0.12369876354932785,
-0.04289717227220535,
0.009379415772855282,
0.023505285382270813,
0.04133201390504837,
0.013409345410764217,
-0.1479630172252655,
0.608409583568... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#supported-tracking-actions | Supported Tracking Actions
The Tracking Manager supports several tracking actions that can be used. These tracking actions are delegated to the
trackers.
Product Impression
Tracks product impression
$trackingManager->trackProductImpression($product)
Product View
Tracks product view (of detail page)
$tracking... | Supported Tracking Actions | [
-0.2728414237499237,
-0.08797945082187653,
-0.1410089135169983,
-0.20957481861114502,
0.047151558101177216,
-0.06283053755760193,
0.48398932814598083,
0.011581368744373322,
0.00038780871545895934,
0.1557447612285614,
0.19598440825939178,
0.08393169939517975,
-0.1683807224035263,
0.27893567... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#configuration | Configuration
The configuration takes place in the pimcore_ecommerce_framework.tracking_manager config section.
If no TrackingItemBuilder is configured, the TrackingItemBuilder will fall back to the default implementation
\Pimcore\Bundle\EcommerceFrameworkBundle\Tracking\TrackingItemBuilder. Further information about T... | Configuration | [
-0.38510316610336304,
-0.0009068211656995118,
-0.07732358574867249,
0.0481015108525753,
0.17715167999267578,
-0.14403702318668365,
0.273303747177124,
-0.18294493854045868,
-0.2511172890663147,
0.2644329369068146,
0.06435808539390564,
0.37453141808509827,
0.012432841584086418,
0.30007818341... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#tracking-manager-with-tenants | Tracking Manager With Tenants
The Tracking Manager supports tenants in a different way than the other framework modules. While with the other modules,
the tenant configuration takes place on the highest level of configuration and each configuration is only valid for one
tenant, the tenant configuration in the tracking ... | Tracking Manager With Tenants | [
-0.12797413766384125,
-0.017483001574873924,
-0.09710261970758438,
0.11723330616950989,
0.32724377512931824,
-0.182288259267807,
0.43660205602645874,
-0.2998253107070923,
0.11061093211174011,
0.3217729330062866,
0.11363331228494644,
0.08812906593084335,
-0.20877692103385925,
0.126743346452... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#working-with-tracking-manager | Working with Tracking Manager
For utilizing the Tracking Manager, just call the corresponding methods of the TrackingManager in your controller.
The framework does the rest (adding necessary code snippets to your view, etc.).
See the following examples | Working with Tracking Manager | [
-0.16096006333827972,
0.015697428956627846,
-0.16748039424419403,
-0.025444582104682922,
0.008240936324000359,
-0.2236579805612564,
0.25561273097991943,
-0.01953170821070671,
-0.12222932279109955,
0.23477904498577118,
0.029549548402428627,
0.28653091192245483,
-0.2571087181568146,
0.467836... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#product-impression | Product Impression
<?php
namespace App\Controller;
use Knp\Component\Pager\PaginatorInterface;
use Pimcore\Bundle\EcommerceFrameworkBundle\Tracking\TrackingManager;
use Pimcore\Controller\FrontendController;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\Response;
class ShopCon... | Product Impression | [
-0.2619472146034241,
-0.2958398461341858,
-0.25216540694236755,
0.0860801711678505,
-0.03501930460333824,
-0.20028109848499298,
0.10767059773206711,
0.13288584351539612,
-0.2671374976634979,
0.1908329874277115,
-0.16503582894802094,
0.11866231262683868,
0.11930735409259796,
0.3617967963218... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#checkout | Checkout
<?php
use Pimcore\Bundle\EcommerceFrameworkBundle\Tracking\TrackingManager;
class CheckoutController extends AbstractCartAware
{
public function startCheckoutAction(TrackingManager $trackingManager) {
...
$trackingManager->trackCheckout($this->getCart());
...
}
}
| Checkout | [
-0.47629472613334656,
-0.33583804965019226,
-0.13153593242168427,
0.05940776318311691,
0.13148094713687897,
-0.16481852531433105,
0.16855370998382568,
0.14016221463680267,
-0.11063630878925323,
0.2567291557788849,
0.08391254395246506,
0.2917865514755249,
0.03958602994680405,
0.532421827316... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#project-specific-data | Project Specific Data
Adding project specific data to tracking items by extending the TrackingItemBuilder class. The extending class has to
be defined as service and configured on the tracker configuration (see above). | Project Specific Data | [
-0.11444342881441116,
0.37613362073898315,
-0.10574036091566086,
0.3296160101890564,
0.046660907566547394,
-0.22674235701560974,
0.0653340145945549,
0.01295548491179943,
-0.36650726199150085,
0.21349914371967316,
0.18657083809375763,
0.3832055628299713,
-0.03147493675351143,
0.473692417144... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#example-for-additional-data-in-product-impressions | Example for Additional Data in Product Impressions
Define a custom item builder:
<?php
use Pimcore\Bundle\EcommerceFrameworkBundle\Model\ProductInterface;
use Pimcore\Bundle\EcommerceFrameworkBundle\Tracking\ProductImpressionInterface;
class TrackingItemBuilder extends \Pimcore\Bundle\EcommerceFrameworkBundle\Trac... | Example for Additional Data in Product Impressions | [
-0.316653847694397,
-0.0814569965004921,
-0.24623990058898926,
0.23976007103919983,
-0.0484892912209034,
-0.18235015869140625,
0.3936654329299927,
0.07212933897972107,
-0.27422159910202026,
0.10785611718893051,
0.002935646800324321,
0.238129660487175,
0.06943318247795105,
0.424073338508605... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Tracking_Manager#external-links | External Links
Google Documentation Enhanced E-Commerce | External Links | [
0.16907000541687012,
-0.3360733389854431,
-0.25657960772514343,
0.02002868615090847,
0.0047448561526834965,
-0.008912969380617142,
0.39231419563293457,
-0.2770349085330963,
0.10127489268779755,
0.03023262321949005,
-0.22473399341106415,
0.22782333195209503,
0.20629377663135529,
0.129877939... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Event_API_and_Event_Manager#events-and-event-listeners | Events and Event Listeners | Events and Event Listeners | [
-0.2923720180988312,
-0.4886212944984436,
-0.25650981068611145,
0.3866772949695587,
-0.08087639510631561,
-0.38111722469329834,
0.16758878529071808,
-0.16936801373958588,
0.104853555560112,
0.45728185772895813,
-0.12174513936042786,
0.17841920256614685,
-0.389316588640213,
0.00816451478749... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Event_API_and_Event_Manager#general | General
This bundle provides additional Events.
It's recommended to have a look into the Pimcore Events and Event Listeners documentation | General | [
-0.515750527381897,
-0.4081123173236847,
-0.22637489438056946,
-0.007659458089619875,
-0.17418880760669708,
-0.06479912251234055,
0.054999757558107376,
-0.0644722729921341,
-0.33699265122413635,
0.1396961361169815,
-0.31879010796546936,
0.5137478113174438,
-0.23079189658164978,
0.235882669... |
https://pimcore.com/docs/platform//Ecommerce_Framework/Event_API_and_Event_Manager#available-events | Available Events
Ecommerce::Index Service
Ecommerce::Checkout Manager
Ecommerce::Commit Order Processor
Ecommerce::Order Agent
Ecommerce::Order Manager
| Available Events | [
-0.17461617290973663,
-0.4754544496536255,
-0.2999067008495331,
0.037502091377973557,
-0.010224245488643646,
0.034969162195920944,
0.11294928193092346,
-0.12678393721580505,
0.43732795119285583,
0.030364898964762688,
-0.07381264120340347,
0.21727119386196136,
0.10820042341947556,
0.5051913... |
https://pimcore.com/docs/platform//Ecommerce_Framework#e-commerce-framework | E-Commerce Framework | E-Commerce Framework | [
0.15023498237133026,
-0.3687334358692169,
-0.4609759747982025,
0.23568184673786163,
0.1323857307434082,
-0.2533305585384369,
0.2398126870393753,
-0.17251081764698029,
0.08882618695497513,
-0.07454491406679153,
-0.03223877772688866,
0.032455939799547195,
0.15194262564182281,
0.7162228822708... |
https://pimcore.com/docs/platform//Ecommerce_Framework#why-pimcore-e-commerce-framework | Why Pimcore E-Commerce Framework
The e-commerce environment has fundamentally changed and e-commerce projects often face new challenges like:
complex product structures: lots of data attributes, complex product relations, configurable product systems,
different sources for products
complex pricing structures: produc... | Why Pimcore E-Commerce Framework | [
-0.06947892159223557,
-0.588588297367096,
-0.24730637669563293,
0.21212805807590485,
0.1353786587715149,
-0.1866341233253479,
0.14877861738204956,
-0.01872662641108036,
-0.27583375573158264,
0.05616350471973419,
-0.15800386667251587,
0.299464613199234,
0.19130024313926697,
0.62039577960968... |
https://pimcore.com/docs/platform//Ecommerce_Framework#provided-functionality-in-a-nutshell | Provided Functionality in a Nutshell
Tools for indexing, listing, searching and filtering products
Implementations of carts, wish lists, comparison lists, etc.
Concepts for flexible and complex pricing, taxes and availability functionality
Functionality and tools for implementing checkout processes
Pricing Rules and V... | Provided Functionality in a Nutshell | [
0.17242859303951263,
-0.43166691064834595,
-0.40390655398368835,
-0.061434488743543625,
0.09594380110502243,
0.14416393637657166,
0.29773184657096863,
-0.015254411846399307,
-0.05561458319425583,
-0.16180481016635895,
0.13781751692295074,
0.32334262132644653,
0.16839979588985443,
0.5671328... |
https://pimcore.com/docs/platform//Ecommerce_Framework#working-with-e-commerce-framework | Working With E-Commerce Framework
Following aspects are short-cuts into the documentation for start working with the E-Commerce Framework:
Architecture Overview
Installation and Configuration
Indexing and Listing Products
Filtering Products
Working with Prices
Working with Carts
Setting up Checkouts
Int... | Working With E-Commerce Framework | [
0.170138880610466,
-0.35351139307022095,
-0.29623717069625854,
0.2292451411485672,
0.20905642211437225,
0.061868276447057724,
-0.0026518567465245724,
-0.34923768043518066,
-0.039448898285627365,
0.07988683134317398,
0.03226843103766441,
0.09181509166955948,
0.2462192326784134,
0.5743607878... |
https://pimcore.com/docs/platform//Targeting/Usage/Concepts#pimcore-concepts-for-personalization | Pimcore Concepts for Personalization
The following core concepts are the essential parts of Pimcores personalization engine. | Pimcore Concepts for Personalization | [
-0.23979032039642334,
-0.15815743803977966,
-0.22990380227565765,
0.15939311683177948,
-0.12152187526226044,
-0.24192635715007782,
-0.1754525601863861,
-0.08306767791509628,
-0.7622480392456055,
0.14676256477832794,
-0.13901926577091217,
0.3534153401851654,
0.000773648323956877,
0.23770146... |
https://pimcore.com/docs/platform//Targeting/Usage/Concepts#target-group | Target Group
It is recommended to group your visitors into target groups. They help you to keep track and have an overview about what
content you need to provide and about which content is delivered to what visitor.
So, a Target Group is an entity which is used to personalize content for.
Target groups are defined cent... | Target Group | [
0.34825313091278076,
-0.4527055025100708,
-0.08535071462392807,
-0.15289413928985596,
-0.015857048332691193,
0.03597230091691017,
0.4614717364311218,
-0.2546636462211609,
-0.15087105333805084,
-0.05501917749643326,
-0.1579163670539856,
-0.3922271132469177,
0.08306964486837387,
0.0143870171... |
https://pimcore.com/docs/platform//Targeting/Usage/Concepts#global-targeting-rule | Global Targeting Rule
Global Targeting Rules define the rule set based on which visitor profiling and content personalization takes place.
Thus they allow to assign target groups, redirect the visitor to certain pages or inject code snippets (special
java scripts, etc.) to the response based on behavioral conditions.
A... | Global Targeting Rule | [
0.7007798552513123,
-0.5325375199317932,
-0.13032880425453186,
-0.2787685692310333,
-0.00641705421730876,
-0.21633198857307434,
0.12672947347164154,
-0.03591177985072136,
0.0004540150403045118,
-0.3767191469669342,
-0.08961047977209091,
-0.27541685104370117,
-0.05911688506603241,
0.0941499... |
https://pimcore.com/docs/platform//Targeting/Usage/Concepts#personalized-document-content | Personalized Document Content
Pimcore Documents provide the possibility to create varying content variants for each defined target group. Once a target
group is selected, all content elements within the document can be overwritten and personalized. For not overwritten
content elements, the content is inherited from the... | Personalized Document Content | [
0.1343759000301361,
-0.4728967845439911,
-0.07043998688459396,
-0.08810857683420181,
-0.3217112421989441,
-0.1956091821193695,
-0.005490517243742943,
-0.042375024408102036,
-0.4324623942375183,
0.17557939887046814,
-0.30903950333595276,
0.3446927070617676,
0.2456161081790924,
0.05161801725... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Define_Target_Groups#define-target-groups | Define Target Groups
It is recommended to group your visitors into target groups. They help you to keep track and have an overview about what
content you need to provide and about which content is delivered to what visitor.
Thus, Target Groups are the core entities for personalizing content.
Target groups are defined c... | Define Target Groups | [
0.2532692551612854,
-0.491914302110672,
-0.11163286864757538,
-0.1715041846036911,
-0.01740068569779396,
-0.16586904227733612,
0.377184122800827,
-0.21470527350902557,
-0.14248888194561005,
0.15221747756004333,
-0.2213049679994583,
-0.12313023954629898,
0.004122811369597912,
0.101514026522... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Visitor_Profiling#visitor-profiling | Visitor Profiling
Visitor profiling is the process of getting to know visitors and assign one or multiple target groups based on their
behaviour.
The result of the ongoing profiling process is a set of target groups, that are assigned with a certain assignment
relevance to the current visitor.
Pimcore provides two way... | Visitor Profiling | [
0.04510342702269554,
-0.4408344030380249,
-0.082573801279068,
-0.12803374230861664,
-0.1480097621679306,
-0.0636863261461258,
0.020434875041246414,
-0.15405800938606262,
-0.4527031183242798,
0.1504928469657898,
-0.22197528183460236,
-0.09910557419061661,
-0.02852015197277069,
0.05281902477... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Visitor_Profiling#associate-target-groups-directly-with-pimcore-documents | Associate Target Groups directly with Pimcore Documents
It is possible to associate Pimcore documents directly with target groups. This can be configured in Settings tab of
each document as soon as there are target groups defined in the system.
Once one or more target groups are associated with a document, the selecte... | Associate Target Groups directly with Pimcore Documents | [
-0.19846774637699127,
-0.17892253398895264,
-0.08456460386514664,
-0.0058255731128156185,
-0.14999909698963165,
-0.25080516934394836,
0.3055892586708069,
-0.4255974590778351,
-0.3743806481361389,
0.24889762699604034,
-0.507228434085846,
0.35184186697006226,
0.22528547048568726,
0.174402952... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Visitor_Profiling#use-global-targeting-rules-to-assign-target-groups | Use Global Targeting Rules to Assign Target Groups
Global Targeting Rules define a rule set based on which visitors can be profiled. Multiple conditions can be combined
to complex criteria for assigning target groups to the current visitor based on their behavior.
When assigning a target group via global targeting rul... | Use Global Targeting Rules to Assign Target Groups | [
0.10735119879245758,
-0.28641951084136963,
-0.2063228040933609,
-0.2734305262565613,
0.018574407324194908,
-0.13813306391239166,
0.41286036372184753,
-0.26759225130081177,
-0.22249050438404083,
0.07789156585931778,
-0.2480405569076538,
-0.11611785739660263,
0.01566336117684841,
0.341659843... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Create_Personalized_Content#create-personalized-content | Create Personalized Content
The simplest way to create personalized content is with Pimcore documents. They provide the possibility to create
varying content variants for each defined target group.
Once a target group is selected, all content elements within the document can be overwritten and personalized. To
overwri... | Create Personalized Content | [
0.06709618121385574,
-0.34010446071624756,
-0.18561457097530365,
-0.13514220714569092,
-0.24838688969612122,
-0.16513203084468842,
0.046574532985687256,
0.02846236526966095,
-0.44285476207733154,
0.35985109210014343,
-0.14921420812606812,
0.5399934649467468,
0.20540235936641693,
0.16485790... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Deliver_Personalized_Content_and_Debug#deliver-personalized-content | Deliver Personalized Content
Once target groups are defined, visitor profiling rules are set and personalized content is created, it is time to
deliver the personalized content to the right people.
Pimcore provides two ways to deliver personalized Content: | Deliver Personalized Content | [
0.11160760372877121,
-0.0902884304523468,
-0.1459822803735733,
-0.08711475878953934,
-0.3090287446975708,
-0.41399192810058594,
0.15759500861167908,
-0.17720894515514374,
-0.5966701507568359,
0.19344159960746765,
-0.3215959966182709,
0.26683151721954346,
0.22845704853534698,
0.255135148763... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Deliver_Personalized_Content_and_Debug#delivering-personalized-content-with-documents | Delivering Personalized Content with Documents
When a document is delivered to the visitor, the best matching variant is picked by Pimcore based on following rule:
If the visitor has only one assigned target group and content exists for that target group, the personalized variant
for that target group will be used
If ... | Delivering Personalized Content with Documents | [
0.19386456906795502,
-0.5330244302749634,
-0.06940137594938278,
0.22591163218021393,
-0.22099803388118744,
-0.30513983964920044,
0.22851894795894623,
0.12569889426231384,
-0.5564877986907959,
0.038342833518981934,
-0.47444427013397217,
0.3285939693450928,
0.40421783924102783,
-0.0552558042... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Deliver_Personalized_Content_and_Debug#delivering-personalized-content-with-global-targeting-rules | Delivering Personalized Content with Global Targeting Rules
In addition to Pimcore document delivery, global targeting rules provide two actions with further possibilities to
deliver personalized content to the visitor.
Redirect: The visitor can be redirected when certain conditions match. E.g. redirect visitor on it... | Delivering Personalized Content with Global Targeting Rules | [
0.3529556095600128,
-0.5446983575820923,
-0.031176550313830376,
-0.19096773862838745,
-0.16944211721420288,
-0.32571879029273987,
-0.3036196529865265,
0.21200086176395416,
-0.3284578323364258,
-0.0897417739033699,
-0.19557438790798187,
0.4465065002441406,
-0.07145139575004578,
0.4923462569... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content/Deliver_Personalized_Content_and_Debug#verify-what-happens---aka-debug | Verify What Happens - aka Debug
The personalization configuration can become quite complex really quick. To get to know what happens, which rules matched
for a certain request, which target groups are assigned and what data is collected, Pimcore injects several information
the Symfony profiler bar.
On the detail page ... | Verify What Happens - aka Debug | [
0.17718736827373505,
-0.14227686822414398,
0.026527145877480507,
0.24941813945770264,
-0.23140953481197357,
-0.3316171169281006,
0.24196366965770721,
-0.26895010471343994,
-0.5609527230262756,
0.06288689374923706,
-0.2663402855396271,
0.2629178464412689,
0.24952076375484467,
0.010788213461... |
https://pimcore.com/docs/platform//Targeting/Usage/How_to_Personalize_Content#how-to-personalize-content | How to Personalize Content
On the following pages you find a short tutorial for how to personalize content.
As the Pimcore behavioral targeting engine is very powerful and flexible, there are multiple ways to archive a result
and the outlined way is just one of many.
The typical workflow of personalizing content contai... | How to Personalize Content | [
0.2854479253292084,
-0.008566699922084808,
-0.14644765853881836,
-0.21327903866767883,
-0.14373035728931427,
-0.21475963294506073,
0.09509480744600296,
-0.1727619469165802,
-0.7089280486106873,
0.12210317701101303,
-0.17248566448688507,
0.41874876618385315,
0.1854761689901352,
0.2624396681... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#examples-for-personalization-and-targeting | Examples for Personalization and Targeting
The following pages show a few examples to better understand how things can be achieved with the Pimcore targeting
engine.
All mentioned rules here are configured and set up in our demo and can be
tested there. | Examples for Personalization and Targeting | [
0.2285793125629425,
-0.2294827699661255,
-0.17842258512973785,
-0.07536638528108597,
0.024329962208867073,
-0.4719511866569519,
0.19838427007198334,
-0.2213382124900818,
-0.46797308325767517,
0.11801868677139282,
-0.23919236660003662,
0.41803914308547974,
0.08579114079475403,
0.35263916850... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#visitor-profiling | Visitor Profiling
The result of the ongoing profiling process is a set of target groups, that are assigned with a certain assignment
relevance to the current visitor. So visitor profiling rules are always some conditions that result in assignment of
an target group. | Visitor Profiling | [
0.2741488516330719,
-0.37379908561706543,
-0.18008218705654144,
-0.16884660720825195,
-0.08216407895088196,
-0.1645442545413971,
0.08388730883598328,
-0.2124447077512741,
-0.32571709156036377,
-0.05711287632584572,
-0.2596110999584198,
-0.11348782479763031,
-0.019938815385103226,
0.2344726... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#learning-about-customer-interests-based-on-behaviour | Learning about customer interests based on behaviour | Learning about customer interests based on behaviour | [
-0.031136373057961464,
0.05928715690970421,
-0.35283657908439636,
0.3204420506954193,
-0.05250877887010574,
-0.36085546016693115,
0.3962126672267914,
-0.08955051749944687,
0.12981773912906647,
0.17753955721855164,
-0.046710044145584106,
0.10236997902393341,
-0.1982778161764145,
0.165973424... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#assign-target-groups-to-documents | Assign Target Groups to Documents
If there is a document, directly associate this document with a target group.
Every time a visitor visits that page, it gets the technical-guy target group assigned. Since one visit might be a
coincidence, multiple visits might hint for a technical interest of that visitor.
To filter ... | Assign Target Groups to Documents | [
0.37935715913772583,
-0.3776148557662964,
-0.1898614764213562,
-0.04890203848481178,
-0.36127838492393494,
-0.277271032333374,
0.12180618941783905,
-0.14306266605854034,
-0.10013473033905029,
0.08272012323141098,
-0.030761051923036575,
0.023122843354940414,
0.15506747364997864,
0.183385267... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#global-targeting-rules-with-simple-conditions-&-actions | Global Targeting Rules with simple Conditions & Actions
Regular visits in a certain shopping category (e.g. football) indicate an interest in football. To track that information,
add a global targeting rule with a URL condition and an action to assign the corresponding target group.
To eliminate coincidence visits,... | Global Targeting Rules with simple Conditions & Actions | [
0.1267312914133072,
-0.3335890471935272,
-0.19697509706020355,
-0.04412863403558731,
0.044455625116825104,
-0.2847296893596649,
-0.012679173611104488,
-0.07852181792259216,
-0.16382846236228943,
-0.21587654948234558,
-0.09104267507791519,
-0.11922139674425125,
-0.17052717506885529,
0.20636... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#guessing-customer-characteristics-based-on-behaviour | Guessing customer characteristics based on behaviour | Guessing customer characteristics based on behaviour | [
0.045693691819906235,
-0.17888188362121582,
-0.2742908298969269,
0.13693220913410187,
0.07039409130811691,
-0.22925496101379395,
0.48628175258636475,
-0.01616528630256653,
0.12852227687835693,
0.14661943912506104,
0.11356424540281296,
-0.03718828037381172,
-0.017688067629933357,
0.01766942... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#global-targeting-rule-with-more-complex-conditions | Global Targeting Rule with more complex Conditions
Similar to the category interest tracking, customer characteristics like favorite color or even gender can be guessed.
To do so, add for example a targeting rule that tracks product filtering for blue products and assigns corresponding
target groups like the profiling_... | Global Targeting Rule with more complex Conditions | [
0.10852990299463272,
-0.2050759196281433,
-0.25949594378471375,
-0.14414329826831818,
-0.031655747443437576,
-0.28052282333374023,
0.28605177998542786,
0.03786597028374672,
-0.11932407319545746,
-0.10181113332509995,
-0.14218448102474213,
-0.13860143721103668,
-0.24100106954574585,
0.35995... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#classify-customers-based-on-behaviour | Classify customers based on behaviour | Classify customers based on behaviour | [
0.047923944890499115,
-0.06693249940872192,
-0.43377962708473206,
-0.005508138332515955,
0.05010010674595833,
-0.14325378835201263,
0.5146039724349976,
-0.0014283600030466914,
0.25543123483657837,
-0.1385089010000229,
-0.025563403964042664,
0.0569617822766304,
-0.18662823736667633,
0.17159... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#identify-regular-customers | Identify regular customers
In addition to collecting customer characteristics, you also could classify customers based on number of orders they made.
For example once a new customer creates an additional order, it becomes a regular customer. See the profiling_regular-customer
rule in the demo for details.
In this case... | Identify regular customers | [
-0.2325628399848938,
-0.17093569040298462,
-0.16873997449874878,
-0.03309628367424011,
0.046119336038827896,
-0.22746767103672028,
0.183353453874588,
-0.32305848598480225,
-0.5443942546844482,
0.030752643942832947,
-0.17699073255062103,
0.07120705395936966,
-0.055545248091220856,
0.1288748... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#personalize-content | Personalize Content | Personalize Content | [
0.26033759117126465,
-0.15907147526741028,
-0.3436773717403412,
-0.033227432519197464,
0.06862324476242065,
-0.04341071844100952,
0.09894350171089172,
0.17628341913223267,
-0.3202000558376312,
0.28297045826911926,
-0.03929844871163368,
0.26837873458862305,
-0.038426097482442856,
0.09640903... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#personalize-content-using-global-targeting-rules | Personalize content using global targeting rules | Personalize content using global targeting rules | [
0.43015366792678833,
-0.1881997287273407,
-0.1935230791568756,
-0.1603706330060959,
0.27593308687210083,
-0.19547688961029053,
0.26217204332351685,
0.1932569444179535,
-0.18535162508487701,
-0.07745108753442764,
-0.07502871751785278,
0.23358923196792603,
-0.23155862092971802,
0.26017567515... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#redirect-visitor-to-a-certain-landing-page | Redirect visitor to a certain landing page
One example for content personalization is to redirect a visitor to a special landing page that is answering this questions.
In our demo the example personalize_redirect-to-landingpage redirects visitors with language german that visited 5 pages
on our website to a landing pag... | Redirect visitor to a certain landing page | [
0.20034855604171753,
-0.44807347655296326,
-0.1734737902879715,
-0.10629814118146896,
-0.1259969174861908,
-0.1365492194890976,
-0.04832543060183525,
0.18659621477127075,
-0.1539086103439331,
-0.06469526886940002,
-0.0229004118591547,
0.07570826262235641,
0.008083518594503403,
-0.068949691... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#inject-special-content-to-mobile-visitors | Inject special content to mobile visitors
Another use case could be, that special users (e.g. mobile users from a certain country) should see a slightly different
layout. See the personalize_device-mobile rule of our demo how this can be archived by injecting additional CSS code
to the page.
| Inject special content to mobile visitors | [
0.3400103747844696,
-0.4720226526260376,
-0.310151606798172,
-0.30843669176101685,
0.09287076443433762,
0.0005956535460427403,
0.6435028910636902,
0.09824172407388687,
-0.20716018974781036,
0.15280210971832275,
0.03434445336461067,
-0.02213018201291561,
0.06381635367870331,
-0.094847030937... |
https://pimcore.com/docs/platform//Targeting/Usage/Examples#personalized-content-documents | Personalized content documents
The most common and most flexible way to customize content is to create customized variants of documents for certain
target groups. See Create Personalized Content
and Deliver Personalized Content for
details.
In our demo several different variants of the portal page are set up - e.g. for... | Personalized content documents | [
0.15162502229213715,
-0.07035236805677414,
-0.19252857565879822,
0.005032593384385109,
-0.1410999745130539,
0.0726795569062233,
0.013819785788655281,
0.15893667936325073,
-0.41473203897476196,
0.01335162203758955,
-0.05922357738018036,
0.16587506234645844,
0.27919161319732666,
0.0211070850... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Visitor_Info#visitor-info | Visitor Info
The VisitorInfo is the central data object which is passed to every part of the targeting system. A new VisitorInfo
is created for every request and enriched with data throughout the matching process. Starting from an empty object, data
will be added to the VisitorInfo from several components, making it ho... | Visitor Info | [
0.42074084281921387,
-0.30200961232185364,
0.005652072839438915,
0.32404661178588867,
0.00002455796129652299,
-0.2774556279182434,
-0.25675028562545776,
-0.11911118030548096,
-0.391171395778656,
0.1732831746339798,
-0.07340839505195618,
-0.4371773898601532,
0.34933382272720337,
-0.04593326... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Visitor_Info#visitor-id | Visitor ID
To identify returning visitors, the engine needs some kind of unique identificator which will be assigned to each visitor.
This identificator, internally referred to as visitor ID, is expected to be generated or set by the browser and to be
stored as a cookie. When creating a VisitorInfo the targeting engine... | Visitor ID | [
0.34869876503944397,
-0.4727243185043335,
-0.013348227366805077,
0.12543094158172607,
0.25764182209968567,
-0.17068059742450714,
0.07178760319948196,
-0.2153855264186859,
-0.13483397662639618,
0.24067354202270508,
-0.16137538850307465,
-0.10316268354654312,
0.20262941718101501,
0.069691330... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Visitor_Info#accessing-the-visitor-info-in-your-code | Accessing the Visitor Info in your code
Similar to the security token in Symfony's security system, you can fetch the current VisitorInfo from a VisitorInfoStorage.
This storage is defined as service an can simply be injected into your services or used as controller action argument when
your controllers are registered ... | Accessing the Visitor Info in your code | [
-0.12780584394931793,
0.20125240087509155,
-0.15960009396076202,
0.2583443522453308,
-0.031039344146847725,
-0.5080559253692627,
0.21295708417892456,
0.015573916025459766,
-0.11070643365383148,
0.2230204939842224,
-0.12749528884887695,
0.11747090518474579,
0.08214025944471359,
-0.170315653... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Conditions#conditions | Conditions
Conditions are logical blocks which can be combined with other conditions inside a target rule. A condition is expected
to implement match() method which always returns a boolean.
To implement a condition, you need to implement 2 parts:
A PHP class implementing the ConditionInterface.
Have a look at existin... | Conditions | [
0.30479303002357483,
-0.16581831872463226,
-0.15805785357952118,
-0.09010876715183258,
-0.1980953961610794,
-0.5501329302787781,
0.15476790070533752,
0.2446337193250656,
0.3228324353694916,
-0.03415336087346077,
0.22025611996650696,
-0.12117410451173782,
0.08569329231977463,
0.075613699853... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Conditions#implementing-a-condition | Implementing a Condition
As stated before, a condition needs to implement the ConditionInterface.
The most important method in the interface is the match() method which receives the current VisitorInfo instance and
is expected to return a boolean which indicates if the condition matches or not.
As an example let's buil... | Implementing a Condition | [
-0.13023199141025543,
-0.1958305984735489,
-0.115715891122818,
-0.04230765253305435,
-0.18987606465816498,
-0.6302829384803772,
0.1748517006635666,
0.03904029354453087,
-0.07611799985170364,
0.16272173821926117,
0.07911905646324158,
0.06250528991222382,
-0.002247108379378915,
0.03027778118... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Conditions#building-a-condition-instance | Building a Condition Instance
When an instance of your condition is build, by default the ConditionFactory
will call the static fromConfig() method with the data configured in the admin UI. Avoid injecting any services or
custom data into your condition and use the data provider system instead to add data to the Visito... | Building a Condition Instance | [
0.011669633910059929,
0.06586175411939621,
-0.037859778851270676,
0.28016671538352966,
-0.1476982980966568,
-0.4790066182613373,
-0.08825872093439102,
0.032577164471149445,
0.13842806220054626,
0.3353564441204071,
-0.05331255495548248,
-0.08938556909561157,
0.15286001563072205,
0.122603006... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Conditions#condition-data | Condition Data
If your condition needs any outside data, implement the DataProviderDependentInterface
and define a list of data provider keys which need to be set on the VisitorInfo before matching. We'll enhance our TimeOfTheDay
condition on the Data Providers chapter. For further examples, you can take a look at exis... | Condition Data | [
-0.05338893085718155,
0.1322159767150879,
-0.1896268129348755,
0.013233081437647343,
-0.32497069239616394,
-0.5279131531715393,
0.12381505221128464,
0.1119157150387764,
0.14101874828338623,
0.1497972160577774,
0.08432941883802414,
-0.2855851352214813,
0.2920013964176178,
0.1674188077449798... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Conditions#condition-variables | Condition Variables
An important part are variable conditions
which support the session_with_variables rule matching scope. A condition implementing this interface is expected to return
an array of the variables which led to match the condition in the getMatchedVariables() method. This data will be used
to determine if... | Condition Variables | [
-0.09170294553041458,
-0.22533230483531952,
-0.1665414720773697,
-0.07253839075565338,
-0.18561500310897827,
-0.4562416672706604,
0.22120842337608337,
0.03351373225450516,
-0.1398794800043106,
-0.01706663705408573,
0.07138827443122864,
-0.06544817984104156,
0.061987727880477905,
-0.1663634... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Conditions#admin-ui | Admin UI
To make your condition configurable, you need to create a JS class defining the admin interface for your condition. To do
so, create a class extending pimcore.bundle.personalization.settings.condition.abstract and register it to the system by calling
pimcore.bundle.personalization.settings.conditions.register(... | Admin UI | [
-0.20159600675106049,
-0.18621233105659485,
-0.11339294165372849,
-0.03341341391205788,
0.09555923193693161,
-0.41490083932876587,
0.13689342141151428,
-0.037207141518592834,
-0.16326595842838287,
0.22450768947601318,
0.022727003321051598,
0.3409903943538666,
-0.0002740781055763364,
0.2397... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Data_Providers#data-providers | Data Providers
A data provider is a service implementing the DataProviderInterface.
Components (e.g. conditions) which implement the DataProviderDependentInterface
can define a set of data providers they depend on, triggering the data provider to load its data before the component
is used.
A data provider does not dire... | Data Providers | [
0.028207406401634216,
0.4008685350418091,
-0.09376958757638931,
0.3299013376235962,
0.1592038869857788,
-0.44900351762771606,
0.10810291767120361,
-0.341901034116745,
-0.2617892324924469,
0.3639816641807556,
0.15277329087257385,
0.15394166111946106,
0.37413081526756287,
0.2340555191040039,... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Data_Providers#implementing-a-data-provider | Implementing a Data Provider
A data provider is simply a class implementing the DataProviderInterface which is registered as service. Basically a
data provider can do anything, however the core data providers do the following:
They store their information on a storage key which is exposed as constant
They always set t... | Implementing a Data Provider | [
-0.11003503948450089,
0.21069051325321198,
-0.031111543998122215,
0.15677103400230408,
-0.014115577563643456,
-0.527786910533905,
0.07880785316228867,
-0.2817758321762085,
-0.3899226188659668,
0.2925017476081848,
0.004795795772224665,
0.3070451319217682,
0.10300226509571075,
0.052753455936... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Data_Providers#consuming-a-data-provider | Consuming a Data Provider
To consume a data provider, implement the DataProviderDependentInterface in your components and specify a list of data
providers to use. As an example, let's update the TimeOfTheDay condition to fetch the current DateTime from our new
provider:
<?php
// src/Targeting/Condition/TimeOfTheDay... | Consuming a Data Provider | [
-0.40255215764045715,
0.25560134649276733,
-0.08385717123746872,
0.14368896186351776,
0.04322975501418114,
-0.5187664031982422,
0.22829745709896088,
-0.0338129997253418,
-0.3120606541633606,
0.2062126249074936,
-0.15209275484085083,
0.12625153362751007,
-0.0035904108081012964,
0.1161710917... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Action_Handlers#action-handlers | Action Handlers
After a targeting rule matched it executes one or more actions as configured in the admin UI. These actions are actually
executed by action handlers, which are services implementing the ActionHandlerInterface.
As with conditions, an action handler consists of 2 parts:
A PHP class implementing the Actio... | Action Handlers | [
0.38036465644836426,
-0.45247963070869446,
-0.09869949519634247,
0.06220480054616928,
-0.17670482397079468,
-0.3701741397380829,
0.19361649453639984,
-0.07111460715532303,
0.08211949467658997,
-0.0017893417971208692,
-0.07878431677818298,
0.11182861775159836,
-0.018852977082133293,
0.19577... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Action_Handlers#implementing-an-action-handler | Implementing an Action Handler
As example, we'll implement a simple Log action handler which will log each matched rule with a configured log level.
The action handler is a normal service which can depend on other services (as we do with the logger here).
You can't rely on a visitor ID being set or a rule being passed... | Implementing an Action Handler | [
-0.08347174525260925,
-0.19300882518291473,
0.02834014967083931,
-0.06756415218114853,
-0.183634415268898,
-0.3974568545818329,
0.2489769607782364,
-0.01208704337477684,
-0.08491050451993942,
0.0682758018374443,
0.0779605358839035,
-0.06885849684476852,
-0.3248292803764343,
0.1060006096959... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Action_Handlers#postponed-actions | Postponed Actions
If your action handler needs to apply data in a later stage of the request/response cycle it can register an action on
the VisitorInfo which can be consumed later. Currently only the response action scope is defined which is executed
in the onKernelResponse event, but more action scopes might be added... | Postponed Actions | [
0.007996564731001854,
-0.1359698623418808,
-0.16189654171466827,
-0.006286201532930136,
-0.14214879274368286,
-0.48396068811416626,
0.18223877251148224,
0.2108345627784729,
-0.14324058592319489,
0.41443154215812683,
0.013231865130364895,
-0.11962427943944931,
-0.04628204181790352,
0.105047... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Action_Handlers#admin-ui | Admin UI
To make your action handler appear in the admin UI, you need to create and register a JS class defining the admin interface
for your action. Create a class extending pimcore.settings.targeting.action.abstract and register it to the system by
calling pimcore.settings.targeting.actions.register().
Have a look at... | Admin UI | [
-0.25126180052757263,
-0.25181475281715393,
0.019869672134518623,
0.11555436998605728,
0.24474486708641052,
-0.239360973238945,
0.07539002597332001,
-0.02845444157719612,
-0.05097127705812454,
0.08476295322179794,
-0.1422176957130432,
0.4783412516117096,
-0.09924771636724472,
0.42081204056... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#targeting-storage | Targeting Storage
[TOC]
To persist data between requests, the targeting engine makes use of a targeting storage service which is responsible for
persisting the given data to a storage. In general, the storage always receives an instance of the VisitorInfo it should
store/retrieve data for and a scope which defines how ... | Targeting Storage | [
0.5120057463645935,
-0.28547582030296326,
-0.12730038166046143,
0.042132847011089325,
-0.04513830691576004,
-0.29085275530815125,
0.09071820974349976,
-0.39396652579307556,
-0.19617725908756256,
-0.06623967736959457,
-0.27988681197166443,
-0.3550429940223694,
0.2624233067035675,
0.08330453... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#configuring-the-targeting-storage | Configuring the Targeting Storage
The targeting storage needs to be defined as service and its service ID needs to be configured with the following config
entry:
pimcore_personalization:
targeting:
storage_id: Pimcore\Bundle\PersonalizationBundle\Targeting\Storage\CookieStorage
| Configuring the Targeting Storage | [
0.1269863098859787,
-0.2686792016029358,
-0.09366630017757416,
-0.1195111945271492,
0.2424861043691635,
-0.14210602641105652,
0.36647459864616394,
-0.09753333777189255,
-0.1835343986749649,
-0.0005065583391115069,
-0.25388509035110474,
-0.023069696500897408,
0.05974917113780975,
0.30305582... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#implement-a-custom-targeting-storage | Implement a Custom Targeting Storage
Basically, a targeting storage is a class implementing the TargetingStorageInterface
which is registered as service. Details how to handle data varies heavily on the underlying storage, but you can take the
core storages as starting point. | Implement a Custom Targeting Storage | [
0.3835340440273285,
-0.32252001762390137,
-0.16781915724277496,
0.019936535507440567,
0.10404150933027267,
-0.07503459602594376,
0.22347143292427063,
-0.22256340086460114,
0.09740039706230164,
0.2017451375722885,
-0.12950459122657776,
-0.012713066302239895,
-0.1998751014471054,
0.313945680... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#core-storage-implementations | Core Storage Implementations
Pimcore implements different storage engines which each has its pros and cons. In general it is recommended to start with
the default implementation - JWT signed cookie - and subsequently choose the engine which fits your requirements best.
In the future more storage implementations are pla... | Core Storage Implementations | [
0.025878602638840675,
-0.29322123527526855,
-0.16742557287216187,
0.08798011392354965,
-0.3233191967010498,
-0.33274298906326294,
0.10276380181312561,
-0.17858430743217468,
0.07759410887956619,
0.032074689865112305,
-0.36399513483047485,
-0.11175836622714996,
0.4023338854312897,
0.11636987... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#cookie-(default) | Cookie (default)
Stores data in a cookie in the user's browser. Can either be used with a plaintext cookie or with a JWT signed one to make
sure the cookie data isn't being tampered with. The cookie storage delegates the actual cookie write/read operation to a
CookieSaveHandler which does the actual cookie work. Below ... | Cookie (default) | [
0.24277275800704956,
-0.18351607024669647,
-0.13960327208042145,
-0.013643577694892883,
-0.245597243309021,
-0.10876096040010452,
0.22104446589946747,
-0.10673144459724426,
0.1293739378452301,
0.09293381124734879,
-0.18297907710075378,
-0.2774678170681,
0.05548650398850441,
0.1607475727796... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#db | Db
Stores data in the database.
Default session scope timeout: 30 minutes
Pros
Easy to use as no additional config is needed
Cons
Can only store data when a visitor ID is present as the ID is part of the primary key
DB can fill up quickly - not to be used on large sites
| Db | [
0.1053534597158432,
-0.4119141101837158,
-0.2736097276210785,
0.1943168193101883,
-0.24810099601745605,
0.1445079743862152,
0.377580463886261,
-0.3000463545322418,
0.00670419167727232,
-0.054900240153074265,
-0.11057741940021515,
-0.3657779395580292,
0.05542482063174248,
0.2461973875761032... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#redis | Redis
Stores data in a redis DB. To use this storage, define a service using the storage implementation as class and add connection
details to the service definition. An example is shipped with the core service definitions.
Default session scope timeout: 30 minutes
Pros
Can efficiently handle large amounts of data
Nat... | Redis | [
-0.040428049862384796,
-0.26593995094299316,
-0.2679150402545929,
0.014057240448892117,
-0.254075825214386,
-0.023594986647367477,
0.3641758859157562,
0.03598992899060249,
0.15909622609615326,
0.027067411690950394,
-0.19316907227039337,
-0.16637632250785828,
0.3006688356399536,
0.110401324... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Targeting_Storage#session | Session
Stores data in the session.
Default session scope timeout: PHP session timeout
To use the session storage, an additional config entry is needed as the session listeners are disabled by default for
performance reasons:
pimcore_personalization:
targeting:
# enable session support
session:
... | Session | [
-0.09460993111133575,
-0.4177277684211731,
-0.1424318552017212,
0.1582019180059433,
0.03715017810463905,
-0.1805199682712555,
0.42222779989242554,
-0.37800028920173645,
-0.2641546428203583,
0.12051626294851303,
-0.3547743260860443,
-0.14380992949008942,
0.183971107006073,
-0.03694421425461... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Frontend_Javascript#frontend-javascript | Frontend JavaScript
When targeting is enabled, a snippet of JavaScript in injected into every response. This snippet contains some information
needed by the frontend regarding the application state (e.g. if debug mode is enabled) and includes the script
pimcore/static6/js/frontend/targeting.js
which handles the fronten... | Frontend JavaScript | [
0.3052503168582916,
-0.6562827229499817,
-0.16393603384494781,
-0.1496778428554535,
0.1285431683063507,
-0.2664993703365326,
-0.007477973122149706,
-0.18009212613105774,
-0.005259539000689983,
0.04875744879245758,
-0.1768280267715454,
0.27257639169692993,
0.2791579067707062,
0.236401602625... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Frontend_Javascript#setting-a-custom-visitor-id | Setting a custom Visitor ID
The targeting.js exposes a method to set a visitor ID programmatically. By doing so, the visitor ID will be set and stored
in the visitor ID cookie which is delivered to the backend.
_ptg.api.setVisitorId('my-custom-visitor-id');
Make sure to use a unique visitor ID for each visitor!
| Setting a custom Visitor ID | [
0.309776246547699,
-0.3401356339454651,
-0.17480520904064178,
0.00787308532744646,
0.0838315561413765,
-0.2569173574447632,
0.31803804636001587,
-0.22238916158676147,
-0.022492321208119392,
0.11583833396434784,
-0.12209873646497726,
-0.023902760818600655,
0.18912968039512634,
0.20790325105... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Frontend_Javascript#changeextend-the-code-snippet-injected-into-the-response | Change/extend the code snippet injected into the Response
The code which is injected into the response is generated by the TargetingCodeGenerator
which fires a TargetingEvents::TARGETING_CODE
event. This event can be used to influence data and the used template which is used to render the code snippet:
<?php
// src... | Change/extend the code snippet injected into the Response | [
0.046252671629190445,
-0.31410232186317444,
-0.09910918027162552,
0.04197489470243454,
0.19645951688289642,
-0.36959749460220337,
0.045419320464134216,
0.202992245554924,
-0.18214376270771027,
0.19457769393920898,
-0.19006891548633575,
0.5080944299697876,
0.10775014013051987,
0.27274271845... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Frontend_Javascript#frontend-data-providers | Frontend Data Providers
Some conditions or data providers might need data from the frontend. To make this possible, a backend implementation can
call $visitorInfo->addFrontendDataProvider() during the matching process to inform the frontend that it needs data from
a specific provider. These frontend data providers n... | Frontend Data Providers | [
0.30607229471206665,
0.04359672963619232,
-0.10298287123441696,
0.07287363708019257,
0.12686075270175934,
-0.42524632811546326,
0.25323212146759033,
-0.13936540484428406,
-0.03508205711841583,
0.14581190049648285,
-0.011205675080418587,
-0.26961299777030945,
0.4445895254611969,
0.202144339... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation/Frontend_Javascript#implementing-a-custom-frontend-data-provider | Implementing a Custom Frontend Data Provider
Simply register your frontend data provider on the window._ptg.dataProviders object before targeting.js is loaded. As
example a simple provider which does nothing more than logging the current user agent to the console:
// /public/js/targeting/frontend.js
(function () {
... | Implementing a Custom Frontend Data Provider | [
-0.019993280991911888,
0.06606651842594147,
-0.02854848839342594,
-0.07858992367982864,
0.15660017728805542,
-0.31449127197265625,
0.23255550861358643,
-0.16699858009815216,
-0.08661426603794098,
0.348932683467865,
-0.18375924229621887,
0.07715586572885513,
0.06751813739538193,
0.248237133... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#development-documentation | Development Documentation
The following section describes the technical concepts and aspects of the Pimcore targeting engine. For usage
description and feature listing see your user docs
first. | Development Documentation | [
0.0006090657552704215,
-0.46812114119529724,
-0.1467742621898651,
0.0008982204017229378,
-0.042827434837818146,
-0.4142165780067444,
0.19304116070270538,
-0.5037588477134705,
-0.720260500907898,
0.17738863825798035,
-0.10678353905677795,
0.31232956051826477,
0.051329296082258224,
0.1601623... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#setup | Setup
You need to enable targeting either by setting the following config
pimcore_personalization:
targeting:
enabled: true
or using the cookie pimcore_targeting_enabled=1.
if you'd like to use geo-related conditions in your
targeting rules it's necessary to configure the underlying data ... | Setup | [
-0.02229432947933674,
-0.2015494853258133,
-0.17646440863609314,
-0.21017223596572876,
0.22124946117401123,
-0.4432486593723297,
0.4402546286582947,
-0.028911272063851357,
-0.16576041281223297,
0.037011127918958664,
-0.1935110092163086,
0.15054748952388763,
0.17173829674720764,
0.244731858... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#configuring-the-maxmind-geoip-data-provider | Configuring the MaxMind GeoIP Data Provider
Follow the official instructions for obtaining and updating the GeoIP database.
Store the database file at the location of your choice, the default location used by geoipupdate is /usr/share/GeoIP/GeoLite2-City.mmdb
Set the path to the database file in your parameters.yaml to... | Configuring the MaxMind GeoIP Data Provider | [
-0.10086411982774734,
0.23334720730781555,
0.00046056194696575403,
-0.01238013245165348,
0.17757141590118408,
-0.24991947412490845,
-0.12432202696800232,
0.032700374722480774,
-0.21650952100753784,
0.29086822271347046,
-0.17781437933444977,
0.4545946419239044,
0.2749631404876709,
0.1229869... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#basic-concepts | Basic concepts
Concept
Description
VisitorInfo
Contains run-time information on the current visitor and is used by all conditions and action handlers to collect/apply data.
DataProvider
Can be used by other components such as conditions to fetch data about the current visitor. E.g. the Device data provider loa... | Basic concepts | [
0.30861935019493103,
-0.202889084815979,
-0.11177976429462433,
0.26855191588401794,
-0.1632237583398819,
-0.4031822383403778,
0.09320131689310074,
-0.0480724535882473,
-0.23267142474651337,
-0.0712331086397171,
-0.15746191143989563,
-0.2864779531955719,
0.24511419236660004,
0.2618359923362... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.