For businesses running their advertising through Venus Digital AI (https://venus-digital.co.il), an advertising management service.

Once connected, the plugin:

Forwards every form submission on the site to your Venus Digital AI leads inbox. Elementor Pro, Contact Form 7, WPForms and Gravity Forms are supported, including forms added later.
Installs your Meta pixel on every page, so campaigns can build audiences and measure conversions.

Your forms keep working exactly as they did — their emails, redirects and stored entries are untouched. The plugin only takes a copy of each submission.

Administrators are excluded from pixel tracking so your own visits do not distort your audiences.

The plugin does nothing at all until a Venus Digital AI account connects this site. It has no settings screen: it is configured over the REST API by the connection, and an unconnected install sends nothing anywhere.

Configuration

There is nothing to configure by hand. Connecting your site from inside Venus Digital AI sets everything up.

External services

This plugin relies on two external services. Both are used only after a Venus Digital AI account has connected this site.

1. Venus Digital AI

What it is: the advertising management service this plugin belongs to.

What is sent, and when, in two cases and no others:

On every form submission: the values the visitor typed into that form (typically name, phone, email and message), the address of the page the form was on, this site’s own address, and — when the visitor arrived from a tagged campaign link — that link’s tracking parameters (utm_source, utm_medium, utm_campaign, utm_adset, utm_content, utm_term), any advertising click identifiers it carried (gclid, gbraid, wbraid, fbc), the Meta pixel’s browser identifier (fbp) if the pixel set one, the submitting visitor’s IP address and browser user agent, and the conversion identifier described under Privacy. Venus Digital AI forwards the lead to Meta’s Conversions API on the business’s behalf, and the IP address and user agent are what Meta uses there to match the conversion to the ad click.
Once an hour, in the background, this site asks Venus Digital AI which Meta pixel it should be using, and which of its pages are advertised landing and thank-you pages. Venus Digital AI can also ask the site to do this immediately (REST route venus/v1/refresh, guarded by this site’s page identifier) when a page is attached to a campaign. The request sends only this site’s page identifier, which the connection stored here, and the reply is pixel identifiers and page addresses, nothing else. No visitor data is involved, and no visitor waits for it: it runs on a scheduled task, not on a page load. It exists because the business may connect their Meta account after this site was connected, and this is how the site learns about the pixel that was created afterwards.

Where: https://venus-digital.co.il
Terms of service and privacy policy (one page): https://app.venus-digital.co.il/?legal=terms

2. Meta (Facebook) pixel

What it is: Meta’s own advertising measurement script.

What is sent, and when: when the pixel is configured, every page load on this site loads Meta’s script (https://connect.facebook.net/en_US/fbevents.js) in the visitor’s browser and reports a PageView to Meta — and, on a thank-you page attached to a campaign, a Lead. This is Meta’s script and Meta’s data collection, not ours. Logged-in administrators are excluded.

Terms of service: https://www.facebook.com/legal/terms/businesstools
Privacy policy: https://www.facebook.com/privacy/policy

Privacy

The plugin stores nothing on this site beyond four settings: the Venus Digital AI endpoint, the page identifier, the pixel identifier and an on/off flag, plus a cached copy of the pixel identifier from the daily check. Form submissions are forwarded, not stored by the plugin.

When a visitor arrives from a link carrying campaign tracking parameters (utm_source, utm_medium, utm_campaign, utm_adset, utm_content, utm_term) or an advertising platform’s click identifier (Google’s gclid, gbraid or wbraid; Meta’s fbclid, stored in Meta’s fbc format), the plugin stores those values in a first-party cookie named venus_utm for 30 days, so that a form they submit later can be attributed to the campaign that brought them. The cookie holds only what the link carried, and nothing the visitor typed or did. It is not set on a visit without such parameters. When a form is submitted, the plugin also reads the _fbc and _fbp cookies that the Meta pixel sets on this site, if present.

The plugin also sets a first-party cookie named venus_eid: a random identifier, with no personal data in it, that lasts one day or until a conversion is reported. The same identifier is sent with the form submission and with the pixel’s Lead event, so that Meta counts one conversion rather than two when both the browser and the server report it.