Conversion tracking in WordPress without code
Define a conversion once – a thank-you page, a click, a form or an event – and send it to GA4, Google Ads, Meta, TikTok, LinkedIn and Snap with consent.
On this page
A conversion is a goal a visitor completes: sending a form, booking a call, buying. In Omea Consent Pro you define it once, and it goes to every ad platform you use – each only with the visitor’s consent.
Add a conversion
- Open Conversions Go to Omea Consent › Conversions and click Add conversion.
- Name it Type a short Name such as
lead– lowercase letters, numbers,_and-. - Choose when it counts Under Counts when a visitor… pick Visits a page, Clicks an element, Submits a form or Custom event, and fill in the page address or CSS selector.
- Add a value and counting rule Optionally set a Value and currency. Under Count choose Once per session, Every time or Once per page per session.
- Choose where it’s sent Under Send to ad platforms, fill in a row for each switched-on platform – for example the GA4 event name or the Meta standard event.
- Save Click Save conversion.
Choosing a trigger
| Trigger | Use it for | Fill in |
|---|---|---|
| Visits a page | A thank-you or confirmation page – the most reliable | Page address, e.g. /thank-you/; * is a wildcard |
| Clicks an element | A button or link, e.g. Book a call | Element (CSS selector), e.g. .book-call, #buy-button |
| Submits a form | A form that is sent | Form (CSS selector), e.g. #contact-form |
| Custom event | Something fired from code or from a server-side event | Nothing – the name is the event |
If a form sends without reloading but has a thank-you page, use Visits a page instead – it’s more reliable.
Fire a conversion from your own code
For a Custom event, fire the event with the same name:
omea.trackEvent('lead');
Or skip the code and add an attribute to the button:
<button data-omea-event="lead">Request a quote</button>
An event only becomes a conversion if a conversion with that name exists. Add data-omea-value="49" to pass a value.
Sent to each platform
| Platform | What you set |
|---|---|
| Google Analytics 4 | Event name, e.g. generate_lead, sign_up, purchase |
| Google Ads | Conversion label (sent as AW-…/label) |
| Tag Manager | Push omea_conversion to the dataLayer |
| Meta | A standard event: Lead, Purchase, CompleteRegistration, Contact, Schedule… |
| TikTok | A standard event: SubmitForm, CompletePayment, CompleteRegistration… |
| Microsoft | The event action from your UET conversion goal |
| The conversion ID from Campaign Manager | |
| Snap | A standard event: SIGN_UP, PURCHASE, SUBSCRIBE… |
A conversion goes only to platforms the visitor has consented to. Conversions that happen before the visitor chooses are queued and sent once consent is given. With a Conversions API switched on, the same conversion is also sent from your server with the same event ID, so the platform counts it once.
Detected automatically
Omea recognises some events without any setup: meeting_booked from HubSpot Meetings and Calendly, and form_submitted from HubSpot Forms and Contact Form 7. Create a conversion with that name (Custom event) to count them.
Server-side events
The Server-side events card turns WordPress actions into events – they work even with ad blockers and without JavaScript. Built in: account sign-ups, logins (not administrators) and comments (all off by default), and WooCommerce purchases, checkouts and add-to-carts (on when WooCommerce is active). Click Make conversion next to an event to count it. See WooCommerce conversion tracking.
Reports on your own site
The free Omea Analytics plugin picks up the same conversions automatically and reports them in WordPress. With Omea Analytics active, this screen moves to Omea Analytics › Conversions – same settings, one place.