url stringlengths 50 196 | text stringlengths 3 17.2k | heading stringlengths 2 103 | embeddings list |
|---|---|---|---|
https://pimcore.com/docs/platform//Targeting/Development_Documentation#visitorinfo-and-visitor-id | VisitorInfo and Visitor ID
When a request is handled, the targeting engine first creates a new VisitorInfo instance. This instance is a data container
which will be used throughout the targeting process to store and pass data between different components of the system.
See Visitor Info for details. | VisitorInfo and Visitor ID | [
0.4010084271430969,
-0.2569584846496582,
-0.057575661689043045,
0.49854567646980286,
-0.029489412903785706,
-0.19713963568210602,
0.16056177020072937,
-0.41754406690597534,
-0.3706369996070862,
0.1748083382844925,
-0.30823540687561035,
-0.2414795458316803,
0.3594307005405426,
0.19485111534... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#target-rule-matching | Target Rule Matching
After building the VisitorInfo and resolving the visitor ID, the matching engine processes every defined targeting rule.
Based on the rule's scope a rule might be skipped (e.g. a session rule is applied only once per session). Every condition
gets the instance of the VisitorInfo and needs to decide... | Target Rule Matching | [
0.31926071643829346,
-0.28000345826148987,
-0.07538110017776489,
0.22090351581573486,
-0.23406097292900085,
-0.36850276589393616,
0.12319065630435944,
-0.12439336627721786,
-0.12713810801506042,
-0.2052290439605713,
-0.15906551480293274,
-0.2948700487613678,
0.2927398681640625,
0.130500718... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#targeting-storage | Targeting Storage
Some data needs to be persisted between requests. To do so, the targeting implementations makes use of a TargetingStorage
which implements a key-value store for targeting data. Data can be set for the visitor (valid for the whole lifetime of a
visitor) or for the session level. When storing data to an... | Targeting Storage | [
0.4616525173187256,
-0.3367089331150055,
-0.11471804231405258,
-0.017892491072416306,
-0.027485476806759834,
-0.10557393729686737,
0.204705148935318,
-0.41063711047172546,
-0.10008259862661362,
0.04562012106180191,
-0.10196975618600845,
-0.29787060618400574,
0.35587048530578613,
0.01653724... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#content-targeting | Content Targeting
After matching all rules, a VisitorInfo may have different assigned target groups. When rendering a document which has
targeted content for multiple target groups, the following logic is applied to determine which version to use for the
current visitor:
If the visitor has only one assigned target gro... | Content Targeting | [
0.30643200874328613,
-0.5737475156784058,
-0.09568320214748383,
0.2581816613674164,
-0.2086317241191864,
-0.20867317914962769,
0.2319139540195465,
0.3223297595977783,
-0.47071099281311035,
-0.043610602617263794,
-0.43649381399154663,
0.022749245166778564,
0.3726195693016052,
-0.11594177037... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#manually-applying-content-targeting | Manually applying Content Targeting
The logic defined above can be applied to any document. Documents which are loaded through Pimcore's standard routing and
rendering features will be automatically configured, but you also manually configure any document to use personalized content
by using the DocumentTargetingConfig... | Manually applying Content Targeting | [
-0.00894480012357235,
-0.09286285191774368,
-0.07927024364471436,
-0.1865158975124359,
-0.10655122995376587,
-0.241208016872406,
0.15335778892040253,
0.10860945284366608,
-0.3556245267391205,
-0.08041778206825256,
-0.2712738513946533,
0.4497683644294739,
0.025010928511619568,
-0.0214804280... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#extending-the-targeting-engine | Extending the Targeting Engine
The targeting engine is designed in a way to be easily extendable by third party code to extend and customize the engine's
behaviour.
See the following resources for further details:
Conditions
Data Providers
Action Handlers
Targeting Storage
Frontend Javascript
| Extending the Targeting Engine | [
0.33352530002593994,
-0.1507367491722107,
-0.21440109610557556,
-0.15515491366386414,
0.1236223503947258,
-0.14471346139907837,
0.1193803921341896,
0.010358327999711037,
-0.02648048661649227,
0.10774971544742584,
-0.10494817048311234,
0.1309954822063446,
0.04203290119767189,
0.315220087766... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#debugging-targeting-data | Debugging Targeting Data
As shown above, targeting date is added to the Symfony profiler. In addition you can enable a dedicated targeting toolbar
which also works outside the dev environment when you are logged into the admin interface.
The toolbar is only shown if a pimcore_targeting_debug cookie exists and is set a... | Debugging Targeting Data | [
-0.11305854469537735,
-0.14382751286029816,
-0.043140728026628494,
-0.050695911049842834,
-0.09157737344503403,
-0.30072909593582153,
0.319164514541626,
0.04491635411977768,
-0.23099170625209808,
0.17861397564411163,
-0.028710342943668365,
0.1539410501718521,
0.004802983719855547,
0.054341... |
https://pimcore.com/docs/platform//Targeting/Development_Documentation#opt-in-for-targeting | Opt-in for Targeting
A user has the possibility to enable targeting at any time, by setting the following cookie `pimcore_targeting_enabled=1` .
Since privacy laws vary from country to country, we recommend that you consult with your legal team or company to check what needs to be done before using this features.
| Opt-in for Targeting | [
-0.16264960169792175,
-0.4009380340576172,
-0.20027372241020203,
-0.3208400011062622,
0.06300698965787888,
-0.2815950810909271,
0.36542370915412903,
-0.18995052576065063,
-0.08645071089267731,
0.19682817161083221,
-0.1941452920436859,
0.062092993408441544,
-0.07146691530942917,
0.086070261... |
https://pimcore.com/docs/platform//Targeting/Installation#installation | Installation | Installation | [
-0.06728437542915344,
-0.4834894835948944,
-0.3417288661003113,
0.20734061300754547,
0.06259846687316895,
0.09173910319805145,
-0.07573223114013672,
-0.07214274257421494,
0.15155638754367828,
0.1816904991865158,
-0.07461769878864288,
0.14365136623382568,
0.041423697024583817,
0.05546558648... |
https://pimcore.com/docs/platform//Targeting/Installation#installation-process | Installation Process
Install bundle via composer:
composer require pimcore/personalization-bundle
Enable bundle in config/bundles.php:
return [
...
Pimcore\Bundle\PersonalizationBundle\PimcorePersonalizationBundle::class => ['all' => true],
...
];
Install bundle via console:
bin/console pimcore:bund... | Installation Process | [
-0.23164908587932587,
-0.12572021782398224,
-0.1546722948551178,
0.1891338974237442,
0.16866526007652283,
-0.0860680341720581,
0.03564898297190666,
-0.0013364080805331469,
-0.4538208246231079,
0.3608667552471161,
-0.08466745167970657,
0.5722777247428894,
-0.27618148922920227,
0.04459123685... |
https://pimcore.com/docs/platform//Targeting/Installation#config | Config
:::info
By default, targeting would be disabled. To enable it, you can either use the cookie pimcore_targeting_enabled=1 or set the following config:
:::
pimcore_personalization:
targeting:
enabled: true
| Config | [
-0.25913262367248535,
-0.42047396302223206,
-0.08193561434745789,
-0.0449969619512558,
0.2324948012828827,
-0.40527620911598206,
0.26399677991867065,
0.11557396501302719,
-0.48201242089271545,
0.1707506775856018,
-0.23239392042160034,
0.18525898456573486,
0.09783752262592316,
0.13139556348... |
https://pimcore.com/docs/platform//Targeting/Installation#uninstallation | Uninstallation
Before uninstalling the bundle, the Target Group references must be removed from DataObject classes, Custom services and Ecommerce Pricing Rules manually. | Uninstallation | [
0.06547928601503372,
-0.20914021134376526,
-0.05844093859195709,
0.08010891079902649,
0.230341374874115,
0.04721350595355034,
0.45676910877227783,
-0.2670750617980957,
-0.2695271372795105,
-0.02977154403924942,
-0.3069877326488495,
0.3761754035949707,
-0.012305199168622494,
0.2630829513072... |
https://pimcore.com/docs/platform//Targeting#behavioral-targeting-and-personalization | Behavioral Targeting and Personalization
Pimcore provides a very powerful integrated behavioral targeting and personalization engine. With this toolkit, it is possible to profile visitors based on their behavior, assign target groups to them and provide personalized content to
these target groups. This makes it possibl... | Behavioral Targeting and Personalization | [
0.08271699398756027,
-0.3819553256034851,
-0.24549387395381927,
-0.06066310033202171,
0.0694786086678505,
-0.053921401500701904,
0.1290547400712967,
-0.0735686793923378,
-0.5185784697532654,
-0.02667311765253544,
-0.2713257670402527,
0.2391098439693451,
0.03821837529540062,
0.3816835582256... |
https://pimcore.com/docs/platform//Targeting#features-in-a-nutshell | Features in a Nutshell
Add behavioral targeting and personalization to Pimcore.
Allow defining target groups.
Set up visitor profiling with rules based on their behavior.
Allow creating personalized versions of documents for defined target groups.
Deliver personalized content to target groups.
| Features in a Nutshell | [
-0.033054351806640625,
-0.27085059881210327,
-0.22208000719547272,
-0.18053650856018066,
-0.27856388688087463,
-0.10128284990787506,
0.10330833494663239,
-0.014367739669978619,
-0.5025750994682312,
0.02828069217503071,
-0.22541669011116028,
0.3220377266407013,
-0.07436255365610123,
0.51149... |
https://pimcore.com/docs/platform//Targeting#documentation-overview | Documentation Overview | Documentation Overview | [
-0.03861241042613983,
-0.42126035690307617,
-0.20801925659179688,
0.0011644525220617652,
0.0821869745850563,
0.09083638340234756,
0.2739754319190979,
-0.20000715553760529,
-0.5904796123504639,
0.17860756814479828,
0.01674804836511612,
0.03403441607952118,
0.1729377955198288,
-0.07302177697... |
https://pimcore.com/docs/platform//Targeting#usage-documentation | Usage Documentation
Pimcore Concepts for Personalization
How to Personalize Content
Define Target Groups
Setup Visitor Profiling
Create Personalized Content
Deliver Personalized Content
Examples for Personalization and Targeting
| Usage Documentation | [
0.2025144398212433,
-0.19598731398582458,
-0.1709013283252716,
-0.07856737822294235,
0.022534852847456932,
-0.13137763738632202,
0.24140521883964539,
-0.2571386694908142,
-0.5596909523010254,
0.14803002774715424,
0.020462285727262497,
0.3053326904773712,
0.11682097613811493,
0.321068406105... |
https://pimcore.com/docs/platform//Targeting#development-documentation | Development Documentation
Installation
Setup and Basic Concepts
Visitor Info
Conditions
Data Providers
Action Handler
Targeting Storage
Frontend JavaScript
| Development Documentation | [
0.2686331272125244,
0.1709395796060562,
-0.2562647759914398,
-0.019150398671627045,
0.07818911969661713,
-0.4130975008010864,
0.3819716274738312,
-0.05706373229622841,
0.008607955649495125,
0.1332547813653946,
0.2624216675758362,
-0.32001709938049316,
0.2536548674106598,
0.4865285158157348... |
https://pimcore.com/docs/platform//Newsletter/Installation#installation | Installation | Installation | [
-0.06728437542915344,
-0.4834894835948944,
-0.3417288661003113,
0.20734061300754547,
0.06259846687316895,
0.09173910319805145,
-0.07573223114013672,
-0.07214274257421494,
0.15155638754367828,
0.1816904991865158,
-0.07461769878864288,
0.14365136623382568,
0.041423697024583817,
0.05546558648... |
https://pimcore.com/docs/platform//Newsletter/Installation#minimum-requirements | Minimum Requirements
Pimcore >= 11
| Minimum Requirements | [
-0.4867402911186218,
-0.6527405977249146,
-0.2514899969100952,
0.17473745346069336,
0.09657440334558487,
-0.25538256764411926,
0.05260014906525612,
-0.00007801126776030287,
-0.08331926167011261,
0.37539610266685486,
0.07385749369859695,
0.20967018604278564,
-0.11901111155748367,
0.27251827... |
https://pimcore.com/docs/platform//Newsletter/Installation#installation-process | Installation Process
Install bundle via composer:
composer require pimcore/newsletter-bundle
Enable bundle in config/bundles.php:
return [
...
Pimcore\Bundle\NewsletterBundle\PimcoreNewsletterBundle::class => ['all' => true],
...
];
Install bundle via console:
php bin/console pimcore:bundle:install ... | Installation Process | [
-0.209943950176239,
-0.1667143553495407,
-0.07290173321962357,
0.1707278937101364,
0.047954458743333817,
0.0005635517300106585,
0.05318889394402504,
0.07122974097728729,
-0.3082810938358307,
0.22763118147850037,
-0.0714053139090538,
0.51485675573349,
-0.12178628891706467,
-0.12765233218669... |
https://pimcore.com/docs/platform//Newsletter/Installation#config-options | Config options
#### SYMFONY MAILER TRANSPORTS
framework:
mailer:
enabled: true
transports:
pimcore_newsletter: smtp://user:pass@smtp.example.com:port
messenger:
routing:
'Pimcore\Bundle\NewsletterBundle\Messenger\SendNewsletterMessage': pimcore_core ... | Config options | [
0.01188315637409687,
-0.056603096425533295,
0.007093753665685654,
0.14706376194953918,
0.0938454270362854,
-0.14838451147079468,
0.45043158531188965,
0.069410540163517,
0.1491062492132187,
0.29724258184432983,
0.01201014593243599,
0.0739336758852005,
0.06753498315811157,
-0.186404943466186... |
https://pimcore.com/docs/platform//Newsletter/Installation#uninstallation | Uninstallation
Uninstalling the bundle does not clean up newsletter documents only the predefined document types. Before uninstalling make sure to remove or archive all dependent documents.
You can also use the following command to clean up you database. Create a backup before executing the command. All data will be lo... | Uninstallation | [
-0.037286896258592606,
-0.00571778230369091,
-0.013209871016442776,
0.17135582864284515,
0.009110958315432072,
0.18289631605148315,
-0.09702298045158386,
0.044024135917425156,
-0.20618247985839844,
0.0035821564961224794,
-0.2857973277568817,
0.5069743394851685,
-0.007353345397859812,
-0.13... |
https://pimcore.com/docs/platform//Newsletter/Installation#best-practice-and-example | Best Practice and Example
See Newsletter Config for a complete example and how to set up your newsletter. | Best Practice and Example | [
0.1038091853260994,
-0.20340022444725037,
-0.09954376518726349,
-0.06779114902019501,
-0.10834354907274246,
-0.1780826449394226,
0.297570139169693,
-0.2489841878414154,
0.060285624116659164,
0.3600218892097473,
0.12161393463611603,
0.005831337533891201,
-0.008418330922722816,
-0.0576664730... |
https://pimcore.com/docs/platform//Newsletter/Installation#document-types | Document Types
This bundle introduces a new document type:
Type
Description
Newsletter
Like an email but specialized for newsletter
| Document Types | [
0.18361273407936096,
-0.14395761489868164,
-0.11125687509775162,
-0.04268314316868782,
0.02533211000263691,
0.2044120579957962,
0.1917717307806015,
0.20465397834777832,
-0.03491504117846489,
-0.046472471207380295,
-0.16251249611377716,
-0.00988063309341669,
-0.31442543864250183,
0.31913626... |
https://pimcore.com/docs/platform//Newsletter/Installation#pimcore-twig-extensions | Pimcore Twig Extensions
This bundle also adds a new twig extension. For more information checkout the main documentation
Test
Description
pimcore_document_newsletter
Checks if object is instanceof Newsletter
| Pimcore Twig Extensions | [
-0.07892647385597229,
-0.3894931674003601,
-0.0887022614479065,
0.10189551115036011,
-0.11005242168903351,
0.004565604496747255,
0.17449809610843658,
0.20961306989192963,
-0.0797499343752861,
0.16610971093177795,
-0.047929469496011734,
0.5121033191680908,
-0.30386555194854736,
-0.186862707... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Documents#newsletter-document | Newsletter Document
Newsletter documents are the way to create and send newsletters directly within Pimcore.
They are based on the normal Pimcore documents and therefore support everything as pages do - starting from MVC pattern
and template creation to document composing within Pimcore backend with areas, drag&dro... | Newsletter Document | [
0.07215452939271927,
-0.24053938686847687,
0.050875525921583176,
-0.0024350984022021294,
-0.10799378901720047,
-0.08644003421068192,
-0.20263086259365082,
0.08970262110233307,
-0.26626330614089966,
0.08337526768445969,
-0.12935863435268402,
0.28995558619499207,
0.04092317447066307,
0.08215... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Documents#additional-settings | Additional Settings
Newsletter documents provide following additional settings compared to default documents:
Subject: Subject of the newsletter.
From: From-Address of the newsletter. As fallback, Pimcore system settings are used.
Add Tracking Parameters to Links: Adds tracking parameters to all links within the news... | Additional Settings | [
-0.07799776643514633,
-0.35185298323631287,
0.10174373537302017,
0.2306511104106903,
0.0024288168642669916,
-0.17001928389072418,
0.08527480065822601,
0.1444922536611557,
-0.13851356506347656,
0.2709018290042877,
-0.10945229977369308,
0.32996657490730286,
0.0477483868598938,
-0.10668078064... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Documents#newsletter-sending | Newsletter Sending
The Newsletter Sending Panel provides the functionality for sending the newsletter.
| Newsletter Sending | [
0.061970777809619904,
-0.33168748021125793,
-0.04790153726935387,
-0.18592196702957153,
-0.07941258698701859,
0.11905933916568756,
0.29590344429016113,
-0.07368380576372147,
0.12957751750946045,
0.1517956405878067,
-0.004411817528307438,
0.21392503380775452,
0.04498985409736633,
0.12167434... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Documents#address-source-adapter | Address Source Adapter
The Address Source Adapter is responsible for extracting the email addresses the newsletter should be sent to. It has to
be selected before another action can take place. Currently following adapters ship with Pimcore. It is easily possible
to integrate custom adapters - see section below.
Defau... | Address Source Adapter | [
0.020664216950535774,
-0.405895471572876,
0.06207353621721268,
0.19738730788230896,
-0.016192292794585228,
-0.06255237758159637,
0.44769832491874695,
-0.29350385069847107,
0.34686344861984253,
0.34181711077690125,
-0.1332869678735733,
0.36917608976364136,
0.10036823153495789,
0.25628331303... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Documents#test-sending | Test Sending
Once a Address Source Adapter is selected, a test sending to a specified email address can be made with the button
Send Test-Newsletter. | Test Sending | [
-0.15897251665592194,
-0.4007711112499237,
-0.018794270232319832,
-0.0477374792098999,
-0.1516496241092682,
-0.15413904190063477,
0.4995100498199463,
-0.1309308558702469,
0.3458799719810486,
0.3403696119785309,
0.13934315741062164,
0.04425304755568504,
-0.08454357087612152,
0.3581074476242... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Documents#sending-the-newsletter | Sending the Newsletter
With Send Newsletter Now the newsletter is sent to all recipients. The sending itself is done based on the system
settings of Pimcore. There you also can configure an external SMTP sending service for mass mail sending. | Sending the Newsletter | [
0.06332230567932129,
-0.35370421409606934,
-0.004446456208825111,
-0.011812057346105576,
-0.18842199444770813,
-0.0750848799943924,
0.08758345246315002,
-0.14703652262687683,
-0.07268423587083817,
0.2811262905597687,
-0.07852490246295929,
0.325376957654953,
0.061134546995162964,
0.10137253... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Documents#creating-a-custom-address-source-adapter | Creating a Custom Address Source Adapter
It is easily possible to implement custom address source adapter. Following files have to be created:
JavaScript Class: This class defines the user interface in the sending panel. It has to be located in
the namespace pimcore.document.newsletters.addressSourceAdapters, named li... | Creating a Custom Address Source Adapter | [
0.09548237174749374,
-0.27933982014656067,
0.048995181918144226,
0.11552683264017105,
0.2042289823293686,
-0.27277350425720215,
0.5262704491615295,
-0.2985694408416748,
0.24640823900699615,
0.3096122741699219,
-0.0659458264708519,
0.26479169726371765,
-0.01803453266620636,
0.27687826752662... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#newsletter-configuration | Newsletter Configuration | Newsletter Configuration | [
0.18006139993667603,
-0.5263422727584839,
-0.10656633973121643,
0.14538808166980743,
0.058035966008901596,
0.20395776629447937,
0.22951345145702362,
-0.19140014052391052,
0.1384556144475937,
0.3462318181991577,
0.039074525237083435,
-0.045254044234752655,
-0.02982177399098873,
-0.051499489... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#general | General
The main advantage is that you can send completely customized / personalized newsletters by using all the data stored
in the system (products, ...).
The content of the e-mail is rendered individually for every recipient (the user object is available in the action and view),
this gives you the absolute freedom f... | General | [
-0.03609326481819153,
-0.4457237124443054,
-0.0391526035964489,
0.3803008496761322,
0.006479357834905386,
0.067509725689888,
-0.04165045917034149,
0.08856160938739777,
-0.1318967342376709,
0.2233142852783203,
-0.489788293838501,
0.30558690428733826,
-0.13141269981861115,
-0.037747047841548... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#basic-setup | Basic Setup
Class definition
The class definition below shows how to build a class used by the newsletter list.
The purpose of the fields gender, firstname, lastname and email should be clear.
newsletterActive and newsletterConfirmed are used to save the state of the user (also used by the frontend framework).
The new... | Basic Setup | [
0.22084560990333557,
0.028186671435832977,
-0.06143117696046829,
0.12123455852270126,
0.33881404995918274,
-0.017702385783195496,
0.21305157244205475,
-0.028302069753408432,
0.37203776836395264,
0.286138653755188,
0.1251353919506073,
0.13760003447532654,
-0.06512466818094254,
-0.0345436669... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#url-prefix-for-static-assets | URL prefix for static assets
You are able to configure the default URL prefix in order to make sure, that your static assets
(e.g. images or CSS files) are getting prefixed correctly.
pimcore_newsletter:
default_url_prefix: 'https://my-host.com'
| URL prefix for static assets | [
-0.18571586906909943,
-0.34114933013916016,
-0.07994141429662704,
-0.07754161953926086,
0.2881714403629303,
-0.2308816760778427,
0.2867116630077362,
0.2001953125,
-0.05695602297782898,
0.18056635558605194,
-0.06411461532115936,
0.1758883148431778,
0.19232775270938873,
-0.1970522403717041,
... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#newsletter-frontend-framework | Newsletter Frontend Framework
Once you have setup your data class, it's possible to use the newsletter frontend framework.
This simple framework allows you to create a hassle free subscribe/confirm/unsubscribe workflow. | Newsletter Frontend Framework | [
-0.20840679109096527,
0.009512457996606827,
-0.09985315799713135,
-0.07266303151845932,
0.17163600027561188,
-0.15600095689296722,
0.03554230183362961,
-0.08735945075750351,
0.1090872585773468,
0.4355471730232239,
0.11385540664196014,
0.11089165508747101,
-0.19123223423957825,
0.2833372950... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#example | Example | Example | [
-0.039029549807310104,
-0.4887920916080475,
-0.3070780634880066,
0.04008098319172859,
-0.14495046436786652,
-0.15570281445980072,
0.2727290093898773,
0.16836415231227875,
-0.006077707279473543,
0.44112470746040344,
0.5344760417938232,
0.21058650314807892,
-0.14281579852104187,
0.0040315156... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#controller | Controller
For example, \NewsletterController: src/Controllers/NewsletterController.php
<?php
namespace App\Controller;
use Pimcore\Bundle\NewsletterBundle\Tool\Newsletter;
use Pimcore\Model;
use Symfony\Component\HttpFoundation\Request;
use Symfony\Component\HttpFoundation\Response;
class NewsletterController e... | Controller | [
-0.08766808360815048,
0.030693141743540764,
-0.10825829952955246,
0.17386475205421448,
0.20654714107513428,
-0.0892772227525711,
0.088128000497818,
0.17681710422039032,
0.012383581139147282,
0.2423567771911621,
-0.132988840341568,
0.11010084301233292,
0.015984250232577324,
-0.2643945813179... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#views | Views
The subscribe action view: templates/Newsletter/subscribe.html.twig
{% extends 'layout.html.twig' %}
{% set request = app.request %}
{% if not success %}
{% if request.get('submit') %}
<div class="alert alert-danger">
{{ "Sorry, something went wrong, please check the ... | Views | [
0.17889483273029327,
-0.38511860370635986,
-0.16586974263191223,
0.05738389119505882,
0.1900407373905182,
-0.132204070687294,
0.06276876479387283,
0.21899932622909546,
0.06017734482884407,
0.24057427048683167,
-0.006546963471919298,
0.10166411846876144,
0.13342350721359253,
0.1456702500581... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#confirmation-e-mail | Confirmation E-Mail
The confirmation e-mail (See: \Pimcore\Tool\Newsletter::sendConfirmationMail) is a simple e-mail document.
In this document the following Twig parameters are available:
{{ firstname }}
{{ lastname }}
{{ token }}
{{ email }}
{{ gender }}
{{ object.someMethod }}
In the document editmode ... | Confirmation E-Mail | [
0.346962571144104,
-0.21894338726997375,
0.08886991441249847,
-0.03458119183778763,
-0.009074300527572632,
-0.11616138368844986,
-0.027743034064769745,
-0.13698013126850128,
-0.31664615869522095,
0.29592010378837585,
0.05233283340930939,
0.42835184931755066,
-0.02570376545190811,
0.1165734... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#sending-newsletters | Sending Newsletters | Sending Newsletters | [
0.21247713267803192,
-0.3008522093296051,
-0.23421169817447662,
0.12286745011806488,
0.06647448241710663,
0.03201156109571457,
0.1850852370262146,
0.09535615891218185,
0.05913686007261276,
0.2919028401374817,
0.1667368859052658,
-0.11616037786006927,
-0.11725950986146927,
-0.12798443436622... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#create-a-newsletter-document | Create a Newsletter Document
To send a newsletter you need an email document, which is used as content for the newsletter (nothing special to consider).
In this document the following Twig parameters are available:
{{ firstname }}
{{ lastname }}
{{ token }}
{{ email }}
{{ gender }}
{{ object.someMethod }}
... | Create a Newsletter Document | [
0.32321643829345703,
-0.14828012883663177,
-0.053919121623039246,
0.015160403214395046,
0.14414861798286438,
0.02198614738881588,
0.2595740556716919,
0.12412799149751663,
-0.0692063719034195,
0.3287043869495392,
0.1704469472169876,
0.1276150941848755,
-0.010375184938311577,
-0.055078629404... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#get-userdata-in-the-email-template | Get UserData in the Email Template
$userObject = $this->getParam('object');
$firstname = $userObject->getFirstname();
$lastname = $userObject->getLastname();
...
In the example below, you can find out how to add the unsubscribe link and how to use firstname in the content.
| Get UserData in the Email Template | [
0.26833873987197876,
-0.178602397441864,
-0.04143634811043739,
0.24954083561897278,
0.11523736268281937,
0.11591120809316635,
-0.02678331360220909,
-0.2505532205104828,
-0.04947603866457939,
0.5397197008132935,
0.057905081659555435,
-0.20869269967079163,
-0.07523101568222046,
-0.0832682177... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#send-a-test-message | Send a Test Message
In newsletter documents, there is additional tab in the top panel, it's called Newsletter Sending Panel.
It's a good practise to check newsletter before it would be used with real emails.
| Send a Test Message | [
0.03798767179250717,
-0.24549268186092377,
-0.08876064419746399,
-0.0745265856385231,
-0.06522096693515778,
-0.03529013320803642,
0.25747567415237427,
0.09571459144353867,
0.14204269647598267,
0.45046451687812805,
0.1639663130044937,
-0.004056683741509914,
-0.10615141689777374,
-0.03744356... |
https://pimcore.com/docs/platform//Newsletter/Newsletter_Config#send-the-newsletter | Send the Newsletter
To send the newsletter you have to specify a source adapter.
We're going to use customer objects as a source, therefore we need to choose the Default object list adapter.
And the Customer class as the source.
Choose the adapter:
Choose the class:
and at the end, just push the Send Newsletter Now b... | Send the Newsletter | [
-0.12535764276981354,
-0.22704251110553741,
-0.013744944706559181,
0.05445623770356178,
0.10743565857410431,
-0.2393890619277954,
0.45571333169937134,
-0.06521182507276535,
0.20882128179073334,
0.3262738585472107,
0.018407326191663742,
0.3284728527069092,
-0.02699100412428379,
-0.021928815... |
https://pimcore.com/docs/platform//Newsletter#newsletter | Newsletter
| Newsletter | [
0.07298334687948227,
-0.24630537629127502,
-0.21495065093040466,
0.24110500514507294,
0.019290702417492867,
0.09719651937484741,
0.13702523708343506,
0.22546769678592682,
0.12648098170757294,
0.33815041184425354,
0.06086301803588867,
-0.11617925763130188,
-0.1319843977689743,
-0.2282926589... |
https://pimcore.com/docs/platform//Newsletter#title:-newsletter-module | title: Newsletter Module | title: Newsletter Module | [
0.4140303134918213,
-0.28200769424438477,
-0.23472897708415985,
0.03139165788888931,
0.15063828229904175,
0.23811770975589752,
0.33473849296569824,
0.058379679918289185,
0.28273510932922363,
0.5304021835327148,
0.05113959684967995,
0.1854880154132843,
-0.1587473750114441,
-0.17732387781143... |
https://pimcore.com/docs/platform//Newsletter#pimcore-newsletter-bundle | Pimcore Newsletter Bundle
This bundle provides a basic newsletter framework with the advantage to use all the data that is already stored in the system. | Pimcore Newsletter Bundle | [
-0.11391325294971466,
-0.2524317502975464,
-0.06173524633049965,
0.22292523086071014,
0.01925594173371792,
0.20854610204696655,
-0.07471060752868652,
0.07335519045591354,
-0.31694886088371277,
0.14355112612247467,
-0.22049975395202637,
0.28555241227149963,
-0.1566391885280609,
0.2843185961... |
https://pimcore.com/docs/platform//Newsletter#features-in-a-nutshell | Features in a Nutshell
Add a basic newsletter functionality to Pimcore.
Add a new Pimcore-specific Document type to create newsletters with Pimcore Documents (and all related concepts and features).
Send newsletters directly from Pimcore Admin UI.
Provide support for setting up a subscribe/confirm/unsubscribe workflow... | Features in a Nutshell | [
-0.08943449705839157,
-0.33141636848449707,
-0.052895788103342056,
-0.09739027917385101,
-0.11123711615800858,
-0.0026031460147351027,
-0.13252732157707214,
0.05660228058695793,
-0.32551324367523193,
0.16842307150363922,
-0.0037405728362500668,
0.38794615864753723,
-0.09430210292339325,
0.... |
https://pimcore.com/docs/platform//Newsletter#documentation-overview | Documentation Overview
Installation
Newsletter Documents
Newsletter Configuration
| Documentation Overview | [
-0.10425756126642227,
-0.2331797480583191,
-0.08548995107412338,
-0.017045503482222557,
0.009104140102863312,
0.27509191632270813,
0.056080181151628494,
-0.033253736793994904,
-0.16162331402301788,
0.10043108463287354,
-0.007827342487871647,
0.021143831312656403,
0.13559114933013916,
-0.09... |
https://pimcore.com/docs/platform//Newsletter#contributing-and-development | Contributing and Development
For details see our Contributing guide. | Contributing and Development | [
-0.04922427237033844,
0.026860656216740608,
-0.489843487739563,
-0.3809370696544647,
0.05355721339583397,
-0.1974574476480484,
0.2226363718509674,
-0.22441139817237854,
-0.07915275543928146,
0.16643762588500977,
0.04506353288888931,
-0.13159820437431335,
0.049286454916000366,
0.20433333516... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Architecture-Overview#architecture-overview | Architecture Overview
The following architecture overview shows available framework components. The component configuration takes place in the
pimcore_customer_management_framework configuration node. Optionally for each component a custom implementation can be
configured and used.
For Details for the components see a... | Architecture Overview | [
-0.15317361056804657,
-0.2039545327425003,
-0.26713839173316956,
0.05022478103637695,
0.20907512307167053,
-0.015709970146417618,
0.20002855360507965,
-0.3928554356098175,
-0.2156602442264557,
0.12946271896362305,
-0.3628234267234802,
0.29933640360832214,
0.2961079180240631,
0.309778481721... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation/Update#update-notices | Update Notices | Update Notices | [
0.12237393110990524,
-0.340903103351593,
-0.19904117286205292,
0.13597510755062103,
0.1686081886291504,
0.13730981945991516,
0.17964835464954376,
-0.010963132604956627,
0.05750878527760506,
0.2487873136997223,
0.2666020393371582,
-0.03168517351150513,
-0.09394606947898865,
-0.1000759750604... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation/Update#update-to-version-4 | Update to Version 4
Execute SQL script src/Resources/sql/segmentAssignment/storedFunctionObject.sql, only for Pimcore 11.
Remove Single Sign On custom implementations & classes e.g. SSOIdentity, OAuth1Token, OAuth2Token and ssoIdentities field
in Customer class.
| Update to Version 4 | [
-0.21562963724136353,
0.012248155660927296,
-0.11718827486038208,
-0.11688774824142456,
0.27842018008232117,
-0.4988786578178406,
0.367460697889328,
0.05568312108516693,
-0.2179407775402069,
0.21818876266479492,
-0.08464167267084122,
0.39504140615463257,
0.24030910432338715,
0.206828460097... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation/Update#update-to-version-3 | Update to Version 3
Activate Generate Type Declarations for all classes generated/used by the Customer Management Framework:
Customer
CustomerSegment
CustomerSegmentGroup
SsoIdentity
Migrate all templates to twig.
Add following line to your firewalls configuration in the security.yml of your app after the p... | Update to Version 3 | [
-0.07332419604063034,
-0.12302141636610031,
-0.12622660398483276,
-0.2376263290643692,
0.38065212965011597,
-0.12513531744480133,
0.39522475004196167,
-0.12792542576789856,
-0.28279316425323486,
0.05076662078499794,
-0.39296096563339233,
0.3108500838279724,
0.14478647708892822,
0.093617759... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation/Update#additional-code-changes-(that-might-affect-your-application) | Additional code changes (that might affect your application)
Migrated SearchQueryParser\QueryBuilder\ZendCompatibility to Doctrine\DBAL\Query\QueryBuilder.
Migrated Zend\Paginator to Knp\Component\Pager.
FilterHandler::addFilter has no operator as parameter anymore (as this was only considered with SearchQuery filter... | Additional code changes (that might affect your application) | [
-0.019356317818164825,
0.21501752734184265,
-0.18077456951141357,
-0.17796409130096436,
-0.06768432259559631,
-0.2867823541164398,
-0.13089214265346527,
0.47123023867607117,
-0.3527085781097412,
0.16279108822345734,
-0.32629093527793884,
0.13389571011066437,
0.054315533488988876,
-0.033289... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation/Update#removed-features-in-version-3 | Removed features in Version 3
Removed SegmentTrackedListener for tracking tracked segments into Piwik/Matomo
(as matomo integration is deprecated in Pimcore 6.9 and removed in Pimcore X).
Migrated all templates to php templates and removed templating helpers.
CSV Importer integration as it is also removed from Pimcore... | Removed features in Version 3 | [
-0.2647271752357483,
-0.13565130531787872,
-0.17043527960777283,
-0.011892266571521759,
0.02768474444746971,
-0.3064402639865875,
0.37415236234664917,
0.5231518745422363,
-0.2964249551296234,
0.19381879270076752,
-0.2022078037261963,
0.3804299831390381,
0.007822827436029911,
0.284060955047... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation/Update#update-to-pimcore-x | Update to Pimcore X
Update to Pimcore 6.9.
Update Customer Management Framework to latest version (compatible to Pimcore 6.9).
Execute all migrations of Customer Management Framework.
Update to Pimcore X.
| Update to Pimcore X | [
-0.44693368673324585,
-0.05057786777615547,
-0.20134226977825165,
-0.11126279830932617,
0.12629202008247375,
-0.15616348385810852,
-0.046579260379076004,
0.0666767805814743,
-0.22862593829631805,
0.28512507677078247,
-0.21585731208324432,
0.4538300931453705,
0.12577150762081146,
0.05995197... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#installation-and-first-configuration | Installation and First Configuration
This section describes the installation of the Customer Management Framework and the first steps of configuration.
Please note that Customer Management Framework requires MariaDB as database. It will not work with default MySQL. MariaDB is used to save activities with the MariaDB D... | Installation and First Configuration | [
-0.19032099843025208,
-0.05507347360253334,
-0.19740000367164612,
0.09392151236534119,
0.25427576899528503,
0.035460278391838074,
-0.08308841288089752,
-0.26694896817207336,
-0.29431086778640747,
0.2608337104320526,
-0.16589389741420746,
-0.0031372399535030127,
-0.11588740348815918,
-0.077... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#server-requirements | Server Requirements | Server Requirements | [
-0.04896339029073715,
-0.2508557438850403,
-0.34222611784935,
0.29863184690475464,
-0.20391477644443512,
-0.10905960947275162,
0.1475227177143097,
-0.14726576209068298,
0.14305222034454346,
0.028400681912899017,
0.21215085685253143,
-0.2814570367336273,
-0.00019674166105687618,
0.289332002... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#database-permissions | Database permissions
All permissions based on
the Core Requirements
and including:
Create routine
Alter routine
| Database permissions | [
0.18237708508968353,
0.006128258071839809,
-0.29821881651878357,
0.19994378089904785,
-0.021597150713205338,
-0.09099192172288895,
-0.04107837751507759,
0.06943129748106003,
-0.05161618813872337,
0.10480143874883652,
-0.18636749684810638,
0.031547240912914276,
-0.16372141242027283,
0.13560... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#installation-process | Installation Process
To install the Customer Management Framework, follow the three steps below:
Install the required dependencies:
composer require pimcore/customer-management-framework-bundle
Make sure the bundle is enabled in the config/bundles.php file. The following lines should be added:
use \CustomerManagem... | Installation Process | [
-0.023787470534443855,
0.08919408917427063,
-0.14830364286899567,
0.14034143090248108,
0.14054317772388458,
0.06087659299373627,
0.009962922893464565,
-0.22496303915977478,
-0.4195089042186737,
0.20826055109500885,
-0.27072402834892273,
0.3592158854007721,
-0.0603901669383049,
0.0659963414... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#configure-customer-class | Configure Customer Class
The CMF installation does not create a data object class for customers. That is because the framework does not limit you
on specific classes or class structures when it comes to customers. The only requirement is that the customer class
has to be 'prepared' to be used in CMF context.
Following ... | Configure Customer Class | [
-0.037833571434020996,
0.3426268994808197,
-0.05343320965766907,
0.12375614047050476,
0.37786781787872314,
0.004562779329717159,
0.3679395914077759,
-0.19374680519104004,
-0.019406111910939217,
0.1251050978899002,
0.06407921761274338,
0.137886181473732,
0.022158881649374962,
0.009996743872... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#segment-assignments-stored-functions | Segment Assignments Stored Functions
The installer creates stored functions on database for auto assigning segments on Assets, Documents & DataObjects.
In case the import fails, please import stored functions manually by defining a delimiter other than ; with following files:
/Resources/sql/segmentAssignment/stored... | Segment Assignments Stored Functions | [
-0.06606561690568924,
0.01958022080361843,
-0.2238740622997284,
0.03341483697295189,
0.33210864663124084,
-0.03958672657608986,
0.33197423815727234,
0.002025927184149623,
-0.12785832583904266,
0.16565601527690887,
-0.14729221165180206,
0.07829028367996216,
0.06327462196350098,
0.0648169592... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#configuration | Configuration
The CMF ships with a default configuration for basic functionality. To start up, no additional configuration should be
needed. To activate additional or customize existing functionality, please have a look at the
configuration chapter. | Configuration | [
-0.250774085521698,
-0.42046287655830383,
-0.1561906486749649,
-0.35909879207611084,
0.15901750326156616,
0.06870400905609131,
0.1798197329044342,
-0.4079570770263672,
-0.23461833596229553,
0.30406275391578674,
0.01417586300522089,
0.008307394571602345,
0.15629252791404724,
0.2314714640378... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#configure-symfony-firewall | Configure Symfony firewall
To configure the symfony firewall for the webservices, add following line to your firewalls configuration
in the security.yml of your app after the pimcore_admin firewall.
security:
firewalls:
pimcore_admin:
# ...
cmf_webservice: '%customer_management_framewor... | Configure Symfony firewall | [
-0.15307217836380005,
-0.07544431835412979,
-0.17200587689876556,
-0.2688583433628082,
0.23677603900432587,
-0.29946982860565186,
0.4545440971851349,
-0.20726783573627472,
0.02808097004890442,
0.1842837780714035,
-0.2503654956817627,
0.061800144612789154,
0.19633930921554565,
0.01775273308... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Installation#setting-up-necessary-cron-jobs | Setting Up necessary cron jobs
There are several cron jobs needed by the CMF. These need to be configured and setup based on the solution requirements.
See CronJob Docs for details. | Setting Up necessary cron jobs | [
-0.18458907306194305,
0.008685985580086708,
-0.24273870885372162,
-0.2234632670879364,
-0.03738488629460335,
-0.16435378789901733,
0.2746092975139618,
-0.22642044723033905,
-0.0948929488658905,
0.35464614629745483,
0.3371107578277588,
0.2215210646390915,
-0.015694953501224518,
0.0863398164... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Configuration#configuration-of-cmf | Configuration of CMF
Being a framework, there are a lot of settings in the CMF. These settings can be configured in a combination of
container service definitions for certain tags and a symfony config tree.
Following you see a full featured example of the configuration. For details of a functionality see corresponding ... | Configuration of CMF | [
-0.18145017325878143,
-0.27289286255836487,
-0.2215743213891983,
-0.06078312173485756,
0.18629300594329834,
-0.19120410084724426,
0.11538595706224442,
-0.14438782632350922,
-0.18452301621437073,
0.4742879569530487,
-0.09229607880115509,
-0.056302472949028015,
0.15996234118938446,
0.0781495... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Configuration#services | Services
e.g. in services.yml:
services:
# example customer save handler config
appbundle.cmf.customer_save_handler.normalize_zip:
class: CustomerManagementFrameworkBundle\CustomerSaveHandler\NormalizeZip
tags: [cmf.customer_save_handler]
# example segment builder config
appbundle.cmf.s... | Services | [
-0.3020874559879303,
0.05492221564054489,
-0.07836221158504486,
0.1108081042766571,
0.24680519104003906,
0.012677566148340702,
0.5289216041564941,
0.19775687158107758,
0.09194481372833252,
0.41043198108673096,
-0.01998833753168583,
0.18770641088485718,
0.04426131397485733,
-0.0240637958049... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Configuration#configuration-tree | Configuration Tree
e.g. in config.yml:
pimcore_customer_management_framework:
# Configuration of general settings
general:
customerPimcoreClass: Customer
mailBlackListFile: /home/customerdataframework/www/var/config/cmf/mail-blacklist.txt
# Newsletter/MailChimp sync related sett... | Configuration Tree | [
-0.09660828113555908,
-0.09721124172210693,
-0.10562345385551453,
0.2060178965330124,
0.2152239978313446,
0.15364770591259003,
0.21843664348125458,
-0.14926542341709137,
-0.06665220856666565,
0.3054560422897339,
-0.06920458376407623,
0.3149302899837494,
0.035813894122838974,
-0.01930466108... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#cronjobs | CronJobs
Following is a list of all cronjobs needed by the CMF bundle. Depending on the project requirements, the execution interval
might be different and some of the cronjobs might not be needed at all. | CronJobs | [
-0.1649884283542633,
-0.015168452635407448,
-0.16110119223594666,
-0.22578123211860657,
-0.15782923996448517,
0.10670628398656845,
0.03506074845790863,
-0.24929136037826538,
-0.2146645188331604,
0.20187437534332275,
0.3319958746433258,
0.22310708463191986,
-0.15954451262950897,
0.033806171... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#segment-building-queue | Segment Building Queue
Handles the calculation of asynchronous segments by processing the segment building queue.
This is needed for segments which could not be calculated directly for performance reasons.
* * * * * php /home/project/www/bin/console.php cmf:build-segments -v > /home/project/www/log/cmf-build-segment... | Segment Building Queue | [
-0.476087361574173,
-0.42087116837501526,
-0.21524286270141602,
0.03007454425096512,
-0.19678190350532532,
-0.0751679465174675,
0.15297137200832367,
0.02932145446538925,
-0.43382203578948975,
0.31924957036972046,
0.25107458233833313,
-0.2904091775417328,
0.14753763377666473,
-0.09917760640... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#action-trigger-queue | Action trigger queue
Handles the execution of delayed actions in ActionTrigger rules.
* * * * * php /home/project/www/bin/console.php cmf:process-actiontrigger-queue -v > /home/customerdataframework/www/website/var/log/cmf-process-actiontrigger-queue-lastrun.log
| Action trigger queue | [
-0.14173226058483124,
-0.2875477969646454,
-0.1793147474527359,
-0.06626343727111816,
-0.1227312758564949,
-0.0973840281367302,
0.09099999815225601,
-0.06418470293283463,
-0.21500098705291748,
0.09197639673948288,
0.2524298429489136,
-0.13488782942295074,
-0.1459646373987198,
-0.0706068873... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#cron-trigger | Cron Trigger
This cronjob is needed if cron triggers are used in ActionTrigger rules. Important: this needs to run once
per minute!
* * * * * php /home/project/www/bin/console.php cmf:handle-cron-triggers -v > /home/project/www/log/cmf-cron-trigger-lastrun.log
| Cron Trigger | [
-0.3581904172897339,
-0.2209181785583496,
-0.16522161662578583,
-0.22984279692173004,
-0.11932159215211868,
-0.18891453742980957,
0.01810349151492119,
0.2658112347126007,
-0.14490360021591187,
0.11164246499538422,
0.3383358418941498,
0.29862838983535767,
-0.4724271595478058,
0.057436361908... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#calculate-potential-duplicates | Calculate potential duplicates
Analyzes the duplicates index and calculates potential duplicates which will be
shown in the potential duplicates list view.
* * * * * php /home/project/www/bin/console.php cmf:duplicates-index -c -v > /home/project/www/log/cmf-potential-duplicates-lastrun.log
| Calculate potential duplicates | [
-0.02239214815199375,
-0.3566059172153473,
-0.1627088487148285,
0.05237670615315437,
-0.2954581081867218,
0.1393212080001831,
0.08724640309810638,
-0.051066722720861435,
0.0829998254776001,
0.15293633937835693,
-0.018689317628741264,
-0.01400379091501236,
-0.10264087468385696,
-0.147318571... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#cmf-maintenance | CMF Maintenance
This cronjob should be configured to be executed on a regular basis. It performs various tasks configured in services.yml
and tagged with cmf.maintenance.serviceCalls.
* * * * * php /home/project/www/bin/console.php cmf:maintenance -v > /home/project/www/log/cmf-cron-maintenance-lastrun.log
| CMF Maintenance | [
-0.2326047271490097,
-0.09775538742542267,
-0.2175203412771225,
-0.2704589366912842,
0.031036561354994774,
-0.034167710691690445,
-0.06924408674240112,
0.04823720455169678,
-0.18954870104789734,
0.2535780668258667,
0.41193297505378723,
0.10228423774242401,
-0.19070906937122345,
-0.19354990... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#newsletter-queue | Newsletter Queue
Processes the newsletter queue. This job should run once every x minutes (e.g. every 5 minutes) when the newsletter/mailchimp sync feature is needed.
* * * * * php /home/project/www/bin/console.php cmf:newsletter-sync -c > /home/project/www/log/cmf-newsletter-sync-lastrun.log
| Newsletter Queue | [
-0.13875508308410645,
-0.2022840827703476,
-0.05027663707733154,
-0.02655516006052494,
-0.24888980388641357,
0.23215016722679138,
-0.09740520268678665,
-0.04862455278635025,
0.25399908423423767,
0.4402276873588562,
0.2078551948070526,
-0.12720181047916412,
0.025455597788095474,
-0.29135927... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Cronjobs#mailchimp-status-sync | Mailchimp status sync
Should run as a night job. Synchronizes status updates from Mailchimp to Pimcore if webhook calls failed. This is important to ensure data integrity also when the system is down for several hours.
Setup a Pimcore user name (e.g. mailchimp-cli) in the CMF config - this user will be visible in the v... | Mailchimp status sync | [
-0.5473693609237671,
0.06754259765148163,
-0.06274431198835373,
0.04413708671927452,
-0.23233622312545776,
0.06607819348573685,
0.11518728733062744,
-0.0462309755384922,
0.1327783316373825,
0.27939891815185547,
0.18066665530204773,
0.11452119052410126,
-0.22115468978881836,
-0.144208237528... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Working-with-Customers#working-with-customers | Working with Customers
As already described in the installation chapter, customers are simple data objects that need to implement certain
interfaces or extend certain abstract classes.
As a result, working with customers is pretty much like working with Pimcore data objects. But there are three aspects to consider:
I... | Working with Customers | [
0.11671911180019379,
0.03781934455037117,
-0.14398948848247528,
0.13167744874954224,
0.19161272048950195,
0.049661993980407715,
0.19074144959449768,
-0.4759499728679657,
-0.3690832257270813,
0.19058366119861603,
-0.26958510279655457,
0.18608884513378143,
0.0962982028722763,
0.1009459942579... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#customer-save-manager | Customer Save Manager
The customer save manager is responsible for all actions/hooks which are executed when a customer object is saved.
It consists of several parts: | Customer Save Manager | [
0.2246224582195282,
-0.3018195927143097,
-0.11010826379060745,
-0.012546863406896591,
0.04444080591201782,
0.3457927107810974,
0.07628586888313293,
-0.3157498240470886,
-0.16294799745082855,
0.10902488231658936,
0.12511330842971802,
-0.028898604214191437,
-0.20594818890094757,
-0.093724161... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#customer-save-handlers | Customer Save Handlers
Customer save handlers special PHP classes that are executed when a customer gets saved and can be used to normalize,
validate, optimize or modify customers on save.
Customer save handlers need to be registered as symfony services with the tag "cmf.customer_save_handler".
So it is possi... | Customer Save Handlers | [
0.017175521701574326,
0.18746328353881836,
-0.14517351984977722,
0.2865007817745209,
0.048836346715688705,
-0.03349362313747406,
0.2500545084476471,
-0.03827136754989624,
-0.41007229685783386,
0.2422923892736435,
-0.1450972557067871,
0.056487321853637695,
0.03210652247071266,
-0.1025828719... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#example-service-definition | Example service definition
services:
appbundle.cmf.customer_save_handler.normalize_zip:
class: CustomerManagementFrameworkBundle\CustomerSaveHandler\NormalizeZip
tags: [cmf.customer_save_handler]
| Example service definition | [
-0.13677601516246796,
-0.07882043719291687,
-0.1370203047990799,
-0.15063978731632233,
0.17862342298030853,
0.17093650996685028,
0.13148339092731476,
0.17952950298786163,
-0.11348363757133484,
0.2652086615562439,
-0.0010827983496710658,
0.44358858466148376,
-0.06539566814899445,
0.28338664... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#built-in-customer-save-handlers | Built in customer save handlers
The CMF offers the following customer save handlers out of the box. They are all located in the namespace
CustomerManagementFrameworkBundle\CustomerSaveHandler and need to be enabled as services by adding
a corresponding service with the tag cmf.customer_save_handler to the container. Al... | Built in customer save handlers | [
-0.1257219910621643,
-0.03051808848977089,
-0.16568081080913544,
-0.1420796513557434,
0.17119118571281433,
0.13008269667625427,
0.16196510195732117,
-0.056229688227176666,
-0.12537124752998352,
0.4082229733467102,
-0.1431957185268402,
-0.08039277791976929,
-0.10818871855735779,
0.000648567... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#cleanup\email | Cleanup\Email
Removes invalid characters from an email field. | Cleanup\Email | [
0.23899909853935242,
0.03897223621606827,
-0.13177719712257385,
0.08140933513641357,
0.39089512825012207,
0.06678343564271927,
0.3132856488227844,
0.29133543372154236,
0.04515671357512474,
0.2208881825208664,
0.15738698840141296,
-0.34188592433929443,
-0.20113378763198853,
-0.1109734401106... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#normalizezip | NormalizeZip
Tries to normalize zip numbers. For example A-1010 would become 1010. It offers zip correction regexes for several countries.
It would be possible to extend the logic for other countries. | NormalizeZip | [
-0.18214522302150726,
0.11691893637180328,
-0.14905008673667908,
-0.21260321140289307,
-0.06923025846481323,
-0.2150573432445526,
0.08567994832992554,
0.3788943290710449,
-0.24837210774421692,
0.16372786462306976,
0.02617519535124302,
0.3183864951133728,
0.12933486700057983,
0.292888849973... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#salutationtogender | SalutationToGender
Maps a salutation field to a gender field. This can automatically adjust the gender based on the salutation. | SalutationToGender | [
0.382671982049942,
-0.0843556746840477,
-0.13602618873119354,
-0.023739606142044067,
0.21483466029167175,
-0.19107389450073242,
0.0553138293325901,
0.19670599699020386,
-0.1427423655986786,
0.19882449507713318,
-0.1464768946170807,
-0.1002623662352562,
0.20770305395126343,
-0.1213192790746... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#removeblacklistedemails | RemoveBlacklistedEmails
Sets the email field to an empty value if the given email address is in a defined blacklist. | RemoveBlacklistedEmails | [
0.15144240856170654,
-0.15295644104480743,
-0.11984709650278091,
0.10903763771057129,
-0.04531797394156456,
0.1190032958984375,
0.5584253072738647,
0.06409468501806259,
0.5176531076431274,
0.24830321967601776,
0.07606825977563858,
0.11366423219442368,
-0.17388758063316345,
0.15798377990722... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#markemailaddressasvalid | MarkEmailAddressAsValid
Marks an email address as valid if it has a valid format. Marking as valid means that a special checkbox get checked. | MarkEmailAddressAsValid | [
0.16882090270519257,
-0.4288271963596344,
-0.04245394468307495,
0.16971474885940552,
0.02447904460132122,
0.04720082879066467,
0.29688289761543274,
0.15242691338062286,
-0.09665446728467941,
-0.12170043587684631,
0.14357608556747437,
-0.2857111990451813,
-0.24979250133037567,
0.16290800273... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#attributelogic | AttributeLogic
Allows to setup a logic for overwriting field values based on other field values. | AttributeLogic | [
0.04775288328528404,
-0.1417587548494339,
-0.23700696229934692,
-0.03273235633969307,
-0.1606748402118683,
-0.2524341642856598,
0.23969563841819763,
0.1869281381368637,
0.10991068929433823,
0.2144705057144165,
0.11801673471927643,
0.3946395218372345,
0.09079337120056152,
0.4355385899543762... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#example: | Example:
appbundle.cmf.customer_save_handler.attribute_logic:
class: CustomerManagementFrameworkBundle\CustomerSaveHandler\AttributeLogic
arguments:
- from: profileStreet
to: street
overwriteIfNotEmpty: true
- from: profileZip
to: zip
overwriteIfNotEmpty: true
In this ... | Example: | [
0.31808754801750183,
0.16511492431163788,
-0.029283832758665085,
0.13752102851867676,
0.23010584712028503,
-0.10535307228565216,
0.09671824425458908,
-0.086393341422081,
-0.26942700147628784,
0.29373350739479065,
0.2857973277568817,
0.29518118500709534,
0.3433385491371155,
0.15892915427684... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#automatic-object-naming-scheme | Automatic Object Naming Scheme
The CMF automatically applies a naming scheme for customer objects depending on a configured logic. This automatic naming
scheme can be disabled if not needed. | Automatic Object Naming Scheme | [
0.2610980272293091,
-0.3258518576622009,
-0.08608757704496384,
-0.05686519667506218,
0.38431277871131897,
0.0540994331240654,
0.40962982177734375,
-0.3468370735645294,
-0.21221770346164703,
0.45138347148895264,
0.11151853948831558,
0.11362926661968231,
0.19113266468048096,
-0.0606972984969... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#example-configuration | Example configuration
pimcore_customer_management_framework:
customer_save_manager:
enableAutomaticObjectNamingScheme: true
customer_provider:
parentPath: /customers
archiveDir: /customers/_archive
namingScheme: '{countryCode}/{zip}/{firstname}-{lastname}'
If the CMF is configured... | Example configuration | [
0.009462292306125164,
0.15607210993766785,
0.0031383545137941837,
0.2717871069908142,
0.11258888244628906,
0.04146503657102585,
-0.1424892693758011,
-0.27175965905189514,
-0.5218435525894165,
0.12806278467178345,
-0.10685775429010391,
0.3325977623462677,
-0.0796775072813034,
0.163427740335... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#customer-save-validator | Customer Save Validator
If enabled the customer save validator will throw exceptions when the customer is invalid according to it's implementation.
These exceptions can be used in try/catch blocks in order to check if the customer is valid. In the Pimcore backend an
error message will alert if somebody tries to save an... | Customer Save Validator | [
-0.02768740803003311,
-0.35662373900413513,
-0.1214062049984932,
-0.051806483417749405,
0.13691455125808716,
-0.030833564698696136,
0.13891080021858215,
-0.3606754243373871,
-0.30890408158302307,
0.23402760922908783,
-0.0325767956674099,
0.012893673032522202,
0.035041242837905884,
-0.01598... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#example-configuration | Example configuration
pimcore_customer_management_framework:
customer_save_validator:
checkForDuplicates: true
requiredFields:
- [email],
- [firstname, name, zip]
customer_duplicates_services:
duplicateCheckFields:
- [email]
... | Example configuration | [
0.08755581080913544,
-0.36596423387527466,
-0.005878574214875698,
0.08153901994228363,
0.06784398853778839,
-0.002172377659007907,
-0.008612098172307014,
-0.2483222633600235,
-0.4108966886997223,
0.16993850469589233,
-0.07367637008428574,
0.212188720703125,
0.04152470827102661,
-0.03453439... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#save-customer-with-disabled-hooks | Save Customer with Disabled Hooks
In most cases it's sufficient to just call $customer->save() to save a customer object.
Sometimes it's needed to save a customer without validation or without applying for example customer save handlers or
segment builders.
The CMF offers a special SaveOptions class to handle the en... | Save Customer with Disabled Hooks | [
-0.33347198367118835,
0.03138117864727974,
-0.1659087985754013,
-0.06457041949033737,
0.2423395961523056,
0.0041541606187820435,
0.053405407816171646,
-0.03313214331865311,
0.04425041750073433,
0.36216112971305847,
-0.008380950428545475,
-0.047857996076345444,
-0.0909833237528801,
-0.16069... |
https://pimcore.com/docs/platform//Customer_Management_Framework/CustomerSaveManager#examples | Examples
<?php
$customer = Customer::getById(1234);
// Disable all hooks and also Pimcore versioning.
$customer->saveDirty();
// Disable all hooks but enable Pimcore versioning.
$customer->saveDirty(false);
// Globally disable on save segment building and also the segment builder que... | Examples | [
-0.3238936960697174,
-0.11549970507621765,
-0.17744556069374084,
0.08369557559490204,
0.05096188560128212,
-0.17968769371509552,
0.26843398809432983,
0.09666934609413147,
-0.3744319975376129,
0.3394245505332947,
0.10649105906486511,
0.08764401823282242,
-0.07430699467658997,
-0.12671166658... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#activities | Activities
An important part of the customer management framework are customer activities. They can be pretty much every activity a
customer can perform - and therefore very simple (for example customer logged in) or quite complex (orders, bookings...).
The CMF can be used to store all customer related activity data an... | Activities | [
-0.002087750006467104,
-0.33420562744140625,
-0.18997560441493988,
0.17705535888671875,
0.2722622752189636,
0.3042542040348053,
-0.2976369857788086,
-0.1349882185459137,
-0.47581911087036133,
0.3297532796859741,
-0.1893947869539261,
-0.17344997823238373,
0.04332435503602028,
-0.14906625449... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#using-pimcore-data-objects-and-other-data-entities-as-activities | Using Pimcore Data Objects and other Data Entities as Activities
Additionally to the generic activity store, it's possible to use Pimcore data objects (or other data entities/sources) as
activities too. They just need to implement the
ActivityInterface
(for Pimcore data objects extend the
AbstractObjectActivity class).... | Using Pimcore Data Objects and other Data Entities as Activities | [
-0.04246468469500542,
-0.019326668232679367,
-0.15328097343444824,
0.17177337408065796,
0.1720646470785141,
-0.2790188193321228,
0.19174246490001678,
-0.23594772815704346,
-0.3269260823726654,
-0.0431591160595417,
-0.33912166953086853,
0.07248964160680771,
-0.2643548846244812,
0.1757890284... |
https://pimcore.com/docs/platform//Customer_Management_Framework/Activities#generic-activities | Generic activities
As mentioned above, activities can use their own persistence additionally to the ActivityStore but don't have to.
It's also possible to save activities only in the ActivityStore. The framework includes a generic activity implementation
which could be used for these cases:
CustomerManagementFrameworkB... | Generic activities | [
0.1710709035396576,
0.017379356548190117,
-0.1190391406416893,
0.13683924078941345,
0.3335054814815521,
-0.07958207279443741,
0.1523059606552124,
-0.08647332340478897,
-0.05482201278209686,
0.03619207441806793,
-0.10490196198225021,
-0.20023705065250397,
-0.3333623707294464,
-0.10679714381... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.