Skip to main content

Customer Insights - Measure templates

Measure templates

Recently a new feature has been added to Customer Insights, which allows to create measures based on templates.


If you select "Choose a template" various templates are offered, that allow the calculation of popular KPIs, like Average transaction value, Loyalty points earned or Time since last purchase:


If you select one of the templates, e.g. "Loyalty points earned" a short description of the measure based on an example, the formula behind the measure and the data, which is required to calculate the measure, is displayed:



As we can see, this template is based on activities and the activities need the following information:
- How many loyalty points have been earned with a purchase
- Activity timestamp of the purchase

Which means we have to setup an activity first, before we can define our measure.

Activities

In this example, we have an entity called "posPurchases", which contains transactional data in the following format:
To add a new activity, we navigate to Data --> Activities and select "Add activity":

We fill out the required data and click on save:

Once our activity definition has been saved, we click on run to generate the activities:

When the activites have been generated successfully, they will appear in the timeline on the customer profile:

Measure

Now that our activites have been generated, we are prepared to define our measure. We navigate to Measures --> New --> Choose a template and choose the template "Loyalty points earned".

In the details screen once again the formula is presented and you can choose for which time period (all time, year to date, ...) the measure shall be calculated.

We will stay with the default "All time":


Now we click on "Add data" and choose the activity, we have previously defined:

Then we have to select the fields that store the necessary information from the activity entity:

This is actually a bit though, since the fields are not represented with the field name of their originating entity, but rather with the general field names of the activity entity. So we have a look at the unified activity entity, to find the correct attributes:


So we go with following selection:
We have finalized our measure definition and click on run:


Now our measure is calculating:

When the calculation has been successful, a new entity is created, storing customerid and the loyalty points earned:

That entity can then for example be used to create segments to send a marketing campaign to all customers having more than 500 loyalty points:


Conclusion

This is still a preview feature and it feels a bit like that, so I expect changes to come. I really like the idea to create measures based on templates, though I would have expected that instead of a customer measure (= own entity) a customer attribute would have been calculated, so that a KPI tile would have been shown on the customer profile.

Also the process to first create an activity, before you can create a measure, makes it a bit complicated. And I think the idea behind this feature was, to give the customers an idea, what measures they could calculate with CI and it should be a starting point for them.

Comments

  1. Your comments are totally true. With the current set up, the tool requires at least 2 users: one data scientist who really knows the data structure, the primary keys and the logic between the entities and the power user of the business division, who will be able to interprete the results and decide on, let's say, marketing campaign.
    From a user point of view, I would expect that building the activity is part of the process for building the measure itself, so that we do not have to cut the process into pieces to be able to work.
    Let's see what the next releases will bring :)

    ReplyDelete
  2. B2B Casino Ireland ᐈ €300 + 300 FS + 200 Bonus Spins
    The B2B 영천 출장샵 Casino has 경산 출장안마 a solid 안양 출장마사지 reputation and is a very 광주광역 출장샵 safe casino. The site has a long-standing reputation with online gambling. It is 진주 출장안마 licensed and

    ReplyDelete

Post a Comment

Popular posts from this blog

Power Automate Get absolute Sharepoint URL from document location

Document Locations If you enable Sharepoint document integration in your model driven apps, you can define for which entities the possibility to upload documents to sharepoint shall be offered and you can define a folder structure. Possible folder structures can either be based on account or contact, which means if you create child items (e.g. opportunities, activities, ...) sub folders are created below. If an entity is enabled for document management a "Files" tab is added to the form of your model driven app and as soon as you click on that tab a folder is automatically generated on Sharepoint. Once the folder has been created you have options to create new or upload existing file or to open the document location (folder) on Sharepoint: What happens behind the scenes is, as soon as you click on the files tab your model driven app checks, weither a "document location" for this item already exists, or not. The document location is an own entity in C

Send e-mails with a link to the record via Power Automate

Today we gonna have a look at how to send an e-mail with a link to a CDS record via Power Automate. In the good old classic workflows, you could directly reference the "record URL" from the dynamic data. But since UCI has been launched and you have the possiblity to target different apps, you already had to do a few more steps in the classic workflows as well. The URL to a CDS record consists of multiple things: CRM URL appid entity name record id So we will work this out one after the other. First we add a "List record" action to lookup the appid of the app, we target. We look for "model driven apps" and filter by the name of the app: Then we initialize a variable with the resulting app id: Then we initialize another variable and extract the CRM_URL: Then we fetch our records, where we want to send out a notification with a link, in this case we look for workorders fullfilling certain criteria: Now we compose the record URL: As a next step we create a new

Working with Optionset lables in Power Automate

Connector Types Power Automate currently offers 3 different connectors, to connect Power Automate with your Dynamics 365 instance: Dynamics 365 Common Data Service Common Data Service (current environment) Today we will look on ways how to retrieve option set labels via the different connectors, for our sample accounts: Dynamics 365 This connector should not be used any more , since in April 2019 it has been announced as being deprecated. https://flow.microsoft.com/en-us/blog/nine-new-connectors-in-april-and-improved-visibility-into-trigger-failures/ With the Dynamics 365 connector it was quite easy to work with optionsets, since it offered both the optionset value (int) and the optionset label (name) in the dynamic content: And here we go, these are our results: Common Data Service Since the Dynamics 365 connector has been deprecated, this is the connector you should use. If you perform a "Get record" or "List records&