Keitaro v11 Full Setup (FB - Black Page - TG) + CF + CAPI Deduplication

Need professional infrastructure setup for traffic from FB to Telegram (GEO India). Traffic goes to a local static Black Page, from there — via a JS button to the Telegram channel. There is no S2S Postback from the final platform, tracking is manual through TG invite links so this does not need to be set up.

Technical assignment:

1. Server, Network, and SSL

• Base: Install Keitaro v11 on a clean Ubuntu 22.04 (I will provide root access). Bind the domain through my empty Cloudflare.

• Hardware stability: Set up automatic log rotation for Nginx and clean ClickHouse/Redis to ensure FB bot traffic does not crash the server. Rigorously synchronize server time (NTP) with UTC for correct FB timestamp operation.

• SSL: Set up Full/Strict + generate a local certificate (anti-error 52x).

• Catch-all (Scaling): Configure the server so that when a domain is banned in FB, I can direct the IP of a new junk domain from CF to the server, and it serves the target campaign without manual re-linking in the tracker.

2. Cloudflare and Nginx setup (Critical for GEO India)

• Cloudflare: Page Rules (Cache Level: Bypass for all URLs). Security: turn off Bot Fight Mode, level Essentially Off.

• Nginx (IPv6 Leak): Mobile India (Jio) operates on IPv6. Nginx inside Keitaro must strictly restore CF-Connecting-IP not only for IPv4 but also for all relevant IPv6 ranges from Cloudflare.

3. Landing page integration and Cloaking

• To start, create placeholders (I will later provide 2 ZIP archives for upload as Local landing pages).

• Stream 1 (Intercept - White Page): Filters: bots (IM Klogs), IPv6 (except real mobile subnets), Data centers, VPN/Proxy, Desktops, non-target GEOs.

• Stream 2 (Target - Black Page): Filters: GEO India, only Smartphones.

4. Dynamics, CAPI, and Deduplication (Architecture)

• API Security: Access Token is strictly configured in the Keitaro backend. On the Black Page, only the public Pixel ID is dynamically passed through (via URL parameter).

• CAPI enrichment (EMQ): Server-side sending must capture fbclid from the incoming link and _fbp (cookie), passing them to CAPI along with IP and UA.

• Conversion bridge (AJAX): Provide me with the exact URL/path for the hidden AJAX request that my developer will attach to the button. Upon clicking, the script will send a ping to Keitaro (lead status), triggering the CAPI firing.

• Deduplication: Pass the macro {subid} into the local Black Page. My JS script will retrieve it and send it to the browser pixel as eventID. The server-side CAPI will carry this same subid.

• Dynamic TG link: A unique Telegram invite link is passed to the Black Page via a macro (e.g., {offer_url}).

Questions before starting:

Before starting, you need to answer these questions in your response:

1. How will you exclude mobile IPv6 traffic from India from the cloaking filter "Data centers," considering CF proxying?

2. Where in my local landing page should the developer declare the macro variables {subid} and {offer_url} so that the Keitaro parser sees them and does not return them as raw text?

3. What URL request should my JS script from the Black Page ping the tracker with to trigger CAPI?

I await your budget and timeline estimate.