Wopisanje

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.

Reviews

There are no reviews for this plugin.

Sobustatkujuce a wuwijarje

„Venus Digital AI“ jo software wótwórjonego žrědła. Slědujuce luźe su pśinosowali k toś tomu tykacoju.

venusdigital

Translate “Venus Digital AI” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.5.0

A conversion is counted once. The browser’s Lead event and the server’s report of the same lead now share one identifier (a random first-party cookie, venus_eid), so Meta de-duplicates them.
Events go to the plugin’s own pixels only (trackSingle). A page that also carries its own pixel no longer receives a second PageView or Lead from the plugin.
The page settings from Venus no longer lapse between hourly refreshes, which could leave a thank-you page not firing Lead. Venus can also ask for a refresh when a page is attached to a campaign.
Form submissions carry the visitor’s IP address and user agent for Meta’s matching, and the address of the page the form was on even when the form submits in the background.
Contact Form 7 submissions are forwarded even when the site’s own email fails. Phone and email fields are recognised by type in Elementor, and by more common labels elsewhere.

1.4.0

Leads also carry the advertising platforms‘ own click identifiers — Google’s gclid, gbraid and wbraid, and Meta’s fbc and fbp — alongside the campaign tracking parameters. These are what Google and Meta need to connect a closed sale back to the click that produced it. Documented under Privacy and External services.

1.3.0

Leads now say which campaign brought them. When a visitor arrives from a link with campaign tracking parameters, those parameters are remembered in a first-party cookie (venus_utm, 30 days) and sent with the form they submit — so a lead can be traced to its source, channel, campaign, ad set, ad and keyword even when the form is on a different page from the one they landed on. Documented under Privacy and External services.

1.2.1

Pages built by a page builder could still be missing from the list Venus offers. A builder often registers its pages as reachable without listing them in archives or searches, and only the first of those two was being asked for. Both are now.

1.2.0

Venus can now read which pages of this site carry a form, and where each form sends people after it is submitted. That is what a conversion campaign needs to know, and until now it had to be answered by hand — a wrong answer sent the campaign to optimise towards a page nobody reaches. Elementor Pro, WPForms, Gravity Forms and Contact Form 7 are read directly; any other form is reported as a form without a destination.
The new address is /wp-json/venus/v1/pages and it answers only to a caller that already knows this site’s Venus page identifier. It returns page titles, addresses and form destinations — all of them visible to anyone who opens the site — and no option, credential or submitted data.

1.1.0

A site can now report to more than one Meta pixel. Pages advertised from different ad accounts each report to the account that owns them, instead of everything going to whichever pixel arrived first.
A page marked as a thank-you page records a conversion (Lead) as well as the page view, so a conversion campaign has something to optimise towards.
The settings refresh runs hourly instead of daily, so a pixel created while a campaign is being built reaches the site before that campaign starts spending.
A page that already carries a Meta pixel of its own — through Elementor, a tag manager, or anything else — no longer gets the same pixel a second time from this plugin. Page views on those pages were being counted twice.
A thank-you page that already carries its own copy of the pixel still records the conversion. The page view is left to the page, so it is counted once, and the conversion is sent on top of it — before this, such a page recorded no conversion at all.

1.0.3

The directory listing now carries the Venus Digital icon and header image. No change to the plugin itself.

1.0.2

The pixel identifier is now kept up to date by a daily background check, so a site connected before its Meta account was connected still starts measuring once a pixel exists. Documented under External services.

1.0.1

The pixel loader is registered through wp_enqueue_script / wp_add_inline_script instead of being printed straight into wp_head.
The on/off setting is sanitized on save, like the other three.
Meta’s links now point at the Business Tools terms, which are the ones that actually govern the pixel.

1.0.0

First release: form forwarding and Meta pixel.