From clicking on WhatsApp to converting back on your phone. announcement.

No. ByteCapture was developed exclusively for... Kommo CRM, and all integration (forms, WhatsApp tracking, CTWA, conversions, and field mapping) is native and specific to it. If you are still choosing a CRM, learn more. o Kommo with Bytebio.

Through the official ByteCapture widget on the Marketplace. KommoYou install the widget on your account, it generates an activation key, and you paste that key into ByteCapture. The connection is made without dealing with API tokens, and it's the recommended approach for most accounts.

No. ByteTrack captures leads in two ways: through a script installed on the website or landing page, or through a Direct Link. With a Direct Link, you generate a URL and place it in the ad or Instagram bio: the person clicks, ByteCapture records the UTMs, location, and device, and takes them directly to WhatsApp. And the lead from a Click to WhatsApp ad is attributed by the Native CTWA, also without a website.

No. Installation involves copying and pasting a line of code into your website, and the configuration of links and forms is done entirely through the control panel. All plans include complete implementation documentation, and the ByteCapture | Assistance service will handle the installation for you if you prefer.

Yes. In forms and WhatsApp tracking, you can map the data to any custom field of the... Kommoincluding lead, contact, and company data.

No. ByteCapture works with attribution metadata, such as click identifiers and campaign data. The content of the messages is never read or stored.

Yes. The data is stored with encryption and isolation by organization, and data governance automatically deletes old records according to the retention plan.

Yes, with data isolation between clients and fast exchange between organizations. There is no agency plan or volume discount: each organization has its own subscription. There are two paths. The agency subscribes to one organization per client and passes it on with its own margin (8 clients in the Pro plan total 8 clients). R$ 1.176 per month). Or each client signs up through the agency's affiliate link, and the agency receives a 35% recurring commission (on the same 8 clients in the Pro plan). R$ 411,60 per month), with no outlay and no risk of default, but without controlling the account.

Portuguese, Spanish, and English. The dashboard, documentation, and public forms are available in all three versions, and each form can have a fixed language.

Based on temporal proximity: ByteCapture compares the tracked click with the lead created in Kommo Next, within the same funnel, you can also filter by origin. It's calibrated inference. The phone number isn't included in this calculation because the phone number... Kommo It's the visitor's username, not an identifier; the timing and funnel rule prevents false positives.

Those who arrive via a Click to WhatsApp ad never visit the website, so there's no temporal proximity to calculate. In this case, Meta delivers the click identifier (ctwa_clid) along with the message, and ByteCapture links the lead to... Kommo That ad is assigned deterministically. If a CTWA lead has already been assigned by time, the CTWA assignment takes priority and corrects the record.

From your ad account. ByteCapture only reads UTMs from WhatsApp click ads; those from website traffic campaigns arrive normally via ByteTrack. Access is read-only: it does not create, edit, pause, or spend budget.

With virtually all of them. Campaigns that lead to a website or landing page with WhatsApp or a form (traffic, reach, engagement, conversion) are attributed by temporal proximity, and Click to WhatsApp ads, which open the conversation without going through the website, by Native CTWA.

Confirm in WhatsApp Manager that the number is active and on the correct WABA and contact support: for now, registering a new account is done with our team, which guides the secure sharing of the WABA at a partnership level. Do not send tokens via message. Each registered WABA account counts as one more link towards the plan limit. The five steps are in the Native CTWA section.

When a lead returns, there's no new lead creation to match with the click. By specifying a reactivation date field in the link, ByteCapture recognizes these returns and assigns the correct source, using the same funnel and source filters.

No. Integration with the Kommo It's native, and ByteCapture doesn't use those intermediaries in data processing either. Fewer pieces in the way means less to break.

Yes, natively, for both: Meta, through the Conversions API (CAPI), and Google Ads, through the Data Manager API, with Enhanced Conversions. When a lead advances in the funnel... Kommo (For example, when a sale is won), ByteCapture sends the conversion event to the platform, linked to the click that generated the lead. Everything is configured in the dashboard, without an external widget, with various settings per funnel and per stage.

In all of them, including the Starter, of R$ 75 per month. This is not a high-end plan feature.

No. The conversion only triggers for leads with a session that carries the platform's click identifier, proof that it came from the ad: fbclid or ctwa_clid for Meta, gclid for Google. Organic leads or those without this parameter do not generate an event, and the ad account only shows attributable conversions.

They also generate offline conversions in Meta. Since they don't go through the website, the event goes with the Meta click identifier to the dataset linked to your WABA, and not to the website pixel, which rejects this type of event. To activate, enable the "WABA Datasets" block in the conversion, select the WABAs, and define the event and value for each one; the funnel and stages follow those of the conversion. In the firing log, these events appear marked as CTWA. Google Ads does not receive conversions from CTWA because it requires gclid.

Link the dataset pixel to the ad account, just like you would with a regular pixel. Without this link, events will still be received, but ad optimization won't utilize them.

Not for offline sending. The conversion happens server-side, directly from ByteCapture to the platform (Meta CAPI or Google Data Manager). Keeping the pixel or tag on the website helps with match quality, but offline sending doesn't depend on it.

The contact data, submitted in SHA-256 format along with the event, is used in Metadata for Advanced Matching (email, phone number, and name); in Google, for Enhanced Conversions (email and phone number). Only the information provided in the lead will be included.

Yes. Register as many accounts as you need (Meta pixels or Google Ads accounts) and route each funnel to the correct account. This is useful for those who manage multiple Business Managers or accounts, or who separate campaigns by product.

It is recorded in the "Error Messages" section and is automatically resent at increasing intervals. You can also force resending using the "Reprocess Errors" button.

Not yet: TikTok Ads is on the roadmap, via the Events API, with offline events via TTCLID, using the same account and conversion model as Meta and Google.

This is what makes more conversions actually be attributed in the ad manager. ByteCapture sends encrypted lead identity data from... Kommo Alongside the event, Meta and Google better recognize the person and credit the conversion to the correct ad. It's also possible to send the sales value to optimize for ROAS.

The entry-level plan is the Starter plan. R$ 75 per month, with 2.000 sessions. The Pro plan costs R$ 147 per month, with 10.000 sessions, and the Business, R$ $297 per month, with 30.000 sessions. Above 30.000 sessions, the plan is the Custom plan, which is negotiable.

There is no permanently free plan. There is a 50-session free trial; after the 50 sessions, you choose a plan, starting from the Starter plan. R$ 75 per month.

The test is measured in sessions: there are 50. Since bots and link previews don't consume sessions, these 50 are real human interactions, and you see attribution working with real traffic.

A session is recorded when a human visitor clicks a tracked WhatsApp button or begins filling out a form. If the same person clicks on WhatsApp and fills out a form on the same visit, that counts as 2 sessions, one of each type; repeated clicks by the same person within 30 minutes count as 1. Only human interactions consume sessions; bots are detected and automatically discarded.

In paid plans, tracking continues normally, and any additional sessions are charged separately. R$ 0,08 each in the Starter, R$ 0,06 on Pro and R$ 0,04 in Business. Limits are renewed on the first day of each month.

According to the plan: 3 months on Starter, 6 on Pro, 12 on Business, and negotiated on Custom. After that, automatic cleanup deletes the records. To compare one year with another, the correct plan is Business.

Every plan includes a 20% discount coupon, for one-time use and valid while the plan is active, on the service. ByteCapture | SupportOne hour with a specialist from Bytebiovia Google Meet or through an action on their platform, which costs R$ 350,00 and it comes out to R$ 280,00 with the coupon. This is a one-off service, not recurring consulting.

The commission is 35%, recurring as long as the referred customer's subscription is active, with a unique referral link per affiliate and automatic processing upon each confirmed payment. To join, contact us.