Platform
Tracking conversions
Your ad platforms optimise on whatever you tell them is a conversion. Left alone, that is a page view or a form submit. Meeton can tell Google Ads, Meta and LinkedIn about the outcomes that matter on a B2B site, a meeting booked or a document downloaded, so campaigns learn from real intent. Separately, Meeton records which ad brought each contact in the first place, and can write that into your CRM.
A conversion event is the ad-platform term for a visitor action you report back so the platform can count it and optimise bidding toward it. Conversion ID, conversion label, pixel and Insight Tag are Google Ads, Meta and LinkedIn vocabulary respectively. Click IDs (gclid, fbclid, li_fat_id…) are the parameters an ad platform adds to a landing URL so a later outcome can be tied back to the click.
Two things Meeton does
| Capability | Where | What happens |
|---|---|---|
| Conversion events | Settings → Meeton AI → Data & tracking → Conversions | When a visitor books a meeting or downloads a document through the widget, the loader fires the Google Ads, Meta Pixel and LinkedIn events you configured, in the visitor's browser, through the platform tags on your page. |
| First-touch attribution | Every contact's record, and CRM sync | The UTM parameters and click IDs from a contact's first landing URL are kept as Where they came from, and can be written into HubSpot or Salesforce fields. |
Conversion events
Settings → Meeton AI → Data & tracking → Conversions: "Configure ad platform conversion events for each type of visitor action tracked by your widget." Settings are team-wide, and the page is read-only for Viewers. The section is not shown for customer-support funnels.
The two actions
| Action | Fires when | Options |
|---|---|---|
| Meeting booked | A visitor books a meeting through the widget calendar: the chat's booking form, the calendar popup, a ?calendarId= link, or an inline #dynameet-calendar embed. A reschedule does not fire it again, and an external calendar (TimeRex, immedio) never does. | Conversion value and currency. |
| Library | A visitor downloads a document from the Library, or unlocks a gated one by submitting the lead form. | Document scope: any document, or specific documents ticked from the list. Trigger scope: Any download event, both gated (form submitted) and ungated (known visitor); or Lead conversions only, which fires only when an anonymous visitor submits the lead form to unlock a download. Plus value and currency. |
Chat started and lead captured are not conversion events today. A chat that ends in a booking or a download reports through those two actions, which is also the moment an ad platform should learn from: a conversation is cheap, a meeting is not.
Conversion value
value.JPY or USD. Defaults to JPY.Google Ads
AW-123456789.AbCdEfGhIjK.gtag("event", "conversion", { send_to: "AW-123456789/AbCdEfGhIjK", value, currency }), only when both fields are filled and the Google tag (gtag) is already on your page. Meeton does not load the Google tag for you; install it site-wide first, in the page or through Google Tag Manager.Meta (Facebook) Pixel
fbq("track", "Lead", { value, currency }) for a standard name; non-standard names are routed to fbq("trackCustom", …) automatically. Names are matched exactly, case included. Requires the Meta Pixel (fbq) already on your page.LinkedIn Insight Tag
lintrk("track", { conversion_id }). No value or currency is sent to LinkedIn._linkedin_partner_id and loads https://snap.licdn.com/li.lms-analytics/insight.min.js. It skips this when the page already has an Insight Tag, and it never runs for bots or on a page where the loader does not boot. This is the only third-party script Meeton ever adds; see Domains & CSP if you run a Content Security Policy.How firing works
- In the visitor's browser, from the page where the booking or download happened, through the platform's own tag. Nothing is sent server-side, and no click ID is attached; the platforms match the event to their click with their own cookies.
- A platform fires only when its fields are filled. Google needs ID and label, Meta an event name, LinkedIn a conversion ID. Leave a platform blank to keep it out.
- No deduplication. Each qualifying download fires again; a second booking by the same person fires again. Use Lead conversions only on the Library action if you want one event per new lead.
- Embed mode and inline embeds fire the same events; so does a booking from an inline calendar. Bookings started from inside a Library modal or a full-screen ad may not report through the calendar event; test your own flow.
Checking it works
There is no test button. Book a test meeting on your own site with the loader's debug log on (JavaScript API → Debugging) and look for Google Ads conversion event fired, Facebook Pixel event fired or LinkedIn conversion event fired; then confirm the hit in Google Tag Assistant, Meta Events Manager's test events, or LinkedIn's conversion status, which each take a few minutes to show it.
First-touch attribution
Independently of the pixels, Meeton keeps the first landing URL of every visitor who becomes a contact and shows it on their record as Where they came from: their first visit to your site, not their last, which is why it can differ from the Source column. Click IDs are labelled by platform: Google Ads (gclid), Meta Ads (fbclid), Microsoft Ads (msclkid), TikTok Ads (ttclid), LinkedIn Ads (li_fat_id), Yahoo! JAPAN Ads (yclid).
With Sync first-touch attribution on under CRM sync, the UTM parameters and click IDs are written into HubSpot or Salesforce fields you name, only while those fields are still empty. Your ad URLs need no change; a standard ?utm_campaign=… is read as is. That is how a contact who browsed for days and converted in the chat, which the ad platform records as no conversion at all, still gets credited to the campaign in your CRM.
Where the numbers show
- Traffic & audience counts contacts by the source of their first visit.
- Meeton Ads reports leads and meetings per journey, and a Conversions figure on marketing insights that means engagement with on-site ads (downloaded, viewed, submitted contact information), not ad-platform conversions. See Results & proof.
- Your ad platform shows the events above against its own clicks, in its own reports.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Nothing reaches Google Ads | The Google tag is not on the page, or the conversion ID lacks its AW- prefix, or the label is wrong | Install the Google tag site-wide; copy ID and label from the conversion action's tag setup; watch the debug log. |
| Nothing reaches Meta | The Pixel is not on the page, or the event name is blank | Install the Pixel; fill the event name. A custom name is fine; it goes through trackCustom. |
| Meta records a custom event instead of a standard one | The name differs in case or spelling from the standard list | Use the exact standard name, for instance Lead, not lead. |
| LinkedIn shows no conversions | No Partner ID (so no Insight Tag), or the conversion ID is wrong | Set both; check the console for LinkedIn Insight Tag initialized. |
| Two LinkedIn tags on the page | Your site already loads the Insight Tag | Expected: Meeton skips its own injection when one exists. Keep yours. |
| Conversions fire but the platform shows no value | Lead value is 0, or LinkedIn, which takes no value | Set a lead value and currency; LinkedIn counts events only. |
| Too many Library conversions | Any download event counts every download, repeats included | Switch to Lead conversions only, or narrow the document scope. |
| The Library card says Library is not enabled | The module is off | Enable it under Library settings; the card links there. |
| A test booking from the dashboard fired nothing | The dashboard's own preview booking flow fires no pixels | Test on your site with the tag installed. |
Frequently asked questions
Does Meeton add tracking scripts to our site?
Only LinkedIn's Insight Tag, and only when you give it a Partner ID. Google and Meta events go through the tags you already have.
Can we send chat starts or captured leads as conversions?
Not today. Meeting booked and Library download are the two actions. A lead captured through a gated download is covered by the Library action with Lead conversions only.
Can we send the events through Google Tag Manager instead?
The events call gtag, fbq and lintrk directly, so a Google tag installed through GTM works as long as it defines gtag on the page. There is no dataLayer push.
Is this the same as the "Conversions" number on the Ads tab?
No. That number counts engagement with Meeton's on-site ads. This page is about events sent to external ad platforms.
Which currency should we use?
The one your ad account bids in. The default is JPY; set USD, EUR and so on if your campaigns run in those.