Conversions

A conversion mapping tells Klickbee: "when a visitor completes this goal, report it to this ad platform". It is how your ads learn which clicks led to a signup or a sale.

Before you start you need:

• a goal (see Goals);
• a pixel for the platform (see Ad pixels), or, for server-side sending, a connected ad account (see below).

How each platform receives conversions

In short:

• Meta uses both paths at once. Klickbee sends the browser event and the server event with the same identifier, so Meta counts the conversion once.
• Google Ads conversions are server-side only. Whether you create the mapping in the dashboard or through Claude, nothing is fired by the Google tag in the browser. Without a Google Ads connection, a Google Ads mapping sends nothing.
• LinkedIn conversions are browser-side only, and need the LinkedIn pixel loaded on the page.

Connect an ad account

Server-side sending needs a connection to your ad account.

1. Open Optimize → Pixels.
2. In the Conversions API panel, click Connect Meta or Connect Google Ads.
3. Sign in on the platform and approve the access it asks for.
4. Back in Klickbee, the row shows Connected with the account name.

To stop sending, click Disconnect on the same row. Access tokens are stored encrypted and are never sent to browsers.

For Google Ads, if your login has access to a single account it is selected automatically; with several accounts you pick one when you create the mapping.

Map a goal to a platform

1. Open Goals.
2. Under the goal, find the Conversions block.
3. Open the Destination… menu and pick a pixel (it appears as "Meta - name", "Google Ads - name" or "LinkedIn - name").
4. Fill in the platform field (see below).
5. Optionally set value key and currency key (see Value and currency).
6. Click Add.

A goal can be mapped once per pixel, and to several pixels. Each mapping is listed under the goal, with a trash button to remove it. If you have no pixel yet, the block asks you to add one on the Pixels page or to connect a platform.

Meta

Choose the Meta event… to report: Lead, CompleteRegistration, Contact, Subscribe, StartTrial, SubmitApplication, Schedule, InitiateCheckout, AddToCart, AddPaymentInfo, Purchase, ViewContent or Search. For a custom conversion, create it in Meta; Klickbee sends standard events.

For the server-side copy, map the goal to a Meta pixel that has its Pixel ID filled in. When you connect Meta, Klickbee adds a placeholder entry called Meta (connected) that has no ID: it cannot send anything on its own. Add your Meta pixel with its ID on the Pixels page and map to that one.

Google Ads

Pick the Conversion action… from your Google Ads account (only enabled actions are listed), or type a name under …or create a new conversion action and click Create: Klickbee creates it in Google Ads for you. With several accessible accounts, choose the account first.

If the menu is empty, the hint tells you why: Google Ads is not connected, no account is accessible with this login, you have not picked an account, or Google Ads could not be reached.

Google Ads needs to know which ad click led to the conversion. Klickbee uses:

1. the visitor's Google click id (gclid, gbraid or wbraid) saved from the landing page of their first visit; or, if there is none,
2. their email address, hashed, if you identified them (see Track events).

A conversion from a visitor with neither cannot be matched to an ad and is not reported.

LinkedIn

Enter the Conversion ID from your LinkedIn Campaign Manager. The conversion fires from the browser when the LinkedIn Insight tag is loaded, so the LinkedIn pixel must be added and enabled.

Value and currency

To report an amount with a conversion, use value key (opt) and currency key (opt). They are the names of properties on your event that hold the amount and the currency code.

For example, send this event from your site:

window.klickbee.track("purchase", { value: 49.9, currency: "EUR" });

Create an Event goal whose Event name is purchase, map it, then set value key to value and currency key to currency.

• The value must be a number and the currency a non-empty text; otherwise it is left out.
• Only Event goals can carry a value, because click and pageview goals have no custom properties.

What to expect

• Server-side conversions are not instant. They are queued and sent in batches every few minutes. Klickbee tries to send each conversion at most 5 times.
• The dashboard does not yet show a list of sent or failed server-side conversions. Check the result in your ad platform (Meta Events Manager, Google Ads conversions).
• Personal data is not sent in clear: an email used for matching is normalised and hashed (SHA-256) before it leaves Klickbee.
• Browser-side conversions follow the same rule as ad pixels: they depend on the pixel being loaded and can be blocked by an ad blocker. That is another reason to connect Meta for server-side sending.
• Browser-side conversion events only fire for visitors Klickbee is tracking. If you use consent mode, a visitor who has not consented triggers none. The pixel itself still loads, as explained in Ad pixels.

Do it with Claude

If you have connected Claude, you can ask it to create a goal and map it in one go ("create a goal for /thank-you and send it to Meta as a Lead"). Google Ads mappings made this way still only take effect once Google Ads is connected in the dashboard.

Related

• Goals
• Ad pixels
• Privacy and consent