GITBOOK-64: No subject

Author: Sofie Toft Kristensen

13/umbraco-ums/.gitbook/assets/engage-custom-goal-ID.png

@@ -70,4 +70,4 @@ To update the Startup.cs file, follow these steps:
 5. Navigate to **/umbraco/swagger** in your browser.
 6. From the top right definition dropdown, check for the **uMarketingSuite Marketing API.**
 
-![]()
+**MISSING IMAGE**

13/umbraco-ums/.gitbook/assets/engage-headless-segment-css.png

@@ -1,6 +1,7 @@
 ---
 description: >-
-  Learn how to use the Headless API to track page views, personalize content, and manage segmentation for visitors.
+  Learn how to use the Headless API to track page views, personalize content,
+  and manage segmentation for visitors.
 ---
 
 # Using the Marketing API
@@ -59,54 +60,49 @@ To track a page view, send a POST request to:
 
 `/umbraco/umarketingsuite/api/v1/analytics/pageview/trackpageview/client`
 
-- Required: `url` property of the page that a user has visited in the site
-- Optional: `reffererUrl` can be set to inform uMarketingSuite where the user came from.
+* Required: `url` property of the page that a user has visited in the site
+* Optional: `reffererUrl` can be set to inform uMarketingSuite where the user came from.
 
 `/umbraco/umarketingsuite/api/v1/analytics/pageview/trackpageview/server`
 
-- Useful when a frontend JAMStack Server such as a NuxtJS server or similar is being used.
-- Can notify uMarketingSuite when a page view has taken place and provide extra information.
-- Requests extra metadata like `headers`, `browserUserAgent`, `remoteClientAddress`, and `userIdentifier`.
+* Useful when a frontend JAMStack Server such as a NuxtJS server or similar is being used.
+* Can notify uMarketingSuite when a page view has taken place and provide extra information.
+* Requests extra metadata like `headers`, `browserUserAgent`, `remoteClientAddress`, and `userIdentifier`.
 
 **Client and Server**
 
 uMarketingSuite gathers information about visitors based on their requests, extracting details from your request like HTTPContext.
 
-- **Client-side**: This version applies when you make an API call directly to Umbraco from your browser. In this case, all the request metadata, such as IP address, cookies, request headers, and so on, comes directly from your browser.
-
-- **Server-side**: If there is a server between the browser and Umbraco, like a NuxtJS server, the requests tracked are from the server rather than the browser. In this scenario, uMarketingSuite does not receive metadata from the end-client's requests. Instead, you can use the server version to add this additional metadata (headers, IP addresses, and so on) to your pageview tracking between the NuxtJS server and Umbraco.
+* **Client-side**: This version applies when you make an API call directly to Umbraco from your browser. In this case, all the request metadata, such as IP address, cookies, request headers, and so on, comes directly from your browser.
+* **Server-side**: If there is a server between the browser and Umbraco, like a NuxtJS server, the requests tracked are from the server rather than the browser. In this scenario, uMarketingSuite does not receive metadata from the end-client's requests. Instead, you can use the server version to add this additional metadata (headers, IP addresses, and so on) to your pageview tracking between the NuxtJS server and Umbraco.
 
 ### Page Events
 
 To track events, send a POST request to:
 
 `/umbraco/umarketingsuite/api/v1/analytics/pageevent/trackpageevent`
 
-- After tracking a pageview using the Analytics TrackPageview API as mentioned above, you will receive both an externalVisitorId and `pageviewId`.
-- Requires a supplied pageview-Id header and a request body containing a `category`, `action` _(optional)_, `label` _(optional)_, and `timestamp` _(optional)_.
+* After tracking a pageview using the Analytics TrackPageview API as mentioned above, you will receive both an externalVisitorId and `pageviewId`.
+* Requires a supplied pageview-Id header and a request body containing a `category`, `action` _(optional)_, `label` _(optional)_, and `timestamp` _(optional)_.
 
 Optionally, provide an External-Visitor-Id header in order to automatically update the in-memory visitor. This helps to automatically reflect segments involving events for said visitors. Without this parameter, the pageview must be flushed to the database (according to the configuration) before any segment-related information is updated. For example: personalization variants based on events.
 
 ### Segmentation - Assets
 
-`/umbraco/umarketingsuite/api/v1/segmentation/assets/item/{path}`
-`/umbraco/umarketingsuite/api/v1/segmentation/assets/item/{id}`
+`/umbraco/umarketingsuite/api/v1/segmentation/assets/item/{path}` `/umbraco/umarketingsuite/api/v1/segmentation/assets/item/{id}`
 
 These requests let you verify if a content page, by ID or Path, has a **JavaScript** or **CSS** variant available for page injection.
 
-![]()
+![](../../.gitbook/assets/engage-headless-segment-css.png)
 
 ### Segmentation - Content
 
-`/umbraco/umarketingsuite/api/v1/segmentation/content/segments`
-`/umbraco/umarketingsuite/api/v1/segmentation/content/segments/{path}`
-`/umbraco/umarketingsuite/api/v1/segmentation/content/segments/{id}`
+`/umbraco/umarketingsuite/api/v1/segmentation/content/segments` `/umbraco/umarketingsuite/api/v1/segmentation/content/segments/{path}` `/umbraco/umarketingsuite/api/v1/segmentation/content/segments/{id}`
 
 These requests return details about segments (personalization and A/B testing) configured for a page. This helps determine if content can be changed by uMarketingSuite or cached more aggressively.
 
 ### Segmentation - Visitor
 
-`/umbraco/umarketingsuite/api/v1/segmentation/content/activesegments/{path}`
-`/umbraco/umarketingsuite/api/v1/segmentation/content/activesegments/{id}`
+`/umbraco/umarketingsuite/api/v1/segmentation/content/activesegments/{path}` `/umbraco/umarketingsuite/api/v1/segmentation/content/activesegments/{id}`
 
 These requests return the segment (personalization and A/B testing) that the current visitor ID of that specific page belongs to based on its cookie.

13/umbraco-ums/.gitbook/assets/engage-journey-scoring.png

@@ -18,7 +18,7 @@ To set custom goals:
 
 Creating the goal is similar to creating a page view or page event goal. The **goal ID** displayed in the code snippet after saving, as it's needed to trigger the goal from the code.
 
-![goal id]()
+![goal id](../../.gitbook/assets/engage-custom-goal-ID.png)
 
 ## Trigger goal in C\#
 

13/umbraco-ums/.gitbook/assets/engage-persona-scoring-with-minimal-deviation.png

@@ -26,20 +26,20 @@ The points of all these different sources are added and this reaches a certain a
 
 In the example, the visitor collected 40 points for the "**Data & Privacy officer**", 30 points for the "**Marketer**", and 0 points for the developer persona:
 
-![]()
+![](../../../.gitbook/assets/engage-persona-scoring.png)
 
 The threshold in this specific case was set to 25 points. As soon as the "**Data & Privacy officer**" reached 25 points Umbraco uMS assumed that this visitor was a "**Data & Privacy officer**".
 
 In this example the "**Think**" customer journey step is assumed based on the collected amount of points:
 
-![]()
+![](../../../.gitbook/assets/engage-journey-scoring.png)
 
 ## Tweaking the scoring
 
 The threshold value and the expected difference between two personas or journey steps can be set in the [customer journey group](setting-up-the-customer-journey.md) and [persona group](setting-up-personas.md).
 
 Setting up a deviation of at least 35 points between two personas the cockpit will show a different visualization in the previous example:
 
-![]()
+![](../../../.gitbook/assets/engage-persona-scoring-with-minimal-deviation.png)
 
 You can see that the "**Data and privacy officer**" still has 40 points and the marketer 30 points. Both have also reached the threshold of 25 points, but there is not a minimal deviation of 35 points. Umbraco uMS algorithm now does not assume a persona yet, but will wait until the deviation is big enough (according to the settings) and the "**Data & privacy officer**" reaches 65 points **(30 points of the marketer + a minimal deviation of 35 points)**.