# Monetize Klaviyo ### Before we Monetize Before you get started on how-to monetize the incremental audiences, we recommend that you check if you have Klaviyo and Blotout EdgeTag setup correctly. {% hint style="info" %} Note: Please ensure you have added Klaviyo and completed the authorization {% endhint %}
Blotout EventEquivalent Klaviyo EventDescription
Blotout_PageViewActive on SiteTop of the funnel - every page
Blotout_ViewContentViewed Product

PDP - Product Page viewed

One per page

Blotout_AddToCartAdded to Cart

Added to Cart event.

One per Cart addition

Blotout_InitiateCheckoutCheckout StartedStarted Checkout
Blotout_PurchasePlaced OrderSite Purchases only
{% hint style="info" %} For a list of standard [Blotout EdgeTag Events please refer to our standard event catalog](/overview/standard-events.md) {% endhint %} If these events are not showing up, please reach out to your Blotout EdgeTag contact directly or via our Slack Forum. ### Calculating Incremental Audience Let's check a couple of segments to measure incremental audiences for lifecycle visitors. The **two we recommend** are PDP page visits and Added to Cart for; 1. Viewed Product incremental audience 2. Added to Cart incremental audience These give you a very good idea on how many incremental members you are able to re-identify. You can do the math by checking revenue per recipient to understand overall incremental revenue. Lets start with Viewed Product. #### Incremental Viewed Product We recommend you use L3 days as a measuring stick to measure incremental audience that your Blotout EdgeTag Server captures for you. * Start with logging in to Klaviyo * Go to Segments and Lists * Create Segment * Follow steps below **Step-by-Step**
Above is an example for comparing Blotout Events with Regular Klaviyo events; here are the rules - **Segment Name:** Test VP (Klaviyo) L3 **Rule 1:** Where someone has done Viewed Product at least once in last 3 days **COMPARE TO (TEST INCREMENTAL)** **Segment Name:** Test VP (Klaviyo + Blotout) L3 **Rule 1:** Where someone has done Viewed Product at least once in last 3 days OR **Rule 2:** Where someone has done Blotout\_ViewContent at least once in last 3 days ***
The above example compares Blotout with Elevar SS plus Klaviyo events. **Segment Name:** Test VP (Klaviyo + Elevar) L3 **Rule 1:** Where someone has done Viewed Product at least once in last 3 days OR **Rule 2:** Where someone has done Viewed Product Elevar SS at least once in last 3 days **COMPARE TO (TEST INCREMENTAL)** **Segment Name:** Test VP (Klaviyo + Elevar + Blotout) L3 **Rule 1:** Where someone has done Viewed Product at least once in last 3 days OR **Rule 2:** Where someone has done Viewed Product Elevar SS at least once in last 3 days OR **Rule 3:** Where someone has done Blotout\_ViewContent at least once in last 3 days **Pro-tip:** Just because everyone says they are server-side, does not mean managing ID assets are very well understood. The upside on mid-funnel here is the same advantage on all growth channels #### Incremental Added to Cart We recommend you use L3 days as a measuring stick to measure the incremental audience that your Blotout Server captures for you. * Start with logging in to Klaviyo * Go to Segments and Lists * Create Segment * Follow steps below **Step-by-Step:**
Refer the above image as an example to comparing Blotout with Regular Klaviyo events; here are the rules - **Segment Name:** Test ATC (Klaviyo) L3 **Rule 1:** Where someone has done Added to Cart at least once in last 3 days **COMPARE TO (TEST INCREMENTAL)** **Segment Name:** Test ATC (Klaviyo + Blotout) L3 **Rule 1:** Where someone has done Added to Cart at least once in last 3 days OR **Rule 2:** Where someone has done Blotout\_AddToCart at least once in last 3 days ***
Above image is Comparing Blotout with Elevar SS plus Klaviyo events. **Segment Name:** Test ATC (Klaviyo + Elevar) L3 **Rule 1:** Where someone has done Added to Cart at least once in last 3 days OR **Rule 2:** Where someone has done Added to Cart Elevar SS at least once in last 3 days **COMPARE TO (TEST INCREMENTAL)** **Segment Name:** Test ATC (Klaviyo + Elevar + Blotout) L3 Rule 1: Where someone has done Added to Cart at least once in last 3 days OR Rule 2: Where someone has done Added to Cart Elevar SS at least once in last 3 days OR Rule 3: Where someone has done Blotout\_AddToCart at least once in last 3 days Pro-tip: Just because everyone says they are server-side, does not mean managing ID assets are very well understood. The upside on mid-funnel here is the same advantage on all growth channels ### Monetization Pro-Tip: You can estimate your daily upside by purely measuring revenue per email from your existing flows There are **two key** variables in building incremental flows; * Variable-1: Get your flow triggers right * Variable-2: Get your email templates right {% hint style="info" %} Note: Blotout cannot help with email or SMS templates but your agency can help you. You can always reach us out on our Shared Slack {% endhint %} Here are the key templates for each of the flows. #### Abandoned Browse Flow 1. Clone your existing Abandoned Browse flow 2. Select "Blotout\_ViewContent" as Event 3. Replace (Clone) -> (Blotout) 4. Start editing the flow 5. Click on Flow Trigger 6. Add Rule -> AND someone has done something zero times (select Viewed Product) since starting the flow 7. Add Rule -> AND someone has done something zero times (select Viewed Product) 1 hour before the flow triggered 8. If someone has Blotout\_AddToCart zero times, since starting this flow 9. If someone has Blotout\_InitiateCheckout zero times, since starting the flow. 10. If someone has Received Email zero times in the last 7 days where Flow equals to {the name of the flow} (flow through which the Blotout flow is cloned). This step is only needed when both flows are live. **Goal**: Goal here is to ensure that user has not seen the Viewed Product Event #### Abandoned Cart Flow 1. Clone your existing Abandoned Cart flow 2. Select "Blotout\_AddToCart" as Event 3. Replace (Clone) -> (Blotout ) 4. Start editing the flow 5. Click on Flow Trigger 6. Add Rule -> AND someone has done something zero times (select Added to Cart) since starting the flow 7. Add Rule -> AND someone has done something zero times (select Added to Cart) 1 hour before the flow triggered 8. If someone has Blotout\_InitiateCheckout zero times, since starting the flow. 9. If someone has Received Email zero times in the last 7 days where Flow equals to {the name of the flow} (flow through which the Blotout flow is cloned). This step is only needed when both flows are live. **Goal**: Goal here is to ensure that user has not seen the Added to Cart Event #### Abandoned Checkout Flow 1. Clone your existing Abandoned Checkout flow 2. Select "Blotout\_InitiateCheckout" as Event 3. Replace (Clone) -> (Blotout ) 4. Start editing the flow 5. Click on Flow Trigger 6. Add Rule -> AND someone has done Checkout Started zero times since starting this flow 7. If someone has Received Email zero times in the last 7 days where Flow equals to {the name of the flow} (flow through which the Blotout flow is cloned). This step is only needed when both flows are live. **Goal**: Goal here is to ensure that user has not seen the Initiate Checkout Event Great! May the force of retention be with you. {% hint style="info" %} Pro-Tip: For high LTV brands where retention is high, we recommend building a Site Revisit flow as well {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.edgetag.io/how-to/monetize-klaviyo.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.