> For the complete documentation index, see [llms.txt](https://docs.getuntitled.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getuntitled.ai/integrations/destinations/klaviyo/klaviyo-tips-and-tricks.md). # Klaviyo Tips and Tricks Optional steps that help your Untitled data work more seamlessly within your Klaviyo account. ### Create a List to Trigger a Flow and use a Custom Property for Attribution {% embed url="" %} This video walks through the process of setting up a Klaviyo List, Flow, Custom Property, and Custom Report for use with your Untitled Audiences. 0:00 Intro\ 0:15 Prerequisites\ 0:33 Create a new List\ 0:56 Create a new Flow\ 1:15 Create a new Custom Property for Untitled Audience members\ 2:32 Create a test contact in the new Flow\ 3:08 Create a Custom Report for the new Klaviyo Property\ 4:00 Complete the Flow\ 4:09 Next Steps with Klaviyo ### Items to check when connecting Untitled data to Klaviyo #### Existing 'unengaged' or 'sunset' flows If you trigger exclusion lists from your campaign receipts or create segments to archive, ensure you double-check on those segment criteria. Some segments are triggered by criteria like "Have not opened an email within 30 days". When an Untitled contact is first imported to Klaviyo, they have not received any email and are sometimes added directly to an exclusion list, meaning they are never used within Klaviyo. Modifying criteria to include "And has received at least 10 emails" negates this issue. #### Triggers for other flows, lists, and campaigns If you currently have strong Flows for 'viewed product' or use a criteria of 'visited site within last 7 days' for a campaign, considering using initial emails to Untitled contacts to drive more contacts into your Flows. For example, a call to action of "view our best selling products" might encourage a click that leads to a strong "Viewed Product" Klaviyo Flow. Consider how all of your Flows work together. Related Content: * [Creating Audiences](/audience-studio.md) * [Using Klaviyo as an Untitled Destination](/integrations/destinations/klaviyo.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.getuntitled.ai/integrations/destinations/klaviyo/klaviyo-tips-and-tricks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.