> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/klaviyo/faq.md).

# FAQ

#### How do I confirm that the Klaviyo channel is set up properly in EdgeTag?

You need to check for Blotout\_events in metrics over klaviyo dashboard to confirm data is flowing.

#### What access level do I need in my Klaviyo Account to complete EdgeTag setup?

You need Admin access to your Klaviyo account to set up the Klaviyo Channel integration with EdgeTag.

#### Why is my Klaviyo channel showing authentication errors?

Klaviyo authentication errors typically occur when API tokens expire due to refresh token issues with the Klaviyo integration. Try redeploying the EdgeTag to refresh the authentication connection with Klaviyo - this usually resolves the token expiration problem.\
If redeploying doesn't work, contact us via Slack. 

#### How do I monetize EdgeTag data in Klaviyo?

Need to clone the flows with Blotout triggers and exclude the audience that are already capturing through existing flows with using profile filters.\
If your plan includes onboarding support, our EdgeTag team can assist with setting up these flows in your Klaviyo account for your review. If you need assistance, contact us via Slack 

#### Can you send New Customer and Returning Customer events to GA4?

New Customer vs Returning Customer (NC/RC) tracking is not currently supported for GA4 integration.\
Future Availability: This feature is planned for a future release and will be added to EdgeTag's GA4 capabilities.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/channels/klaviyo/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.