url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#activitystore | ActivityStore
The ActivityStore is responsible for saving and reading activity data from/into the database. By default a MariaDb
implementation is used. The attributes of the activities just need to be a valid JSON object. There is no limitation in
the number of attributes and nesting of attributes. The MariaDB impleme... | ActivityStore | [
0.0950092300772667,
-0.32789549231529236,
-0.2200862318277359,
0.47579047083854675,
0.18179404735565186,
-0.08900801092386246,
-0.12073054909706116,
0.018667563796043396,
0.005636465270072222,
0.31557199358940125,
-0.30290651321411133,
-0.10820962488651276,
-0.04273012652993202,
0.07580787... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#activitymanager | ActivityManager
On top of the ActivityStore the ActivityManager is responsible for handling activities in the CMF. It's a relatively
lightweight component which just handles the process of tracking activities. Most of the work is done within the
ActivityStore - the ActivityManager is just responsible for putting everyt... | ActivityManager | [
0.23524029552936554,
-0.5221147537231445,
-0.11773548275232315,
0.004138793796300888,
0.29250943660736084,
0.28387680649757385,
0.16624976694583893,
-0.3298959732055664,
-0.18055634200572968,
0.2358175665140152,
-0.14512261748313904,
-0.12083689123392105,
-0.0929713025689125,
0.00190327025... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#tracking-an-activity | Tracking an activity
Example:
<?php
// $activity needs to implement ActivityInterface
\Pimcore::getContainer()->get('cmf.activity_manager')->trackActivity($activity);
| Tracking an activity | [
-0.5641804337501526,
-0.23498405516147614,
-0.18895696103572845,
0.1348487287759781,
0.11666177213191986,
-0.3663700520992279,
0.2800760567188263,
0.15499085187911987,
-0.25845786929130554,
0.4472079575061798,
0.14332637190818787,
0.09131574630737305,
-0.312375009059906,
0.1354194283485412... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#activityview | ActivityView
The CMF plugin contains a list view for displaying activities. This is added as a tab within the customer objects.
| ActivityView | [
-0.26526957750320435,
-0.3059084117412567,
-0.2773049771785736,
0.006436498370021582,
0.16260650753974915,
0.04497171938419342,
0.11946055293083191,
-0.027085790410637856,
-0.00124637340195477,
0.2847903072834015,
-0.3518003523349762,
0.07655950635671616,
-0.317436158657074,
0.109096661210... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#handle-how-activities-are-displayed-in-the-activityview | Handle how activities are displayed in the ActivityView
It's possible to handle how activities are displayed within the ActivityView by implementing the following three methods
of the ActivityInterface:
<?php
/**
* Returns an associative array with data which should be shown additional to the type and activity date... | Handle how activities are displayed in the ActivityView | [
-0.0598839670419693,
-0.3983200490474701,
-0.252170592546463,
0.2430417388677597,
0.17125752568244934,
-0.3805074393749237,
0.2683185040950775,
0.18366841971874237,
-0.19040636718273163,
0.13056634366512299,
-0.2021975815296173,
0.05401802062988281,
-0.10477450489997864,
0.1195029914379119... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#include-links-to-pimcore-elements-(e.g.-objects)-in-activity-view | Include links to Pimcore elements (e.g. objects) in activity view | Include links to Pimcore elements (e.g. objects) in activity view | [
-0.11020180583000183,
-0.16899830102920532,
-0.21847359836101532,
0.11393025517463684,
0.20184952020645142,
-0.40021175146102905,
0.16412751376628876,
0.12060089409351349,
0.004316325299441814,
0.048036009073257446,
-0.38560137152671814,
0.5976125597953796,
-0.05818227306008339,
0.26948270... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#example:-add-link-to-a-data-object-in-detail-view | Example: add link to a data object in detail view
<?php
public static function cmfGetDetailviewData(ActivityStoreEntryInterface $entry)
{
/**
* @var ActivityViewInterface $activityView
*/
$activityView = \Pimcore::getContainer()->get('cmf.activity_view');
return ['data object'=>$activi... | Example: add link to a data object in detail view | [
-0.31026822328567505,
-0.182138130068779,
-0.18385441601276398,
0.1286727488040924,
0.062127478420734406,
-0.26343005895614624,
-0.08452577888965607,
0.05954397842288017,
-0.2991500794887543,
0.2229434847831726,
0.07788525521755219,
0.5075892210006714,
0.019491245970129967,
0.1035680472850... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#example:-add-link-to-an-asset-in-overview-view-with-special-css-class-and-translation-key | Example: add link to an asset in overview view with special css class and translation key
<?php
public static function cmfGetDetailviewData(ActivityStoreEntryInterface $entry)
{
/**
* @var ActivityViewInterface $activityView
*/
$activityView = \Pimcore::getContainer()->get('cmf.activity_view'... | Example: add link to an asset in overview view with special css class and translation key | [
-0.47312501072883606,
-0.21284575760364532,
-0.2508663535118103,
0.11820386350154877,
0.3093451261520386,
-0.1769026666879654,
-0.05663011968135834,
0.3100455403327942,
-0.16702069342136383,
0.2107008844614029,
-0.13570764660835266,
0.29509735107421875,
0.026041485369205475,
-0.00841012410... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#activitystore-entry-metadata | ActivityStore entry metadata
It's possible to store metadata items for activity store entries. This could be useful for example for segment builders to store if an activity was already processed. | ActivityStore entry metadata | [
-0.018047979101538658,
-0.21016351878643036,
-0.24527296423912048,
0.07220256328582764,
0.35772204399108887,
-0.08879651129245758,
0.276577889919281,
-0.035309456288814545,
-0.33058813214302063,
0.11773299425840378,
-0.045283086597919464,
0.19815748929977417,
-0.27754145860671997,
0.187073... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#examples | Examples
<?php
$entry = $activityStore->getEntryById(465374);
//get all metadata items
$data = $entry->getMetadata();
//get single metadata item data
$data = $entry->getMetadataItem('BookingSegmentBuilder state');
//overwrite single metadata item
$entry->setMetadataItem('BookingSegmentBuilder state',... | Examples | [
-0.044528424739837646,
-0.14044176042079926,
-0.24731160700321198,
0.19909480214118958,
0.12729428708553314,
-0.24673907458782196,
0.15482355654239655,
0.24976547062397003,
-0.42045047879219055,
0.3701231777667999,
-0.09431096911430359,
0.30231285095214844,
0.012897958047688007,
0.04793349... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#customer-segments | Customer Segments
Customer segmentation is the practice of dividing a customer base into groups of individuals that are similar in specific
ways relevant to marketing, such as age, gender, interests and spending habits.
The customer management framework includes tools for creating and managing customer segments and seg... | Customer Segments | [
0.012912020087242126,
-0.25506341457366943,
-0.12475831061601639,
0.002979536773636937,
0.15465089678764343,
0.15362663567066193,
0.3655255138874054,
-0.04964319244027138,
-0.5897670984268188,
-0.0015245898393914104,
-0.2386346012353897,
-0.12118435651063919,
0.08336978405714035,
-0.134432... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#manual-vs.-calculated-segments | Manual vs. calculated segments
The customer object contains two separate object relation fields for manual and calculated segments. Manual segments are
added within the Pimcore backend UI by drag and drop. Calculated segments could be added by the CMF within the segment building
process.
| Manual vs. calculated segments | [
0.09198538959026337,
-0.12410194426774979,
-0.05842573568224907,
0.05387793481349945,
0.06769335269927979,
-0.3210044205188751,
0.4992561340332031,
-0.6035748720169067,
-0.524731457233429,
0.02116522751748562,
-0.3367396295070648,
0.11372060328722,
0.4987725019454956,
0.0628649964928627,
... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#optional:-use-path-formatter-for-an-alternative-version-of-displaying-the-related-customer-segments: | Optional: use path formatter for an alternative version of displaying the related customer segments:
Just add CustomerManagementFrameworkBundle\PathFormatter as formatter class to customer segment relation fields in the Pimcore class editor if you prefer this segment relation presentation. | Optional: use path formatter for an alternative version of displaying the related customer segments: | [
-0.3819844722747803,
-0.08247406035661697,
-0.17034660279750824,
0.20545367896556854,
0.21674254536628723,
-0.24870547652244568,
0.4585704803466797,
0.06170012429356575,
-0.45686423778533936,
0.003925017546862364,
-0.3465621769428253,
0.4368904232978821,
0.21348829567432404,
0.107674948871... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#segmentmanager | SegmentManager
The SegmentManager is responsible for managing, creating and reading CustomerSegments and CustomerSegmentGroups within
the CMF. Take a look at the SegmentManagerInterface
for additional inline PHP docs for each implemented method.
The SegmentManager is registered as CustomerManagementFrameworkBundle\Segm... | SegmentManager | [
-0.00004174709101789631,
0.04480341449379921,
-0.09917547553777695,
0.12947119772434235,
0.1730472892522812,
0.20779353380203247,
0.6244664192199707,
-0.33067750930786133,
-0.3678261339664459,
0.2976974546909332,
-0.14227516949176788,
-0.14600993692874908,
0.017726588994264603,
-0.33796659... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#segmentbuilders | SegmentBuilders
Segment builders are PHP classes which need to implement the
SegmentBuilderInterface.
They could be used to create automatically calculated segments based on the customer data. For example it would be possible
to create a SegmentBuilder "Age" which divides customers into segments of age groups... | SegmentBuilders | [
-0.20850998163223267,
-0.03073870576918125,
-0.1934056282043457,
0.1932387501001358,
-0.05942260101437569,
-0.039741870015859604,
0.5368638634681702,
0.04105730354785919,
-0.29160577058792114,
0.1719471514225006,
0.35679930448532104,
-0.23489201068878174,
0.06256259232759476,
0.05555917695... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#execute-on-customer-save-vs.-async | Execute on Customer Save vs. Async
SegmentBuilders can be implemented to be either executed directly on customer save or to be executed asynchronously via a cron job.
Take a look at the executeOnCustomerSave() method of the SegmentBuilderInterface. If this returns true it's executed
directly on customer save, otherwise... | Execute on Customer Save vs. Async | [
-0.28717041015625,
-0.08772461861371994,
-0.1251683235168457,
-0.07585014402866364,
-0.09163806587457657,
-0.4580855965614319,
0.48721662163734436,
-0.2460864782333374,
-0.2682558000087738,
0.3436189889907837,
0.24057377874851227,
0.21248281002044678,
-0.09410879760980606,
-0.0259856823831... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#create-your-own-segmentbuilder | Create your own SegmentBuilder
As mentioned above they need to implement the SegmentBuilderInterface. Most of the work is done in the
prepare(SegmentManagerInterface $segmentManager) and
calculateSegments(CustomerInterface $customer, SegmentManagerInterface $segmentManager) methods.
prepare() is called when a Segment... | Create your own SegmentBuilder | [
-0.16978269815444946,
-0.052034974098205566,
-0.13828374445438385,
0.11462816596031189,
0.09352346509695053,
-0.23525752127170563,
0.685505747795105,
-0.1461900919675827,
-0.29393404722213745,
0.2925434112548828,
-0.036294758319854736,
0.09108056128025055,
0.04210187867283821,
0.1083895787... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#segmentmanager-sample-calls: | SegmentManager sample calls:
<?php
/* Create a segment called "male" within the segment group "gender". The segment group "gender" will be created too if
it doesn't exist.
If the segment already exists it will not be reacreated but the existing segment will be returned.
*/
$segm... | SegmentManager sample calls: | [
-0.04466932266950607,
-0.1639406532049179,
-0.24226517975330353,
0.1172422468662262,
-0.02875738963484764,
-0.03515980392694473,
0.4715844392776489,
0.1180448830127716,
-0.4279462993144989,
0.10256971418857574,
-0.10128670185804367,
-0.07859272509813309,
-0.062039799988269806,
-0.268099248... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#optional:-store-the-creation-date-and-how-often-a-segment-was-added | Optional: Store the Creation Date and How Often a Segment was Added
The CMF offers a mechanism to handle potentially expiring segments by storing the creation date and a counter how often
a segment was added if it applies multiple times. For example, if there is a segment "interested in hiking", it might
be i... | Optional: Store the Creation Date and How Often a Segment was Added | [
-0.42009618878364563,
-0.030550582334399223,
-0.16041278839111328,
0.21685799956321716,
-0.1030765250325203,
-0.20539909601211548,
0.16973178088665009,
-0.06855315715074539,
-0.43064823746681213,
0.18672914803028107,
0.11145354062318802,
-0.2487632930278778,
-0.22582502663135529,
-0.011236... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#extract-segment-application-counter-of-customers | Extract segment application counter of customers
<?php
// get all segment application counters of a customer
$all = $segmentManager->getSegmentExtractor()->getAllSegmentApplicationCounters($customer);
/*
example result (segmentId => application counter)
[
6692709 => 1,
6694297 => 1,
669715... | Extract segment application counter of customers | [
-0.2124275118112564,
-0.35260751843452454,
-0.4119621515274048,
0.4588124454021454,
-0.03638465702533722,
-0.137965127825737,
0.2557981014251709,
0.15095174312591553,
-0.22265934944152832,
0.3433094322681427,
0.03421728312969208,
-0.06205826997756958,
0.07437758892774582,
-0.11886081099510... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#registration-of-segment-builders | Registration of Segment Builders
Segment builders need to be configured as services in the symfony service container. All segment builders which are
registered as services with the tag cmf.segment_builder will be executed during segment building process. | Registration of Segment Builders | [
-0.3282123804092407,
0.04818095266819,
-0.05248968303203583,
0.012292664498090744,
0.009398531168699265,
-0.21851879358291626,
0.5705496668815613,
0.0023365106899291277,
-0.19717012345790863,
0.23478318750858307,
0.17010772228240967,
-0.03587954491376877,
0.22510308027267456,
-0.0172148868... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#example-service-definitions | Example service definitions
services:
appbundle.cmf.segment_builder.state:
class: CustomerManagementFrameworkBundle\SegmentBuilder\StateSegmentBuilder
tags: [cmf.segment_builder]
appbundle.cmf.segment_builder.gender:
class: CustomerManagementFrameworkBundle\SegmentBuilde... | Example service definitions | [
-0.05687097832560539,
-0.16117402911186218,
-0.21015609800815582,
-0.05827295035123825,
0.2363176941871643,
0.09634613245725632,
0.5079129338264465,
0.13361774384975433,
-0.249995157122612,
0.12258270382881165,
0.07788440585136414,
0.19779440760612488,
-0.010705353692173958,
-0.00221309927... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#built-in-segment-builders | Built-in Segment Builders
The CMF framework includes some SegmentBuilders which can be used out of the box: | Built-in Segment Builders | [
-0.35781148076057434,
-0.33907049894332886,
-0.25095412135124207,
-0.0991666242480278,
0.07532232254743576,
-0.15988358855247498,
0.26928234100341797,
0.07952730357646942,
-0.4083499312400818,
0.2711128890514374,
0.008426466025412083,
0.13666579127311707,
-0.06840197741985321,
0.2239394932... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#agesegmentbuilder | AgeSegmentBuilder
Calculates age range segments based on a birthday field.
configuration option
description
segmentGroup
name of the segment group
birthDayField
name of the birthday field in the customer object
ageGroups
array of arrays to define the used age groups. Example: [[0,50],[51,100]] would result i... | AgeSegmentBuilder | [
0.038810085505247116,
-0.16092398762702942,
-0.20846199989318848,
0.3705472946166992,
-0.11740162968635559,
-0.021849121898412704,
0.6808027625083923,
-0.1433790773153305,
-0.05133897066116333,
0.11972156167030334,
-0.08507256954908371,
-0.25767210125923157,
0.42745742201805115,
-0.0985174... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#gendersegmentbuilder | GenderSegmentBuilder
Calculates segments based on the gender field.
configuration option
description
segmentGroup
name of the segment group
maleSegmentName
name of the male segment
femaleSegmentName
name of the female segment
notsetSegmentName
name of the segment if the gender of the customer is not male o... | GenderSegmentBuilder | [
0.09105101227760315,
-0.2813760042190552,
-0.16449443995952606,
0.21169887483119965,
0.1535380482673645,
-0.0617772676050663,
0.7003495693206787,
-0.0886395126581192,
-0.4497338831424713,
0.08209232985973358,
0.07617834955453873,
-0.22141358256340027,
0.4614269733428955,
-0.034292761236429... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#statesegmentbuilder | StateSegmentBuilder
Calculates state segments based on the zip field and zip ranges for each state. It currently works for AT, DE and CH
configuration option
description
segmentGroup
name of the segment group
countryTransformers
define the data transformers which should be used for each country - the data tran... | StateSegmentBuilder | [
-0.3454786241054535,
-0.0690363347530365,
-0.16956253349781036,
0.18258395791053772,
-0.11122079938650131,
-0.24812324345111847,
0.4187529981136322,
0.2442401647567749,
-0.033414483070373535,
0.18538923561573029,
0.013118388131260872,
0.29066604375839233,
0.5613996982574463,
0.413382709026... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#console-commands | Console commands
Following console commands are available for segment building process. | Console commands | [
-0.5430717468261719,
-0.346174031496048,
-0.2994336485862732,
-0.22527943551540375,
0.057942863553762436,
-0.0766848549246788,
0.36909109354019165,
0.23720683157444,
-0.5716875791549683,
0.23601168394088745,
-0.1620059311389923,
0.19616100192070007,
0.06093220412731171,
0.14193540811538696... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#build-segments-for-customers-in-the-changes-queue | Build Segments for Customers in the Changes Queue
This should be executed on regular basis, see also CronJobs:
php pimcore/cli/console.php cmf:build-segments
| Build Segments for Customers in the Changes Queue | [
-0.5291612148284912,
0.018894828855991364,
-0.29121077060699463,
-0.03345488756895065,
-0.1664612740278244,
-0.271984726190567,
0.22009813785552979,
-0.01470846775919199,
-0.4167006015777588,
0.2058115005493164,
0.27825236320495605,
0.1896437555551529,
-0.042847439646720886,
0.182290211319... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#build-segments-for-all-customers: | Build Segments for all Customers:
php pimcore/cli/console.php cmf:build-segments -f
| Build Segments for all Customers: | [
-0.48991870880126953,
-0.17995521426200867,
-0.28064677119255066,
0.0011460942914709449,
-0.013136913999915123,
-0.19242145121097565,
0.3270660638809204,
0.16129061579704285,
-0.5107181072235107,
0.3236624300479889,
-0.08682350814342499,
-0.004099780693650246,
0.1592997908592224,
0.2873937... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#build-segment-x-for-all-customers-(provide-symfony-service-id-of-segmentbuilder): | Build Segment x for all Customers (provide Symfony Service id of SegmentBuilder):
php pimcore/cli/console.php cmf:build-segments --segmentBuilder='appbundle.cmf.segment_builder.state'
| Build Segment x for all Customers (provide Symfony Service id of SegmentBuilder): | [
-0.4665604829788208,
0.08816487342119217,
-0.19091707468032837,
-0.014685978181660175,
0.027743112295866013,
-0.3321426808834076,
0.4419025778770447,
0.23788341879844666,
-0.24887284636497498,
0.2813309133052826,
-0.07752005755901337,
0.3736231327056885,
0.15587200224399567,
0.274016052484... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSegments#segment-assignment-to-pimcore-elements | Segment Assignment to Pimcore Elements
In addition to customers, it is also possible to assign segments to other Pimcore elements. So, elements like documents
can be tagged with segments. That information can be used later on for several use cases, e.g. tracking activities like
user xy has visited several pages that ar... | Segment Assignment to Pimcore Elements | [
0.08609721064567566,
-0.22533710300922394,
-0.2255404144525528,
0.09227432310581207,
0.13940955698490143,
-0.1419912427663803,
0.646094024181366,
-0.1619110107421875,
-0.4413791000843048,
0.13334715366363525,
-0.33017268776893616,
0.23087559640407562,
0.20122487843036652,
0.260987609624862... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#assigning-segments-to-pimcore-elements | Assigning Segments to Pimcore Elements
In addition to customers, it is also possible to assign segments to other Pimcore elements. So, elements like documents
can be tagged with segments. That information can be used later on for several use cases, e.g. tracking activities like
user xy has visited several pages that ar... | Assigning Segments to Pimcore Elements | [
0.07903075963258743,
-0.27594470977783203,
-0.1993253231048584,
0.11552466452121735,
0.07227010279893875,
-0.2052149921655655,
0.567586362361908,
-0.2331208437681198,
-0.3797092139720917,
0.06219400838017464,
-0.32850325107574463,
0.19726888835430145,
0.24402879178524017,
0.333389818668365... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#configuration | Configuration
The assignment of segments can be configured to better suit your needs in the configuration. | Configuration | [
-0.04518084600567818,
-0.3158215284347534,
-0.2977103590965271,
0.1049291342496872,
0.02571096457540989,
-0.17049936950206757,
0.6193104982376099,
-0.11244672536849976,
-0.2007102370262146,
0.2732168734073639,
-0.13458071649074554,
0.06318603456020355,
0.21450059115886688,
0.12875154614448... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#allowed-element-types | Allowed element types
The types of elements segments can be assigned to are specified within the symfony configuration.
The structure can be seen in the example below:
pimcore_customer_management_framework:
segment_assignment_classes:
types:
document:
page: true
email: true
... | Allowed element types | [
0.1115083172917366,
-0.3391852080821991,
-0.10912162810564041,
0.3487984836101532,
0.2582947611808777,
-0.28492215275764465,
0.4743984341621399,
0.06277422606945038,
-0.2325989454984665,
0.08753401786088943,
-0.3419507145881653,
0.17269842326641083,
0.13904139399528503,
0.27088525891304016... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#segment-assignment | Segment Assignment
To assign segments to elements, just open the additional Segment Assignment tab (which is visible as soon as the
segment assignment is activated for the certain type) and assign segments via drag & drop or the search function.
| Segment Assignment | [
-0.03576814383268356,
-0.4244001805782318,
-0.2321559190750122,
-0.07100585848093033,
0.11645444482564926,
-0.10293407738208771,
0.4307539463043213,
0.13388575613498688,
-0.11057151108980179,
0.34094950556755066,
-0.23110438883304596,
0.14581331610679626,
0.07078427076339722,
0.22758933901... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#inheritance | Inheritance
Assignments of segments are inherited along the element's tree so they can be conveniently set for whole groups of
elements.
However, this might not always be intended. | Inheritance | [
0.09366822987794876,
-0.41909313201904297,
-0.17920848727226257,
0.10053977370262146,
0.23905731737613678,
0.009186134673655033,
0.8612266182899475,
-0.03078208491206169,
-0.09720204770565033,
0.37917211651802063,
-0.12610633671283722,
-0.07939205318689346,
0.25124892592430115,
-0.14839857... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#breaking-the-chain-of-inheritance | Breaking the chain of inheritance
Using the checkbox, you can disable inheritance for any node in the tree and, by extension,
remove implicitly assigned segments of parents from that node's children.
| Breaking the chain of inheritance | [
0.06256908178329468,
-0.20213286578655243,
-0.2401295155286789,
0.16565372049808502,
0.17090041935443878,
-0.16055352985858917,
0.05357915163040161,
0.22506093978881836,
-0.11116840690374374,
0.2385353296995163,
-0.28505757451057434,
0.5071025490760803,
-0.11032761633396149,
-0.02043594978... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#use-assigned-segments-for-targeting-and-personalization | Use Assigned Segments for Targeting and Personalization
The assigned segment can be a valuable data source for targeting and personalization. Therefore Pimcore automatically
issues Track Segement actions every time a document with assigned segments is opened by an user. This information is
stored in the Targeting Store... | Use Assigned Segments for Targeting and Personalization | [
-0.015943391248583794,
-0.15943120419979095,
-0.1000056341290474,
0.1368473768234253,
-0.1405041664838791,
-0.24850669503211975,
0.4874546229839325,
-0.15317796170711517,
-0.4903597831726074,
-0.011889757588505745,
-0.3000594973564148,
0.29541298747062683,
0.03672829270362854,
0.1220197305... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#indexing | Indexing
As an effort towards scalable performance, assigned segments, both inherited and directly assigned,
are indexed in a separate table as a simple id mapping.
Whenever an element's assigned segments are saved using SegmentAssignerInterface,
that element and its children are queued to be indexed by IndexerInterfac... | Indexing | [
0.00544898072257638,
-0.18608398735523224,
-0.2313394397497177,
0.21537142992019653,
0.025624670088291168,
0.22956478595733643,
0.42650261521339417,
0.083904929459095,
0.11009984463453293,
0.35285717248916626,
-0.18788565695285797,
0.00014284499047789723,
0.19802448153495789,
-0.0572106875... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#working-with-assignments | Working with assignments | Working with assignments | [
0.23202843964099884,
-0.06083147972822189,
-0.3400476574897766,
-0.08910606056451797,
0.15883596241474152,
-0.15525780618190765,
0.35636675357818604,
-0.14325131475925446,
-0.18387246131896973,
0.4558027982711792,
0.1060061827301979,
0.2562394440174103,
-0.14996226131916046,
-0.07072490453... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#retrieving-assigned-segments-for-an-element | Retrieving assigned segments for an element
To retrieve segments assigned to a certain element,
SegmentManagerInterface::getSegmentsForElement and
SegmentManagerInterface::getSegmentsForElementId
return an array of fully hydrated CustomerSegments. | Retrieving assigned segments for an element | [
0.11843200773000717,
-0.5201088786125183,
-0.3044130802154541,
0.29309338331222534,
0.16595150530338287,
-0.2184174805879593,
0.5772585272789001,
-0.04467059299349785,
0.10079626739025116,
0.17540784180164337,
-0.33735746145248413,
-0.00548951793462038,
0.1017167791724205,
-0.1014928519725... |
https://pimcore.com/docs/platform//Customer_Management_Framework/SegmentAssignment#filter-elements-by-assigned-segments | Filter elements by assigned segments
When working with Pimcore listings, QueryServiceInterface
can provide you with a condition narrowing the results down to elements that are assigned a specific single segment,
one or more, or all segments in an array of ids.
The relevant element type is determined by the type of the ... | Filter elements by assigned segments | [
-0.3053804934024811,
-0.27555954456329346,
-0.244143545627594,
0.20790694653987885,
-0.24309365451335907,
-0.45096710324287415,
0.26394182443618774,
0.46046677231788635,
-0.0034475226420909166,
0.07248209416866302,
-0.3489069938659668,
0.16994769871234894,
-0.04877655580639839,
0.087632700... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerDuplicatesService#customer-duplicates-service | Customer Duplicates Service
The CMF ships with a Customer Duplicates Service which helps to find, merge and avoid duplicate entries. It consists of
three major parts:
Part 1 - Mechanisms for Searching Duplicates of a given Customer
Part 2 - Duplicates Index
Part 3 - Duplicates View
The first two Parts are for configu... | Customer Duplicates Service | [
0.16499291360378265,
-0.43390992283821106,
-0.12148995697498322,
-0.0741288959980011,
-0.20207707583904266,
0.1320800930261612,
0.23151138424873352,
-0.32686564326286316,
-0.2758193016052246,
-0.013102266006171703,
-0.31958523392677307,
-0.00036203322815708816,
0.15954214334487915,
-0.1097... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerDuplicatesService#part-1---mechanisms-for-searching-duplicates-of-a-given-customer: | Part 1 - Mechanisms for Searching Duplicates of a given Customer:
This is done directly via the database/customer object list. The duplicate service will find active customers where the
configured fields are equal to the given customer. Simple strtolower/trim transformations are done so that the
comparisons are case in... | Part 1 - Mechanisms for Searching Duplicates of a given Customer: | [
0.18063148856163025,
-0.14097869396209717,
-0.1709805577993393,
0.0038884999230504036,
-0.10830261558294296,
0.05190427973866463,
-0.041361503303050995,
-0.09068254381418228,
-0.2223505973815918,
0.006978737190365791,
-0.20667001605033875,
0.1182887852191925,
0.021629776805639267,
-0.07735... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerDuplicatesService#samples-for-part-1: | Samples for Part 1:
<?php
// Create a new Customer Instance
$customer = new Customer();
$customer->setBirthDate(new Date('1982-12-07'));
$customer->setFirstname("Markus");
$customer->setLastname("Moser");
$customer->setZip("5020");
$customer->setPublished(true);
$custom... | Samples for Part 1: | [
0.0855640396475792,
-0.10173048824071884,
-0.19679643213748932,
0.06984446942806244,
-0.04173395782709122,
0.0227418914437294,
0.22004076838493347,
-0.05389406904578209,
-0.17122714221477509,
0.16296698153018951,
0.14405833184719086,
-0.05103912577033043,
-0.1873577982187271,
-0.1425516754... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerDuplicatesService#part-2---duplicates-index | Part 2 - Duplicates Index
The duplicates index is used for searching globally for (fuzzy matching) duplicates. The found duplicates will be visible
in the customer duplicates view (see Part 3) and the user has the possibility to merge these duplicates manually.
In order to make a performant search for duplicates possib... | Part 2 - Duplicates Index | [
0.22457845509052277,
-0.2573961317539215,
-0.26632562279701233,
-0.02082175575196743,
-0.32866376638412476,
0.17590419948101044,
0.08294964581727982,
0.04471815004944801,
-0.012147670611739159,
0.0776229053735733,
-0.3188602328300476,
0.006796546280384064,
0.12124571204185486,
-0.299148678... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerDuplicatesService#example-config | Example Config
pimcore_customer_management_framework:
duplicates_index:
enableDuplicatesIndex: true
duplicateCheckFields:
- firstname:
soundex: true
metaphone: true
similarity: \CustomerManagementFrameworkBundle\DataSimilarityMatcher\SimilarText
zip:
simil... | Example Config | [
-0.22762203216552734,
-0.09910428524017334,
-0.08630126714706421,
0.13564790785312653,
-0.1081017479300499,
-0.06056497246026993,
0.2905401587486267,
0.04995543882250786,
-0.17874537408351898,
0.10763326287269592,
-0.2688494920730591,
0.40418392419815063,
0.07298599928617477,
-0.0024121324... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerDuplicatesService#console-command | Console Command
Following console command is available to calculate and update the duplicates index. If needed, it should be configured
as CronJob.
php pimcore/cli/console.php cmf:duplicates-index
Options:
-c - Calculate potential duplicates. This needs to run as cron job, for example once a day.
-a - Analyse false... | Console Command | [
-0.2562227249145508,
-0.2614611089229584,
-0.12511363625526428,
0.14683181047439575,
-0.36779484152793884,
-0.05639607831835747,
0.1263640969991684,
-0.060237761586904526,
-0.13747823238372803,
0.22280681133270264,
-0.2125970870256424,
0.251842737197876,
0.021929167211055756,
0.08505243062... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerDuplicatesService#part-3---duplicates-view | Part 3 - Duplicates View
The duplicates view is the frontend for manually checking, merging or declining potential duplicates found based on the
duplicates index.
It gets populated when the console commands of the duplicates index are executed and its usage should be quite self explaining.
| Part 3 - Duplicates View | [
0.19381959736347198,
-0.4455927312374115,
-0.15104825794696808,
-0.06967131793498993,
-0.26264306902885437,
0.15924619138240814,
0.25465914607048035,
0.0418042428791523,
0.14947833120822906,
-0.08804976940155029,
-0.18350909650325775,
0.004427962005138397,
0.041494425386190414,
-0.05538075... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ActionTrigger#actiontrigger-services---customer-automation-rules | ActionTrigger Services - Customer automation rules
The CMF plugin offers tools to automate customer related actions based on rules. Every rule consists of one or more
triggers, a condition and one or more actions.
Currently following implementations of triggers, conditions and actions are available:
Trigger
New Custo... | ActionTrigger Services - Customer automation rules | [
0.014238376170396805,
-0.4720442593097687,
-0.13825994729995728,
-0.20601385831832886,
-0.03227279335260391,
-0.16528019309043884,
0.3095102608203888,
-0.12118671089410782,
-0.2889655828475952,
-0.10036099702119827,
0.19339409470558167,
0.14251813292503357,
-0.29408976435661316,
0.15850646... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ActionTrigger#implement-custom-elements-of-rules | Implement Custom Elements of Rules
Custom implementations for triggers, conditions and actions can be added by additional bundles. To do so, the server-side
part and the frontend part have to be added by
implementing a php class in a certain namespace and extending an abstract class
implementing a javascript class in ... | Implement Custom Elements of Rules | [
0.0810028538107872,
-0.4541577994823456,
-0.14412908256053925,
-0.04040439426898956,
-0.18357402086257935,
-0.24509331583976746,
0.05172232538461685,
-0.022509055212140083,
0.03803601488471031,
0.12096200883388519,
0.29018938541412354,
0.17151224613189697,
-0.26948806643486023,
0.281935572... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync/LinkActivityTracking#link-activity-tracking | Link Activity Tracking
The CMF provides you with features to track opened links of newsletters as customer activities. So you can track activities
directly in customer object within Pimcore and use this information for further processing (like assigning customer
segments, etc.) and personalization. | Link Activity Tracking | [
-0.2764551043510437,
-0.27149003744125366,
-0.07972760498523712,
0.02946595475077629,
0.05969127267599106,
-0.025290321558713913,
0.07334677129983902,
-0.19063329696655273,
-0.0675392672419548,
0.1910325437784195,
-0.4302612543106079,
0.18053852021694183,
-0.3759467601776123,
0.13555604219... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync/LinkActivityTracking#functionality-in-a-nutshell | Functionality in a Nutshell
Central definition object for creating links in newsletters.
Created links link to a landing page and consider additional parameters for tracking
Campaign tracking in google analytics
with UTM parameter
Activity tracking for each customer in CMF
via cmfc parameter
by default filled wit... | Functionality in a Nutshell | [
-0.0647977963089943,
-0.5593844056129456,
0.03989551216363907,
-0.013399140909314156,
0.0042405943386256695,
0.027942735701799393,
-0.1420029103755951,
-0.2060491442680359,
0.09183650463819504,
0.08420953154563904,
0.01961173675954342,
-0.16458244621753693,
-0.17725589871406555,
0.14571945... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync/LinkActivityTracking#detailed-configuration-workflow | Detailed Configuration Workflow
Create LinkActivityDefinition object and fill out data (at least Type and Landing page link)
Link LinkActivityDefinition object in link in newsletter (just via d&d) - Pimcore generates corresponding link to landing page with all parameters.
Link will look like something like ... | Detailed Configuration Workflow | [
-0.12589940428733826,
-0.36277779936790466,
0.07362314313650131,
0.123728908598423,
0.009969865903258324,
-0.35656195878982544,
0.024938644841313362,
0.0058761537075042725,
0.08395616710186005,
-0.09720712900161743,
-0.29334425926208496,
0.33444857597351074,
-0.07761713862419128,
0.3761724... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync/LinkActivityTracking#additional-configuration | Additional Configuration
In CMF symfony configuration tree, there are two options for the link activity tracker:
activity_url_tracker:
enabled: true
# used for automatic link generation of LinkActivityDefinition data objects
linkCmfcPlaceholder: '*|ID_ENCODED|*'
enabled: Enable or di... | Additional Configuration | [
-0.18039445579051971,
-0.03323989361524582,
0.06275765597820282,
0.05984807014465332,
0.19542285799980164,
-0.11163077503442764,
0.3740457594394684,
0.0015818527899682522,
0.35209164023399353,
0.3546656668186188,
0.004109862260520458,
-0.07066182792186737,
-0.13297007977962494,
-0.08544207... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync/LinkActivityTracking#usage-in-combination-with-built-in-newsletter-sending | Usage in combination with built-in Newsletter sending
Link activity tracking can also be used with internal Pimcore newsletters. Configuration workflow stays the same, the
only thing that needs to be adapted it the linkCmfcPlaceholder in configuration tree:
activity_url_tracker:
enabled: true
# used... | Usage in combination with built-in Newsletter sending | [
-0.2498733550310135,
-0.2025453746318817,
0.03261210769414902,
0.06367425620555878,
0.055318206548690796,
-0.3569331765174866,
0.249838724732399,
-0.028637880459427834,
0.09977219253778458,
0.12199929356575012,
-0.18455098569393158,
0.41975969076156616,
-0.2557142674922943,
0.2673415839672... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync/MultipleMailchimpAccounts#multiple-mailchimp-accounts | Multiple Mailchimp Accounts
Optionally it's possible to configure the service container to be able to handle multiple mailchimp accounts. Principally it's handled the same way like newsletter lists via mailchimp provider handler services (see Configuration for an example definition)*[]:
But additionally to the standard... | Multiple Mailchimp Accounts | [
-0.13821527361869812,
0.11930393427610397,
-0.0426192544400692,
0.1985350102186203,
0.09757400304079056,
0.13507787883281708,
0.5644850730895996,
-0.07754465937614441,
0.47470682859420776,
0.3630561828613281,
-0.19719044864177704,
0.25304633378982544,
-0.05803857371211052,
0.17664590477943... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#mailchimpnewsletter-sync | MailChimp/Newsletter Sync
The CMF offers built-in support for synchronizing customer data with MailChimp. It synchronizes configured parts of the
customer data and optionally also can export mail templates based on Pimcore mail documents.
Other newsletter systems could be integrated too by implementing the NewsletterP... | MailChimp/Newsletter Sync | [
-0.3590339720249176,
-0.10008133947849274,
-0.06803500652313232,
-0.0036876399535685778,
-0.09777955710887909,
0.24925976991653442,
0.10073552280664444,
-0.009614112786948681,
0.17752163112163544,
0.3286188244819641,
-0.13054467737674713,
0.17315079271793365,
-0.15398605167865753,
0.171719... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#configuration | Configuration
The newsletter synchronisation has to be enabled in CMF configuration. Additional configurations are
newsletterQueueImmediateAsyncExecutionEnabled: customer is synchronized with MailChimp on every save.
MailChip API settings.
Further than that, the CMF can handle multiple MailChimp lists. Each list is ... | Configuration | [
-0.16440267860889435,
0.047269370406866074,
0.001576278475113213,
0.12310630828142166,
0.07410934567451477,
0.29075658321380615,
0.2665294408798218,
-0.13040748238563538,
0.3211576044559479,
0.42914095520973206,
-0.23395781219005585,
-0.01423026341944933,
-0.0025258369278162718,
-0.2293696... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#prepare-data-objects-for-mailchimp-sync | Prepare Data Objects for MailChimp Sync | Prepare Data Objects for MailChimp Sync | [
-0.22444353997707367,
0.0014387000119313598,
-0.10304028540849686,
0.11105198413133621,
0.017773782834410667,
0.1695827692747116,
0.0967903584241867,
0.1537119448184967,
0.44391173124313354,
0.2656356394290924,
0.01261059194803238,
0.1285504549741745,
-0.1475440412759781,
0.218508869409561... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#customer | Customer
It's needed to add a newsletterStatus and mailchimpStatus field into the customer class for each MailChimp list:
The fields need to be named with the shortcut of the associated provider handler as a suffix (e.g. newsletterStatusList1
and mailchimpStatusList1).
The newsletter status is a project-specific setti... | Customer | [
0.04254420846700668,
0.19448606669902802,
-0.15639524161815643,
0.3665105402469635,
0.17507536709308624,
-0.022223083302378654,
0.30110764503479004,
-0.04174783080816269,
0.4359518885612488,
0.3635534942150116,
-0.17757457494735718,
0.22735805809497833,
-0.079464390873909,
-0.0268941130489... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#customersegmentgroup | CustomerSegmentGroup
Besides customers, also customer segments can be exported as interest groups to MailChimp. To configure that, add a checkbox
called exportNewsletterProvider{PROVIDER_HANDLER_SHORTCUT} for each list to the CustomerSegmentGroup class.
See below for more details. | CustomerSegmentGroup | [
-0.17907185852527618,
0.05715714395046234,
-0.11302848905324936,
0.1647057682275772,
0.075405552983284,
0.4034084677696228,
0.5662550330162048,
0.04241175204515457,
0.23389416933059692,
0.17792107164859772,
-0.4851275086402893,
0.17976517975330353,
-0.04094643145799637,
0.1907481998205185,... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#exporting-customers-to-mailchimp | Exporting Customers to MailChimp | Exporting Customers to MailChimp | [
-0.03002874180674553,
-0.044142890721559525,
-0.2791411578655243,
0.03390694037079811,
0.1357429027557373,
0.23921625316143036,
0.4608105421066284,
-0.0055402484722435474,
0.45062026381492615,
0.3317171037197113,
-0.17188894748687744,
-0.011805055662989616,
-0.07394997030496597,
0.20301856... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#newsletter-queue | Newsletter Queue
Exporting customer data to MailChimp is handled asynchronously. This means, that each time when a customer get's saved it
will be added to the newsletter queue (represented by a database table).
A cronjob in the background, which should run every few minutes, then processes the queue items. If they wer... | Newsletter Queue | [
0.2181427776813507,
-0.19573423266410828,
-0.05102846398949623,
0.19789953529834747,
-0.4587567448616028,
0.2611446678638458,
0.15275830030441284,
-0.27841925621032715,
0.4511663019657135,
0.22410008311271667,
0.06263808906078339,
-0.02300873026251793,
-0.13157935440540314,
-0.180458560585... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#immediate-execution-of-export-on-customer-save | Immediate execution of export on customer save
Although the export is handled asynchronously it is possible to enable that a queue entry will be processed immediately
after a customer is saved. This will still run as background task. The queue will be only triggered asynchronously exactly
for the saved customer. If the... | Immediate execution of export on customer save | [
-0.07275386899709702,
-0.1814907044172287,
-0.05290843918919563,
-0.18301917612552643,
-0.1703338474035263,
-0.1027640849351883,
0.36821669340133667,
-0.3737030029296875,
-0.038266997784376144,
0.20777948200702667,
0.13689135015010834,
-0.13551747798919678,
-0.018887128680944443,
0.0587823... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#webhook | Webhook
The CMF offers a MailChimp webhook endpoint to receive updates from MailChimp. The webhook is implemented as webservice
and is handled the same way as the REST webservice in the Pimcore core.
So the steps to enable the webhook are as following:
Enable the Pimcore core webservice feature.
Create a Pimcore user ... | Webhook | [
-0.32233184576034546,
-0.17445433139801025,
-0.09314700216054916,
-0.03087693266570568,
-0.164505735039711,
0.19068241119384766,
-0.0021277600899338722,
-0.08336121588945389,
0.1980273425579071,
0.14154836535453796,
-0.39106741547584534,
0.24478664994239807,
0.03382531926035881,
0.14807133... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#cronjob-for-syncing-data-from-mailchimp-to-pimcore | Cronjob for syncing data from MailChimp to Pimcore
The webhook makes it possible that updates in MailChimp are synced in more or less real time to Pimcore. But sometimes
this might not work (for example when the server is down). Therefore the CMF offers an additional cronjob, which could
run once a day and synchronize ... | Cronjob for syncing data from MailChimp to Pimcore | [
-0.3558548390865326,
-0.2092103511095047,
-0.10701651871204376,
-0.050433289259672165,
-0.36710453033447266,
0.1771424561738968,
-0.03791721910238266,
0.011141826398670673,
0.23108580708503723,
0.35801514983177185,
0.07078853994607925,
0.2835511565208435,
-0.206268772482872,
0.210201621055... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#exporting-customersegments-to-mailchimp | Exporting CustomerSegments to MailChimp
Customer segment exports are handled by the newsletter queue too (see above). MailChimp has a limit of 60 interest groups
(the equivalent for CustomerSegments in MailChimp) per list. Therefore the CMF offers a configuration option for what
CustomerSegmentGroups should be exported... | Exporting CustomerSegments to MailChimp | [
-0.15767614543437958,
0.008018414489924908,
-0.15211956202983856,
0.1856875866651535,
0.17822256684303284,
0.15197351574897766,
0.4914865791797638,
0.021480316296219826,
0.116762176156044,
0.35710427165031433,
-0.3974926471710205,
-0.07239510118961334,
0.00775059312582016,
0.00708849355578... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#exporting-newsletter-templates-to-mailchimp | Exporting newsletter templates to MailChimp
As soon as the newsletter sync is enabled, a "Export Template to MailChimp" button will appear in email documents:
With this it's possible to create the newsletter within Pimcore and then use it for emailing campaigns within MailChimp. | Exporting newsletter templates to MailChimp | [
-0.2768273651599884,
-0.08088639378547668,
0.01905568689107895,
0.03193085640668869,
0.0290084108710289,
-0.03226154297590256,
0.03384110704064369,
0.16097921133041382,
0.17442487180233002,
0.2994757294654846,
-0.18141861259937286,
0.4265629053115845,
-0.16252866387367249,
0.36308997869491... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#logging | Logging
The CMF logs MailChimp sync related changes on three different levels:
Customer activities are tracked on each MailChimp status change
In the notes and events tab of the customer a list of successful exports will be shown.
Errors are logged into the application logger.
| Logging | [
0.005762908142060041,
-0.05322212353348732,
-0.02125842496752739,
0.25067320466041565,
-0.30226972699165344,
0.114188052713871,
-0.002743854420259595,
-0.3228708505630493,
0.22285011410713196,
0.2022547721862793,
0.05712446942925453,
-0.02151467464864254,
-0.27213937044143677,
-0.028904050... |
https://pimcore.com/docs/platform//Customer_Management_Framework/NewsletterSync#addressing-a-customer-segment-with-pimcore's-own-newsletter-functionality | Addressing a customer segment with Pimcore's own newsletter functionality
The CMF comes equipped with its own address source adapter, selectable from the Newsletter Sending Panel in newsletter documents.
Here multiple customer segments can be selected to send a newsletter to all customers related to any of them.
For t... | Addressing a customer segment with Pimcore's own newsletter functionality | [
-0.10293804854154587,
-0.330404669046402,
-0.020467139780521393,
0.040345076471567154,
0.20583438873291016,
-0.13686732947826385,
0.575205385684967,
-0.2032037377357483,
-0.21881850063800812,
0.31854119896888733,
-0.3265482187271118,
0.246895432472229,
0.003541052108630538,
0.1075458601117... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#webservice | Webservice
The CMF plugin has a built-in REST webservice. Access is handled via API-Keys, which can be configured
for Pimcore Users in settings menu of CMF.
Add the API-Key as X-API-Key HTTP header (recommended) or apikey url parameter to your request.
The webservices also support session authentication, this means tha... | Webservice | [
-0.17940734326839447,
-0.17290186882019043,
-0.13679619133472443,
-0.08558531850576401,
-0.05033699795603752,
-0.17868810892105103,
0.051494549959897995,
-0.16421696543693542,
-0.13756103813648224,
0.3757161498069763,
-0.05849948525428772,
0.16443386673927307,
0.2294069528579712,
0.1294301... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#api-reference | API Reference | API Reference | [
0.04021725058555603,
-0.16586712002754211,
-0.3433080315589905,
-0.02913201041519642,
0.0495108887553215,
-0.30697450041770935,
0.1271536499261856,
0.11156017333269119,
0.14335690438747406,
0.2658202648162842,
0.05541926249861717,
0.2744326889514923,
0.061559900641441345,
0.053541459143161... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#customers-api | Customers API
The customers API implements standard REST calls for customer CRUD actions:
Path
Method
Description
/__customermanagementframework/webservice/customers
GET
Fetch all customers
/__customermanagementframework/webservice/customers/{id}
GET
Fetch a single customer
/__customermanagementframework/web... | Customers API | [
0.224992036819458,
0.004380418919026852,
-0.32151514291763306,
-0.10378681868314743,
-0.1930997371673584,
-0.1791376769542694,
-0.10843595117330551,
0.06605803221464157,
-0.01983976736664772,
-0.09600652009248734,
0.05586251989006996,
0.1884557008743286,
0.31321194767951965,
-0.05702408403... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#activities-api | Activities API
The activities API implements standard REST calls for activity CRUD actions:
Path
Method
Description
/__customermanagementframework/webservice/activities
GET
Fetch all activities
/__customermanagementframework/webservice/activities/{id}
GET
Fetch a single activity
/__customermanagementframewor... | Activities API | [
0.1329447627067566,
-0.20509406924247742,
-0.2889964282512665,
-0.08611121773719788,
-0.1170310452580452,
-0.37485626339912415,
-0.28919491171836853,
0.21493197977542877,
-0.15854808688163757,
0.05262802168726921,
-0.03783946856856346,
0.17201557755470276,
0.16066521406173706,
-0.010006378... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#deletions-api | Deletions API
The deletions API delivers information about deletions of customers and activities:
Path
Method
Description
/__customermanagementframework/webservice/deletions
GET
Fetch all segments
The request can be filtered by passing the following params as query params:
Parameter
Possible Values
Descrip... | Deletions API | [
0.29830899834632874,
0.143095463514328,
-0.3125573396682739,
0.3666309416294098,
-0.4503208100795746,
-0.1990206390619278,
0.0613800548017025,
0.14657704532146454,
-0.20897531509399414,
-0.07033238559961319,
-0.16080228984355927,
0.2504858672618866,
0.009341652505099773,
-0.290043979883193... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#segments-api | Segments API
The segments API implements standard REST calls for customer segment CRUD actions:
Path
Method
Description
/__customermanagementframework/webservice/segments
GET
Fetch all segments
/__customermanagementframework/webservice/segments/{id}
GET
Fetch a single segment
/__customermanagementframework/w... | Segments API | [
0.10354457050561905,
-0.187563955783844,
-0.2588423490524292,
-0.10466784983873367,
-0.20097613334655762,
-0.24317829310894012,
-0.03290513530373573,
0.28042545914649963,
-0.2946840822696686,
0.022783342748880386,
0.012204228900372982,
0.16402587294578552,
0.3080954849720001,
0.03158353269... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#segment-groups-api | Segment groups API
The segment groups API implements standard REST calls for customer segment group CRUD actions:
Path
Method
Description
/__customermanagementframework/webservice/segment-groups
GET
Fetch all segment groups
/__customermanagementframework/webservice/segment-groups/{id}
GET
Fetch a single segmen... | Segment groups API | [
0.14413347840309143,
-0.15647760033607483,
-0.2511581778526306,
-0.15326479077339172,
-0.23114460706710815,
-0.18068259954452515,
0.18063129484653473,
0.2704554796218872,
-0.3060302436351776,
0.0359918512403965,
-0.1708565205335617,
0.10902891308069229,
0.38245028257369995,
-0.150283873081... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Webservice#segments-of-customers-api | Segments of customers API
The segments of customers API allows to add segments to customers and remove segments form customers:
Path
Method
Description
/__customermanagementframework/webservice/segments-of-customers
POST
Add/remove segments
Example POST body JSON:
{
"customerId": 12345,
&quo... | Segments of customers API | [
0.30978983640670776,
0.07218004763126373,
-0.297197163105011,
-0.02116149663925171,
-0.07627909630537033,
0.01508273370563984,
0.13950622081756592,
0.07522985339164734,
-0.08159841597080231,
-0.057559311389923096,
-0.1516258716583252,
0.13955001533031464,
0.427325576543808,
-0.039108719676... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#list-views | List Views
The CMF provides two additional views for visualizing the data in Pimcore backend UI. | List Views | [
-0.3493330478668213,
-0.2700629234313965,
-0.2774147689342499,
-0.03360585495829582,
-0.06605090200901031,
-0.03773534670472145,
0.09812649339437485,
0.09931718558073044,
-0.06652200222015381,
0.20845571160316467,
-0.43390846252441406,
0.38005805015563965,
0.07139367610216141,
0.2286869436... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#customer-view | Customer View
The customer view is a list view of customers with additional filter and export functionality and few configuration
possibilities. It can be opened via the main menu in Pimcore backend UI and lists all customers that are matching the
filter criteria independently of their location in the object tree. Alth... | Customer View | [
-0.050561413168907166,
-0.12344644963741302,
-0.30453261733055115,
-0.00108703866135329,
-0.17785833775997162,
-0.20107558369636536,
0.06169026345014572,
0.04255567118525505,
-0.12568987905979156,
-0.03130945563316345,
-0.5941263437271118,
0.22135215997695923,
0.049513667821884155,
0.22164... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#configuration-options | Configuration options
Search Columns: In CMF configuration it can be configured which columns should be considered
during searching and filtering in the customer list. For details see the CMF configuration section.
Filter for Segments: The customer view also allows for filtering based on assigned segments. This can... | Configuration options | [
0.08626631647348404,
-0.012229959480464458,
-0.2532051205635071,
0.07836318016052246,
0.03953956812620163,
0.10127117484807968,
0.17324383556842804,
0.08355395495891571,
-0.009510435163974762,
0.010517735965549946,
-0.42708519101142883,
-0.03508877009153366,
0.17215794324874878,
0.05090506... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#advanced-filter-settings | Advanced Filter Settings
For reuse of defined filters, it is possible to save a configured filter. The advanced filter setting are
only available when accessing the customer view via the menu and will be hidden when viewing customers of a specific segment.
Every user can add new filters and update their existing filter... | Advanced Filter Settings | [
-0.13235799968242645,
-0.23294512927532196,
-0.2241871953010559,
-0.22479961812496185,
0.021824322640895844,
-0.21504388749599457,
0.2811625897884369,
-0.21518106758594513,
-0.07640379667282104,
0.1322334110736847,
-0.47200825810432434,
0.0947566032409668,
-0.06337673217058182,
0.229898169... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#creating-new-filters | Creating new filters
All Users will have the possibility to select, save and update their defined filters by defining filter criteria for
customer fields in the Customer section and select segments in the Segments section.
By clicking the Save Filter button a new dialog will be opened. In this dialog the filter can als... | Creating new filters | [
-0.1150449737906456,
-0.012499065138399601,
-0.278754323720932,
-0.32690879702568054,
-0.22072374820709229,
-0.2433832287788391,
0.18989689648151398,
-0.11873506754636765,
0.12016419321298599,
0.1333741992712021,
-0.36049938201904297,
0.017451990395784378,
-0.03984462469816208,
0.235415935... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#sharing-filters | Sharing filters
Users can access filters shared with them either via the customers menu and by selecting the filter or directly via the menu
if the Shortcut Available option was set for the filter.
Users can re-share their shared filters when they have the Share configurations permission by clicking the Share Filter
b... | Sharing filters | [
0.10123104602098465,
-0.12631013989448547,
-0.2499852329492569,
-0.13640107214450836,
-0.293681263923645,
-0.16177435219287872,
0.18807558715343475,
-0.40280064940452576,
-0.02947300113737583,
0.2245805859565735,
-0.6778655052185059,
0.004179387353360653,
-0.03965068235993385,
0.3073942363... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#creating-new-customer-object | Creating new customer object
For quickly adding new customers a button is available inside the Filters section beside the filter selection. This button is
only available if the user has save permission to temporary new customer directory set in CMF configuration
key pimcore_customer_management_framework -> customer_... | Creating new customer object | [
-0.12103552371263504,
-0.2154025137424469,
-0.08082791417837143,
-0.21075493097305298,
0.125069722533226,
0.10460592061281204,
0.0064969672821462154,
-0.4305161237716675,
-0.16989748179912567,
0.31699416041374207,
-0.3185489773750305,
0.16616952419281006,
0.05914059653878212,
-0.0178204532... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#activity-view | Activity View
The activity view provides a overview of all activities of a certain customer and is shown as additional tab in the
customer object editor.
For each activity also a detail page is available. | Activity View | [
0.12349116802215576,
-0.3029283285140991,
-0.16424107551574707,
0.023494599387049675,
0.058215800672769547,
0.07929819077253342,
0.27278366684913635,
-0.024105284363031387,
-0.018700389191508293,
0.13943032920360565,
-0.39529597759246826,
-0.07510071992874146,
-0.2508484423160553,
0.034539... |
https://pimcore.com/docs/platform//Customer_Management_Framework/ListViews#configuration-options | Configuration options
Activity details in list view: The information of an activity shown in the activity list is defined by the activity
implementation with the method
public static function cmfGetOverviewData(ActivityStoreEntryInterface $entry).
It should return an associative array of all data that should be shown... | Configuration options | [
0.009174645878374577,
-0.591838002204895,
-0.21363933384418488,
0.2485547661781311,
0.17950111627578735,
-0.24467366933822632,
0.09370371699333191,
-0.038190968334674835,
-0.3026508390903473,
0.35468387603759766,
-0.21541078388690948,
0.20297832787036896,
0.19081389904022217,
-0.0461143851... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#additional-conditions-and-actions-to-pimcore-global-targeting-rules | Additional Conditions and Actions to Pimcore Global Targeting Rules
The CMF adds following conditions and action to the Pimcore Global Targeting Rules: | Additional Conditions and Actions to Pimcore Global Targeting Rules | [
-0.02842310629785061,
-0.35261431336402893,
-0.12482556700706482,
-0.26179584860801697,
0.09410692751407623,
-0.5278485417366028,
0.04225591942667961,
-0.022011416032910347,
-0.2099241018295288,
0.030924325808882713,
-0.1317254602909088,
0.3176192343235016,
-0.1073986291885376,
0.359490334... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#condition-[cmf]-has-segment | Condition [CMF] Has Segment
This condition checks if the current user has the given segment assigned. There are two data sources supported:
Targeting storage with tracked segments (see also Action [CMF] Track Segment).
User profile with assigned segments.
To consider these data sources use the checkboxes Consider Tra... | Condition [CMF] Has Segment | [
-0.0855788066983223,
-0.38577160239219666,
-0.18931837379932404,
-0.09356193989515305,
-0.2652454078197479,
-0.3340459167957306,
0.36464861035346985,
0.1090790331363678,
-0.08435790240764618,
0.1461484432220459,
0.1718936711549759,
-0.21576674282550812,
-0.24604614078998566,
0.129714399576... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#condition-[cmf]-customer-logged-in | Condition [CMF] Customer Logged-In
This condition checks if currently a user is logged in. There are no further config options to this condition.
| Condition [CMF] Customer Logged-In | [
-0.16876618564128876,
-0.5574711561203003,
-0.1694822907447815,
-0.25003212690353394,
-0.11432220786809921,
-0.12069720029830933,
0.2195250391960144,
0.03423872962594032,
-0.09599924832582474,
0.20473898947238922,
0.19323217868804932,
-0.13612666726112366,
-0.0853588730096817,
-0.078878581... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#condition-[cmf]-customer-segments-have-changed | Condition [CMF] Customer Segments have changed
This condition checks if the segments of the currently logged-in user have changed. If no user is logged in, condition
always returns null. There are no further config options to this condition.
| Condition [CMF] Customer Segments have changed | [
-0.17891274392604828,
-0.40120264887809753,
-0.12299846112728119,
-0.08357663452625275,
-0.2114984542131424,
-0.3058849275112152,
0.30957117676734924,
0.08826059103012085,
-0.2170657515525818,
0.1427600085735321,
0.2651864290237427,
-0.23296977579593658,
-0.18618105351924896,
-0.0923096314... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#action-assign-target-group | Action Assign Target Group
The CMF extends the default Assign Target Group action with following options:
Assign connected Customer Segment to logged-in Customer: If a user is logged-in, the action checks if there is
a segment object connected to the given target group. If so, it assigns it to the customer object.
T... | Action Assign Target Group | [
-0.019799349829554558,
-0.5307722091674805,
-0.05229274928569794,
-0.4375753700733185,
-0.11235343664884567,
-0.10361083596944809,
0.4216230809688568,
-0.20168201625347137,
-0.19686166942119598,
0.056633129715919495,
-0.10455707460641861,
0.037103161215782166,
-0.049881357699632645,
0.1434... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#action-[cmf]-track-segment | Action [CMF] Track Segment
The Track Segment action stores the given segment to the Targeting Storage of the current user. This information can
be used later on, e.g. with the Has Segment condition.
| Action [CMF] Track Segment | [
-0.13352714478969574,
-0.40094560384750366,
-0.1502372771501541,
-0.08981893956661224,
-0.05381316691637039,
-0.17388378083705902,
0.3004183769226074,
0.06402689963579178,
-0.43037301301956177,
0.18165108561515808,
0.14701373875141144,
-0.21632175147533417,
-0.44867604970932007,
0.16105902... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#action-[cmf]-track-activity | Action [CMF] Track Activity
The Track Activity action tracks an activity of the given Activity Type to the currently logged in user.
Consider profiling consent: If a user is logged-in, the action checks the profilingConsent attribute of the user.
If profilingConsent is not true, the action will be ignored.
It does n... | Action [CMF] Track Activity | [
-0.22493195533752441,
-0.6066785454750061,
-0.07650937885046005,
-0.27564752101898193,
-0.16335973143577576,
-0.0881640836596489,
0.02525206282734871,
0.008695335127413273,
-0.10347357392311096,
0.1533014476299286,
0.24106194078922272,
-0.25658729672431946,
-0.4792076647281647,
0.285600066... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Targeting_Role_Components#action-[cmf]-apply-target-groups-from-assigned-customer-segments | Action [CMF] Apply Target Groups from Assigned Customer Segments
The Apply Target Groups from Assigned Customer Segments action applies all customer segements from the currently
logged-in customer that are linked to a target group to the targeting engine. This might be necessary for keeping information
stored in the cu... | Action [CMF] Apply Target Groups from Assigned Customer Segments | [
0.2065962255001068,
-0.30271491408348083,
-0.1021115705370903,
-0.387712299823761,
-0.07729805260896683,
-0.11983677744865417,
0.10698404163122177,
-0.18737468123435974,
-0.25770020484924316,
-0.12291859090328217,
-0.08789044618606567,
-0.016520407050848007,
0.1936085969209671,
0.051254633... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Action_Trigger_Service_Components#special-triggers,-conditions-and-actions-in-cmf-action-trigger-service | Special Triggers, Conditions and Actions in CMF Action Trigger Service
In addition to the Pimcore Global Targeting Rules there are also additional triggers, conditions and actions for integration
of Targeting with the CMF Action Trigger Service. | Special Triggers, Conditions and Actions in CMF Action Trigger Service | [
-0.01196057628840208,
-0.5289468765258789,
-0.054371584206819534,
-0.2723057270050049,
-0.04715242609381676,
-0.3454975485801697,
-0.024942688643932343,
-0.1818317025899887,
-0.1892649382352829,
-0.028400976210832596,
-0.0641925185918808,
0.2420489639043808,
-0.10412026941776276,
0.3395050... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Action_Trigger_Service_Components#trigger-[targeting]-segment-tracked | Trigger [Targeting] Segment Tracked
This trigger fires every time a segment is tracked to the Targeting Store - for example by a Global Targeting Rule or
when a document with an assigned segment is opened by an user. There are no further configuration
options, it only stores the segment for later use in conditions and ... | Trigger [Targeting] Segment Tracked | [
-0.16374963521957397,
-0.5933029651641846,
-0.0893150120973587,
-0.2649565041065216,
-0.03635316342115402,
-0.21449941396713257,
0.4369559586048126,
0.0862833708524704,
-0.2095022350549698,
-0.09217501431703568,
0.10372304171323776,
0.1303802728652954,
-0.32855233550071716,
0.2766882181167... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Action_Trigger_Service_Components#trigger-[targeting]-assigned-target-group | Trigger [Targeting] Assigned Target Group
This trigger is fired every time a target group is assigned to the current user - either by a Global Targeting Rule or
when a document with an assigned target group is opened by an user.
This trigger can be used to modify customer objects (e.g. assigning segments, changing valu... | Trigger [Targeting] Assigned Target Group | [
0.29728177189826965,
-0.5714883804321289,
-0.11766970902681351,
-0.19877099990844727,
0.038313332945108414,
-0.05633329972624779,
0.4960583448410034,
-0.31741806864738464,
-0.1339292973279953,
-0.01455348264425993,
-0.02544596791267395,
0.20602697134017944,
0.07296185940504074,
0.035850849... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Personalization/Additional_Action_Trigger_Service_Components#condition-[targeting]-tracked-segments-count | Condition [Targeting] Tracked Segments Count
This condition can check how often the tracked segment is tracked in the Targeting Storage. It always uses the segment
stored by the Segment Tracked trigger.
Optionally the condition can be restricted to certain segments by adding segments to the list.
| Condition [Targeting] Tracked Segments Count | [
0.07760791480541229,
-0.4688006341457367,
-0.17012155055999756,
0.07757152616977692,
-0.03742782399058342,
-0.2833288311958313,
0.3069711923599243,
-0.00824015587568283,
-0.09477902203798294,
0.1366100311279297,
0.27729764580726624,
-0.21616587042808533,
-0.3162209093570709,
0.262629151344... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.