> For the complete documentation index, see [llms.txt](https://docs.twoowls.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twoowls.io/getting-started/important-checklists/advertiser-checklist/verify-sending-domains.md).

# Verify sending domains

{% hint style="info" %}
🦄**Protecting your data:** Verifying sending domain is a way for Facebook to know that you have permission to send conversion data from the site to the pixel. \
\
If they don't have this, imagine how everyone would be able to **send malicious data** to your pixel, messing up your pixel altogether!&#x20;
{% endhint %}

Let's follow **8 simple steps** to verify your domain!<br>

{% hint style="info" %}
📝**Preparation:** \
**- Shopify side:** You need to have access to the header section of your Shopify theme, or have contact with people that do.\
\&#xNAN;**- Facebook side:** Your account needs to be assigned with the Admin permission to be able to verify a domain
{% endhint %}

## Copy the meta verification tag from Facebook

![](/files/dj94N6DDVpaXdXlKK4WR)

![](/files/BUCb1EyxjCYkFnhuQpkZ)

### Paste the verification tag to the head section of your theme

![](/files/UetdrxjUNi95GenZtZE5)

![](/files/JJUieWnchTLfobfooUUP)

### Confirm verification

![](/files/SjYNdz4y6SC97dx5gqAP)

![](/files/MsVvS0rLkxtCaR6aQz8y)

{% hint style="info" %}
**CAPI events for IOS 14.5 opted-out users:** Two Owls Conversion API <mark style="background-color:green;">**track 100% of sales**</mark>, but for Facebook to be able to use that data for ad targeting or optimization, you need to ensure that the events are **listed in the 8 prioritized conversion event list**!&#x20;
{% endhint %}

{% content-ref url="/pages/YrgkFoYZPboyD5CA1QJW" %}
[Set up Aggregated Event Measurement](/getting-started/important-checklists/advertiser-checklist/set-up-aggregated-event-measurement.md)
{% endcontent-ref %}


---

# 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.twoowls.io/getting-started/important-checklists/advertiser-checklist/verify-sending-domains.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.
