Feed my Pixel

Description

Feed my Pixel connects your WordPress site to LeiAI Hub, a CRM for sales teams. Your forms arrive in the Hub as leads, your team works them in a pipeline, and every sale (online or closed later by phone, WhatsApp or in person) is reported back to the ad platforms you connect in the Hub, together with the campaign the person came from.

Ad platforms optimize for whatever you report to them. If they only see form submissions, they bring you more people who fill out forms. When they see your real sales and their value, they look for people who actually buy.

What the plugin does

• Attribution tag on every page: remembers which ad or campaign each visitor came from (gclid, fbclid, ttclid, UTM parameters) so the lead or sale can be matched to the right campaign later.
• Contact forms sent from the server: Contact Form 7, WPForms, Elementor Pro, Gravity Forms, Fluent Forms and Ninja Forms, plus the car dealer quote form of the CES theme. Submissions are sent from your server, so ad blockers do not lose them.
• Ready-made form: the [feed_my_pixel] shortcode shows the lead form configured in your Hub.
• WooCommerce: every paid order reaches the Hub as a sale, with its amount and order number. If the order is later refunded or cancelled, the sale is withdrawn.
• Consent: an optional advertising consent checkbox at checkout. Personal data is only used for advertising when the buyer agrees.
• Reliable delivery: if the Hub is temporarily unavailable, deliveries are queued and retried every hour.
• Compatible with WooCommerce High-Performance Order Storage and the block checkout.

Requirements

Feed my Pixel is the WordPress connector for LeiAI Hub, an external service. You need a LeiAI Hub account to use it. The plugin itself is free; LeiAI Hub is a paid service offered by LeiAI (Chile). Learn more at crm.leiai.online.

External services

This plugin connects to LeiAI Hub, a CRM service provided by LeiAI. It is required for the plugin to work. The Hub address is the one included in the connection code you paste in Settings → Feed my Pixel (for example https://crm.leiai.online or your company’s own Hub address).

What is sent, and when:

• On every public page (only if “Install the attribution tag” is enabled): the visitor’s browser loads the script tag.js from your Hub. The script stores the campaign the visitor came from (ad click identifiers such as gclid, wbraid, fbclid and ttclid, and UTM parameters) in the _leiai_attr first-party cookie and in the browser’s local storage, for 90 days. When a plain HTML form with an email field is submitted, it sends that form to the Hub together with the campaign data and, if the site already uses them, the Google Analytics, Meta Pixel and TikTok Pixel identifiers stored in their own cookies (_ga, _fbp, _fbc, _ttp).
• When a visitor submits a supported contact form: your server sends the Hub the form fields (name, email, phone, company, message and other non-sensitive fields; passwords and files are never sent), the visitor’s IP address, the page and the campaign data stored in the _leiai_attr cookie, and the Google Analytics client and session IDs read from the _ga cookies.
• When a WooCommerce order is paid, refunded or cancelled: your server sends the Hub the order number, status, total, currency, items, the buyer’s name, email, phone and company, the campaign data, and whether the buyer gave advertising consent.
• When you save the settings or click “Test connection”: your server checks the connection with the Hub.

Depending on the connections the site owner sets up inside LeiAI Hub, the Hub then reports leads and sales to Google Analytics, Google Ads, Meta and TikTok. Email addresses and phone numbers are sent to those platforms hashed (SHA-256) and, by default, only when the person gave advertising consent.

• LeiAI Hub terms of service: https://crm.leiai.online/terminos
• LeiAI Hub privacy policy: https://crm.leiai.online/privacidad
• How LeiAI Hub uses Google Ads and Google Analytics: https://crm.leiai.online/acerca

The plugin adds a suggested text to your site’s privacy policy (Settings → Privacy) describing this processing.