> ## Documentation Index
> Fetch the complete documentation index at: https://www.conductor.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Integrate Cloudflare Logpush with Conductor Intelligence
> Send log file data from Cloudflare Logpush to Conductor Intelligence's Pages report.
Note that the instructions in this article describe the process for integrating with Conductor Intelligence. You can also integrate Cloudflare Logpush for Conductor Monitoring's [Log File Analysis](/docs/monitoring/setting-up-the-cloudflare-logpush-integration/) feature.
Cloudflare Logpush is available exclusively on Cloudflare's **Enterprise** plan.
Integrating [Cloudflare Logpush](https://developers.cloudflare.com/logs/about/) with Conductor Intelligence consists of two phases:
* Enabling log files and creating an [AWS S3 bucket](https://aws.amazon.com/s3/) in Conductor Intelligence.
* Configuring Cloudflare Logpush in the Cloudflare UI.
## Enabling log files and creating an AWS S3 bucket in Conductor Intelligence
In Conductor Intelligence:
1. Go to the [Pages & Crawling](https://app.conductor.com/u/pages-and-crawling) settings activity (**Settings** > **Pages & Crawling**).
2. From the list of configured subdomains, identify the subdomain with the pages for which you want to see log file data.
3. In the **Log Source** column for that subdomain, click **Connect**.
4. In the Cloudflare Logpush section, from the **Connect a log source** window, click **Connect**.
5. In the **Connect Cloudflare Logpush** window:
1. If you have configured Cloudflare Logpush for your root domain, select whether you want to apply this integration to all relevant subdomains. This allows you to integrate Cloudflare once for all applicable subdomains rather than for each subdomain individually. If Cloudflare is configured at the subdomain level, leave this check box clear and configure individual log file integrations for each subdomain.
2. Click **Create Bucket**.
Conductor Intelligence will generate the following details you will need to complete this integration in Cloudflare in the next section:
* **Bucket**
* **Region**
You'll also see a placeholder for **Ownership token**. You'll need to save a configuration in Cloudflare before this Ownership token is generated. We'll come back to this.
You can now close this window. These credentials and your integration will persist while you perform the remaining setup in Cloudflare.
## Configuring Cloudflare Logpush
Cloudflare Logpush needs to be manually configured in the Cloudflare UI.
1. Go to the **Logs** section in the Cloudflare UI: log in to your Cloudflare account, choose the website for which you want to send log file data to Conductor Intelligence, and click **Analytics** > **Logs**.
2. In the **Logpush** section, click **Connect a service**.
3. In the **Select Data Set** step, select **HTTP requests** as the data set.
4. Select the following Data Fields that need to be provided in the HTTP request log. All required Data Fields are preselected by default, apart from the following two that need to be specified manually:
* ClientRequestScheme (in the ClientRequest category)
* ClientRequestUserAgent (in the ClientRequest category)
* Client IP
* ClientRequestHost
* ClientRequestMethod
* ClientRequestURI
* EdgeEndTimestamp
5. After ensuring that the required Data Fields are selected, click **Next**.
6. Select Amazon S3 as the destination and click **Next**.
7. Enter the **Bucket** and **Path** and the **Bucket region** from the credentials generated in Conductor Intelligence to the corresponding fields in the **Enter destination information** step. The default selection should be kept for all other options:
1. Enter the entire Conductor Intelligence "Bucket" value in the **Bucket** field in Cloudflare. Leave the **Path** field blank.
2. Enter the "Region" value from Conductor Intelligence in the **Bucket region** field in Cloudflare.
8. Once done, click **Validate access**.
9. After initiating access validation, Cloudflare sends a file to the Conductor Intelligence S3 bucket that contains the **Ownership token**. Validate access to the S3 bucket by copy-pasting the Ownership token from Conductor Intelligence to Cloudflare:
1. Back in Conductor Intelligence's **Pages & Crawling** activity, click **Connect** to open the Cloudflare integration you started above. The **Ownership token** should now be visible. Copy this to your clipboard.
2. Navigate back to the Cloudflare UI and paste the Ownership token to the corresponding field:
3. Click **Push**. After that, you should see the Logpush service that you have just created in the overview.
## Filter away non-search engine traffic
To ensure you capture visits from all of the bots for which Conductor supports detection, you might need to create filters for your log files. Be sure you allow all of the following user agents:
* bingbot
* Googlebot
* OAI-SearchBot
* ChatGPT-User
* GPTBot
* PerplexityBot
* Perplexity-User
**(Note:** These strings are case sensitive. Confirm you have the precise upper- and lower-case letters.**)**
## Disabling Log File Data in Conductor Intelligence's Pages Reports
1. In **Pages & Crawling**, hover over the subdomain for which you want to remove Cloudflare Logpush and click **Edit** in the **Log Source** column.
2. In the bottom-right of the **Connect Cloudflare Logpush** form, click **Remove**.
3. Click **Remove Log Source** to confirm.
Conductor Intelligence cannot access your Cloudflare account, so you also need to remove the Logpush service manually in the Cloudflare UI.