Skip to main content
KenectReviews and messaging

Kenect fills your inbox with texts. Your ads can't tell which ones bought.

Kenect's Text Us widget turns a website visit into a text thread with your business number, and the ad click that brought the visitor stays behind on the web page. Its events go out through postMessage, which Google Tag Manager doesn't hear without a listener. We capture the real send-message event with the click attached, then return paid text-to-pay deposits to Google Ads and Meta so bidding learns from buyers, not browsers.

Free30 minutesNo obligation

Kenect · what breaks

What goes wrong with Kenect and your ads

  1. 01

    Google Ads says the website produces no texts

    The widget announces each message through window.postMessage, not the data layer. Without a listener, GTM never sees it, so a powersports dealer's search campaigns look dead while the Kenect inbox fills up, and budget gets cut from ads that work.

  2. 02

    Widget opens counted as leads

    Kenect fires EVENT_WIDGET_OPENED the moment someone taps Text Us and EVENT_SEND_MESSAGE only after Kenect's server confirms the message. Count the open, and Smart Bidding chases shoppers who never typed a phone number.

  3. 03

    The thread moves to SMS and the source is gone

    Once the visitor hits send, the conversation carries on by text from your Kenect number. Kenect's Zapier lead push maps a contact name and phone number, and its docs name no campaign field, so an RV dealer or collision shop can't see which ad started the deal.

  4. 04

    Deposits paid by text never reach your ad accounts

    A trailer deposit or a repair invoice collected through text-to-pay shows as PAID inside Kenect and nowhere else. Google Ads and Meta value a small service invoice and a boat deposit the same, and neither learns which keywords bring buyers.

Kenect · the fix

What changes once Kenect is tracked

  • Bidding trained on paid Kenect deposits

    Google Ads and Meta get the paid text-to-pay amount, matched to the stored click or hashed phone, so spend follows deposits.

  • Every webchat lead carries its ad source

    Click ID, UTMs and the location or department picked travel with the lead, so each rooftop sees its own numbers.

  • Direct texts and Messenger kept separate

    Texts to your number from a sign and Messenger replies stop inflating the webchat count your ads are judged on.

Kenect · architecture

What Kenect actually lets you hook into

Everything here comes from Kenect's own resource center. Where its documentation is silent, it's listed as something we check.

  1. 1

    Widget events through postMessage

    Seven documented event types, including EVENT_SEND_MESSAGE with messageId, contact name, phone and optional location and department. The send event fires only after Kenect's server responds, and Kenect's sample calls gtag; GTM and Meta Pixel aren't covered.

  2. 2

    Zapier lead push and message posting

    Kenect's Zapier app sends new leads, from the widget or texted straight to your number, plus every inbound message. Existing-contact updates don't trigger it.

  3. 3

    CRM and DMS connections

    Kenect lists integrations such as VinSolutions, DealerSocket, Lightspeed, HubSpot, Salesforce, Lead Docket and Clio Grow. We confirm which ones return a sold or signed status we can use.

  4. 4

    Text-to-pay records

    Credit card requests with amount and invoice number, marked PAID or REQUEST SENT, with a CSV download. No payment webhook is documented, so we confirm the export route on your account.

  5. 5

    No ad platform connection

    No Google Ads, GA4 or Meta connection is listed, and Kenect Analytics reports response times, messages and reviews, not ad source.

Kenect · diagnose

Where Kenect tracking breaks, in diagnostic order

Start with the widget, because on most Kenect sites nothing is listening to it at all.

  1. 01

    Check whether anything listens for EVENT_SEND_MESSAGE

    Send one test message and look for it in GA4 DebugView.

  2. 02

    Find which event the conversion is built on

    A conversion built on widget opens is the usual fault.

  3. 03

    Confirm the click ID survives to the phone number

    Trace the stored click to the number on the Kenect lead.

  4. 04

    Separate webchat from direct texts and Messenger

    Zapier's lead push mixes them, so source is set at send time.

  5. 05

    Compare PAID transactions with reported revenue

    Per invoice number, over a closed month, with voids and refunds removed.

Kenect · prove

The QA evidence on your Kenect setup

Run on your live site with the real Text Us widget and a real text-to-pay request.

Source of truth

Kenect records: new webchat leads by date and location, and the payments CSV of PAID text-to-pay transactions with amount and invoice number

  • One widget message sent from an ad-tagged URL, with the click ID confirmed against that phone number.
  • Exactly one lead conversion per messageId in Google Ads and Meta Events Manager.
  • Widget opens and closed prompts confirmed absent from every conversion action.
  • A test text-to-pay request paid, then voided, with the value added and reversed.
  • Paid transactions reconciled by invoice number against both ad platforms over a closed month.
  • Repeated 30 days later and after any change to the Text Us widget code or your website header.

Kenect · free audit

What we check in the free audit

  • Check whether anything listens for EVENT_SEND_MESSAGE
  • Find which event the conversion is built on
  • Confirm the click ID survives to the phone number
  • Separate webchat from direct texts and Messenger
  • Compare PAID transactions with reported revenue

Checked against

Kenect records: new webchat leads by date and location, and the payments CSV of PAID text-to-pay transactions with amount and invoice number

Get my free conversion tracking audit

Free30 minutesNo obligation

Kenect · when not to buy

When you don't need this on Kenect

Plenty of Kenect accounts are fine with lighter work, and we'll say so on the call.

  • If you don't run paid ads and Kenect mostly sends service reminders and review requests, there's nothing to attribute.
  • If most leads come from listing sites or OEM lead feeds, not your own ads, start there.
  • If deals close on the showroom floor and the money never touches text-to-pay, we'd track qualified webchat leads and stop there.
  • If you only need the widget's send-message event in GA4 and nothing more, Kenect's own sample code and a developer may be enough.

Kenect · what we deliver

The event map on Kenect

  • Widget opened

    EVENT_WIDGET_OPENED, recorded as engagement for reporting. Never imported as a conversion.

  • Webchat message sent

    The lead event, from EVENT_SEND_MESSAGE with its messageId as the deduplication key, the hashed phone and the landing-page click ID.

  • Location or department picked

    A parameter, so multi-store dealers split conversions by store or service lane.

  • Lead qualified

    From the CRM or DMS Kenect already pushes to, once we confirm it exposes a status.

  • Text-to-pay paid

    The money event: PAID transactions with amount and invoice number, joined to the original click by phone number.

  • Refunds, voids and repeat customers

    Voids and refunds reverse the value. Unpaid REQUEST SENT items and existing service customers stay out of acquisition.

Written guarantee

95%+ tracking accuracy

Measured against Kenect records: new webchat leads by date and location, and the payments CSV of PAID text-to-pay transactions with amount and invoice number. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Kenect questions, answered

Yes, with a listener. Kenect's widget sends events by postMessage, so EVENT_SEND_MESSAGE has to be pushed into the data layer before a tag can fire on it.

Free · 30 min

Find out what your Kenect leads are really worth

Free30 minutesNo obligation